NanoGPT Privacy Policy
Last Updated: November 17, 2026
NanoGPT LLC ("NanoGPT," "we," "us," or "our") values your privacy and is committed to taking reasonable steps to protect your personal information. We aim to limit the information we collect and store to what is reasonably needed to provide and operate our Services, as described in this Privacy Policy.
This Privacy Policy describes our practices regarding information we collect from or about you when you use our website, platform, services, and features, including all associated software applications (collectively, "Services").
You may request a copy of a prior Privacy Policy at support@nano-gpt.com.
Scope
This Privacy Policy applies to personal information collected through:
- Our website and any webpages that link to this Privacy Policy;
- Our applications, features, and services (including APIs) that link to this Privacy Policy;
- Interactions with third-party sites or services where our Services are embedded and link to this Privacy Policy.
Capitalized terms not defined in this Privacy Policy have the meanings given in our Terms of Service.
NanoGPT determines how account, billing, security, support, and service-administration information is used. Where we process personal information on a business customer's behalf and instructions, our role and the customer's role depend on the processing involved and any applicable data-processing agreement. That customer may also provide a privacy notice. These arrangements do not remove our responsibilities under applicable law.
Personal information we collect
We collect personal information as described below when you use our Services, communicate with us, or create an account. NanoGPT does not train models on your Input or Output, sell your Content, or use your Content for advertising. NanoGPT no longer loads advertising pixels or sends advertising conversion events. See Your privacy choices and Your rights and requests below.
- Account Information: If you choose to create an account, we collect your email address, and may also store your name, profile image, a hashed version of your password, passkey (WebAuthn) credential handles, and two-factor authentication settings. This information is necessary to provide login, authentication, and account security features. You can also use our services without creating an account by using an anonymous session. We support multiple authentication methods, including email and password, Google OAuth, GitHub OAuth, and WebAuthn/passkeys. When you sign in via Google or GitHub, we receive limited profile information (such as your name, email, and profile image) from those providers in accordance with their privacy policies.
- Payment Information: When you make payments, we use third-party payment processors. For credit or debit card payments we use Stripe as our payment processor. We do not receive or store your full payment card details. Stripe collects and stores certain personal information related to your payment transactions. Account deletion includes an attempt to delete the associated Stripe customer records, but this does not erase every payment record: Stripe may retain transaction and other information for its independent purposes and legal obligations. Contact us about information we hold or control. You can also contact Stripe about its independent processing through its data deletion request page. For cryptocurrency or other payment methods, we may use processors and swap services such as BTCPay Server, Nanswap, or THORChain; these providers may collect and process transaction details (such as wallet addresses, transaction identifiers, and amounts) under their own privacy policies. We receive limited transaction metadata to credit your account. To confirm cryptocurrency payments and to screen them for sanctions, we look up the transaction identifiers and wallet addresses involved with public blockchain nodes and block explorers, which see those lookups. For API payments made with the x402 protocol, signed payments in USDC on Base, or in USDC or USDT on Solana, are verified and settled through a payment facilitator (Coinbase by default), which receives the payment details, including the paying wallet address. Direct USDC transfers on Base and Nano payments are verified by us, and Lightning payments through BTCPay Server.
- Communication Information: If you communicate with us, we may collect your name, contact information, and the contents of your messages to the extent that you choose to share these details with us.
- Social Media Information: When you interact with our pages on third-party sites like X and Discord, we may collect information you choose to provide, such as your contact details.
Information Related to Your Use of the Services
We aim to minimize data collection and limit the use of IP addresses, as described below:
- Prompts and Conversations: By default, we do NOT store prompt or conversation content on our servers. If you enable optional features such as conversation sync or sharing, we store the necessary content (encrypted where applicable) so those features can work.
- Optional API Request Logging and Support Debugging: API-key owners may opt in to encrypted storage of new /v1/chat/completions request and response bodies in private object storage. Logs expire after a selected period of 1 to 30 days, become unavailable through the log-access tools, and are scheduled for deletion. The database retains the associated ownership, consent, request metadata, expiry, encryption reference, and opaque object key rather than the captured body. These private request logs are off by default and are available to the API-key owner. A separate, off-by-default setting allows authorized NanoGPT staff to inspect only logs captured while that support-access setting is enabled for debugging and support. This permission does not authorize model training or general product-improvement use. Turning support access off revokes further staff access through our support tools without clearing the logs from the owner's account. Support access is recorded in an audit log. Disabling request logging or clearing logs removes them from active access and initiates deletion of the stored payloads. Physical deletion may occur later as cleanup processes run or retry a failed storage operation.
- Responses API: Our OpenAI-compatible Responses API can store request and response data encrypted (AES-256-GCM) to support conversation threading, response retrieval, and background processing. Storage is off by default for ordinary requests; background processing requires storage. When storage is enabled, records expire after 7 days by default. Expired records become unavailable through the Responses API and are scheduled for deletion by our cleanup processes. Physical deletion may occur after expiration as those processes run. You can set the store parameter to false to disable local Responses API storage for a request. When storage is enabled, retention is configurable per request with retentionDays or retention_days from 0 to 365 days; setting retention to 0 disables retention for that request. User and team default retention settings are also available through API endpoints. See the Responses API retention documentation for the exact request fields and settings APIs. You may also provide your own encryption key (via the X-Encryption-Key header) for customer-managed encryption at rest. This key is provided with API requests and used server-side to encrypt/decrypt stored responses, and is not persisted by us.
- Optional PII Redaction: If you enable PII redaction, you choose one of two redaction providers, Tinfoil or Grepture. This feature is for private information inside prompts, messages, context, and responses; we do not attach your NanoGPT account name, email, or raw account or session identifier as account metadata to model-provider requests. Redaction does not remove the stable identifier described below. Redaction is designed to detect and mask supported PII categories, but may not identify every sensitive detail.
- Tinfoil: We send the text of your request to Tinfoil's PII filter, which runs in a hardware-attested secure enclave. Before sending, we verify the enclave's attestation and encrypt the text so that only the verified filter can read it. The filter returns where personal information appears; we replace those values with placeholders before memory, web search, other NanoGPT features, and the model provider receive the request, and we restore the placeholders in the response before returning it to you. In web chat's on-device mode, your browser performs these steps and NanoGPT only relays the encrypted text to the filter. We keep the link between placeholders and original values only while the request is processed. So that unchanged text is not scanned again, we keep for up to three days a record of where personal information was found in a text, stored under a keyed hash of that text; the record holds positions and categories only, not the text or the values. Tinfoil processes the text under the Tinfoil Privacy Policy. Requests to Responses API routes that need the model provider's built-in tools are redacted through Grepture even when Tinfoil is chosen.
- Grepture: We route the request and response content sent to the model provider through Grepture, which masks supported PII categories before the provider receives the request and restores them before the response returns to you. Memory, web search, and other NanoGPT features receive your original content. Grepture receives the request and response content necessary to detect, mask, and restore supported PII categories, and may process operational metadata and traffic-log data as described in Grepture's Privacy Policy. Grepture's subprocessors are listed on its Subprocessors page, and further company information is available in Grepture's Impressum.
- Memory & Global Memory Sync: Memory is disabled by default. If enabled, Global Memory items are stored in your browser until you explicitly enable sync. Recoverable sync encrypts stored snapshots but NanoGPT infrastructure can decrypt them; it is not zero-knowledge. Passphrase mode encrypts snapshots in your browser before upload, and NanoGPT cannot read or recover those contents. You can view, edit, disable, delete, or clear memory. The default remote suggestion analyzer uses a TEE-backed provider route, but your browser sends the analyzed excerpts to NanoGPT in plaintext before NanoGPT forwards them; this is not browser-to-enclave Private Mode. A custom remote analyzer may not use a TEE. The optional local browser analyzer keeps analysis on the device, but saved memory may still be sent to the chat model when Memory is used. Saved items remain stored until you delete or clear them; disabled or expired items are excluded from active use but may remain stored. Capacity is configurable in Memory settings.
- Context Memory: Context Memory is a separate feature for long chats, run by a third party, PolyChat. Its per-chat setting is off by default. When it is on for a chat, we send conversation text to PolyChat with each eligible message once the chat reaches about 10,000 tokens; an active tool exchange may be held back until a later turn. Images, audio and other binary attachment parts are excluded, but text extracted from attached files (such as a PDF) and their filenames are sent as conversation text, along with other text included in messages, such as system or character instructions, search and tool results, code output, and reasoning embedded in message text. PolyChat builds a memory of the conversation and, when the chat is too long for the model, returns a shortened version that we send to the model instead. When a stable conversation ID and account information are available, we also send a keyed, one-way identifier made for that one chat, so that its memory can be viewed and deleted later. The identifier itself does not contain your name, email, or account ID, and does not link your chats to each other; conversation text may still identify you. PolyChat keeps the memory for the retention period set for the chat (30 days by default; you can choose 1 to 365 days) and processes it under the PolyChat Privacy Policy. You turn Context Memory on or off per chat in web chat, where a new chat starts with the choice you made last, or per request in the API. When you delete a chat that used Context Memory from all your devices, or delete your account, we ask PolyChat to delete the memories of your chats. Memory we cannot match to a chat, such as memory from API requests sent without a conversation ID, is not covered by that request and expires at the end of its retention period, as does any memory whose deletion request fails. Context Memory is refused on requests that require Zero Data Retention or EU-only processing, and it is not used in Private Mode. For very long chats on some models that are covered by a subscription, we may use Context Memory ourselves, at no charge to you, without you turning it on; this does not happen for requests that require Zero Data Retention or EU-only processing, in Private Mode, or with your own provider key.
- Previously Imported Google Drive Files: Google Drive import has been retired. Files previously imported may remain in your local library, NanoGPT-managed object storage, or your configured Bring Your Own Storage bucket. No single maximum retention period applies to these stored copies. Removing an item from your local library or deleting your account does not necessarily delete the remote object immediately; content in your own bucket remains subject to the storage lifecycle you configure.
- AI Detection and Plagiarism Checks: If you use our AI detection or plagiarism checking features, we send the text, image or video you submit to the detection provider that runs the check (Sapling for Standard text checks, Pangram for all other checks) so it can return a result. Images and videos you upload, and videos you check by link, are first copied to temporary NanoGPT storage; we remove them when the check finishes and permanently delete them within about two hours, including when the check never runs. Images you check by link are downloaded for the check and not stored. Your recent checks are saved only in your browser. Each provider processes what you submit under its own privacy policy and terms.
- CAPTCHA Verification: We use Cloudflare Turnstile to check that a request comes from a person and not a bot, at points where automated abuse is likely. These currently include starting to use NanoGPT without an account, requesting an email sign-in code, and starting a card payment with a card that is not already saved. The check runs in your browser and is loaded from Cloudflare, so Cloudflare may process your IP address and browser information as part of this verification. This data is subject to Cloudflare's Privacy Policy.
- Last Use of Your Account: When you use your account, signed in or with an API key, we record the time. We keep one such time per account, replaced each time you use it, for up to 120 days, and use it to tell whether an account is still in use. It is deleted with your account.
- IP Addresses: Our hosting and security systems necessarily process your IP address when you connect. NanoGPT does not attach IP addresses to prompts, model-provider requests, usage records, support tickets, or bug reports. Our application uses raw IP addresses temporarily in rate-limit and abuse-prevention systems, where they are automatically deleted after the relevant security window expires. Retention varies by control, and we do not publish individual thresholds because doing so could weaken those protections. Some keyed or one-way identifiers derived from an IP address are also kept as separate security records, for password-reset protection, payment-fraud prevention, counting character launches only once, and diagnosing failed sign-ins. These records have their own retention, so the end of a rate-limit window does not by itself remove them. We do not intentionally write raw IP addresses into application log messages. Our hosting providers, Vercel and Fly.io (which runs part of our API, including api.nano-gpt.com, and some background services), separately process network information such as IP addresses under their own privacy policies: Vercel's Privacy Policy and Fly.io's Privacy Statement. Their retention of those infrastructure records is set by them, so we do not claim a fixed duration for their independent processing.
- Stable Model Provider Identifiers: When you use OpenAI, Meta, Anthropic or Google Gemini models, most routes send the model provider a stable hashed account or session identifier for safety and abuse prevention, and some routes for other models do too. This identifier can associate requests from the same account or session. You can turn it off in your privacy settings. See Stable identifiers sent to model providers below.
- Usage Data: We do not attach IP addresses to model-usage records such as token counts, models, charges, and timestamps. Our hosting and security systems process IP addresses as described above.
Image, Audio, Video, and Potential Biometric Processing
Some models accept or generate images, audio, or video and may perform processing that is regulated as biometric processing in some jurisdictions. Depending on the model and feature, this may include voice cloning or voice conversion, speaker identification, voice-preserving translation, face cloning, face transformation, or analysis of facial or vocal characteristics. A Model Provider may extract or generate data such as voiceprints, voice models, face geometry, or faceprints to fulfill the request.
When you use these features, NanoGPT transmits the media and related instructions to the Model Provider selected for the request. The Model Provider's handling, retention, and use of that data is governed by its own terms and privacy practices. NanoGPT's own storage of submitted or generated media follows the feature-specific storage and retention practices described in this Privacy Policy, including optional storage, sharing, sync, and Responses API features.
NanoGPT does not itself sell submitted media or biometric data and does not use them to train models. Any separate rights or practices of a Model Provider are governed by that provider's terms and privacy policy.
If media contains another identifiable person, you must provide any legally required notice and obtain all rights, permissions, consents, and other lawful bases required to submit the media and use the selected feature. You must not submit another person's image, likeness, or voice for cloning, identification, or other biometric processing without that person's informed consent where consent is required by law.
We may collect limited product telemetry (for example, how often certain interface features are used, such as chat tools) to evaluate feature usefulness and improve the service. For this telemetry, we use an in-house first-party system rather than third-party analytics tools for privacy reasons. Some of these product events are linked to your account. Product events are kept for 90 days and then deleted, and events linked to your account are deleted when you delete your account. This telemetry does not include message content.
Separately, our hosting provider Vercel measures how fast pages load (Vercel Speed Insights). For each measurement, Vercel receives the timing, the kind of page you are on, with chat names, share and invitation codes, and query strings removed, and the network information described under IP Addresses above. A measurement also names the part of the page it refers to, and on a chat page that name can include the text of a heading from a reply.
NanoGPT has retired advertising pixels, Google Tag Manager, and advertising conversion reporting. Our Advertising Policy explains this change.
For model-usage records, we store request metadata such as input and output token counts, the model used, charges, discounts, whether web search or memory was used for billing, and the request timestamp. These records power the Usage page. Account, payment, security, support, telemetry, and optional content-storage information is handled as described elsewhere in this Privacy Policy.
Our platform uses your local browser storage to hold settings and conversation history. We also use a session cookie that contains a signed session identifier (and optional security flags, such as pending 2FA) so we can retrieve your session and balance from our servers. If you arrive via a referral or campaign link, we may set a referral/source cookie to attribute signups or payments. If you enable conversation sync, we store snapshots using your selected encryption mode in our cloud storage or your own configured storage. Passkey and passphrase modes encrypt snapshots in your browser before upload; access to those stored snapshots requires your encryption credentials or a supported recovery method. Convenience mode uses encryption managed by NanoGPT, and our infrastructure can decrypt those snapshots to restore your chats. These protections concern stored snapshots; content you use in model requests is still processed as described above. You can use the available controls to delete synced snapshots. If you share a conversation, we store a share snapshot, encrypted if you choose, for the retention period you select so the link can work.
How we use personal information
We use the personal information described in this Privacy Policy, including information you provide, information received from sign-in or payment providers, and information generated through your use of the Services, for the following purposes:
- To provide, operate, and troubleshoot the Services, including authentication and session management;
- To process your payments and update your account balance;
- To provide optional features you enable, such as sync, sharing, memory, request logging, and integrations;
- To communicate with you about our Services and events, including account, service, and security notices;
- To send new account holders up to four getting-started emails over about two weeks, which you can stop at any time with the unsubscribe link. We record clicks on links in these emails, and whether you use the Services afterwards, to decide whether to send the later emails and to measure whether they are useful. To choose which tips to send, we also use counts of which features you have used, such as how many images you have generated or whether you have used the API, never the content of your prompts or chats. We do not use tracking pixels or record email opens;
- To review, route, and respond to support requests, bug reports, and suggestions you submit;
- To understand feature usage and improve the Services using the limited first-party telemetry described above, which excludes message content;
- To help prevent fraud, unlawful activity, abuse, and misuse of the Services, and to support the security and integrity of our systems;
- To detect, prevent, and investigate violations of our Terms of Service, including by automatically screening the text prompts of image and video generation requests for prohibited content such as sexual content involving minors;
- To comply with legal obligations and protect our rights, privacy, safety, or property, and/or that of our affiliates, you, or other third parties.
Legal bases where required
Where data protection law requires a legal basis, we rely on performance of a contract for processing necessary to provide the Services you request, such as account access, payments, and processing your requests. We rely on legitimate interests for proportionate security and abuse prevention, fraud prevention, service reliability, support, limited product telemetry, and getting-started emails to account holders, subject to balancing those interests against your rights. We rely on consent for optional ad-source measurement and other processing that requires consent, and on compliance with legal obligations where the law requires processing or retention. Enabling a feature does not by itself establish a lawful basis for every use of someone else's personal information.
Disclosure of personal information
We disclose personal information to the service providers and other recipients described throughout this Privacy Policy for the purposes explained here, including hosting, storage, email delivery, payments, security, support, and the features you use. Service providers that operate automated moderation tools for us process the text being screened in order to detect and prevent violations of our Terms of Service. The following sections provide more detail:
- Service Providers: When you submit a prompt, it is passed to the provider that serves your request (such as OpenAI, Anthropic, Sakana AI, or another LLM provider), in some cases through a gateway as described under Routing and fallbacks below. While we do not store prompt or conversation content by default (unless you enable optional features like conversation sync or sharing), these service providers may store and process this information according to their own privacy policies. If you provide personal information within the prompts that you send, these service providers will have access to this personal information. We make reasonable efforts to minimize provider retention and support deletion through the settings each provider makes available to us. Providers operate their own infrastructure, and their handling of data remains subject to their own practices, policies, and legal obligations. For credit card processing, we use Stripe, which collects and processes payment information according to their own privacy policy.
- Routing and fallbacks: Many models are offered by more than one provider. We choose which provider serves each request, and if that provider is unavailable or returns an error, we may retry with another provider of the same model. The provider that serves a request can therefore differ from the model's usual provider and can change between requests. Some routes go through a gateway, which either runs the model itself or passes your request on to another company that does. OpenRouter, Amazon Bedrock and Microsoft Azure are some examples of the gateways we use; this is not a complete list. When a gateway passes your request on, both the gateway and that company process it. Your privacy settings apply to every attempt, including fallbacks. If you require Zero Data Retention, we send text-model requests only along routes we classify as Zero Data Retention, covering both the gateway and the company behind it. If no such route is available, the request fails rather than going to another provider. This classification relies on each provider's own commitments, as described below. Zero Data Retention does not apply to image, video, audio or 3D generation: those requests still run when you require Zero Data Retention, and the providers that serve them may store your prompts, input media and outputs.
- EngyAI: When requests are routed through EngyAI, your prompts, conversation context, and outputs are processed through its inference service. Its handling of this information is subject to the EngyAI privacy policy and EngyAI terms of service.
- Aoru: When requests are routed through Aoru, it processes your prompts, conversation context, and outputs for inference, including automated prompt moderation. Aoru's privacy policy states that inputs and outputs are processed in memory, discarded when the request completes, and not used to train, fine-tune, or evaluate models. It retains content-free usage metadata and security/access logs for up to 60 days; billing and support records have separate retention periods. Its policy also permits sharing generated search queries with a search provider when Aoru's web search tool is invoked. NanoGPT relies on these provider statements and does not independently verify Aoru's internal processing or retention. See the Aoru privacy policy and Aoru terms of service.
- Astorias: Astorias publishes zero retention and no training for inference prompts and outputs, subject to legal, abuse, and security exceptions. Account, billing, and operational metadata may be retained. Astorias supports automatic prompt caching, and cross-request cache hits have been observed; its published request-only KV lifetime wording does not establish a cache retention period. Inference location has not been verified. See the Astorias privacy policy.
- TokenWatt: When requests are routed through TokenWatt, your prompts, conversation context, tool definitions, and outputs are processed in memory on GPU servers in US data centers to serve the request. TokenWatt states, and confirmed to us in writing, that prompts and completions are not stored, not logged, and not used for training. It keeps request metadata (request IDs, timestamps, model, status, token counts and latency) for 30 days. See the TokenWatt privacy policy.
- UncensuredAI: When requests are routed through UncensuredAI, it processes your prompts, conversation context, and outputs for inference. UncensuredAI’s signed zero data retention statement dated 16 November 2026 covers all processors, including reserve and fallback routing: prompts and completions are not stored, logged or used for training. Only operational and billing metadata, such as request identifiers and token counts, is retained. See the UncensuredAI privacy policy.
- Hyperresearch (Ousia 1): When you use Ousia 1, your prompts, conversation context, and outputs are sent to Hyperresearch, which researches your question on the web and answers with cited sources. Searches based on your question are sent to search providers, some of which may use them to improve their services. Since November 14, 2026, Hyperresearch deletes the question and answer of requests it receives through NanoGPT 1 day after each request settles. Its subprocessors for these requests are Cloudflare, OpenRouter (which passes model requests to Anthropic), and the search providers Parallel, Exa, Valyu, and Firecrawl. NanoGPT does not classify Hyperresearch as zero data retention, and requests that require zero data retention or EU-only processing are not routed to it. See the Hyperresearch privacy policy and terms of service.
- CoralBricks (Coral Bricks AI Inc.): When your request is routed through CoralBricks, including when you select it, your prompts, conversation context, images, tool-call content, and outputs are sent to CoralBricks for inference. Its policy states that customer content is not used for model training, fine-tuning, or model improvement. NanoGPT's CoralBricks organization is set to zero data retention for both content and metadata: your prompts, outputs, tool-call arguments, model settings, and request headers are not stored. Its prompt cache is temporary in-memory storage, and NanoGPT sends a hashed, user-specific cache namespace to separate prefix caches. Operational data (model, endpoint, token counts, timings, status, and billing records) is retained, and the requesting IP address may be kept in security logs to prevent fraud and abuse. Processing may occur in the United States and other jurisdictions. This classification applies to NanoGPT's CoralBricks account. See the CoralBricks privacy policy and terms of service.
- Gonka24: Gonka24 is an independent broker that may process your prompts, conversation context, and outputs through the Gonka inference network and other providers. Its routes do not offer guaranteed zero data retention. Gonka24 retains data for operational, security, billing, and legal purposes without a fixed retention period. Its policy excludes training its own models on customer content by default, but third-party providers have separate policies. See the Gonka24 privacy policy and Gonka24 terms of service.
- LongCat (Meituan): When you select a model routed directly through LongCat, LongCat processes your prompts, conversation context, and outputs. This direct route is not classified as Zero Data Retention. LongCat's published terms permit use of inputs and outputs for service improvement, brand promotion, and marketing; restrictions on use for model training or improvement require a separate written arrangement. LongCat's privacy policy permits retention as reasonably necessary for its stated purposes. NanoGPT has not verified a separate no-retention or no-training arrangement for this route. See the LongCat privacy policy and LongCat platform terms.
- Hyperfusion: When you select Hyperfusion, it processes your prompts, conversation context, and outputs on its own infrastructure in Dubai, United Arab Emirates. Hyperfusion has confirmed to NanoGPT that prompts and outputs are not recorded, monitored, or used for model training, and that inference for these UAE-hosted endpoints is handled in-house. Temporary inference caching may occur in memory; Hyperfusion states that this cache can be disabled by the provider. We do not represent that caching is disabled for every request. Hyperfusion retains request metadata, including time, size, and target model, for 30 days for billing and fraud investigation. Our zero data retention classification for Hyperfusion refers to its prompt and output retention commitment; it does not exclude temporary memory caching or retention of this metadata. These statements apply to the UAE-hosted endpoints offered through NanoGPT and are based on Hyperfusion's written confirmations to us. See Hyperfusion's website for its service information.
- Netra Runtime: When you select Netra Runtime, it processes your prompts, conversation context, and outputs. Netra has committed not to use this content for model training, but does not guarantee zero data retention. See the Netra Runtime privacy policy and Netra Runtime terms of use.
- Arnict: Arnict states that prompts and outputs routed through its service are processed for inference and are not archived or used for training. Arnict confirms that temporary inference caches are held only in GPU memory (VRAM) and expire 15 minutes after last use. Account, usage and billing metadata may be retained. See the Arnict privacy policy and Arnict terms of service.
- OrcaRouter (Continuum AI Pte. Ltd.): When requests are routed through OrcaRouter, including its OrcaCyber models, your prompts, conversation context, images, tool-call content, and outputs are processed on OrcaRouter's inference infrastructure. OrcaRouter's privacy policy states that prompt and output content is processed in transit, is not stored unless request logging is enabled for the account, and is not used to train models. OrcaRouter retains request metadata, such as token counts and timestamps, for up to 13 months. It operates from Singapore and uses infrastructure in Singapore, the United States, and Japan. NanoGPT has not signed a zero-retention agreement with OrcaRouter, and we do not classify this route as Zero Data Retention. See the OrcaRouter privacy policy and terms of service.
- Gradiated (PostHog Inc.): When routed through Gradiated, your prompts, context, tool payloads and outputs are processed by its inference platform and hosting subprocessors. NanoGPT disables trace capture and omits the task header used to opt into stored training traces. Gradiated confirms that these requests are processed in memory without prompt/output retention, including for abuse investigations, or training use. Non-content usage, security and billing metadata may be retained. See its privacy policy and terms of service.
- Kitani: When requests are routed through Kitani, your prompts, conversation context, and outputs are processed through its inference platform, which may use third-party capacity. NanoGPT requires zero data retention for Qwen 3.8 27B, GLM 5.3, Kimi K3, DeepSeek V4.1 Flash, GLM 5.3 Flash Uncensored, MiMo V2.6 Flash RL, and MiMo V2.6 Pro RL requests through Kitani, including applicable thinking variants. Kitani confirms that prompts and outputs for these routes are not retained or used for training. Requests fail when no qualified ZDR deployment is available. Kitani reports encrypted inference transport (TLS) for the reviewed DeepSeek V4.1 Flash, uncensored, and MiMo RL routes. These requirements apply to these reviewed models, not every Kitani deployment. Prompts for the Morgana v1.2 image model are sent to Kitani, which returns the generated image; Kitani publishes no retention tier for that model, so it is not classified as Zero Data Retention. Kitani retains usage and billing metadata. See the Kitani privacy policy and Kitani terms of service.
- LongStories: When you use a LongStories model, your idea and a pseudonymous identifier are sent to LongStories, which makes the video and keeps its own copy under its privacy policy. It may process this data in the United States and other countries.
- eu/jev (Bevelites GmbH): Jeff processes the state and typed questions you submit for decision inference in Germany. eu/jev states that API content is not persisted in its database or application logs or used to train models. Temporary tokens and intermediate calculations can remain in worker memory across requests and are not immediately erased after completion. Account, usage, billing and security metadata may be retained. NanoGPT therefore rejects requests requiring strict zero data retention. See the eu/jev privacy policy and Data Processing Agreement; the agreement must be concluded before submitting personal data on behalf of a business or other controller.
- SubQ: SubQ Snap processes the state, typed questions and inline images you submit for decision inference. SubQ documents deletion of inputs and outputs within 60 days, with exceptions for policy investigations and legal requirements. NanoGPT has not verified zero data retention for this Snap account, so requests requiring ZDR are rejected. See the SubQ data-retention documentation and SubQ privacy policy.
- TypeSafe (TypeSafe AI, Inc.): Jev decision requests may be sent to TypeSafe directly. TypeSafe processes the state, any images and the typed questions you submit in the United States. TypeSafe states that it does not train or fine-tune models on your input and shares input only with its service providers. It keeps personal data for as long as reasonably necessary to provide its services and does not publish a fixed retention period, so requests requiring zero data retention are not sent to TypeSafe directly. See the TypeSafe privacy policy.
- 50X (50X Holding LLC): When 50X serves a DeepSeek V4.1 Flash 1017 request, including through Auto, your prompts, conversation context, tool-call content and outputs are sent to 50X for inference. 50X has signed a statement for NanoGPT that prompts and outputs on this route are not kept in persistent storage after a request finishes, by 50X, its GPU hosting provider or any other subprocessor, and are not used to train, fine-tune or evaluate models. Prompt-derived prefix cache state may be held temporarily in volatile memory to speed up later requests. 50X keeps operational records without prompt or output content, such as request IDs, token counts, latency and status codes. NanoGPT classifies this route as Zero Data Retention based on that statement. See the 50X zero data retention policy and 50X privacy policy.
- Unrestricted: When this provider serves your request, text prompts, conversation context and outputs are processed on a dedicated DeepInfra GPU instance in the United States. Unrestricted has confirmed in writing that prompts and outputs are not stored, logged or used for training, including by its GPU host. Computed attention state (KV cache) can remain in GPU memory between requests for cached-input processing. Billing and connection metadata is retained separately. See Unrestricted's website.
- Entrim: When your request is routed to Entrim, including through Auto, your prompts, conversation context, images, and outputs are processed through ingress in Frankfurt, Germany, with inference in Slovenia. Entrim has confirmed account-wide zero data retention for NanoGPT: prompts and outputs are not retained or used for training or evaluation. Temporary GPU-memory caching uses separate namespaces for individual NanoGPT users; disk-backed and host-memory KV caching are disabled. Entrim retains operational metadata for up to 90 days, and some metadata processing may occur outside the EEA. This classification applies to NanoGPT's Entrim account and does not mean that all metadata is deleted immediately. See Entrim's website for service information.
- RunAnywhere (Wally), including RunAnywhere Fast: When you select RunAnywhere, your prompts, conversation context, supported images, and outputs are processed by its hosted Wally service. The current model catalog reports US datacenters, and RunAnywhere identifies Google Cloud as its model-serving processor. Its Privacy Policy states that production Wally does not store prompt or completion bodies. Usage records, including token counts, timestamps, model, request ID, and spend, are retained separately for billing, abuse prevention, and support. Usage and billing records kept for legal, tax, or accounting obligations may survive account deletion; the policy does not specify a fixed retention period for those records or a separate model-training commitment. Prompt/output zero retention does not mean that all metadata is deleted immediately.
- SCX.ai: When you select SCX (Global) or SCX (EU only), SCX processes your request under its privacy policy. SCX confirms that API prompts and outputs are not retained or used for training. SCX (EU only) restricts inference, including SCX's own fallback inference, to the EU; the Global option may process requests in other regions. SCX retains operational metadata for billing, security, and reliability.
- Pareto Inference: Pareto defaults to zero data retention for its standard inference API: prompts and outputs are not kept in persistent storage after a request finishes, and model training requires separate opt-in. Temporary in-memory prompt caching may be used; operational, security, account, and billing metadata may be retained. Upstream fallback is restricted to providers OpenRouter designates as zero data retention. See the Pareto Inference zero data retention policy for scope and exceptions, the privacy policy, and the terms of service.
- OpenScale: OpenScale processes model requests on its own GPUs hosted at iForte and RunPod. Its gateway and database run on Google Cloud. OpenScale states that these infrastructure providers do not access request content and that prompts and outputs are not retained or used for training. Its published policy provides for request metadata retention for 30 days. NanoGPT does not currently classify OpenScale as zero retention; this awaits its signed Supplier Data Addendum. Zero-retention requests are not routed to OpenScale.
- Prima Era (Prima Era S.R.L.): When requests are routed through Prima Era, your prompts and outputs are processed on infrastructure run by its sub-processors Nebius and Amazon Web Services in the United States, the United Kingdom, France, Sweden, India, Indonesia, South Korea and Brazil. Under its agreement with NanoGPT, Prima Era processes this content only in memory, doesn't store it on disk or use it for training, and doesn't forward requests to other providers. It keeps request metadata, such as token counts, for 90 days, and daily usage totals for accounting. NanoGPT classifies this route as Zero Data Retention based on these commitments; this does not mean that no billing or security metadata is processed.
- StreamLake (STREAMLAKE PTE. LTD., part of Kuaishou): When your request is sent to StreamLake's own API, your prompts, conversation context, images, tool-call content, and outputs are processed on StreamLake's infrastructure in Singapore, where its caches and logs are also kept. StreamLake keeps prompts and outputs in its service logs for up to 30 days, only to investigate and fix errors and other service problems, and then deletes them. This logging can't be turned off for NanoGPT's account. StreamLake has confirmed in writing that it does not use NanoGPT requests for model training and does not use these logs for any other purpose. It keeps request metadata, such as token counts and timestamps, for 30 days. Its prompt cache is held in memory, is shared across StreamLake's customers, and may keep cached prompt data for up to 7 days to speed up repeated requests. Because of the 30-day logs, NanoGPT does not classify StreamLake as Zero Data Retention, and requests that require Zero Data Retention are never sent to StreamLake, either directly or through OpenRouter. Requests that reach StreamLake through OpenRouter are handled under OpenRouter's arrangements with StreamLake. See the StreamLake privacy policy and terms of service.
- Inworld (Theai, Inc. dba Inworld AI): When a text model Inworld hosts itself serves your request, your prompts, conversation context, supported images and outputs are sent to Inworld for inference; Inworld also processes the text you convert to speech. Inworld has confirmed to NanoGPT in writing that zero data retention is on for NanoGPT's account: prompts and outputs are processed in memory and redacted from its logs, are not used for training, and are served from Inworld's own deployment in the United States without falling back to other providers. Voice cloning is the exception: Inworld keeps the source audio you upload to create a cloned voice. NanoGPT sends Inworld text requests only for models Inworld hosts itself and classifies those routes as Zero Data Retention based on these commitments; this does not mean that no billing or security metadata is processed.
- Messaging & Notification Tools: To help our team respond quickly, bug reports, suggestions and support tickets you submit are forwarded to the tools our team uses to handle them. Bug reports and suggestions are forwarded to an internal messaging service (Discord) and to our internal support tool. Support tickets and your replies to them are forwarded to our internal support tool. These copies include the content you choose to provide, such as your message and, for bug reports and suggestions, the images you attach, together with your numeric account ID. A bug report also includes what you leave ticked in the report form, such as the reported chat message, the prompt before it, technical diagnostics and your support key, and technical details of the request it is about, such as its ID, the model and the billing outcome. Automated alerts that our systems send to our team's messaging tools (Discord and Telegram), for example about a withdrawal request or a failed gift redemption, can include account IDs and payment details such as amounts and wallet addresses.
- Important Note on Provider Data Policies: We send providers the content and related information needed to process your request, as described above. We do not intentionally attach your NanoGPT account name, email, raw account or session identifier, or IP address to model-provider requests. Most routes for OpenAI, Meta, Anthropic and Google Gemini models, and some routes for other models, carry the stable hashed identifier described below. Content you submit may itself identify you. Providers may collect or store that content under their own data retention practices. We make reasonable efforts to use available retention and deletion controls, but we rely on provider statements and cannot independently guarantee their retention, deletion, or security practices. This also applies to routes labeled Zero Data Retention: ZDR is a best-effort routing classification based on the provider's claim, not independent visibility into or verification of its servers and internal setup. Some providers and intermediaries, including OpenRouter, screen requests for child sexual abuse material on all routes, including Zero Data Retention routes, and may retain flagged content for human review, reporting, and legal preservation where the law requires it.
- Exercise caution and avoid submitting personal or sensitive information in your prompts, especially when using models from providers with indefinite data retention policies.
- Legal Requirements: We may share limited Personal Information if required by law, including in response to valid legal process and in reports we are legally required to make (for example, reports of apparent child sexual abuse material to the National Center for Missing & Exploited Children), or to protect our rights and the safety of our users. Where the law or an investigation requires it, we may preserve related records for longer than our usual retention periods.
Stable identifiers sent to model providers
When you use OpenAI, Meta, Anthropic or Google Gemini models, most routes send a stable hashed account or session identifier to the model provider or the intermediary serving your request, and some routes for other models do too. You can turn this off (see below). We use this identifier to help prevent abuse, enforce applicable usage policies, and protect access to the Services. The hashed identifier allows requests from the same account or session to be associated without sending your name, email address, or raw account identifier.
This identifier is separate from your conversation content. Anonymized or Zero Data Retention routing, content redaction, and settings for local history or request storage do not disable it on covered routes. Providers process identifiers and related security records under their applicable agreements and data practices. Information you include in prompts may itself identify you. See OpenAI's API data controls for more information.
To turn this off, turn on Skip routes that need a stable account ID in your privacy settings. We apply this setting when we route each request; it is not only a recorded preference. With it on, your text requests in web chat and the API carry none of the stable identifiers we generate, including fallbacks and requests with your own provider keys: each route either sends none or is skipped. Models that only run on routes that need the identifier are unavailable while it is on, and other models may have fewer backup routes. Turning it on does not recall identifiers already sent. Image, audio, video, embedding and batch requests are not covered by this setting yet.
Aggregated and De-identified Information
We may process information in aggregated or de-identified form so it cannot reasonably be used to identify you. We use this information to:
- Analyze and improve the performance and reliability of our Services;
- Understand usage trends and feature preferences;
- Publish or share high-level statistics about our Services.
Your privacy choices
- Advertising tracking: Advertising pixels and conversion reporting have been retired. See our Advertising Policy.
- Marketing and getting-started emails: Use the unsubscribe link in any of these emails or contact us to opt out. We may still send necessary account, payment, security, and legal notices.
- Sync, sharing, and memory: Use the relevant settings to disable future syncing or memory use, delete stored items, or revoke share links. Disabling a feature is separate from deleting content already stored. Link revocation does not recall copies saved by recipients.
- API request logging and staff access: These are separate opt-ins in API-key settings. Turning off staff access revokes further access through our support tools; turning off logging or clearing logs initiates payload deletion as described above, except where a legal preservation obligation or an active abuse investigation requires us to keep those records, in which case they are hidden from your account and deleted when that obligation ends.
- PII redaction: Manage redaction and choose its provider (Tinfoil or Grepture) in chat, account, and API-key settings or through supported request overrides. The chosen provider receives the original content necessary for redaction, as described above. Turning redaction off means the selected model provider may receive unredacted content. Redaction may miss personal information and is not a guarantee of anonymity.
- Provider retention: Supported settings let you require a Zero Data Retention route for text models. Image, video, audio and 3D requests are not covered. This requirement applies to fallback and gateway routes as well as the first provider tried, as described under Routing and fallbacks. Coverage and restrictions depend on the endpoint and enabled features; ZDR does not mean no billing or security metadata is processed. Anonymized routing refers to withholding attached NanoGPT account names, emails, and raw account or session identifiers. These settings do not remove the stable model provider identifier described above; the separate setting to skip routes that need a stable account ID turns it off for text requests. Personal information you include in your prompt remains visible to the provider, and provider retention and training policies still apply. Changing a routing setting does not delete earlier requests.
Withdrawing consent does not affect the lawfulness of processing based on consent before withdrawal. It does not stop processing that has another lawful basis, such as the billing and security records we keep ourselves. This exception does not limit the setting to skip routes that need a stable account ID: with it on, we do not send the identifier described under Stable identifiers sent to model providers with the requests it covers. You can separately request deletion or exercise other applicable rights below. Optional settings do not waive those rights.
Your rights and requests
Depending on location, individuals may have certain statutory rights in relation to their Personal Information. For example, you may have the right to:
- Access your Personal Information and information relating to how it is processed.
- Delete your Personal Information from our records.
- Rectify or update your Personal Information.
- Transfer your Personal Information to a third party (right to data portability).
- Restrict how we process your Personal Information.
- Withdraw your consent where we rely on consent as the legal basis for processing at any time.
- Object to how we process your Personal Information.
- Opt out of sale, sharing, or targeted advertising, and limit certain uses or disclosures of sensitive personal information, where applicable law provides these rights.
- Exercise applicable rights concerning decisions based solely on automated processing that have legal or similarly significant effects.
- Lodge a complaint with your local data protection authority.
To exercise applicable privacy rights, contact support@nano-gpt.com or use the relevant controls in the Services. You do not need to create an account or use particular wording. Describe your request and provide enough information for us to locate the relevant records, such as an account email or support identifier if you have one. You may also contact us if your personal information appears in content submitted by someone else.
Where needed and permitted by law, we may request proportionate information to verify your identity or an authorized agent's authority, using information already available to us where possible. Do not send passwords, API keys, sign-in tokens, recovery phrases, or unnecessary identity documents. Requests to opt out of sale, sharing, or targeted advertising do not require the same identity verification as requests for access or deletion; we may need enough information to apply the choice to the relevant records.
We respond within the time required by applicable law. Where the EU GDPR applies, we respond without undue delay and generally within one month; complex or numerous requests may allow up to two additional months, with notice and reasons within the initial month. Where the California Consumer Privacy Act applies, requests to know, delete, or correct generally have a 45-day response period, with a further 45 days where permitted and notified. Opt-outs and requests under other laws may have different deadlines. We charge no fee unless applicable law permits one and we explain it to you.
If we cannot fully comply, we will explain the applicable reason and any available appeal or complaint options. You may ask us to review a decision by contacting the same address; where the law provides an appeal right, we will handle it under that law. You may contact your data protection authority or other competent regulator without first contacting us or completing an appeal. We will not unlawfully discriminate against you for exercising your rights.
Where we process information on a business customer's behalf, we handle requests according to our role and applicable law, including assisting that customer where required. We handle requests concerning information we hold or control and, where required, notify, instruct, or assist relevant recipients and service providers. Providers that independently control information may also need to handle a separate request. Local-only content and content encrypted with credentials unavailable to us may require action by you; this does not remove rights concerning information we hold or control.
Children
Our Services are not directed to or intended for anyone under 18, and you must be at least 18 to use them. If we learn that we have collected personal information from someone under 18, we will take reasonable steps to delete it and prevent further use of the Services.
Security and Retention
We use commercially reasonable administrative, technical, and physical safeguards designed to help protect your Personal Information. For cloud storage of media, user-uploaded content, synced conversations and other stored content, we use Cloudflare R2 object storage. Shared conversation snapshots and some audio and video uploads are stored with Vercel Blob. Email sent to your NanoGPT inbox address is received by Amazon SES and kept briefly in Amazon S3 (Frankfurt) until we process it into our own storage. Data stored with these providers is subject to Cloudflare's Privacy Policy, Vercel's Privacy Policy and the AWS Privacy Notice. If you configure your own storage bucket for sync, that content is stored with the provider you choose. No method of transmission or storage is completely secure, and we cannot guarantee the absolute security of your information or that our safeguards will prevent every instance of unauthorized access, disclosure, alteration, or loss. These limitations do not affect our obligations or your rights under applicable law. We retain personal information for as long as reasonably necessary for the purposes described in this Privacy Policy, taking account of the type of information, the features and settings you use, and applicable legal requirements. Feature-specific expiration and deletion practices are described above. Account, payment, and security records may be needed for billing, accounting, fraud prevention, dispute resolution, or legal compliance after you stop using the Services; this does not extend the content-retention periods described above.
The safety and security of your information also depends on you. If you use a password to access any part of our Services, you are responsible for keeping it confidential and for not sharing it with anyone.
Deletion and retention limits
Account closure, disabling a feature, revoking access, and deleting stored content are different actions. Account deletion removes or de-identifies selected records and initiates cleanup, but is not a promise that every record, backup, or remote object disappears immediately. A record is not necessarily anonymous merely because a name or email has been removed. You can contact us for a privacy request covering information beyond the account-deletion controls.
- Local conversation history is held on your device. Optional cloud content follows its feature-specific settings, expiry, and deletion processes described above.
- Account, payment, usage, and security records are retained according to their continuing service, accounting, fraud-prevention, dispute, or legal purpose. Support messages and attachments may be retained to handle the request and related follow-up or disputes.
- Deleting your account does not automatically delete support tickets and bug reports you sent us, our replies, or their attachments, such as screenshots. Copies may also exist in the tools our team uses to handle support, such as email and internal messaging services. To have them deleted, contact support@nano-gpt.com.
- Stable identifiers and related security records already received by providers or intermediaries follow their applicable retention practices and legal obligations. Deleting local chats, changing API keys, or closing your account does not itself delete those records. You can contact us to exercise applicable privacy rights.
- Stored imports and media may require separate cleanup from local library or account deletion. Information in your own storage is also subject to your storage configuration and lifecycle.
- Deletion from active systems may precede physical removal from storage or backups. Cleanup failures can require retries. Any retention exception must have an applicable purpose and legal basis; a legal preservation obligation may limit deletion for the information it covers.
Processing locations
NanoGPT is a U.S. company, and our Services and providers may process information in the United States and other countries. Processing locations depend on the feature and provider route. An EU inference option does not by itself mean that account, billing, support, or every other processing stage remains in the EU. International transfers are subject to applicable legal requirements. Contact support@nano-gpt.com for information about the relevant processing locations and applicable transfer safeguards. This policy does not represent that every provider offers the same regional or contractual protections.
Third-Party Services
Our Services may link to or integrate with third-party websites, applications, or services. Those services have their own privacy policies governing their independent processing of information, and we do not control those independent practices. Our collection and disclosure of information to these services is described in this Privacy Policy, and our responsibilities under applicable law continue to apply. Please review the applicable privacy policies of any third-party services you use.
- Web Search & Browsing Providers: Linkup Privacy Policy, Tavily Privacy Policy, Exa Privacy Policy, Kagi Privacy Policy, Brave Search Privacy Notice, Perplexity Privacy Policy, Valyu Privacy Policy, Sofya Privacy Policy.
- Keiro Web Search: When you select Keiro, we send your search query and selected search options to Keiro to retrieve results. Keiro is not available for requests requiring zero data retention.
- SpecStream Web Search: Only when you select SpecStream, we send your search query to SpecStream SAS to retrieve results. SpecStream forwards queries to public search engines under those engines' own policies; our requests exclude China-based engines. Some requests use Apify proxy egress in the United States. Cloudflare proxies SpecStream's API traffic, and Cloudflare Workers AI ranks search results, so query and result data can pass through outside services. Under its written agreement with NanoGPT, SpecStream stores no queries or results on any of our keys, including requests ending in errors or timeouts. This commitment covers SpecStream's own systems, not the outside search engines or network services. Its 24-hour page-copy and seven-day working-copy retention does not apply to our keys. SpecStream hosts its own processing on IBM Cloud in Madrid, Spain; server logs without query, URL or page text are kept for up to 30 days. Database backups in Spain and the EU are kept for up to 30 days and contain billing records rather than queries or results. Content-free billing records are retained for 10 years. SpecStream remains unavailable for requests requiring zero data retention. See the SpecStream Privacy Policy and Data Processing Agreement; our written addendum governs the commitments specific to NanoGPT.
- Audio & Media Generation: Some audio, image, video and 3D generation features use third-party providers (such as FAL AI, Runware, WaveSpeed, and Replicate) to process prompts or media inputs and return outputs. These providers may store your prompts, input media and outputs under their own retention practices. Zero Data Retention settings do not apply to these requests, so they are not refused when you require Zero Data Retention. Data shared with these providers is subject to their respective privacy policies: FAL AI Privacy Policy, Runware Privacy Policy, WaveSpeed Privacy Policy, Replicate Privacy Policy.
- Content Extraction & Transcripts: When you ask NanoGPT to read a web page, the page address is sent to a page-reading service (BerryCrawl by default, or Firecrawl, Linkup or Sofya). YouTube transcripts are fetched through YouTube Transcript, or through a transcript scraper on Apify when that fails. When you ask for text recognition (OCR) on a PDF, its pages are sent to Mistral AI or Novita. BerryCrawl Privacy Policy, Firecrawl Privacy Policy, YouTube Transcript Privacy Policy, Mistral AI Privacy Policy, Novita Privacy Policy.
- Data Lookup & Social Media Tools: These tools run when you or a model acting on your request invokes them, in the app or through the API, and we send the provider the tool inputs and service options needed for the lookup. Hunter receives the company domain or name, the person's name, LinkedIn handle or email address, or the search you ask it to find, verify or look up. Apify runs the scrapers for Reddit, TikTok, Instagram, Facebook, LinkedIn and Google Maps, and receives your search terms, the profile or page addresses you give, and your search options. X receives the search terms, account names and post, list or Space identifiers you look up with the X tools. Hunter Privacy Policy, Apify Privacy Policy, X Privacy Policy.
- Connected Tools (Monid): If you connect your own Monid account, we store the access it grants us, encrypted, until you disconnect. When a model in web chat wants to use a Monid tool, we show you the request first, and only after you approve it do we send that tool's name and inputs to Monid. Monid processes them under its own terms.
- GitHub Repositories: When you turn on the GitHub repository tool, the model can read public GitHub repositories that you or it point to; we send GitHub the repository name, branch, file paths and any code search terms needed to read them. See the GitHub Privacy Statement.
- Context Memory: PolyChat Privacy Policy. See Context Memory above for what PolyChat receives.
- AI Detection & Plagiarism Checks: Pangram Privacy Policy.
- Payment Providers: Stripe Privacy Policy, BTCPay Server Privacy Policy, Nanswap Privacy Policy, Coinbase Privacy Policy (x402 payments).
- Hosting, Storage & Infrastructure: Our hosting providers Vercel and Fly.io, Cloudflare (R2 object storage and Turnstile), Neon (our database), Upstash (our cache, used for rate limits, billing state and other short-lived data), and Amazon Web Services (Amazon SES, which delivers the emails we send you and so receives your email address and the message, and which receives email sent to your NanoGPT inbox address; Amazon S3, which temporarily stores that inbound email until we fetch it; and Amazon SNS, which sends us receipt notifications containing the email's metadata and headers). Vercel Privacy Policy, Fly.io Privacy Statement, Cloudflare Privacy Policy, Neon Privacy Policy, Upstash Privacy Policy, AWS Privacy Notice.
- Files Your Browser Downloads: Some optional features load files straight from another company into your browser, which shows that company your IP address: running Python code in your browser (files from jsDelivr), running a model locally in your browser (files from Hugging Face and GitHub), and embedded YouTube videos (from YouTube's privacy-enhanced youtube-nocookie.com domain; some start loading when you point at a model card or open a setup guide).
Changes to this Privacy Policy
We may update this Privacy Policy from time to time by posting the revised policy and updating the date on this page. Updates apply prospectively, subject to applicable notice and consent requirements. We will provide any notice and obtain any consent required by law before a change requiring that notice or consent takes effect. Posting an update does not itself authorize a new use of information that requires consent. You may request prior versions through our contact address below.
How to contact us
If you have any questions or concerns about this Privacy Policy, please contact our NanoGPT Support Team at support@nano-gpt.com.
List of AI Model Providers Terms
AI Model Provider Terms: When using our Services, depending on which model is used, you agree to abide by the terms of the respective AI model providers:
- 01.AI: If you use 01.AI models, you agree to abide by the 01.AI terms.
- 50X (50X Holding LLC): If your request is routed through 50X, 50X processes your prompts, conversation context, and generated outputs to provide inference, subject to the 50X privacy policy and 50X zero data retention policy. The 50X entry above describes its signed zero-retention commitment for NanoGPT.
- Abliteration.ai: If you use an Abliteration.ai model, your request and response content is processed under the Abliteration.ai privacy policy, terms of service, and data-handling policy. Abliteration.ai states that API prompts and completions are processed transiently, are not stored, and are not used for training. NanoGPT relies on that provider statement.
- AionLabs: If you use AionLabs models, you agree to abide by the AionLabs terms.
- Akash: If you use Akash models, you agree to abide by the Akash privacy policy.
- Alibaba: If you use Alibaba models, you agree to abide by the Alibaba Cloud terms.
- Amazon Bedrock: If you use Amazon Bedrock models, you agree to abide by the AWS Service terms.
- Ambient: If you use Ambient models, you agree to abide by the Ambient terms of service, Ambient privacy policy, and Ambient data handling policy.
- Anthropic: If you use Anthropic models, you agree to abide by the Anthropic usage terms.
- Aoru: If your requests are routed through Aoru, your use is subject to the Aoru terms of service, including its acceptable-use restrictions, and Aoru privacy policy.
- Arcee AI: If you use Arcee AI models, you agree to abide by the Arcee AI privacy policy.
- Arli AI: If you use Arli AI models, you agree to abide by the Arli AI terms.
- Aster, including Aster Fast: If your request is routed through Aster, Aster processes your prompts, conversation context, and generated outputs to provide inference.
- Astorias: If you use Astorias models, you agree to abide by the Astorias terms of service and Astorias privacy policy.
- AtlasCloud: If you use AtlasCloud models, you agree to abide by the AtlasCloud privacy policy.
- Autoloops: When Autoloops serves your request, your prompts, images, tool messages, and outputs are processed on Autoloops-operated GPUs in the United States. Autoloops states it does not store prompts or outputs or use them for training; token-count and latency metadata are retained. This is a provider commitment, not an independent audit.
- Azure: If you use Azure models, you agree to abide by the Microsoft terms of use.
- Baidu: If you use Baidu models, you agree to abide by the Baidu AI terms.
- Baseten: If you use Baseten models, you agree to abide by the Baseten terms of service and Baseten privacy policy.
- Celeris: If you use Celeris models, your request and response content is processed under the Celeris privacy policy and Celeris terms of service.
- Cerebras: If you use Cerebras models, you agree to abide by the Cerebras privacy policy.
- Chutes: If you use Chutes models, you agree to abide by the Chutes terms.
- Cloudflare: If you use Cloudflare models, you agree to abide by the Cloudflare terms of service and Cloudflare privacy policy.
- Cohere: If you use Cohere models, you agree to abide by the Cohere terms of use.
- CoralBricks: Requests are subject to the CoralBricks terms of service and privacy policy. The information-sharing disclosure above explains NanoGPT's zero-retention setting, the operational data CoralBricks keeps, and its training restrictions.
- CoreWeave: If you use CoreWeave-routed models, you agree to abide by the CoreWeave Terms of Service, Data Processing Agreement, and Privacy Policy.
- Creekside Compute: If your request is routed through Creekside Compute, Creekside Compute processes your prompts, conversation context, and generated outputs to provide inference.
- Crusoe: If you use Crusoe models, you agree to abide by the Crusoe terms of service and Crusoe privacy policy.
- Darkbloom: If a model request is routed through Darkbloom, its request and response content is processed under the Darkbloom privacy policy and terms of service. Darkbloom says ordinary coordinator logs are designed not to contain prompt content and does not claim general-purpose training rights, but its policy permits operational retention and exceptions for support, abuse review, legal compliance, and disputes. Its terms state that end-to-end encryption between consumer and provider is not currently guaranteed.
- Decart: If you use Decart models, you agree to abide by the Decart terms of service and Decart privacy policy.
- DeepInfra: If you use DeepInfra models, you agree to abide by the DeepInfra terms.
- DeepSeek: If you use DeepSeek models, you agree to abide by the DeepSeek terms of use.
- DekaLLM: If you use DekaLLM models, you agree to abide by the DekaLLM terms of service and DekaLLM privacy policy.
- DigitalOcean: If you use DigitalOcean models, you agree to abide by the DigitalOcean Privacy Policy and DigitalOcean Terms of Service.
- DiscreteStack: If your request is routed through DiscreteStack, DiscreteStack processes your prompts, conversation context, and generated outputs to provide inference, subject to the DiscreteStack API privacy policy. DiscreteStack states that this processing takes place in the EU.
- Doubao: If you use Doubao models, you agree to abide by the Doubao terms.
- Entrim: If your request is routed to Entrim, including through Auto, the applicable model licenses and service terms apply. The Entrim disclosure above describes the account-specific privacy commitments for NanoGPT, EU inference, isolated GPU-memory caching, and operational metadata retention.
- eu/jev (Bevelites GmbH): Jeff use is subject to the eu/jev terms of service and privacy policy. A Data Processing Agreement is required before submitting personal data on behalf of a business or other controller.
- FAL: If you use FAL models, you agree to abide by the FAL terms of service.
- Featherless: If you use Featherless models, you agree to abide by the Featherless terms.
- Firecrawl: If you use Firecrawl, you agree to abide by the Firecrawl privacy policy.
- Fireworks: If you use Fireworks models, you agree to abide by the Fireworks terms of service.
- Friendli: If you use Friendli models, you agree to abide by the Friendli terms of service and Friendli privacy policy.
- Gemini: If you use Gemini models, you agree to abide by the Gemini usage terms.
- Gerra: If you use Gerra models, you agree to abide by the Gerra privacy policy.
- GMICloud: If you use GMICloud models, you agree to abide by the GMICloud terms and conditions.
- Gondola / Venice: If a model request is routed through Gondola, its request and response content may be processed by Gondola and its Venice upstream under the Gondola privacy policy, Gondola terms of service, Venice privacy policy, and Venice terms of service.
- Gonka24: If you select Gonka24, your use is subject to the Gonka24 terms of service and Gonka24 privacy policy.
- Google AI Studio: If you use Google AI Studio models, you agree to abide by the Google Cloud terms.
- Google Vertex: If you use Google Vertex AI models, you agree to abide by the Google Cloud terms.
- Greenference: Model requests may be processed by Greenference under its terms and data policy.
- Groq: If you use Groq models, you agree to abide by the Groq terms of use.
- H Company: If you use H Company models, you agree to abide by the H Company privacy policy.
- Heabsy (FEYA, s.r.o.): If your model request is routed through Heabsy, your prompt and completion content is processed under the Heabsy privacy policy and Heabsy terms of service. For models served on its own infrastructure, Heabsy states that content is processed in memory, including transient prefix caching, without durable storage or content logging, and is not used to train, fine-tune, or improve models. Heabsy retains usage metadata and financial records for 10 years, application logs for 30 days, and security audit logs for one year. These content-retention and no-training commitments do not apply to models fulfilled by third-party inference providers, whose own data policies apply.
- Hyperbolic: If you use Hyperbolic models, you agree to abide by the Hyperbolic privacy policy.
- Hyperfusion: If you select Hyperfusion, your use is subject to the applicable model licenses and Hyperfusion's service terms. The Hyperfusion entry in the information-sharing section above explains its commitments for NanoGPT requests, including UAE processing, prompt/output handling, temporary memory caching, and 30-day request-metadata retention. See Hyperfusion's website for its service information.
- Inception: If you use Inception models, you agree to abide by the Inception privacy policy.
- Inceptron: If you use Inceptron models, you agree to abide by the Inceptron privacy policy and Inceptron terms of service.
- Inflection: If you use Inflection models, you agree to abide by the Inflection developer terms.
- Inworld (Theai, Inc. dba Inworld AI): If your request is routed through Inworld, your use is subject to the Inworld terms of service and Inworld privacy policy. The Inworld entry in the information-sharing section above describes its commitments for NanoGPT requests.
- Io Net: If you use Io Net models, you agree to abide by the io.net terms and io.net privacy policy.
- IONOS: Requests to models hosted by IONOS CLOUD are processed on its infrastructure in Germany. According to its AI Model Hub data handling policy, prompts and outputs are not logged or retained, used for training, or shared with model developers. IONOS records billing and operational metadata, including timestamps, model names, and token counts.
- Krea: When using models served directly by Krea, prompts and any reference images are sent to Krea to generate outputs. See the Krea privacy policy and Krea terms of use.
- LLM API (LLM API Inc.): Some requests are routed through LLM API, a gateway that passes them on to the company running the model, such as Azure, Amazon Bedrock or Google Vertex AI. Under its agreement with NanoGPT, LLM API doesn't store or log your prompts or responses. It keeps usage records, such as token counts, cost and the model used, for billing. The company running the model processes your request under its own policy. See the LLM API privacy notice and terms of use.
- LongStories: If you use LongStories models, you agree to abide by the LongStories terms of service and privacy policy.
- Lucidity (Synth): Prompts and conversation context submitted to Synth 2.5 Flash Preview or Synth 2.5 Pro Preview are sent to Lucidity for inference. Lucidity has directly confirmed zero data retention for Synth API requests made through NanoGPT: prompts and outputs are not retained or used for training. See the Lucidity privacy policy and Lucidity terms of service.
- Lyber: Lyber deletes request data visible to its service but retains billing metadata. Lyber is not currently a zero-data-retention provider; full ZDR is expected after its private hardware rollout. See the Lyber privacy policy and Lyber terms.
- Mancer: If you use Mancer models, you agree to abide by the Mancer terms of service and Mancer privacy policy.
- Mara: If you use Mara models, you agree to abide by the Mara AI policies.
- MegaNova: If you use MegaNova models, you agree to abide by the MegaNova privacy policy.
- Meta: If you use Meta Llama models, you agree to abide by the Meta privacy policy.
- Minimax: If you use Minimax models, you agree to abide by the Minimax terms of service.
- Mistral: If you use Mistral models, you agree to abide by the Mistral terms of use.
- Mixlayer: If you use Mixlayer models, you agree to abide by the Mixlayer terms of service and Mixlayer privacy policy.
- Modal: If you use Modal models, you agree to abide by the Modal privacy policy and Modal terms of service.
- ModelRun: If you use ModelRun models, you agree to abide by the ModelRun terms of service and ModelRun privacy policy.
- Moonshot AI: If you use Moonshot AI models, you agree to abide by the Moonshot AI privacy policy.
- Morph: If you use Morph models, you agree to abide by the Morph terms of service and Morph privacy policy.
- Munito: If your request is routed through Munito, Munito processes your prompts, conversation context, and generated outputs to provide inference.
- NCompass: If you use NCompass models, you agree to abide by the NCompass terms of service and NCompass privacy policy.
- Nebius: If you use Nebius models, you agree to abide by the Nebius terms of service and Nebius privacy policy.
- Neuralwatt: If you use Neuralwatt models, you agree to abide by the Neuralwatt terms of service and Neuralwatt privacy policy.
- NextBit: If you use NextBit models, you agree to abide by the NextBit terms of service and NextBit privacy policy.
- NovitaAI: If you use NovitaAI models, you agree to abide by the NovitaAI terms of service.
- Nube: If your request is routed through Nube, Nube processes your prompts, conversation context, and generated outputs to provide inference.
- Ollama: If your request is routed through Ollama, Ollama processes your prompts, conversation context, and generated outputs to provide inference.
- OpenAI: If you use OpenAI models, you agree to abide by the applicable OpenAI Services Agreement and OpenAI Usage Policies.
- OpenRouter: If your request is routed through OpenRouter, including as a fallback, you agree to abide by the OpenRouter privacy policy.
- OrcaRouter: If your request is routed through OrcaRouter, including its OrcaCyber models, your use is subject to the OrcaRouter terms of service and privacy policy. The information-sharing disclosure above explains how OrcaRouter handles request content and metadata.
- Pangram: If you use Pangram AI detection or plagiarism checking, you agree to abide by the Pangram privacy policy and Pangram terms of service.
- Parasail: If you use Parasail models, you agree to abide by the Parasail privacy policy.
- Pareto Inference: If you use Pareto Inference models, you agree to abide by the Pareto Inference terms of service and Pareto Inference privacy policy.
- Particle AI: If your request is routed through Particle AI, Particle AI processes your prompts, conversation context, images, tool-call content, and generated outputs to provide inference, subject to the Particle AI privacy policy.
- Perplexity: If you use Perplexity models, you agree to abide by the Perplexity usage terms.
- Phala: If you use Phala models, you agree to abide by the Phala Cloud privacy policy and Phala Cloud terms.
- Poe: If you use Poe models, you agree to abide by the Poe terms of service and Poe privacy policy.
- Pokee: If you use Pokee-Isaac, your request and response content is processed under the Pokee privacy policy and Pokee terms of service. Pokee states that developer API prompts and outputs are not used for training. Its infrastructure provider retains an approximately 120-character preview of each message for 1 day and stores the encrypted raw request payload for up to 7 days before automatic deletion.
- PolyChat: If you use PolyChat models, you agree to abide by the PolyChat privacy policy.
- Poolside: If you use Poolside models, you agree to abide by the Poolside privacy policy.
- PPQ (PayPerQ): Some Gemini, Claude, OpenAI and Meta Muse requests are routed through PPQ, a gateway that passes them on to the model's provider (Google Vertex AI, Anthropic, Amazon Bedrock, OpenAI, Microsoft Azure or Meta), usually through OpenRouter. PPQ's privacy policy says it doesn't store prompts; it keeps usage records, such as token counts and the model used. The model's provider processes your request under its own terms. See the PPQ privacy policy and terms of service.
- Prima Era (Prima Era S.R.L.): If your request is routed through Prima Era, your use is subject to the Prima Era terms of service and privacy notice. The Prima Era entry in the information-sharing section above describes its commitments for NanoGPT requests, including processing locations, its Nebius and Amazon Web Services sub-processors, and metadata retention.
- PrimeIntellect: If your request is routed through PrimeIntellect, its content may be processed under the Prime Intellect terms of service and privacy policy. Inference-specific retention, training guarantees, and processing locations have not been verified.
- Public AI: Requests to models hosted through Public AI are sent to Public AI and its inference partners. Public AI confirmed to NanoGPT that it does not store API prompt logs or user data; it records the requested model and request status. Training use and inference-partner coverage have not been explicitly confirmed, so these routes are not classified as Zero Data Retention. See the Public AI terms and privacy policy.
- Redpill: If you use Redpill models, you agree to abide by the Redpill privacy policy.
- Reka: If your model request is routed through Reka, its request and response content may be processed by Reka under the Reka privacy policy and Reka terms of use.
- Relace: If your model request is routed through Relace, its request and response content may be processed by Relace under the Relace privacy policy and Relace terms of use.
- Replicate: If you use Replicate models, you agree to abide by the Replicate terms.
- River: Requests explicitly routed to River are processed by River under its privacy policy and terms. NanoGPT has not verified zero-retention or model-training commitments for this endpoint.
- RouteCortex: If a model request is routed through RouteCortex, its request and response content is processed under the RouteCortex privacy policy and terms of service. RouteCortex states that prompts and completions are processed in memory and are not logged.
- RunAnywhere (Wally), including RunAnywhere Fast: If you select RunAnywhere, the applicable model licenses, RunAnywhere Terms of Service, Acceptable Use Policy, and Privacy Policy apply. The disclosure above distinguishes zero retention of prompt/output bodies from retained usage and billing metadata.
- RunInfra: If your request is routed through RunInfra, its content is processed under the RunInfra privacy policy and RunInfra terms of service. RunInfra states that prompts and completions are not used to train or improve models. Prompt prefixes may remain in a serving-machine cache, and non-streaming responses requested with an Idempotency-Key may be retained for up to 24 hours for replay. Usage and billing metadata are retained. This route is not classified as Zero Data Retention.
- Runware: If you use Runware models, you agree to abide by the Runware privacy policy.
- Sable: If your request is routed through Sable, Sable processes your prompts, conversation context, images, tool-call content, and generated outputs to provide inference, subject to the Sable privacy policy. Sable states that it does not log, store, or train on prompts or outputs. It does keep a numerical prompt cache, usually for an hour to a few days, and usage records that include keyed one-way hashes of prompt beginnings, so this route is not zero data retention.
- Sail Research: If you use Sail Research models, you agree to abide by the Sail Research Data Processing Addendum.
- Sakana AI (Fugu): If you use Sakana AI or Fugu models, you agree to abide by the Fugu Privacy Policy, Sakana Fugu Terms of Service, and Sakana Fugu Usage Policy.
- SambaNova: If you use SambaNova models, you agree to abide by the SambaNova terms and conditions.
- SiliconFlow: If you use SiliconFlow models, you agree to abide by the SiliconFlow privacy policy.
- SpaceXAI: If you use SpaceXAI models, you agree to abide by the SpaceXAI Privacy Policy and SpaceXAI Terms of Service.
- StepFun: If you use StepFun models, you agree to abide by the StepFun privacy policy, StepFun terms of service, and StepFun data processing agreement.
- Straitly (Straitly, Inc.): Some requests for Claude models (Anthropic) and GPT models (OpenAI) are routed through Straitly, a gateway that passes them on to Anthropic or OpenAI for inference. Straitly then processes your prompts, conversation context, images, tool-call content, and outputs, and the model's provider processes your request under its own terms. Straitly's privacy policy says it doesn't store prompt or response content; it keeps request metadata, such as timestamps, the model used, token counts, and latency, and it can keep error messages and refusal reasons from the model's provider, which may quote part of a request. NanoGPT does not classify Straitly as zero data retention: under our agreement, request content may be held in encrypted, access-restricted storage until Straitly confirms its zero-retention terms in writing. Requests that require zero data retention or EU-only processing are not routed to Straitly. See the Straitly privacy policy and terms of service.
- StreamLake (STREAMLAKE PTE. LTD.): If your request is routed through StreamLake, your use is subject to the StreamLake terms of service and privacy policy. StreamLake keeps prompts and outputs in troubleshooting logs for up to 30 days; the StreamLake entry in the information-sharing section above describes its handling of NanoGPT requests.
- Tencent Cloud: If your request is routed through Tencent Cloud, Tencent Cloud processes your prompts, conversation context, and generated outputs to provide inference.
- TensorX: If you use TensorX models, you agree to abide by the TensorX terms and TensorX privacy policy.
- Tenstorrent: The console terms linked by OpenRouter permit logging inputs and outputs and using them for training and optimization. Separate retention and training guarantees for OpenRouter inference have not been verified. See the Tenstorrent privacy policy; do not assume zero retention or exclusion from training.
- Tinfoil: If you use Tinfoil models, you agree to abide by the Tinfoil privacy policy.
- TokenWatt: If your request is routed through TokenWatt, your use is subject to the TokenWatt terms of service and TokenWatt privacy policy.
- Together: If you use Together models, you agree to abide by the Together terms of service.
- TypeSafe (TypeSafe AI, Inc.): If you use Jev, you agree to abide by the TypeSafe acceptable use policy. The TypeSafe privacy policy describes how TypeSafe handles your input.
- Uomi: If you use Uomi models, you agree to abide by the Uomi terms of service and Uomi privacy policy.
- Venice: If you use Venice models, you agree to abide by the Venice terms of service and Venice privacy policy.
- Wafer: If you use Wafer-routed models, you agree to abide by the Wafer privacy policy, Wafer terms of service, and Wafer's Zero Data Retention commitments where applicable.
- WaveSpeed: If you use WaveSpeed models, you agree to abide by the WaveSpeed privacy policy.
- Weights & Biases: If you use Weights & Biases models, you agree to abide by the Weights & Biases terms of service and Weights & Biases privacy policy.
- Xiaomi: If you use Xiaomi models, you agree to abide by the Xiaomi privacy policy.
- YouTube Transcript: If you use YouTube Transcript, you agree to abide by the YouTube Transcript privacy policy.
- Z.AI: If you use Z.AI models, you agree to abide by the Z.AI terms of service and Z.AI privacy policy.
- Zai: If you use Zai models, you agree to abide by the Zai privacy policy.
- ZenMux: If a model is routed through ZenMux, your request and response content is processed under the ZenMux privacy policy and ZenMux terms of service. ZenMux does not currently publish a model-API zero-retention or training guarantee, so avoid including sensitive information.