Privacy at a glance
This page explains privacy across outrun.to, the Outrun API, dashboard and Telegram bot.
Playground text chats are temporary by default. Saved only when you choose. Outrun does not retain temporary text-chat content. We keep limited account, billing, security and content-free usage records. AI-provider retention rules are separate.
“Content” means messages, prompts, responses, uploads and generated content. Media, Workspace, Telegram, support and connected apps have different storage behavior, described below.
Temporary chats and optional history
New Playground text conversations and model comparisons start with Save chat history off. Active content stays in browser memory while needed; Outrun processes it to answer without saving a transcript, title or summary. Refreshing or closing the page clears the conversation from the Playground. Outrun cannot restore it.
Turning saving on asks you to confirm before the current conversation and future messages are stored. Saved entries can be reopened or deleted in Your history. New conversations still start as temporary. Starting a temporary chat does not delete an existing saved copy.
Saved conversations and inline images are encrypted at rest using keys managed by Outrun. Outrun processes readable content to provide the features you request. This is different from end-to-end encryption.
Information we keep and why
We keep account and sign-in identifiers, preferences and session/security records to operate accounts; model, request/job ID, time, token counts, status and charges for billing and reliability; and payment/invoice, credit and redemption records for purchases and accounting. Payment services handle their own payment details.
- Temporary text chats and comparisons: no persistent Outrun transcript or content-derived history.
- Optional saved text history: retained in your account until deleted from active history.
- Media and Workspace: require saving consent. Media jobs can retain prompts, settings, results and delivery files; Workspace saves conversation and tool history.
- Telegram and support: Telegram processes bot interactions; bot account and generation records are separate from temporary Playground chats. Support submissions and attachments are retained to answer your request.
Direct API text calls are not added to account chat history. The docs Playground keeps text in memory and recent media on your device. Other apps can save their own copies.
Privacy across every model
No content in request logs
Outrun’s no-content-logging standard applies to every model. We keep prompts, responses, uploads and raw provider error bodies out of operational request logs.
Temporary Playground text chats are not saved. Saving text history is optional; media and Workspace use separate storage features. Essential account, billing and security records are kept to run the service.
AI providers process requests under their own retention policies. ZDR means zero data retention; a ZDR badge identifies an extra provider routing control. Provider audit exceptions still apply, including records that can represent generated text for up to 30 days.
Deletion, retention and security
Deleting an entry removes it and stored image previews from active history. It does not cancel submitted work, reverse charges or immediately remove backup, legacy-log or processor-held copies. This change does not erase existing history or historical content-bearing records.
Media links may expire. We keep the account, payment, billing, security and support records needed to run the service, track credit, resolve payment issues and protect accounts. Backups have separate retention schedules.
Essential cookies support sessions and security. Access controls and encryption help protect stored information, but no system guarantees absolute security. Keep credentials private and replace exposed keys.
Website analytics
We use PostHog in the United States to understand page journeys, referral domains, campaign source/medium/name and selected product actions, such as model selection and clicks to add balance or create a key. We use a random browser identifier and, when signed in, your Outrun account reference to connect these events. We do not send your name, email, prompts, responses, API keys, payment details, support messages or full URLs with queries or fragments to analytics. Session replay and automatic page-content capture are disabled.
Website analytics starts automatically when you visit, including before sign-in, unless you have turned it off or your browser privacy signal disables it. Visits are anonymous until sign-in; signed-in activity is linked using your Outrun account reference. We store the analytics setting and a random visitor identifier on this browser. You can turn analytics off at any time in Preferences under Privacy & account or using the control below; your account remains available. We respect Global Privacy Control and Do Not Track browser signals. PostHog receives connection information needed to process analytics requests. See PostHog’s privacy notice.
Questions and support
Have a question about privacy or your data? Message Outrun support. Keep your API keys and prepaid codes private.
Outrun is for adults aged 18 or older. Contact support about children’s information. We update this page as features change.