Privacy Policy

Last updated: 11 July 2026

Relay (“we”, “us”) is an AI attention layer for Gmail operated by PlayFusion Technologies. This policy explains what Google user data we access, how we use it, who we share it with, how we protect it, and how long we keep it.

Google Limited Use compliance

Relay’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.

The use of raw or derived user data received from Workspace APIs (including Gmail and Google Calendar) will adhere to the Google User Data Policy, including the Limited Use requirements. We do not use Google user data to develop, improve, or train generalized AI and/or ML models. We do not sell Google user data or transfer it to third parties for advertising, data brokerage, or creditworthiness purposes.

Data access — what Google user data we access

Raw Google user data:

• Gmail (gmail.readonly): message metadata (subject, sender, recipients, dates, labels), snippets, and message bodies needed to sync your inbox and power attention features
• Gmail (gmail.compose): ability to create and send email only when you explicitly tap Send on a reply or AI draft
• Google Calendar (calendar.events): ability to create calendar events only when you explicitly tap Add to Calendar for a detected deadline
• Sign-in (openid, email, profile): your Google account email, name, and profile identifier for authentication

Aggregated / anonymized data:

• Operational metrics such as sync success rates, AI feature usage counts, and error rates — without message content

How our application uses Google user data

• Authenticate you and link your Gmail account to Relay
• Sync and display your inbox on your device
• Categorize mail into attention queues (Needs Response, Waiting On Me, Newsletters, etc.)
• Generate AI summaries and draft replies when you request them
• Create calendar events when you request them
• Provide customer support when you contact us
• Improve reliability and security of Relay’s user-facing features

We do not use Google user data for targeted advertising, selling ads, credit scoring, surveillance, or any purpose unrelated to providing or improving Relay’s user-facing features.

With whom we share, transfer, or disclose Google user data

We share Google user data only with processors needed to run Relay:

• Google — Gmail, Sign-In, Calendar, Firebase Cloud Messaging
• OpenRouter — LLM inference for categorization, summaries, and drafts. We send minimal excerpts (subject, sender domain, short snippets / selected text). OpenRouter is used only to generate outputs for your account; we do not authorize use of your Gmail data to train generalized AI/ML models
• Hostinger — application and database hosting
• RevenueCat / Google Play — subscription status only (not Gmail content)

We do not sell Google user data. We do not transfer it to data brokers, advertisers, or AI providers for model training beyond providing the feature you requested.

Data protection mechanisms for sensitive Google user data

• OAuth refresh tokens encrypted at rest
• TLS for data in transit
• Full message bodies stored primarily in an encrypted cache on your device
• Privacy Shield blocks sensitive mail (password resets, OTPs, auth codes) from AI processing
• Admin console never exposes email bodies, AI summaries, or drafts
• Access controls, rate limits, and audit logging on the API

Data retention & deletion

• On our servers: account profile, encrypted OAuth tokens, and email metadata for attention feeds. Full message bodies are not retained in our database; they may pass through server memory briefly during sync and are cleared after delivery to your device
• On your device: encrypted local mail body cache and AI outputs you generate
• Retention window: metadata outside your analysis window is purged by scheduled cleanup jobs
• Deletion: disconnect Gmail or delete your account in Settings, or email hello@tryrelay.in. Sign-out clears the local encrypted body cache

What we store on our servers

• Account profile (email, display name, plan settings)
• Gmail account linkage and encrypted OAuth refresh token
• Email metadata for attention feeds (labels, priority, deadlines, waiting flags)
• Message envelope fields (subject, sender, recipients, snippet) — not full message bodies

What stays on your device

• Session token in secure storage
• App preferences (theme, onboarding state)
• Encrypted local mail body cache for messages synced on that device
• AI summary and draft outputs after you generate them

AI processing

Relay uses OpenRouter for AI features you explicitly request (summaries, drafts) and for categorization when enabled. We send minimal excerpts — subject, sender domain, and short snippets — not full bodies for sensitive categories. Password resets, OTPs, and verification codes are blocked from AI processing. AI is used only to provide features in your Relay account; it is not used to train generalized models on your Gmail data.

Your controls

• Disable AI categorization or AI dashboard briefing in Settings
• Disconnect Gmail at any time
• Delete all Relay data from the app
• Clear local encrypted body cache on sign-out

Contact & deletion

Questions or deletion requests: hello@tryrelay.in. You can also delete your account in the Relay app under Settings. Account deletion page: tryrelay.in/delete-account.html.