Privacy Policy
Brightcall.ai | Brightcall AB
On this page
Effective date: 4 November 2026. Applicable to the Brightcall.ai website, Brightcall business communication services and optional AI-assistant connectors.
1. Who we are and scope
Brightcall AB (corporate registration number 556883-8329; VAT SE556883832901), Brunnsgatan 6, 111 38 Stockholm, Sweden ("Brightcall", "we", "us"), provides business communications services under the Brightcall.ai brand, including cloud telephony, contact centre software, Speed to Lead, AI voice agents, integrations, and related software and support.
This Policy applies to individuals visiting our websites, interacting with us, using Brightcall accounts, or whose personal information is processed in connection with our Services. Customer organisations that use Brightcall typically determine which contacts to call, which data to upload, and whether recording or AI processing is enabled. Our Services are intended for businesses and are not directed at children.
Controller and processor roles. Brightcall is generally a processor of customers' call, contact, lead and other business-service data on the customer's documented instructions. Brightcall acts as a controller for its own website, sales, account administration, security, support and legal compliance activities. A customer remains responsible for its own legal grounds, notices and consents for calls and recordings.
For an on-premises deployment, the allocation of responsibilities depends on the agreed architecture, support access and customer contract; on-premises installation does not by itself establish that Brightcall has no access to personal data.
2. Categories of personal data
- Business and account details: names, business contact details, account identifiers, user roles, billing and contractual details, account preferences. We obtain business contact details from the individuals themselves, their employers and our partners. Providing account and billing details is required to enter into and perform the contract.
- Leads and contacts processed for customers: names, telephone numbers, email addresses, CRM attributes, lead sources and related customer-entered information.
- Telephony and AI service data: calling and called numbers, call timestamps, direction, duration, outcomes, recordings where enabled, transcripts, summaries, AI-generated tags and other call information.
- AI agent configuration: projects, prompts, instructions, knowledge bases, greeting messages, language, voice, agent persona, custom fields, version and change history. Free-form fields may contain personal information entered by customers.
- Website and technical information: IP addresses, device/browser information, website interactions, application activity, diagnostics, event logs and cookies or similar technologies where used.
- Connector account and security information: authorised account, connection app name, scope (read or read/write), token-related records, connection creation/revocation events, last use and technical security/audit logs.
- Support and feedback: information submitted to support, technical error reports, customer feedback and communications with Brightcall.
3. Purposes and legal bases
Processing activity | Purpose and lawful basis (Brightcall as controller) |
|---|---|
Accounts and service administration | Manage accounts, provide requested services, fulfil contracts and communicate with business users (GDPR Article 6(1)(b) where applicable; Article 6(1)(f), our legitimate interest in managing business relationships, for business contacts). |
Billing and legal records | Invoice, account, tax and compliance administration (Article 6(1)(b), 6(1)(c) and, where appropriate, 6(1)(f), our legitimate interest in keeping accurate business records). |
Security and reliability | Prevent abuse, protect services and customer accounts, debug faults and investigate incidents, including through connector security and audit logs (Article 6(1)(f), our legitimate interest in keeping the services secure, and 6(1)(c) where legally required). |
Marketing and website analytics | Respond to people who contact us or request information about our services, and inform existing customers about similar services where the law permits (Article 6(1)(f), our legitimate interest in responding to enquiries and informing customers about our services) and measure website use and advertising (Article 6(1)(a), consent, where required). |
Service improvement | Analyse feedback and error and performance data to fix faults and improve the Services (Article 6(1)(f), our legitimate interest in reliable services). |
AI-assistant connections | Authenticate connections and carry out requests made by the user’s assistant (Article 6(1)(b) for the account holder; Article 6(1)(f), our legitimate interest in operating the connection securely). |
Website callback and demo requests: when you ask us through our website to call you back or to book a demo, we use the details you provide to do so, including through automated or AI-assisted calls; where an AI agent is used, it identifies itself as AI (Article 6(1)(b), steps you request before entering into a contract; Article 6(1)(f), our legitimate interest in answering your request).
When Brightcall processes service content on behalf of a customer, the customer determines the processing purposes and appropriate legal basis; our data processing agreement with the customer and the customer’s instructions govern our handling of that content.
4. Voice AI, feedback and model improvement
Brightcall does not use customer calls, call recordings, transcripts, contacts, leads, or other customer service content to train or fine-tune AI models. This policy describes Brightcall's own practices; a connected third-party AI assistant processes content provided by the user under that assistant provider's separate policies.
Brightcall may use customer feedback and system-generated error or performance information to investigate faults and improve the reliability and quality of its services. Brightcall does not use underlying customer call recordings or transcripts for model training. Any personal information incidentally included in feedback or error reports remains protected under this Policy and applicable agreements. Operational logs used to investigate faults may contain call identifiers, phone numbers and technical metadata; access to them is limited to authorised personnel, and they are kept for 12 months and then deleted. We receive the numbers in these logs from our customers and from call signalling.
Depending on the customer's choice and requirements, Brightcall's AI functions (speech-to-text, text-to-speech, call summaries and outcomes, and live AI voice agents) run either on models operated by Brightcall or on external AI providers acting as Brightcall's subprocessors. External AI providers process customer content only under a data processing agreement, and Brightcall does not permit them to use it to train their models. These providers are named in our subprocessor list (see Section 6). The optional ChatGPT and Claude connector (Section 5) is separate and does not transmit call audio or recordings.
5. Optional ChatGPT, Claude and other AI-assistant connections
A Brightcall account owner or an authorised full-access team member may connect a compatible AI assistant using their own account and choose read-only or read-and-write permissions. Brightcall support staff and authorised reseller partners may also connect an assistant to their own Brightcall account and use it, within their existing support or partner access, for the customer accounts they are permitted to manage; such use is governed by our agreement with the customer, and these connections and any changes made through them are logged. Connections can be reviewed, with the time each was last used, and revoked in General settings > Connected apps, and an agent’s change history records which app made each change. Revocation stops further authorised requests.
Connector scope: AI-agent settings and the calls handled by AI agents. The optional ChatGPT and Claude connector may read and, where authorised, edit AI-agent configuration, such as scripts, instructions, knowledge bases, greetings, language, voice, custom fields and configuration history, and may revert an agent to an earlier version. It may also list and read the calls handled by an AI agent in the customer's account. For each call this covers the time, direction, duration and outcome, the other party's phone number with its middle digits hidden, the customer's own line number, the call transcript, and technical diagnostics such as agent log lines, tool-call errors and response times. The connector does not transmit call audio or recordings and does not have access to leads or contact databases. The connected assistant requests call data only while working on the user's task, for example to check a test call after an agent has been changed. A requested transcript is returned in full, and only to the authorised user's connected AI assistant. Transcripts reflect what was said on the call and may therefore contain personal data, including special-category data such as health information if a caller chooses to mention it. Brightcall does not request or intentionally collect such data through the connector. Free-text settings and knowledge-base entries may also contain personal data that the customer chooses to add. Customers must not place passwords, API keys or other sensitive information in these fields, and must not use the connector to process protected health information, payment card data, government identifiers or access credentials. The customer is responsible for how it uses call data within its AI assistant.
When a user asks a connected assistant to work with AI-agent settings or calls, the connected assistant receives the requested configuration fields, call details or transcripts and corresponding results from Brightcall, subject to user permissions. That assistant provider may independently process this content in accordance with its own privacy terms. Disconnecting an assistant stops subsequent requests but does not erase data already received by that external provider. The connector receives only the requests the assistant sends to it; it does not receive, store or use your conversations, chat history or assistant memory. Text sent in a request, such as a new prompt or a change comment, is stored in the agent’s settings and change log.
Connector technical and audit records may include the connected application name, authorised user/account, permissions, connection events, IP address, timestamps and most recent use. Access tokens are valid for one hour and are renewed while the connection is in use; a connection not used for 30 days ends automatically.
6. Recipients and sharing
We disclose information as needed to provide or secure the Services, under applicable contracts and safeguards, to the following categories:
- Telecommunications carriers, SIP/VoIP routing providers and SMS delivery providers. Some telecommunications carriers act as independent controllers for the traffic they carry.
- Cloud infrastructure, hosting, back-up and technical operations providers.
- External AI providers (speech-to-text, text-to-speech and language models) when the customer has chosen cloud-based AI functions (see Section 4).
- Payment, billing, professional advisory, fraud prevention and customer-support providers.
- Customer-authorised CRMs, integrations, partners and connected AI-assistant providers to the extent requested by users.
- Public authorities or others where disclosure is required by applicable law.
- Advertising, analytics and marketing-automation providers for our website and dashboard.
- Authorised reseller partners, for the customer accounts they manage.
- Communication, collaboration and productivity providers (email, meetings, messaging and issue tracking) and transactional email delivery providers.
Brightcall does not sell customer call content or customer lists and does not use customer content to train AI models. Access to customer information is limited to authorised personnel and approved service providers with a legitimate need and subject to applicable confidentiality and security safeguards. A current list of our subprocessors, their location and the transfer safeguards used is available at https://www.brightcall.ai/sub-processors.
7. Regional hosting and international transfers
Customer service data is hosted in the European Union/EEA, with EU-based cloud infrastructure providers. Brightcall also operates its own servers in Sweden, hosted in a third-party colocation facility. At the customer's request, Brightcall may agree to another hosting region or provide an on-premises deployment of its PBX and/or AI services. Customer-specific arrangements and the allocation of responsibilities for on-premises infrastructure are set out in the relevant contract or deployment documentation.
The selected hosting region determines the default location of stored customer service data; it does not mean that all support, telecommunications routing or other processing necessarily occurs in that region. Personal data of customers in the EU/EEA is accessed only by Brightcall AB staff, authorised reseller partners for the customer accounts they manage, and the subprocessors listed in Section 6. Where a subprocessor is located outside the EEA (for example in the United States), the transfer relies on the EU-US Data Privacy Framework where the recipient is certified, and otherwise on the EU Standard Contractual Clauses. Where GDPR applies to a transfer outside the EEA, Brightcall follows applicable Chapter V safeguards, including an adequacy decision or Standard Contractual Clauses where required, together with relevant supplementary measures; a copy of these safeguards is available from legal@brightcall.ai. The hosting region agreed with the customer applies to its deployment.
8. How long we retain information
Brightcall follows the GDPR storage-limitation principle. Call recordings, where enabled, are kept while the customer's account is active, for the current calendar year and the two preceding calendar years; older recordings are deleted. When a customer's account is closed and has had no active calls for 90 days, its recordings are deleted. Call records, transcripts, summaries and call metadata are kept while the customer's agreement is active, unless the customer deletes them earlier, and are deleted within 90 days after the account is closed. Leads and contact lists uploaded by the customer are deleted within 90 days after the agreement ends. Backup copies are kept for up to 90 days and then deleted, unless the law requires longer retention. Financial and other statutory records may have longer mandatory retention periods.
Data category | Retention period or criterion |
|---|---|
Customer leads and related metadata | Kept in the active service until the customer deletes them or asks us to, or until the customer agreement requires their deletion, and in any case deleted within 90 days after the agreement ends; copies in backups are kept for up to 90 days and then deleted. Deleting a lead also removes its metadata; deleted dialer contacts first stay in a restorable archive for 14 days, and the phone number stays in call records until those records are deleted. |
Deleted lead backups | Kept in separate backups for up to 90 days after the lead is deleted from the active service, then deleted automatically. |
Call recordings, call records, transcripts, summaries and call metadata | Call recordings, where enabled, are kept while the account is active for the current calendar year and the two preceding calendar years; older recordings are deleted. When the account is closed and has had no active calls for 90 days, its recordings are deleted. Call records, transcripts, summaries and call metadata are kept while the customer's agreement is active, unless the customer deletes them earlier, and are deleted within 90 days after the account is closed. Copies in backups are kept for up to 90 days and then deleted. |
Account and billing information | Contracts, account records and business contact details are kept while the agreement is active and for 5 years after it ends, to establish or defend legal claims. Invoices and accounting records are kept for 7 years from the end of the calendar year in which the financial year ended, as required by the Swedish Accounting Act (Bokföringslagen). |
AI agent settings | Current AI-agent settings and knowledge-base content are maintained while configured and used by the customer, or until the customer deletes or changes them. Earlier versions of these settings are kept in the account’s change log and follow the retention of security and activity records. |
Security, activity and connector logs | Security and connector activity records, including IP addresses, are kept for 12 months and then deleted, unless the law requires us to keep them longer. |
Connector authentication and grants | Access tokens typically expire after one hour; refresh tokens expire after 30 days; revoking a token ends its access immediately. Expired access tokens are deleted automatically; records of ended connections and access are kept for 12 months after the connection ends and then deleted. |
Support tickets and feedback | Support requests, technical feedback, and error information are kept while the case is open and deleted within 12 months after it is closed, unless needed longer for legal claims or to comply with law. |
Website analytics and marketing contacts | Website analytics and marketing contact data are kept for up to 12 months and then deleted. |
Customers may request return or deletion of personal data processed on their behalf in accordance with their agreement with us. Deleting a lead from the active system also removes its related metadata from that system; a limited lead identifier and submission timestamp may be retained only where necessary for legal claims or a legal requirement. Backup copies are deleted within 90 days of the lead’s deletion and are not used for normal operations. For on-premises deployments, the customer and Brightcall follow the allocation of backup, access and deletion responsibilities established in their deployment agreement.
9. Security
Brightcall maintains organisational and technical safeguards designed to protect confidentiality, integrity and availability, including role-based access controls, secure authentication, encryption where appropriate, audit logging, supplier due diligence, vulnerability management, incident handling and business-continuity procedures. These include multi-factor authentication for production access, encryption of data in transit and at rest in line with our cryptography policy, daily backups stored separately from production systems, quarterly vulnerability scans of public-facing systems and an annual penetration test. Confidential production customer data is not used in development or test environments, and administrator access to customer data is logged. Brightcall AB holds ISO/IEC 27001:2022 certification for the scope stated on its current certificate; certification is not a guarantee that incidents cannot occur.
10. Privacy rights and customer choices
Where Brightcall acts as controller, individuals may have rights under applicable law to request access, correction, erasure, restriction of processing, portability, or to object to processing, and to withdraw consent where consent is the basis. Please contact legal@brightcall.ai or call one of the numbers below. We respond within one month; complex requests may take up to two further months, and we will tell you if so. Identity verification may be needed and some legally required records cannot be erased immediately. Brightcall does not make decisions with legal or similarly significant effects about individuals solely by automated means.
Right to object. Where we rely on legitimate interests, you may object at any time on grounds relating to your particular situation. You may object to direct marketing at any time, and we will then stop using your data for it.
For call, lead and other data held on behalf of a business customer, individuals should generally contact that customer first. Brightcall supports the customer in responding to lawful requests as required by our agreement with the customer. You may lodge a complaint with the data protection authority where you live or work, or with Integritetsskyddsmyndigheten (IMY), the Swedish authority.
Authorised account users may manage their own integration, recording, retention and data-deletion settings to the extent offered by their plan or service agreement. Connected AI assistants can be disconnected in General settings > Connected apps; this does not automatically erase copies already transmitted to the external assistant provider.
11. Cookies and website technology
We use cookies and similar tracking technologies, including advertising pixels, both on our website and in the Brightcall dashboard, as listed below. Strictly necessary cookies, which are needed to operate the website and the authenticated service, are used without consent. All other technologies, including analytics, marketing and advertising pixels (such as Google Ads, the LinkedIn Insight Tag and the OpenAI Ads Measurement Pixel), are loaded only after you have given your prior consent in the consent banner. Your consent is voluntary, given separately for each purpose, and based on the information in this section; refusing it does not limit your use of the website or the service. You can withdraw your consent at any time, as easily as you gave it, via the ‘Cookie settings’ link on our website. You can also block or delete cookies in your browser settings. The technologies we use on our website and dashboard are: strictly necessary: Cloudflare (security and content delivery), Cloudflare Turnstile and hCaptcha, loaded by Chargebee (protecting forms, sign-in and payment pages against bots and abuse), Webflow (website hosting) and its content-delivery providers Fastly, Amazon CloudFront and Amazon S3 (delivering website files, images and scripts), Brightcall's own locale and callback services (detecting your country to show the right local website, and operating the callback widget when you use it), Usercentrics (our cookie consent tool, which stores your consent choices), Chargebee (billing and payments in the dashboard) and Intercom (the customer support chat that is part of the service, including in the dashboard; its cookies keep your chat session and conversation history); functional: Google Fonts (web fonts); analytics: Google Tag Manager (used only to load other tags), Google Analytics, HubSpot Analytics and PostHog, hosted in the EU, which collects page views, clicks, technical errors and page-speed data so that we can understand and improve the website and dashboard; for signed-in users, PostHog may also receive the user ID and email address to analyse product use (PostHog session recording is switched off); marketing (advertising): Google Ads (conversion measurement and remarketing), the HubSpot ads pixel, the LinkedIn Insight Tag and the OpenAI Ads Measurement Pixel; Google Ads and the OpenAI Ads Measurement Pixel may use hashed contact details you submit in our forms for matching, where enabled. These tools may receive your IP address, browser and device information and the pages you visit. Google, HubSpot, LinkedIn and OpenAI receive this data as independent controllers or, for its collection on our website, as joint controllers with us under Article 26 GDPR; the essence of these arrangements is available from legal@brightcall.ai. Where they process it in the United States, transfers rely on the EU-US Data Privacy Framework where the recipient is certified, and otherwise on Standard Contractual Clauses.
12. Contact and changes
Brightcall AB (registration no. 556883-8329), Brunnsgatan 6, 111 38 Stockholm, Sweden. Privacy and legal enquiries: legal@brightcall.ai. Telephone (Sweden): +46 8 446 83 999. Telephone (United States): +1 980 202 0158. Brightcall AB has not appointed a data protection officer; privacy enquiries: legal@brightcall.ai.
We may update this Privacy Policy when our services, legal requirements or data handling change. Material changes will be communicated as required by law. The effective date at the top shows the current version.