KonnektAI Privacy Policy
Version 2026-10-08.
Courtesy translation; in case of any discrepancy, the Portuguese version prevails.
Correction of 2026-10-16: the retention period of the CPF is now written in full (it used to say "Same", the period of the row above). Nothing changed in how the data is processed, and the accepted version stays the same.
Addition of 2026-10-27: section 4.3, about Meta channels (Facebook Page Messenger and Instagram): what data Meta provides, what for, for how long and how to request deletion.
What changed since version 2026-10-01: sections 4.1 and 4.2 (the same, in English), about Google Calendar data.
1. The two roles
KonnektAI processes two kinds of data, and the responsibility changes with the kind:
- Data of those who use the platform (you and the contracting party's team): Enough is the controller.
- Data of the patients who talk to the service: the contracting party is the controller, and Enough is the processor, acting on its behalf. Patients exercise their rights with the contracting party.
This policy deals mainly with the data of those who use the platform, and summarizes what we do with the patients' data.
2. Your data that we process, and why
| Data | What for | For how long |
|---|---|---|
| Name, e-mail and phone | Identify you, allow sign-in and send platform notices | While the account exists, plus the legal period after deletion |
| CPF (Brazilian taxpayer ID) | Unequivocally identify who is responsible for a recorded act, and keep a single identity across contracting parties | While the account exists, plus the legal period after deletion |
| Password (stored only as a cryptographic hash) | Authenticate | While the account exists; no one sees the password |
| Second factor and recovery codes (encrypted) | Protect the account | While the factor is enabled |
| Record of your acceptance (document, version, date, IP) | Prove that you accepted these terms | While the acceptance is in effect, plus the evidence period |
| Audit trail and sign-in attempts (action, date, IP, browser) | Be accountable, detect attacks, investigate incidents | Period being defined; when you are deleted, your name is removed and the record of the act remains |
| Technical records (logs) | Diagnose failures | 90 days, without the content of patient messages |
The legal bases are the performance of the contract with the contracting party, compliance with a legal obligation, the regular exercise of rights and the legitimate interest in keeping the platform secure.
3. Patient data, in summary
- The channel identifier (the WhatsApp number, for example) and the text of the conversations are stored, because there is no service without knowing whose conversation it is. Conversations may contain health data typed by the patient.
- We do not keep patient records: name, health plan and history are read from the contracting party's management system at the time of service.
- The incoming message is stored as it arrived, in private storage, so that none is lost. The retention period for conversations is being defined with the legal team, and the contracting party will be informed before it takes effect.
4. Who the data is shared with
Only with these, and only to provide the service:
- Channel providers (WhatsApp and its providers, Telegram): where the message passes through.
- Artificial-intelligence provider: the minimum excerpt of the conversation, under a no-retention, no-training contract.
- The contracting party's management system: it is their system; KonnektAI reads and books appointments in it.
- Amazon Web Services: the infrastructure where everything runs, in Brazil and in the United States.
- E-mail provider: your e-mail and the content of the notices — never patient data.
We do not sell data, and we do not use it for advertising.
4.1 Google data (Google Calendar)
When a business connects Google Calendar to KonnektAI, the person connecting authorizes, on Google's screen, three accesses — and only these:
- see the list of their calendars (
calendar.calendarlist.readonly), so the manager can choose which calendars serve each service; - see when each calendar is busy (
calendar.freebusy) — only the start and end of busy periods, without title, description or attendees —, so the service offers the business's customer only free times; - create, change and cancel events (
calendar.events), only those KonnektAI itself created — the appointment the business's customer asked for in the conversation. Events created by other people or systems are not changed or deleted, and their content is not used.
What we store:
- the renewal credential that Google issues (refresh token), encrypted, never shown on screen and deleted when the business disconnects;
- the identifier of the calendars that serve each service (the primary calendar's is the Google account e-mail);
- in the events we create: the title, with the service name and the customer's phone number, and internal marks (the business, the customer and the service) to find them later;
- in the conversation history: the times offered to the customer and the references of their bookings (the calendar and event identifiers), so they can confirm, reschedule or cancel; and, when the booking awaits the team's approval, the request in the approval queue (the time and the calendar identifier).
Busy periods are not stored: they are read on demand and discarded.
Who we share with: to answer the business's customer, the conversation assistant (the artificial-intelligence provider in item 4) receives the free times and the customer's own bookings — date and time, service and calendar identifier —, under a no-retention, no-training contract. No other Google data leaves KonnektAI.
Limited Use. The use and transfer, to any other application, of information received from Google APIs follow the Google API Services User Data Policy, including the Limited Use requirements. In particular: Google data is used only to offer and book appointments in the business's calendar; it is not sold; it is not used for advertising; it is not used to train generalized artificial-intelligence models; and no one at Enough reads it, except with the business's express consent for a support request, when the law requires, or to investigate abuse or a security incident.
How to undo: the business disconnects Google on the Management system screen — the credential is deleted and KonnektAI no longer reads or writes anything in the calendar — and can also remove the access at myaccount.google.com/permissions. Events already created stay in the business's calendar, which is theirs.
4.2 Google user data (English version of section 4.1)
When a business connects Google Calendar to KonnektAI, the person connecting grants, on Google's consent screen, three accesses — and only these:
- see the list of their calendars (
calendar.calendarlist.readonly), so the manager can choose which calendars serve each service; - see when each calendar is busy (
calendar.freebusy) — only the start and end of busy periods, without title, description or attendees —, so the assistant offers the business's customers only free times; - create, change and cancel events (
calendar.events), only those KonnektAI itself created — the appointment the business's customer asked for in the conversation. Events created by other people or systems are not changed or deleted, and their content is not used.
What we store:
- the refresh token Google issues, encrypted, never shown on screen and deleted when the business disconnects;
- the identifiers of the calendars that serve each service (the primary calendar's identifier is the Google account e-mail);
- in the events we create: the title, with the service name and the customer's phone number, and internal marks (business, customer and service) to find them later;
- in the conversation history: the times offered to the customer and the references of that customer's bookings (calendar and event identifiers), so they can confirm, reschedule or cancel; and, when a booking awaits the team's approval, the request in the approval queue (the time and the calendar identifier).
Busy periods are not stored: they are read on demand and discarded.
Who we share with: to answer the business's customer, the conversation assistant (the artificial-intelligence provider in section 4) receives the free times and that customer's own bookings — date and time, service and calendar identifier —, under a no-retention, no-training contract. No other Google data leaves KonnektAI.
Limited Use. KonnektAI's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. In particular: Google data is used only to offer and book appointments in the business's calendar; it is not sold; not used for advertising; not used to train generalized artificial-intelligence models; and no one at Enough reads it, except with the business's express consent for a support request, when required by law, or to investigate abuse or a security incident.
How to undo: the business disconnects Google on the Sistema de gestão screen — the credential is deleted and KonnektAI no longer reads or writes anything in the calendar — and can also remove the access at myaccount.google.com/permissions. Events already created stay in the business's calendar, which is theirs.
4.3 Meta channels (Facebook Page Messenger and Instagram)
When a business connects its Facebook Page to KonnektAI, to serve customers on Messenger, or, once available, its Instagram account, the person from the business who connects it logs in with Facebook and chooses, on Meta's screen, which Pages to give KonnektAI. From then on, Meta provides us with:
- the Page access token, stored encrypted, never shown on screen or written to technical logs, and deleted when the business disconnects the channel;
- the Page identifier and name, which are public, to know which business each message belongs to;
- the identifier of the person who authorized (the person's app-scoped identifier, issued by Meta), stored only as a cryptographic hash, to find that person's connections when they withdraw authorization or request data deletion;
- the messages the business's customers send to the Page and each customer's identifier on the Page, to show the conversation to the team and reply on the same channel;
- the customer's public name on their profile, when Meta provides it, stored with the contact, so the team knows who they are talking to.
What for: only to receive and answer the messages customers send to the business's Page. This data is not sold, not used for advertising, and KonnektAI never starts a conversation.
Who is responsible: the messages and the customers' data belong to the business that connected the channel, which is the controller; Enough is the processor and processes this data on the business's behalf. The data of the person who connects, as someone who uses the platform, follows section 2.
For how long: the token, while the Page is connected; the customer's public name, the same period as the contact; the hash of who authorized, while the connection exists or until the deletion request; the message as it arrived from Meta, 7 days; the time of the last message of each conversation, 8 days, to respect Meta's reply window; and the conversations, the same period as other conversations (section 3).
How to request deletion: the business disconnects the channel in Integrations › Channels, and the token is deleted right away. The person who authorized can also request deletion of their data in their Facebook settings: Meta lets us know, and we delete the record of who authorized right away. Removing the app without requesting deletion only makes the connection ask for someone from the business to reconnect it. A customer who talked to a business asks that business for deletion, or writes to adm@enoughsolutions.com, and we forward the request to the business. The step by step, and how to track the request, are at konnektai.com.br/en/data-deletion.
5. Security
Passwords stored only as a hash (Argon2id); third-party credentials encrypted; access by profile, checked on the server on every request; separation between contracting parties in every query; a record of every administrative act; encrypted traffic.
6. Your rights
You may request confirmation of processing, access, correction, anonymization, portability, information about sharing and the deletion of your account. Deletion anonymizes your data and preserves the record of acts in the audit trail, because it is the proof of who did what for the contracting party and for third parties. Requests: [data protection officer's e-mail — to be filled in].
7. Changes
Changes to this policy create a new version, which you will need to accept to keep using the platform.
8. Data protection officer and contact
Data protection officer (DPO): [name and e-mail — to be filled in]. Enough Solutions — [company name, CNPJ and address — to be filled in once the company is incorporated].
KonnektAI