Privacy policy

1. Your Agentonic account data

• Identification: your email address, the name you choose to display and your sign-in credentials, managed by Supabase Auth. Members with an administration role in your workspace see your email.
• What you create on the platform: agents, instructions, documents you upload, conversations with the agents and the results of their evaluations.
• Content-free activity records: which operation happened, when and with what outcome, for audit and security. They never hold the text of your mail, files or messages.

2. Google data we access

We access your Google account only if you connect it to an agent, with the permissions Google shows you on its consent screen. We request the narrowest scopes that allow each feature:

• Gmail (https://www.googleapis.com/auth/gmail.modify): the account's address; the messages and threads (senders, recipients, subjects, dates, labels and content) the agent searches or reads at your request; the drafts it creates, updates or deletes; the messages it sends; and the user labels it creates or applies after your confirmation. This scope would also allow archiving or trashing; Agentonic never does either.
• Google Drive (https://www.googleapis.com/auth/drive.file): the name, type, modification date and content of the files you select with Google's picker, and of the documents the agent creates or updates with your confirmation. We see no other file in your Drive.
• Basic identity when picking files (openid, email, profile): when you use Google's picker, Google may also share your email address and basic profile data. We use them only to check that the account is the one you connected.

3. How we use Google data

• Answering you: the agent reads the messages or files your request needs and writes the answer in your conversation. Mail is read when you ask; it is not synchronized or imported into the agent's knowledge.
• Drafting, sending and labeling for you: every draft, send or label is shown with its exact recipients and content and runs only after your confirmation. The only exception is a send or draft you pre-authorize in a scheduled task: at most one per run, cancellable until it starts.
• Knowledge from Drive: Drive files you import into a knowledge collection are indexed so the agent can answer with citations. They are re-read periodically to reflect your changes.
• Learning your style (only with your separate consent): we analyze up to 200 of your sent messages from the last 90 days to draft a writing-style guide that you review and accept. The messages are not stored; only the guide you accept is kept.
• Security and support: we keep content-free records of each operation (for example, that a message was sent and when) for audit, abuse detection and to answer your questions.

We do not use Google data for advertising, profiling, credit or insurance decisions, or any purpose other than providing and improving the features described here.

4. Who we share data with

We do not sell personal data or Google data, and we do not share them with data brokers or advertisers. The processors that handle data on our behalf, solely to provide the service, are:

• OpenAI (API): receives the conversation text and the content of the messages or files needed to generate the answer you asked for, and the samples for the style guide. We use the API under terms that exclude training models on that data; OpenAI may retain it for up to 30 days for abuse detection.
• Voyage AI (API): receives the text of the documents you import into knowledge, including those from Drive, to compute search indexes, and passages to rank results. It does not train models on them.
• Supabase (Frankfurt, Germany): hosts the database, authentication and file storage.
• Microsoft Azure: hosts the servers where the applications and agents run.
• Resend: sends account emails (invitations and password resets). It receives no Google data.
• Google: the Gmail and Drive APIs, under Google's policies.

We may disclose data when the law requires it. Nobody at Avilabs reads your mail, files or conversations unless you expressly authorize it to resolve an issue or the law obliges us.

5. No AI model training

Data obtained from Google APIs, raw or derived, is not used to develop, improve or train artificial-intelligence or machine-learning models, whether generalized or third-party. The only personalized outputs are the ones you request for yourself: the style guide you review and accept, and the answers in your conversations. The AI providers we use are contracted under terms that exclude training on the data we send them.

6. How we protect data

• Google credentials (tokens) are encrypted with AES-256-GCM using a key kept outside the database and rotated; they are refreshed on each use and erased on disconnect.
• All communication is encrypted (TLS). The database enforces restricted roles and row-level security policies: each application and each agent reaches only what belongs to it.
• Agents run in isolated services with no network access and no credentials; a gateway holding the keys performs each call and checks authorization at that moment.
• Every action that writes to your account requires your confirmation, runs exactly once and is never retried automatically when the outcome is uncertain.
• Automated evaluations and Avilabs staff never access a real mailbox or Drive.

7. How long we keep data

• Google credentials: until you disconnect the account, the workspace removes you or Google revokes them. On disconnect they are erased immediately and, if no other connection of yours in Agentonic uses the same account, we also revoke access at Google.
• Conversations (including answers that quote your mail or files): 30 days from the last message. Closing a conversation erases its content immediately.
• Actions awaiting confirmation: their arguments (recipients, text) are erased when they run, are cancelled or expire; a sweep checks them every 15 minutes.
• Style guide: until you replace it, delete it or disconnect the account. The analyzed messages are not stored.
• Drive files imported into knowledge: until you remove them from the collection or disconnect the account; the text and derived indexes are then erased.
• Content-free activity records and billing data: per the workspace's retention, and as audit evidence.
• Backups managed by Supabase: expire within 7 days.

8. Your rights and how to exercise them

• Disconnect Google: in the agent, Configuración → Conexiones → Desconectar. You can also withdraw access from your Google account at myaccount.google.com/permissions.
• Delete data: closing conversations, removing files from knowledge and disconnecting accounts erases what is described above. To delete your account or all your data, write to us; we handle it within 30 days.
• Access, correct or object: write to the contact address and we will answer.

9. Changes and contact

If we change this policy, we will publish the new version on this page with its effective date and notify you in the application when the change affects Google data.

Contact: leonardo@avilabs.tech. Controller: Avilabs LLC.