Privacy Policy

Privacy contact

For questions about how Ramea handles your data, use the support and privacy channel on Contact.

Account and conversation data

Supabase Auth manages email/password authentication, sessions and optional multi-factor authentication. Ramea stores your account identifier and email, conversation titles and messages, branch relationships, model choices and preferences in PostgreSQL. Ramea does not store your account password. Your provider API key is encrypted at rest in the database and is not returned by the key-status API.

AI providers

When you send a message, Ramea sends your prompt, the ancestor messages on the selected path and your system instruction to OpenRouter and the selected upstream model provider. Sibling branches are excluded. Your stored OpenRouter key authenticates these server-side requests.

After the first successful exchange, a small excerpt of the first prompt is also sent through OpenRouter to a separate inexpensive model to name the conversation. No entire conversation is sent for title generation. Provider processing and retention depend on your OpenRouter account, routing and provider policies; Ramea does not promise that providers never retain data.

Browser storage and analytics

Authentication cookies support sessions. Local storage holds theme, preferences and active conversation/path identifiers; it does not persist chat content in the app settings stores. Optional Plausible analytics is disabled until the operator configures it and you accept. Events contain fixed usage names and validated campaign labels, not prompts, message text, conversation titles, account identifiers or authentication credentials. Your IP address and browser information are available to the analytics service as part of network requests. See Cookies and preferences.

Logs and service providers

Vercel and Render host the frontend and backend. Supabase and OpenRouter process data needed to run the service. Operational logs may contain request metadata. Application error reporting, when explicitly enabled, removes request bodies, authorization data and prompt/provider/database details. Optional analytics uses Plausible. Processing may occur outside your country under the the applicable provider terms. Contact the operator for retention and transfer details.

Retention and deletion

Saved conversations remain until you delete them. Delete a conversation from history, or remove your provider key in Settings. Temporary messages with a time limit are pruned on reads and periodic maintenance. The session option follows the backend server session: cleanup runs at startup and periodic maintenance, not immediately when your browser tab closes. Deleting a temporary parent may also remove its descendants.

Account deletion and data-access/export requests currently require operator assistance. Use the public request channel on Contact. Deletion from the live database does not necessarily remove copies held in hosting backups or by AI providers immediately. Contact the operator for the applicable retention schedule.

Your choices and rights

You can reject or withdraw optional analytics without losing access to Ramea. Depending on applicable law, you may request access, correction, deletion, restriction or portability of personal data, and complain to your supervisory authority. Use the Contact page to send these requests.