AI Provider
Sign in

Privacy & security, in plain words

We never store your messages or the replies. Here is how that works, how we protect your account, and the limits of what we can promise.

What we keep

  • Your email addressSo you can sign in and get receipts.
  • A scrambled copy of your keySo we can check it. It can't be turned back into the key.
  • Numbers about each requestWhen it ran, how many tokens it used and what it cost. Tokens are small pieces of words.
  • Payment recordsKept by our payment processor, as the law requires.

What we forget

  • Your messagesEverything you type or paste in.
  • The repliesIncluding the short reasoning step before each answer.
  • Your files and documentsAnd we never use your words to train an AI.
  • Copies in logsOur code never writes message text anywhere. An automated test checks it on every change.

Your text has nowhere to go

Our database holds accounts, keys, credit and numbers about each request. It has no place for message text: no column, no file, no bucket. When a request comes in, our code holds the text in memory just long enough to check it, pass it to the AI and stream the answer back. When the request ends, that memory is freed.

Logs never see message text

Logs are where text usually leaks. Our code only writes short notes like "request failed" or "payment received", with an account number, never the words of a request or reply. We also don't pass along error messages from the AI's servers, because they can repeat part of a message.

An automated test sends a unique marker word through the whole API, error paths and tool calls included. Then it checks every log line, every call to our payment and email providers, and every row of every table in our database. If the marker shows up anywhere, the test fails and the change can't ship.

The AI runs on dedicated GPUs

The AI runs on dedicated GPUs (the chips that do the work) that we rent in US data centers. Our provider's policy is not to store or log what we send them.

Your keys

  • We show a key once, when you make it, and keep only a hash: a one-way scrambled copy mixed with a secret value. We can check a key, but nobody can turn the hash back into the key, us included.
  • Each key can have its own monthly spending cap, and you can switch any key off instantly from the Keys page.
  • The Keys page shows how many different internet addresses used each key today, so you can spot a leaked key. We store those addresses only as hashes, for 7 days.
  • Key and secret checks use constant-time comparisons, so timing can't reveal how close a guess was.

Your account

  • You sign in with Google or a one-time link we email you. Links work once and expire after 15 minutes. There's no password to steal.
  • Your session is a signed cookie that scripts can't read. "Sign out on every device" ends all sessions at once.
  • If someone makes an account with your email before you do, the account isn't really theirs: once you prove the inbox is yours, you take it over, their keys stop working and their sessions end.
  • Every form on this site checks that the request really came from our own pages.

In transit

All traffic uses HTTPS (an encrypted connection). Card details go straight to Stripe's own pages and never touch our servers. Stripe's messages to us are signed, and we reject any that aren't.

Safety checks without storage

Every request and reply is checked for sexual content involving minors: first with fixed patterns, then with a quick yes-or-no question to the same AI. Both checks run in memory as part of the request. If the check can't run, the request is refused rather than let through.

Keeping it fast and fair

There's no free credit, so nobody can farm accounts for free use. On top of that, every plan has limits on requests at once and per minute, and there's a ceiling on how many requests run on our GPUs at the same time, across everyone. When it's full, you get a polite "try again in a few seconds" instead of a slow queue.

What we can't promise

  • We can't control what happens to text on your side: your app, your logs, your browser history.
  • Like every web service, our hosting provider keeps short-lived request records (internet address, time, page requested). These don't include what you sent.
  • We hold no security certifications today. If you need a security questionnaire or a data processing agreement, the Business plan includes one on request.
  • Not for US patient health records: we don't sign HIPAA business associate agreements.

Report a security issue

Email hello@aiprovider.org with "security" in the subject. We read every report. Please give us a fair chance to fix a problem before you share it publicly. See also our privacy policy.