Privacy Policy

Last updated: November 16, 2026 | Versão em português

Dattia takes the privacy of the people who use the platform seriously. This Privacy Policy describes which personal data we process, for what purpose and on which legal basis, who we share it with, how long we keep it and how you exercise your rights, in compliance with Brazil's General Data Protection Law (Law No. 13,709/2018, LGPD) and with the policies of the third-party platforms we integrate with.

It applies to the Dattia Revenue Intelligence platform, available at https://crm.dattia.com.br and on the domains of authorized partners that offer the same platform under their own brand, to the institutional website and to the public forms our customers create with the platform.

This English version is provided for convenience. If the two versions differ, the Portuguese version prevails.

1. Our roles: controller and processor

The platform serves companies, so we act in two distinct roles defined by the LGPD:

  • Controller: for the data of the people who create an account and use the platform (registration, authentication, billing, usage records and communications with us). In these cases we decide how and why the data is processed, and this policy is the complete reference.
  • Processor: for the data that customer organizations enter into or connect to the platform in the course of their own business: contacts and leads, WhatsApp conversations, emails, calendar events, meeting recordings, form responses and lookup results. In these cases the customer organization is the controller, defines the purposes and answers for the legal basis of the processing; we process this data exclusively according to its instructions and to the settings made on the platform.

If your data is on the platform because a customer company recorded it (for example, you are a business contact of a customer of ours), the request for access, correction or deletion should be addressed to that company. You can still write to us and we will forward the request to the responsible customer, as described in section 17 and on the data deletion page.

2. Data we process

2.1. Account and organization data (as controller)

  • Registration: full name, email, phone and password (stored only as a cryptographic hash, never in clear text). The CPF (Brazilian taxpayer number) is processed when you register it as an alternative sign-in identifier.
  • Organization: company name, industry, the website you provide and the company profile built during onboarding from the public website you indicate (summary, products, target audience, differentiators, competitors), always reviewable and editable.
  • Payments: for subscriptions paid through Pix, the payer's name and document and the payment status, processed by the payment gateway. We do not store credit card data.
  • Usage and technical records: IP address, session identifiers, access dates and times, relevant actions on the platform (activity log) and usage metrics of the artificial intelligence features (model used, token volume and duration), used for auditing, security and billing.
  • Support: the content of the messages you send us when asking for help.

2.2. Data processed on behalf of customer organizations (as processor)

  • Contacts and leads: name, email, phone, company, potential value, notes, remarks, pipeline stage, source and campaign attribution data (when coming from ads or forms with UTM parameters).
  • Connected communications: WhatsApp messages of the number connected by the organization, emails and calendar events of the Google account connected by each user, and meeting recordings and transcripts when the note-taking feature is triggered.
  • Public forms: the data visitors fill in on forms embedded in customers' websites, with UTM parameters and the IP address of the submission, used only to limit abuse and fraud.
  • Files and knowledge: documents, spreadsheets and images uploaded to the organization's knowledge base, with text extraction for search.
  • Lookup and research results: responses from data bureaus consulted by the organization (section 10) and company dossiers built with web research (section 11).

3. Purposes and legal bases

We process personal data on the legal bases of article 7 of the LGPD:

  • Performance of a contract: creating and maintaining your account, authenticating access, providing the contracted features, processing payments and providing support.
  • Legitimate interest: keeping the platform secure, preventing fraud, spam and abuse, measuring and improving the product with aggregated data and sending operational communications about the service.
  • Consent: connecting third-party service accounts (Google, Meta, ClickUp, Notion), triggering the recording of a meeting and receiving marketing communications. Consent can be withdrawn at any time.
  • Compliance with a legal obligation: keeping application access records for the period required by the Marco Civil da Internet (Brazil's Internet Civil Framework), keeping tax documents and complying with orders from competent authorities.

We do not use personal data for automated decisions with legal effects on you without human review, and we do not sell personal data under any circumstances.

4. Google user data

The platform uses each user's Google account for three things: signing in to the CRM, using Google Calendar and using Gmail from inside the CRM. The connection is individual, made through Google's own OAuth flow, and each permission appears on Google's consent screen before any access. The Gmail and Calendar permissions are requested only when you connect those integrations, never at sign-in. We never see or store your Google password.

4.1. What we access, per permission, and what for

  • Identity (openid, userinfo.email, userinfo.profile): your name, email address, profile picture and Google account identifier. We use them to authenticate sign-in with Google and to show which account is connected.
  • Google Calendar (calendar.events): the events of your calendars: title, time, attendees, description and video call link. We use them to show your calendar in the CRM and to create, change and cancel the meetings you schedule through the platform, with a Google Meet link when you ask for one.
  • Sending through Gmail (gmail.send): allows sending emails on your behalf. We use it only when you command the sending of an email or a reply from inside the CRM. This permission gives no access to reading your mailbox.
  • Gmail mailbox (gmail.modify): the messages in your mailbox: sender, recipients, subject, body, attachments and labels. We use them to display your emails inside the CRM, link them to the matching contacts, suggest new contacts from the people who exchange emails with you, and mark messages as read and archive them when you do so through the platform. We do not delete messages from your mailbox.

Your mailbox and your calendar are personal: other users of your organization have no access to them, whatever their role. What the organization sees is the CRM record generated from them, such as the meeting in a contact's history.

4.2. Limited Use

Dattia's use and transfer to any other app of information received from Google APIs will adhere to Google API Services User Data Policy, including the Limited Use requirements.

In practice, this means that:

  • we use Google user data only to provide and improve the features visible to you on the platform itself, described in section 4.1;
  • we do not sell Google user data under any circumstances;
  • we do not transfer this data to third parties, except when necessary to provide these features with your consent, for security reasons, to comply with the law or in the event of a corporate reorganization, with prior notice;
  • we do not use this data for advertising of any kind, nor to build advertising profiles;
  • no person on our team reads this data, except with your explicit consent, when necessary for security reasons (such as investigating abuse), to comply with the law, or when aggregated and anonymized for internal operations;
  • Google user data is not used to develop, improve or train generalized artificial intelligence or machine learning models.

4.3. Artificial intelligence features over emails

When your organization contracts the artificial intelligence features, the content of emails may be sent to the language model providers listed in section 9 in two situations: when you ask the assistant for an action that involves an email of yours, and when the platform reads the emails exchanged with a CRM contact to generate that contact's summary and context notes. In both, only the content needed for the feature is sent, under contracts that forbid its use for model training. Without the artificial intelligence features contracted, no email content is sent to these providers.

4.4. Storage, retention, revocation and deletion

  • Storage: the access and refresh tokens granted by Google are stored encrypted (AES-256-GCM) and used exclusively for the operations above. The synchronized copies are kept in your organization's database, with access restricted to you.
  • What is copied: the initial synchronization brings up to 200 messages from the last 90 days and the events from 30 days back to 180 days ahead; after that, only what changes. Attachments are not copied: they are fetched from Gmail when you open them.
  • Retention: the copies are kept while the Google account stays connected.
  • Disconnecting: you can disconnect the account at any time in the platform settings. On disconnection we revoke the authorization at Google and immediately delete the tokens and the synchronized emails and events. Only the CRM records created from them remain, such as the meeting in a contact's history.
  • Revoking at Google: you can also revoke access directly at myaccount.google.com/permissions. After that the platform stops accessing your account and asks for a new connection.
  • Requesting deletion: to request the deletion of any remaining data, write to brenner@dattia.com.br or follow the data deletion page.

5. Data received from Meta (Facebook and Instagram)

When a customer organization connects its own Facebook account and authorizes a Page, we start receiving the sign-ups people submit on the lead ad forms (Lead Ads) of that Page: the fields filled in on the form (such as name, email and phone) and the attribution data of the campaign, ad set and ad. This data is used exclusively to create the contact in the CRM of the advertising organization, which is its controller.

We do not access the personal profile, the friends list or other account information of whoever filled in the form. Access can be revoked at any time by disconnecting the integration on the platform or removing the app in the Facebook settings, and the deletion of the data received can be requested as described on the data deletion page.

6. WhatsApp

The customer organization can connect a WhatsApp number to the platform through connection providers. The messages sent and received on that number, with the contacts' name and profile picture when the provider makes them available, are stored to build the organization's conversation inbox and linked automatically to the CRM contact with the same phone.

Visibility follows each user's role in the organization: members see the conversations of their own contacts and the ones assigned to them; administrators see the conversations of the organization's number. We do not use the content of the messages for any other purpose, and the customer organization answers for compliance with WhatsApp's policies and for the legal basis of the communications it sends.

7. Meeting recording and transcription

When the organization contracts the meeting note-taking feature, the organizer can, meeting by meeting, send a recording assistant to the video call. Nothing is recorded by default: sending it is an explicit choice for each meeting, and the assistant joins the call as a visible and identified participant, so that everyone present can see it.

The recording is processed by a specialized sub-processor (section 13) to generate the transcript, which is linked to the meeting and to the contact in the CRM and can be analysed by the platform's artificial intelligence features (section 9). The meeting organizer is responsible for informing the participants and obtaining the consents required by the applicable law before triggering the recording.

8. Public forms

Customers can create forms that are embedded in their own websites to capture contacts. Whoever fills in one of these forms has the data sent directly to the CRM of the organization that created it, which is its controller. We also record the UTM parameters of the visit, when present, and the IP address of the submission, used only to limit abusive submissions. It is up to the customer organization to present its own privacy policy to those who fill in its forms.

9. Artificial intelligence features

The platform offers an assistant and automatic analyses (such as the summary and evaluation of recorded meetings). To generate these answers, the content strictly needed for the request, such as the question asked, the relevant CRM data, emails exchanged with a contact (section 4.3) or the transcript excerpt under analysis, is sent to language model providers contracted by us, currently OpenAI and Anthropic, under API terms that forbid the use of this data to train their models.

  • we do not use customer data to train our own models or third-party models;
  • we record metrics of each use (model, token volume, duration) for auditing and billing, without duplicating the content;
  • sensitive actions commanded by AI, such as sending an email, require the user's explicit approval before running;
  • AI-generated content may contain errors and must be reviewed by a person before it supports decisions.

10. Data bureau lookups

Organizations that contract the lookup module can query Brazilian data bureaus by CPF, CNPJ (company taxpayer number) or vehicle plate, using credentials the organization itself contracted with the bureau. In this flow the customer organization is the controller: it defines the purpose of the lookup and answers for the legal basis before the data subject. We act as processor, transmitting the query and storing the result in the organization's environment.

  • access to the module is restricted to the organization's administrators;
  • each lookup is recorded in an auditable history, with date, author and request identifier;
  • recent results are reused for up to 30 days to avoid repeated lookups of the same document;
  • the customer is forbidden to use lookup results for a discriminatory, unlawful or abusive purpose, as set out in the Terms of Use.

11. Web research

When the research feature is contracted, the platform can, at a user's request or by decision of the assistant during a conversation, search public internet sources about the companies of the contacts, through a search provider contracted by us. The result becomes a company dossier, with the sources indicated, and no search is triggered automatically without an action by the user.

12. Cookies and session technologies

We use only cookies essential to the operation of the platform: a session cookie to keep you signed in, a cross-site request forgery (CSRF) protection token and interface preferences. We do not use advertising cookies or third-party trackers that follow you across other sites.

You can set your browser to refuse or delete cookies, but without the session cookie it is not possible to stay signed in.

13. Who we share data with

We share personal data only in the situations below:

  • Inside your organization: users of the same organization access CRM data according to each one's role (members see their own records; administrators see the organization's).
  • Sub-processors: suppliers that process data on our behalf, listed below, bound by contract to protect the data and to use it only to provide the contracted service.
  • Legal obligation: when required by law, court order or request from a competent authority.
  • Protection of rights: when necessary to investigate fraud or abuse, or to exercise rights in judicial or administrative proceedings.

13.1. Current sub-processors

  • Vercel (United States): application hosting and storage of uploaded files.
  • Neon (United States): PostgreSQL database, with an isolated database per whitelabel customer.
  • Resend and SMTP providers (United States): sending of the platform's transactional emails.
  • Google (United States): Gmail and Google Calendar APIs, when the user connects their own account (section 4).
  • Meta Platforms (United States): receipt of ad sign-ups and communication through WhatsApp (sections 5 and 6).
  • OpenAI and Anthropic (United States): processing of the artificial intelligence features (section 9).
  • Recall.ai (United States): meeting recording and transcription, when the feature is triggered (section 7).
  • Exa (United States): web research about companies, when the feature is used (section 11).
  • Pix payment gateway (Brazil): processing of paid subscriptions.
  • WhatsApp connection providers: infrastructure for sending and receiving messages of the number connected by the organization.
  • Data bureaus (Brazil): responses to the lookups commanded by the organization with its own credentials (section 10).
  • ClickUp and Notion (United States): only when the organization connects its own accounts to link tasks and pages to CRM records.

This list is updated when a supplier joins or leaves the operation; the version in force is always the one published on this page.

14. International data transfer

Some of the sub-processors listed above process data outside Brazil, mainly in the United States. These transfers are carried out under article 33 of the LGPD, with suppliers that adopt contractual data protection safeguards compatible with Brazilian law, and limited to what is necessary to provide the service.

15. Information security

  • encryption of data in transit (HTTPS/TLS) across the whole platform;
  • passwords stored with a bcrypt hash; integration credentials and tokens encrypted at rest with AES-256-GCM;
  • data isolation per whitelabel customer in dedicated databases, besides the separation per organization inside each database;
  • role-based access control, with the minimum visibility needed for each function;
  • logging of relevant activities for auditing;
  • periodic backups and segregated production environments.

The full description of the practices, including the responsible vulnerability disclosure channel, is on the Security page.

No system is immune to incidents. If a security incident may bring relevant risk or harm to data subjects, we will notify those affected and the National Data Protection Authority (ANPD) under the terms of the LGPD.

16. Retention and deletion

  • account and CRM data is kept while the account or the organization is active;
  • after termination, the data is deleted from the active systems and eliminated from the backups within 90 days;
  • access records are kept for the minimum period of 6 months required by the Marco Civil da Internet;
  • billing and tax records and bureau lookup histories are kept for the retention periods required by law or necessary for the regular exercise of rights.

17. Your rights as a data subject

The LGPD guarantees you, among others, the rights to confirm the existence of processing; access your data; correct incomplete, inaccurate or outdated data; request anonymization, blocking or elimination of data that is unnecessary or processed in breach of the law; request portability; obtain information about the sharing carried out; withdraw consents; and request a review of automated decisions.

To exercise any right, write to privacidade@dattia.com.br. We answer within 15 days. When the request concerns data of which a customer organization is the controller, we will forward it to that organization and give the technical support needed to handle it. You can also file a complaint with the ANPD.

18. Data deletion

The complete instructions for requesting the deletion of data, including the data received through the integrations with Google and Meta, are on the data deletion page.

19. Children and adolescents

The platform is intended for professional use by people over 18. We do not knowingly collect data from children or adolescents; if we identify a registration under these conditions, it will be closed and the data deleted.

20. Changes to this policy

We may update this policy to reflect changes in the service or in the law. Relevant changes will be communicated by email or by a notice on the platform with reasonable advance, and the last updated date at the top of this page always indicates the version in force.

21. Contact and Data Protection Officer

Questions about this policy or about the processing of your data can be sent to the channels below. The Data Protection Officer (DPO) answers through the dedicated channel.

Dattia

Privacy: privacidade@dattia.com.br

Google user data: brenner@dattia.com.br

Data Protection Officer (DPO): dpo@dattia.com.br

Support: suporte@dattia.com.br