Privacy at Relay

What product usage events Relay collects

After you allow analytics, Relay records defined events such as a product page view, login attempt or completion, question submission, first answer completion, agent checks, synthesis completion, feedback, saving, sharing, and a return session. Events include random visitor and session identifiers, Relay’s internal user ID when signed in, the page path, sanitized campaign fields, referrer domain, related thread or request IDs when available, and tightly limited event properties.

Relay stores the first-party event log in its own application database. It is the source of truth for product metrics. Duplicate event IDs are ignored. Each event also carries an event timestamp and schema version so retries and future migrations can be handled safely. Relay does not use fingerprinting or collect device fingerprint attributes.

Authentication and account data

Relay uses Supabase Auth for email/password and Apple sign-in. Relay uses your internal account ID to associate your library and public contributions. Your email is used for account access and displayed in your account screen; it is never sent to product analytics. Passwords are submitted directly to Supabase Auth and are not written to Relay’s product-event or model-call databases.

Questions, answers, and AI providers

A question, imported answer, or follow-up is sent through Relay’s server to the AI provider selected for that request. Relay does not put prompt or response text in analytics or model operational logs. Unsaved requests are not intentionally persisted by Relay as user content. Questions and answers are stored when you explicitly save a private thread or publish a public thread.

AI providers process submitted content under their own terms. Relay requests non-persistent processing where the provider interface supports it, but does not make broader promises about a provider’s systems.

If you connect an AI client to Relay, the client can submit a question and answer only after you approve the connection. Each submitted answer review is saved as a private thread in your Relay library. You can deny the connection without changing your account.

Model-call operational metadata

For reliability and cost control, Relay records request and thread IDs, internal user ID when signed in, provider, model, task type, routing, token counts returned by the provider, latency, estimated cost when a verified price is configured, success or failure, normalized error code, retry count, and timestamp. These records do not contain prompts or generated answers. Estimated costs are estimates, not invoices.

Feedback

The two structured feedback choices and any optional text you submit are stored by Relay for product improvement. Optional feedback text is limited to 1,000 characters, rate-limited, and never forwarded to a third-party analytics provider. Feedback is optional and does not block continued use.

Third-party analytics

Relay supports an optional server-side PostHog connection. It is used only when a PostHog project is configured and you have allowed analytics. Only the same sanitized event taxonomy is forwarded. Relay does not use PostHog autocapture or session replay, and never forwards form contents, page text, emails, names, questions, answers, or authentication data.

Cookies and browser storage

Relay uses browser storage for your language, analytics preference, random visitor and session identifiers, temporary in-progress drafts, and Supabase authentication session. The browser session identifier is also used for anonymous usage limits and abuse prevention, even when optional analytics is declined. A random visitor identifier and your consent choice and timestamp remain on this device so Relay can honor that choice; declining clears campaign attribution and product-funnel progress while keeping authentication and security controls working.

Campaign and referral data

Relay accepts only utm_source, utm_medium, utm_campaign, and utm_content. Values are length-limited and character-validated. Relay stores only a referrer domain, never a full referrer URL that could contain sensitive query parameters.

Retention

Default retention is 30 days for anonymous product events, 180 days for authenticated product events, 90 days for model operational logs, and 180 days for optional feedback. These periods are configurable. Relay runs a daily cleanup procedure and provides an owner-only manual cleanup action. User-created threads are not removed by analytics cleanup.

Deletion requests

Automated account deletion is not yet available in the web product. To request deletion of your Relay account, stored threads, contributions, feedback, or associated analytics records, email relay.ai.info2026@gmail.com. Relay will confirm the account and scope before taking action.