Privacy

How Avo handles your data

This policy explains what Avo collects, why it is processed, which services receive it, how long it is kept, and the choices available to you.

Last updated: July 27, 2026

Information We Collect

The information Avo handles depends on the features you use and the services you connect.

•Account and billing information: your name, email address, sign-in-provider identifiers, authentication metadata, subscription status, and payment status. Stripe processes payment-card details; Avo does not store full card numbers.
•Content you provide: notes, tasks, journal entries, documents, projects, calendar items, messages, files, images, videos, and other workspace content.
•Sensitive content you provide: Avo features can contain health, medication, mood, financial, location, household, and child-profile information. This content is not sold and is not used for advertising.
•Household and family details: Avo can save household facts you provide in conversation, including a child's first name, approximate age, or birthday, for enabled memory and family features. Kid profiles are created and managed by a parent. You can review, edit, delete, or ask Avo to forget saved details.
•Connected-service data: when you connect services such as Gmail or Google Calendar, Avo receives the authorized data and OAuth credentials needed to provide those features.
•Voice and AI data: prompts, relevant workspace context, generated outputs, voice transcripts, and generation media. Live voice microphone audio is handled as described below.
•Usage and diagnostic data: feature activity, subscription limits, generation counts, voice-session duration, device and browser details, error logs, and security signals used for reliability, billing, and abuse prevention.

How We Use Your Data

Avo processes data to operate the product and the features you enable.

•Provide and synchronize your account, workspace, connected services, generated media, and subscription features.
•Answer AI requests using your prompt and the workspace or connected-service context relevant to that request.
•Run enabled background features such as memory consolidation, pattern detection, digests, reminders, and proactive suggestions. These processes may use existing account content without a new prompt each time.
•Protect accounts and infrastructure, prevent abuse, troubleshoot failures, enforce limits, and comply with legal obligations.
•Measure aggregate or de-identified product activity to improve reliability and product decisions. Avo does not build advertising profiles.

Services That Receive Data

Avo does not sell personal information and does not use it for targeted advertising.

•Infrastructure and business operations: Google Cloud, Firebase, Vercel, and Stripe.
•Error monitoring: Sentry receives technical error context, browser and device details, and a sample of performance traces. When an error occurs, it may also record a replay of that session's interface activity. Sentry is not used for advertising or analytics profiling.
•Google features: Gemini, Gmail, Google Calendar, speech, Places, and Weather services receive the data needed for the feature you use.
•AI conversations and voice: OpenAI receives the prompts, conversation context, and audio needed for OpenAI-powered chat and Realtime voice sessions.
•Media generation: PiAPI and Seedance receive generation prompts and optional reference media.
•Search and information services: search, map, weather, food, and recipe providers—including Google Places—receive the request terms needed to return results. For weather and nearby-place requests, this includes your device location after browser permission; if you decline, Avo uses the home area in your settings. Avo does not store the coordinates from these requests.
•We may also disclose information when required by law, to protect users or the service, or as part of a corporate transaction subject to appropriate safeguards.

Connected Google Services

Connecting Google services is optional. Google shows the requested permissions before you authorize access.

•Gmail features cache only message metadata — message identifiers, sender details, labels, and timestamps. Subject lines, previews, and message bodies are deliberately not stored; they are fetched live from Google each time a feature needs them, such as displaying, summarizing, drafting, or answering a request about email.
•Authorized Gmail or Calendar content may be sent to Google Gemini when needed to provide an AI feature you request or enable. Avo does not use Google Workspace data for advertising, credit decisions, or training a general-purpose AI model.
•OAuth credentials are stored server-side so Avo can perform the connected features you authorize. Disconnecting Gmail revokes the connection and schedules its cached email data for removal.
•Human access to Google user data is restricted to cases where you give specific consent, access is needed for security or abuse investigation, the law requires it, or the data is aggregated and anonymized for internal operations.

Avo'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.

How we protect your data

Avo uses layered safeguards. No online service can promise absolute security, but these controls reduce common account, browser, and infrastructure risks.

Encryption

Data is encrypted in transit and protected by platform-managed encryption at rest

Account and access protection

Sign-in protections and authorization controls limit access to accounts and workspace data

Request and browser safeguards

Protected changes are validated, and browser and service controls reduce common web and abuse risks

Monitoring and engineering checks

Diagnostics, rate limits, automated tests, and security checks help detect failures and known risks

AI, Memory, and Personalization

Avo does not use your content to train its own shared AI models.

•Avo sends prompts and the relevant account or connected-service context to model providers when an AI or enabled background-personalization feature needs it.
•Avo uses paid Google Gemini API services. Google states that prompts and responses from paid services are not used to improve its products, but it may retain them for a limited period for abuse monitoring, security, or legal obligations.
•Conversation history and voice transcripts are stored in your Avo account and may be processed for enabled memory, summaries, patterns, and proactive features. Other providers follow their own retention terms; Avo limits what it sends to what the selected feature needs.

Live Voice and Audio

Live voice connects your device directly to OpenAI Realtime or Google Gemini Live, depending on the selected feature and provider availability.

•Avo issues a short-lived credential so your browser or mobile device can send microphone audio directly to the active voice provider. Raw microphone audio is not received or stored by Avo's servers.
•Avo stores the text transcript as chat history, where enabled memory and personalization features can use it like a typed conversation.
•Session resumption is enabled to make brief reconnects more reliable. For Gemini Live sessions, Google states that conversation state, which can include text, audio, and video, may be retained for up to 24 hours when session resumption is used.

Retention and Account Deletion

Different records have different retention periods. Provider safety logs, legal holds, and backups may follow separate schedules.

•Account and workspace content is generally retained while your account is active and the feature needs it, unless a shorter feature-specific period applies.
•Gmail cache records are scheduled for removal after 30 days and are purged when the Gmail connection is disconnected.
•Eligible expired Starter-account data is scheduled for cleanup after 120 days. Records needed for security, billing, legal compliance, or a different documented feature period may be retained longer.
•AI-generated image and video files are scheduled for removal after 60 days. Generation history and metadata can remain after the media file is removed.
•Account deletion has a 30-day grace period. The automated processor then removes registered Firestore data, the Firebase Authentication account, and stored files such as uploads, photos, profile and family images, generated media, and export archives.
•Feedback you submit, including its attachments, is retained as product signal after account deletion. Provider security logs, billing records, legal holds, and backups follow their own schedules.

Your Choices, Privacy Rights, and Contact

Control connected features, exercise applicable privacy rights, or ask a question about your data.

•Disconnect connected services to stop new access. Deleting a connection does not necessarily delete content you previously copied into another Avo feature.
•Review available memory, notification, and integration settings to limit future processing by those features.
•Request access, correction, export, restriction, objection, or deletion. Avo may need to verify your identity.
•Depending on where you live, privacy law may provide additional rights or a right to appeal a request decision. Avo will respond as required by applicable law.
•Browser settings can control optional cookies and local browser storage. Cookies required for authentication and security are necessary to operate signed-in sessions.

Submit requests from the email associated with your Avo account, or contact privacy@heyavo.ai.