Privacy Policy

This Privacy Policy explains what data Ryvon AI ("Ryvon", "we", "us") collects when you use the Ryvon platform at app.ryvon.ai ("the Service"), why we collect it, how it is stored, and the choices you have. It applies to every account type the Service offers: guest, email/password, and Google sign-in.

In short: we only access what you explicitly connect, we only use it to carry out the actions you ask for, we never sell your data, and we never use data read from your Google account to train AI models or to serve advertising.

1. Who we are

Ryvon AI is operated by the Ryvon AI team. For any privacy question, data request, or complaint, contact us at support@ryvon.ai — every request is handled personally, by a person, not a form.

2. Data we collect directly

• Account data — name, email address, and (for email/password accounts) a hashed password. If you sign in with Google, we receive your Google account's name, email address and profile photo.
• Workspace data — the workspace(s) you create or join, your role, and any teammates you invite.
• Content you create — chat messages, workflow definitions, call scripts, uploaded files and documents, and anything else you type into the Service.
• Usage and diagnostic data — pages visited, actions taken, error reports, and approximate performance timings, used to keep the Service working and to fix bugs.
• Billing data — if you subscribe to a paid plan, our payment processor (Stripe) handles your card details directly; we store only your subscription status, plan, and billing history, never your full card number.

3. Data from connected accounts (Google and other services)

Ryvon lets you connect third-party accounts so its AI and workflows can act on your behalf. We only request access to a service once you deliberately click "Connect" for it, and every connection can be removed at any time from Connectors in your workspace settings.

3.1 Google

When you connect a Google account, you choose which of the following Google scopes to grant. Each is requested only for the specific Ryvon feature it powers, and is never used for anything else:

• Gmail — read (gmail.readonly) and send (gmail.send). Feature: the Gmail connector in Chat and Workflows. Read access lets you ask Ryvon to find, open or summarize messages in your inbox; send access lets you ask Ryvon to draft or send an email. Ryvon only reads or sends a message when you directly ask it to, or when a workflow step you built and activated is configured to do so.
• Google Calendar (calendar). Feature: the Calendar connector. Lets you ask Ryvon to view your schedule, and to create, update or cancel events on your behalf.
• Google Sheets (spreadsheets). Feature: the Sheets connector. Lets you ask Ryvon to read data from a spreadsheet you point it at, or write results back into one.
• Google Drive — file scope only (drive.file). Feature: the Drive connector. This scope does not grant access to your Drive in general — only to files Ryvon itself creates, or that you explicitly open with Ryvon's file picker. Ryvon cannot list, browse or search the rest of your Drive.
• Google Analytics — read-only (analytics.readonly). Feature: the Analytics connector. Lets you ask Ryvon to read and summarize metrics from an Analytics property you have access to.
• Basic profile and email (userinfo.profile, userinfo.email). Used only to identify your Google account and show your name and photo in the Service.

Ryvon's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. Concretely, that means Google user data accessed through Ryvon:

• is used only to provide or improve the specific, user-facing Ryvon feature you invoked it for;
• is never sold, rented, or transferred to data brokers or advertisers;
• is never used to serve advertising of any kind, in Ryvon or elsewhere;
• is never used to train, retrain, or fine-tune general-purpose or third-party AI/ML models;
• is only shown to you (the account holder) and, transiently, to the specific AI model call that carries out the single request you made, never to any other user or workspace member unless you shared it yourself;
• is only accessed by Ryvon's own systems performing the action you requested — no Ryvon employee reads your Google data as a matter of course, only when you ask for support and only with your involvement.

3.2 Other connectors

Ryvon supports optional connections to a range of other services, each used only for the actions you configure: Slack, Microsoft 365 (Outlook, Teams), Notion, HubSpot, Salesforce, Zoho CRM, Pipedrive, Twilio (SMS and voice), WhatsApp, Instagram and Facebook (via Meta), Discord, GitHub, GitLab, Trello, Asana, Monday.com, Jira, Mailchimp, Calendly, Cal.com, Zoom, LinkedIn, Zendesk, Freshdesk, Webflow, Dropbox, Airtable, Apollo.io, Stripe, Intercom, and connection to your own email account via SMTP/IMAP. Each connector accesses only the categories of data (for example, contacts, tickets, or messages) needed for the actions available for that connector, and only when you have connected it.

4. How we store connected-account credentials

Access tokens and refresh tokens for every connected account are encrypted at rest (AES-256-GCM) before being written to our database, and are decrypted only in memory, at the moment a request needs them, to call that service's API on your behalf. Disconnecting a connector deletes its stored credentials.

5. AI processing

To answer questions, run workflows, and power the voice call agent, Ryvon sends the relevant parts of your request — and, where a step requires it, data read from a connected account — to the AI provider currently configured for that feature (which may include Anthropic, OpenAI, or Google's Gemini models), and, for voice, to our voice infrastructure providers (Vapi and ElevenLabs) and telephony provider (Twilio). These providers process the data solely to generate the response or perform the call, under their own data-processing terms, and Ryvon does not permit them to use your data to train models for other customers.

6. Where your data is stored

Application data is stored in a managed PostgreSQL database (Neon). Transactional email (for example, sign-up confirmations) is sent through Resend. Error and performance monitoring, where enabled, is handled by Sentry. None of these providers may use your data for any purpose other than providing their service to Ryvon.

7. Cookies

Ryvon uses a session cookie to keep you signed in and a small cookie to remember which workspace you last used. We do not use third-party advertising or tracking cookies.

8. Your choices and rights

• Disconnect a connector at any time from Connectors in workspace settings — this immediately deletes the stored credentials for that connection.
• Export or delete your account by contacting support@ryvon.ai; we will delete your account data, including connector credentials, within a reasonable time of a verified request, except where we are required to retain records by law (for example, billing records).
• Access or correct your account information from your workspace settings, or by asking us directly.
• If you are in the UK, EU, or another jurisdiction with its own data-protection law, you may have additional rights under that law; contact us and we will honour them.

9. Data retention

We keep account and workspace data for as long as your account is active. Connector credentials are kept only while a connector is connected and are deleted immediately on disconnect. Call recordings and transcripts are kept only as long as needed for the purpose you created them for, or until you delete them.

10. Children

The Service is not directed at, and we do not knowingly collect data from, anyone under 16.

11. Changes to this policy

If we make a material change to this policy, we will update the effective date above and, where appropriate, notify account holders directly.

12. Contact

Questions about this policy or your data: support@ryvon.ai.