Google API Services Disclosure
This page describes how Celdaro accesses, uses, stores, and protects information obtained through Google APIs, in compliance with the Google API Services User Data Policy.
Important Notice
Celdaro's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.
Table of Contents
1. What is Celdaro?
Celdaro is a B2B AI assistant designed for small and medium-sized businesses (SMBs). It helps teams manage business communications, emails, follow-ups, responses, and commercial productivity more efficiently.
Connecting Gmail is entirely optional. Users can use Celdaro without ever connecting a Gmail account. Gmail integration is only activated when a user explicitly chooses to connect their Gmail account from the Settings page.
- Manage and organize business email communications
- Classify and prioritize incoming messages
- Detect commercial intent and urgency in emails
- Generate AI-powered summaries of conversations
- Prepare draft responses for user review and approval
2. What Google Data Celdaro Accesses
Celdaro requests different Google permission scopes depending on the context. Login scopes are requested during sign-up. Integration scopes are requested only when the user explicitly connects their Gmail account.
Login Scopes
| Scope | Purpose | Data Accessed | Data Stored |
|---|---|---|---|
openid | Authentication | User ID | Not stored |
email | User email address | Email address | Email stored in database |
profile | User display name | Name and profile photo | Name stored in database |
Integration Scopes (only when the user explicitly connects Gmail)
| Scope | Purpose | Data Accessed | Data Stored |
|---|---|---|---|
gmail.readonly | Read and classify emails | Incoming/outgoing emails | Metadata + cleaned text preview (max 1,000 chars) for AI classification. Full HTML body is NOT stored. |
gmail.send | Send user-approved replies | Outgoing email delivery | Not stored — one-time action with explicit user confirmation |
userinfo.email | Identify connected account | Email address | Email stored in integration record |
3. Why Celdaro Needs Gmail Read-Only Access
Celdaro requests the gmail.readonly scope only after the user explicitly connects their Gmail account from the Settings → Integrations page. This scope is never requested during initial sign-up or login.
Celdaro uses Gmail read-only access to:
- Classify incoming emails by priority and category
- Detect urgency and commercial intent in messages
- Generate AI-powered summaries of email conversations
- Identify follow-up opportunities for business communications
- Prepare suggested draft replies for user review and approval
4. Why Celdaro Needs Gmail Send Permission
Celdaro requests the gmail.send scope only to send emails when the user explicitly clicks or confirms a send action. This scope is requested only after the user explicitly connects their Gmail account.
Every email requires explicit user confirmation before sending. Celdaro never sends emails automatically or without the user's explicit approval. The user must review the draft and click a confirmation button to send any email.
5. How Celdaro Uses Gmail Data
When a user connects their Gmail account, Celdaro uses the accessed email data exclusively to provide the following functionality:
- Classify incoming messages by priority and category
- Detect commercial intent and urgency in emails
- Generate AI-powered summaries of email conversations
- Identify follow-up opportunities for business communications
- Prepare draft responses for user review and approval
All Gmail data processing is performed solely to deliver the features requested by the user. No Gmail data is used for any purpose other than the functionality described above.
6. What Celdaro Does Not Do
Celdaro is committed to minimal, transparent, and secure use of Google data. The following is an explicit list of actions Celdaro does not perform:
- Celdaro does not request gmail.modify
- Celdaro does not request https://mail.google.com/
- Celdaro does not delete, archive, label, mark, or modify Gmail messages
- Celdaro does not sell Google user data
- Celdaro does not use Google user data for advertising
- Celdaro does not use Google user data to train generalized AI models
- Celdaro does not send emails without explicit user confirmation
7. Data Minimization
Celdaro follows the principle of data minimization. Only the minimum amount of data necessary to provide its functionality is stored:
- Email metadata: sender, recipient, subject, date
- Limited cleaned text previews (maximum 1,000 characters) for AI classification
- AI-derived classifications and summaries
- Encrypted OAuth tokens
The following data is not persistently stored:
- Full HTML email bodies are not persistently stored
- Email attachments are not stored persistently
8. AI Processing
Celdaro sends email text to AI providers (OpenAI) to power its intelligence features such as classification, summarization, intent detection, and draft generation.
AI Provider Data Protection
- Email data is processed by OpenAI under a Data Processing Agreement (DPA).
- OpenAI does not use data sent via API for model training (per OpenAI's API data usage policy).
- No OAuth tokens, passwords, or credentials are ever sent to AI providers.
9. Token Security
Celdaro takes the security of OAuth tokens and user credentials very seriously:
- OAuth tokens are encrypted at rest using Fernet (AES-128-CBC + HMAC-SHA256)
- Multi-tenant data isolation: each company's data is strictly isolated
- All communications between Celdaro and Google APIs occur over TLS 1.2+
- Tokens are never stored in plaintext
- Tokens are never sent to AI providers or any third party
10. Disconnect and Revoke Access
You can disconnect Gmail and revoke Celdaro's access to your Google data at any time, using either of the following methods:
From Celdaro
Go to Settings → Integrations → Disconnect Gmail. Celdaro revokes the Google OAuth token immediately upon disconnection.
From Google
Go to myaccount.google.com → Security → Third-party apps with account access → Celdaro → Remove Access.
Revocation is immediate and free. Local tokens are deleted and access is revoked at Google. No justification is required.
11. Limited Use Compliance
Celdaro fully complies with the Google API Services User Data Policy, including the Limited Use requirements:
- Google user data is used only to provide the functionality requested by the user
- Google user data is not sold to third parties
- Google user data is not used for advertising purposes
- Google user data is not used to train generalized AI models
- Google user data is not transferred to third parties except as necessary to provide user-requested functionality
- OAuth tokens are encrypted at rest (AES/Fernet)
- Multi-tenant architecture ensures data isolation by company
Celdaro's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.
12. Data Deletion
You can request complete deletion of your data at any time:
13. Contact
For any questions regarding how Celdaro uses Google data:
Have questions about how your Google data is used?
Contact us at support@celdaro.com and we will respond within 72 business hours.
This document was last updated on May 20, 2026. Previous versions are available upon request.