Privacy Policy

Quick Informatica S.A. (“Quick Informatica”, “Sabio”, “we” or “our”) develops and operates Sabio, an AI assistant platform for organizations.

This Privacy Policy explains how we collect, use, store and protect information when someone uses Sabio or connects a Google account, Gmail or another integration available on the platform.

1.Data Controller

Quick Informatica S.A.
Humberto 1° 133, 3rd floor
C1107, Autonomous City of Buenos Aires, Argentina
Contact email: hola@sabioia.com

2.Information We Collect

Depending on the features used, Sabio may process:

Sabio account data

• Name and email address.
• User and organization identifiers.
• Information needed to authenticate and maintain the session.

Google identity and profile data

To authenticate the user and link their Google account to Sabio, Google may provide:

• The Google account's unique identifier.
• Full name.
• Profile photo.
• Primary email address.
• Preferred language or locale.
• Other public profile information Google includes within the profile permission.

Google's consent screen may describe this permission using general categories, such as public personal information, preferred languages, gender or other information published by the user.

Sabio uses only the information needed to authenticate the user, link the account and display basic account details. Sabio does not use this information for personalized advertising, commercial profiling or training general-purpose AI models.

Gmail-related data

When the user connects Gmail, Sabio may receive and store:

• The connected Google account's identifier.
• Associated email address.
• Authorized permissions.
• OAuth access tokens, refresh tokens and ID tokens.
• Token expiration dates.
• Technical information needed to renew authorization.

The integration uses the following standard Google permissions:

• openid, to associate the user's identity with Google.
• email, to retrieve the primary email address.
• profile, to retrieve basic profile information.
• https://www.googleapis.com/auth/gmail.send, to send emails on the user's behalf.

The gmail.send permission allows emails to be sent on the user's behalf. Sabio does not request permissions to read the inbox, manage Gmail settings, delete messages or access general mailbox content. Gmail permissions documentation .

Other integrations

When enabled, Sabio may process information related to Meta, WhatsApp Business or other services connected by the organization.

This information may include business account identifiers, phone numbers, messages, connection status and other data needed to operate those integrations.

Conversation and email content

When the user uses Sabio, the platform may process:

• Instructions provided to the assistant.
• Conversation messages and responses.
• Email recipients, subjects and bodies.
• Information needed to generate, modify or send a message.
• Attachments, when the relevant feature is enabled.

Email content may remain within a Sabio conversation if it was used or generated during that conversation.

Technical information

We may collect technical and operational information, such as:

• Authentication logs.
• Connection errors.
• Sending status.
• Operation dates and times.
• Technical identifiers needed to diagnose issues and prevent abuse.
• Audit logs related to operations performed on the platform.

OAuth credentials are stored in internal records associated with the account in Sabio's database. Full OAuth tokens are not intentionally included in logs, error messages, conversations or responses sent to the browser.

3.How We Use Information

We use information to:

• Authenticate the user and maintain their account.
• Link a Google account to a Sabio account.
• Connect and manage the Gmail integration.
• Prepare and send emails at the user's request.
• Execute instructions provided to the Sabio assistant.
• Generate, summarize or transform content when the user uses those features.
• Configure and maintain other integrations enabled by the organization.
• Maintain and protect the security of the service.
• Diagnose errors and provide support.
• Generate operational and usage metrics.
• Meet legal obligations and respond to valid requests from authorities.

We do not sell personal information or use Gmail content for personalized advertising.

4.Sharing, Transfer and Disclosure of Google Data

When the user connects a Google or Gmail account, Sabio may process:

• The connected account's identifier and email address.
• Name and profile photo.
• Basic profile information provided by Google.
• Authorized permissions.
• OAuth tokens and their expiration dates.
• Information needed to send emails through Gmail.
• The content of emails the user requests to send, including recipients, subject, body and attachments where applicable.

Sabio shares, transfers or discloses this data as follows:

Google's OAuth services process authentication, credential issuance and token renewal.

Refresh tokens remain in Sabio's backend and are used only to request new access tokens from Google. ID tokens are used for authentication and identification.

The Gmail API receives a valid access token to authorize sending the message. Refresh tokens and ID tokens are not sent to the Gmail API to send emails.

Data obtained directly from Google or the Gmail API is not shared with Anthropic, OpenAI or Google AI. OAuth tokens, Google profile data and information automatically obtained from Gmail are not sent to AI model providers.

When the user uses an AI feature, Sabio may send instructions, conversations and content entered or generated within Sabio to Anthropic, OpenAI or Google AI. If the user manually copies information from Gmail into a conversation or instruction, that information may be processed as part of the content submitted by the user.

Sabio does not sell Google data, use it for personalized advertising or use it to create, train or improve general-purpose AI models. Information received through Google Workspace permissions is used only to provide visible features requested by the user.

Human access to Google data is restricted to authorized personnel and may occur only when necessary to:

• Provide support with the user's consent.
• Investigate security issues or abuse.
• Meet legal obligations.
• Resolve technical incidents.

Use of information received from Google Workspace complies with the Google Workspace API User Data Policy , including its Limited Use requirements.

5.Technology Providers

To provide the service, Sabio uses technology providers including:

• Vercel, to host the application and run backend functions.
• Supabase, to host the database and associated services.
• Google, to authenticate accounts and send emails through the Gmail API.
• Anthropic, to use Claude models.
• OpenAI, to use GPT models.
• Google AI, to use Gemini models.
• Meta and Twilio, where applicable to Meta or WhatsApp Business integrations.

These providers may process information on Sabio's behalf in accordance with their policies, data processing agreements and applicable settings.

6.International Transfers

Technology providers used by Sabio may process information in countries other than the user's country of residence.

Where appropriate, Sabio seeks to apply suitable contractual, technical and organizational measures to protect transferred information.

7.Credential Storage and Lifetime

OAuth credentials needed to maintain the Gmail connection are stored in Sabio's database and processed on the server.

Access tokens issued by Google are short-lived credentials. When they expire, Sabio may request renewal using the refresh token, provided it remains valid.

Token lifetime depends on Google and may vary according to application status, consent settings, account activity and other security conditions.

Sabio retains credentials while the integration remains connected, unless they must be deleted earlier for security, compliance or maintenance reasons.

8.Disconnecting Gmail

The user can disconnect Gmail in Sabio's settings.

When Gmail is disconnected, Sabio removes the connected account's local association and the OAuth credentials stored in its operational systems. From that point, Sabio stops using those credentials to send emails.

Disconnecting Gmail in Sabio does not automatically revoke permission granted directly to Google. The user can review or revoke that permission in their Google account's security settings.

Disconnecting Gmail does not necessarily delete conversations or logs previously stored in Sabio. Deletion of that data is handled under the applicable retention rules.

Credentials or technical logs may temporarily remain in backups or recovery systems during normal retention cycles.

9.Retention of Conversations and Logs

Sabio may store conversations with assistants, including instructions, responses and email-related content, to maintain conversation continuity, provide service features, generate metrics and provide support.

We may also retain technical and audit logs related to authentication, errors, sending and other operations performed on the platform.

Information is retained for as long as needed to provide, protect and improve the service, meet legal obligations and resolve disputes. The specific period may depend on the organization's settings, the type of information and applicable operational or legal requirements.

Conversations and logs may remain in backups or recovery systems during those systems' normal retention cycles.

10.Security

We apply reasonable technical and organizational measures to protect information against unauthorized access, loss, alteration or disclosure.

OAuth credentials are processed on the server and must not be exposed to the browser, other users or application logs.

However, no system can guarantee absolute security against all risks.

11.User Rights

The user may:

• Request access to information associated with their account.
• Request correction of inaccurate information.
• Request deletion of their data, where applicable.
• Disconnect Gmail.
• Revoke Sabio's access from their Google account.
• Request information about the processing of their data.

Requests may be sent to hola@sabioia.com.

Deletion requests may be subject to legal obligations, security needs, dispute resolution and normal backup cycles.

12.Changes to This Policy

We may update this Privacy Policy to reflect changes to Sabio, available integrations, providers used or legal requirements.

We will publish the updated version on this page and indicate the date it was last modified.