OpenScale
Privacy Policy
Last updated: November 16, 2026
1. Overview
This policy explains what OpenScale, operated by AFG Ventura Teknologi Pte Ltd ("we", "us"), collects when you use openscale.so and the OpenScale API, and how we use it. The short version: we collect what we need to run the service and bill you, we do not sell your data, and the only advertising measurement we use is X's, Meta's and Google's, described below, which tells us when a visitor from our ads signs up, verifies a card or buys credits.
2. What we collect
- Account information: your name, email address, and a hashed form of your password. We never store passwords or API keys in plain text.
- Google sign-in: if you continue with Google, we receive your name, email address, profile picture and Google account id, and use them only to create your account and sign you in. We do not access any other Google data and do not share it with anyone. Our use of information received from Google APIs adheres to the Google API Services User Data Policy.
- Billing information: your payment history and credit balance. Card details are handled by our payment processor and never touch our servers.
- Usage data: API request metadata such as timestamps, model used, token counts, and response status, used for billing and the usage views in your dashboard.
- Request content: the inputs you send to models and the outputs they return pass through our systems to serve your request. Chat Completions and Messages requests are never stored. Responses API responses are stored for 30 days unless you opt out, as described in the data policy section below.
- Cookies: a session cookie to keep you signed in, the X (Twitter) advertising pixel on openscale.so, which sets cookies so X can attribute sign-ups to our ads on X, and a cookie that keeps the X click id when you arrive from one of our X ads; the Meta (Facebook and Instagram) advertising pixel, which sets cookies so Meta can attribute sign-ups, free trials and purchases to our ads on Meta, including one that keeps the Meta click id when you arrive from one of them; the Google Ads tag, which sets cookies so Google can attribute visits to our ads on Google; and our own first-party cookies that remember an anonymous visitor id and the page, referring site and time of your first and latest visit before you sign up, so we know which link brought you. These are saved with your account when you sign up and never shared. We use no other advertising or tracking cookies.
- Site analytics: with that visitor id, we record the pages you view on openscale.so, the buttons and links you click, which sections of a page you reach and how far you scroll, the campaign tags and ad click ids on the link you arrived from, the referring site, and your device type and country. We use it to see which ads and pages bring people to OpenScale and where they leave. It never includes what you type into forms, your prompts or your API usage. If you create an account, this history is linked to it.
3. How we use it
- To provide and operate the service and your dashboard.
- To meter usage and bill your credit balance.
- To prevent abuse, fraud, and security incidents.
- To send you service emails such as verification, receipts, and important account notices. We do not send marketing email without your consent.
4. Who we share it with
We share data only with the providers we need to run the service:
- Model providers: when you call the API, your request content is forwarded to the model provider that serves the model you selected. Their handling of that content is governed by their own policies.
- Infrastructure: our hosting and database provider (Google Cloud).
- Payments: our payment processor (Stripe), for checkout and receipts.
- Email: our email delivery provider, for transactional messages.
- Advertising measurement: X (Twitter) receives the pages you visit on openscale.so and, when you create an account, a sign-up signal with an internal account id, to measure our ads on X. When you start a checkout or buy credits (and, for accounts that verified a card under our earlier free credit offer, when you verified it), our server also tells X directly, sending an internal account id, a one-way SHA-256 hash of your email address, the X click id if you came from one of our X ads, the purchase amount, and the IP address and browser user agent of the checkout. X uses these only to match the event to an ad. We never send X your email address in readable form, your card details, your API usage or your request content. You can limit browser measurement with your browser's tracking protection, and ad matching with your X ad personalization settings.
- Meta ads: Meta receives the pages you visit, a signal when you click a sign-up button, and, when you create an account, get the free trial, start a checkout or buy credits, that event with an internal id and the purchase amount. For sign-ups, free trials and purchases our server also tells Meta directly, sending a one-way SHA-256 hash of your email address and of your account id, the Meta click and browser ids, and your IP address and browser user agent. Meta uses these only to match the event to an ad. We never send Meta your email address in readable form, your card details, your API usage or your request content. You can limit this with your browser's tracking protection and your Meta ad preferences.
- Google ads: Google receives the pages you visit on openscale.so. If you came from one of our Google ads, our server also tells Google when you create an account, start a checkout or pay (a top-up or a plan payment, including renewals), sending only the Google click id from the link you arrived from, the time and the amount. Google uses these only to match the event to an ad. We never send Google your email address, your card details, your API usage or your request content. You can limit this with your browser's tracking protection and your Google ad settings.
We do not sell personal data. We may disclose information if required by law.
5. Data policy for model requests
This section is the authoritative statement of how API request content is handled:
- No training: we never use your prompts or model outputs to train models, and we never sell them.
- Chat Completions and Messages: request and response bodies sent to
/v1/chat/completionsand/anthropic/v1/messagesare never stored. They pass through to the model and are gone once the reply is sent. - Responses API storage: like OpenAI's Responses API, responses created with
storeon (the default) are stored so thatprevious_response_id, conversations, background responses and retrieval work. We store the response's input and output items, the settings it echoes (such as instructions, tools and metadata) and its token usage, and for background responses their stream events. Stored responses are deleted 30 days after they are created. Conversations you create are kept until you delete them. You can delete a response or a conversation at any time through the API (DELETE /v1/responses/{id},DELETE /v1/conversations/{id}), and a request withstore: falsestores nothing. - Zero data retention switch: an account owner or admin can turn on zero data retention under Settings in the dashboard. From then on nothing is stored for the account, and every response and conversation already stored is deleted at once. Features that need stored data (
previous_response_id, conversations, background responses and the Batch API) are then unavailable. - Batch API: files you upload to the Batch API, and the results it produces, are kept for 30 days and can be deleted through the API at any time.
- Request metadata: for every request we store metadata only (timestamps, model, token counts, latency, response status), which we keep for 30 days for billing, abuse prevention, and reliability work.
- Playground: requests you make from the in-dashboard playground are part of your account history and may be stored so you can review them.
- Zero data retention, end to end: every chat model in the catalog is served under the same terms wherever it runs, whether on our own infrastructure or on a serving partner we have bound to them: no retention of request or response content where the model runs and no training on it. Every model is served from Singapore, and serving locations are published in our
/v1/modelscatalog.
6. Retention
We keep account and billing records for as long as your account is active and as needed for accounting obligations. Request metadata is kept for 30 days as described above, and you can ask us to delete it. Stored Responses API responses are deleted 30 days after they are created, Batch API files 30 days after they are uploaded, and conversations when you delete them. When you close your account we delete your personal data within a reasonable period, except what we must keep by law.
7. Security
Traffic to and within the service is encrypted in transit, API keys are stored hashed, and access to production systems is restricted. No system is perfectly secure, so if we learn of a breach affecting your data we will notify you without undue delay.
8. Your rights
You can access and update your account details in the dashboard, and you can ask us to export or delete your data by emailing hello@openscale.so. We will respond within a reasonable time.
9. Changes to this policy
We may update this policy from time to time. For material changes we will notify you, for example by email or a notice in the dashboard.
10. Contact
Privacy questions: hello@openscale.so.