Legal

Privacy Policy

Last updated

NeverMetered is an inference API, so the most sensitive thing you send us is your prompts. We don't store them and never train on them. This policy explains what we do keep (mostly account details and request metadata), why, and your rights.

Contents
  1. Who we are
  2. Your prompts and outputs
  3. Data we collect
  4. Legal bases
  5. Cookies and local storage
  6. Who we share data with
  7. International transfers
  8. How long we keep data
  9. Your rights
  10. Security
  11. Children
  12. Changes to this policy

1.Who we are#

Keep Pushing Forward Ltd (Offices in the UK) runs NeverMetered and is the controller of the personal data described here. For anything about privacy, email legal@nevermetered.com.

2.Your prompts and outputs#

We don't store your prompts or the model's outputs, and we never use them to train models. Here is exactly what happens to them:

  • Processed in memory. Requests pass through our API gateway to an inference server, which generates the response and streams it back. Content isn't written to our database or to our logs; logs record request metadata such as ids, timings, token counts and the number of messages.
  • Short-lived prefix cache. To make follow-up requests faster, inference servers keep the intermediate computation for recent prompts (a “KV cache”) in GPU and system memory. It is not a copy of your text in readable form, is never returned to anyone as output, is overwritten as new requests arrive, and is lost when a server restarts. We route your conversations to the same server for a short time so the cache can help you.
  • Responses API objects. If you use the OpenAI Responses API without store: false, the inference server keeps the response in memory so you can continue the conversation with previous_response_id, retrieve it or delete it through the API. Stored responses are only available to your account, are held in a size-limited in-memory store, and disappear when evicted to make room, when you delete them, or when the server restarts. They are never written to disk. We keep a record of which account owns a response id for 7 days.
  • Staff access. Our team can see request metadata (for support, capacity planning and abuse prevention) but has no store of your content to look at.

3.Data we collect#

CategoryWhatWhy
AccountName, email address (and a normalised form of it, to detect duplicate accounts), password hash, email verification status, account roleTo create and secure your account and contact you
Security and abuse preventionIP address and browser user agent when you sign up and for each sign-in session; a random device identifier stored in a cookie and linked to the accounts that use that browser, with the last IP seen; sign-in rate-limit counters; daily free-request counters per account, device and network (IPv4 address or IPv6 /56 prefix)To keep accounts secure, stop automated sign-ups and enforce one free allowance per person
API keysA one-way hash of each key, a short prefix so you can recognise it, its name, limits and when it was last used. We can't recover a key.To authenticate API requests
Usage metadataFor each API request: time, API key, model, endpoint, streaming or not, status and error code, finish reason, input, cached input, output and reasoning token counts, queue time, time to first token, duration, and which server handled it. Plus daily totals.To run and schedule the service, show your usage dashboard and CSV exports, plan capacity and investigate problems
BillingStripe customer id, plan, subscription status and renewal date, invoice amounts, tax, currency and links to Stripe-hosted invoices. Card details go directly to Stripe; we never see or store them.To sell plans, grant access and keep tax and accounting records
Support and auditEmails you send us; a log of admin and billing actions taken on accountsTo help you and to keep an accountable record of changes

5.Cookies and local storage#

NamePurposeLifetime
Session cookieKeeps you signed inUp to 30 days
nf_didA random device identifier used for security and to share one free allowance per device. It isn't used for tracking across other sites.2 years
Theme and layoutRemembers light/dark mode and sidebar state (browser local storage, never sent to us)Until you clear it
Cloudflare TurnstileBot check on sign-up, sign-in and password reset formsSet by Cloudflare

All of these are strictly necessary for the service. We don't use advertising cookies or third-party analytics trackers.

6.Who we share data with#

We don't sell personal data. We share it only with service providers that help us run NeverMetered, under contracts that limit their use of it to providing their service to us:

ProviderPurposeData involved
StripePayments, invoicing, tax calculation and the billing portalName, email, billing address, tax ids, payment details, purchase history
Cloudflare (Turnstile)Bot protection on sign-up, sign-in and password resetIP address, browser and device signals
Our cloud and GPU hosting providersHosting of the website, API and inference serversAll account and usage data; prompts and outputs in memory while requests run

We may also disclose data if the law requires it, to protect people or the service from harm or fraud, or as part of a merger or sale of the service (with notice to you).

7.International transfers#

Our providers may process data in countries other than yours. Where data about people in the UK, EEA or Switzerland is transferred to a country without an adequacy decision, we rely on appropriate safeguards such as standard contractual clauses.

8.How long we keep data#

  • Account, API key, security and usage data: while your account is open. When you close your account, we delete it along with its keys, sessions, devices and usage records.
  • Daily free-request counters: 7 days. Platform performance metrics are aggregate and contain no personal data; we keep them for 90 days.
  • Billing records (invoices and payment history, held in Stripe): as long as tax and accounting law requires, typically up to 7 years.
  • Abuse prevention: if an account is closed for abuse, we may keep identifiers such as its email address, device ids and network identifiers for up to 12 months to stop the same abuse from returning.

9.Your rights#

Depending on where you live, you can ask us to:

  • give you a copy of your personal data (your usage and request history can also be downloaded as CSV from the dashboard at any time);
  • correct inaccurate data (you can change your name in your account settings; contact us to change your email address);
  • delete your data and close your account;
  • restrict or object to processing based on legitimate interests; and
  • transfer your data to another service.

Email legal@nevermetered.com from the address on your account. We'll respond within one month. You also have the right to complain to your local data protection authority. California residents have the rights to know, delete and correct, and we don't sell or share personal information for cross-context behavioural advertising.

10.Security#

Traffic is encrypted with TLS. API keys are stored only as hashes, passwords are hashed, credentials for our inference servers are encrypted at rest, and access to production systems is restricted. Sign-in and sign-up are rate limited. If we become aware of a breach affecting your data, we'll notify you and the relevant authorities as the law requires.

11.Children#

NeverMetered is a developer service and isn't directed at children. You must be at least 16 to create an account. If you believe a child has given us personal data, contact us and we'll delete it.

12.Changes to this policy#

We'll update this policy when our practices change and revise the “Last updated” date. If a change materially affects how we use your data, we'll email you before it takes effect. See also our Terms of Service.

Contact

Keep Pushing Forward Ltd, Offices in the UK. Email legal@nevermetered.com.