Skip to content

Privacy Policy

What CentRouter stores about you, who else receives it and how long it is kept.

Last updated

What this page covers

This page lists what CentRouter (“we”) stores about you when you use it, who else receives your data, and how long we keep it.

It describes what the service does today. When that changes, this page changes with it.

Account data

For your account we store:

  • Your name and email address, and whether the email is verified.
  • A hash of your password if you set one. We never store the password itself.
  • Your language.
  • The date you accepted the Terms of Service and which version, if they were published when you signed up.
  • If you turn on two-factor authentication: its secret and your backup codes, stored encrypted.
  • Your referral code, and who invited you if you signed up through a referral link.
  • What our staff set for your account: its group and discount, its rate limits, whether it is blocked, and notes written for support.

When our staff change your account by hand, for example with a manual top-up or a block, the action is recorded in an audit log together with who made it.

Sign-in sessions

Each time you sign in, we store a session with the IP address and the browser (user agent) it came from, when it was created and when it expires. You can see your sessions and sign them out in Settings.

When you log in from the CLI, we store hashes of its one-time codes. Expired codes are deleted.

API Keys

For each API Key we store its name, a short prefix, a SHA-256 hash of the key, when it was created, last used and revoked, its Spend Limits and its list of allowed models.

We do not store the key itself, with two exceptions, both stored encrypted:

  • The first key made at sign-up, until you confirm on the Overview that you saved it, for 7 days at most.
  • The key the Portal creates for the Playground. It stays on our server so the Playground can call the gateway for you, and it is never sent to your browser.

Requests

We do not store or log the content of a Request or of its response. Your prompts, anything you attach and the model’s output pass through the gateway and are not kept.

For each Request we record:

  • The time, the API Key and the model.
  • The endpoint, whether it streamed, and the outcome: status, HTTP status and error code.
  • The Token counts by kind, and whether they were estimated.
  • The prices, the charge, the amount saved and the latency.
  • Which of our model sources answered, how many were tried, and what the Request cost us.

Orders and payments

  • For each Order: the USD amount and any bonus, the amount and currency you were asked to pay, the Exchange Rate used for a Rupiah Order, the Payment Provider and Payment Method, the Payment Provider’s reference, the checkout instructions shown to you (for example a QR code or a payment link), its status and its times.
  • From the Payment Provider’s confirmation: its reference, the status, the amount paid and the currency.
  • Which Vouchers you redeemed and when.
  • The Ledger: every change to your Balance, including top-ups, usage, Vouchers, adjustments and Referral Rewards.

Card numbers and other payment details are entered on the Payment Provider’s own page or in your banking app. They never reach us, and we do not store them.

Cookies and browser storage

We set only the cookies the Portal needs to work:

  • Sign-in cookies: one that keeps you signed in, a short-lived one during two-factor sign-in, and one that remembers a device if you choose to trust it.
  • locale: your language.
  • sidebar_state: whether the sidebar is open.
  • gs_ref: the referral code from the link that brought you here, kept for 30 days so the invitation can be linked to your account when you sign up.

Your browser’s local storage holds your theme (dark or light), that you copied a tool config on the Setup page, and which announcements you dismissed. These stay in your browser.

We use no advertising or analytics cookies.

The sign-up page loads Cloudflare Turnstile, which checks that a person is signing up. Cloudflare may use its own cookies and browser storage for that check.

Who receives your data

  • Model providers. To be answered, the body of your Request is sent to a provider that runs the model you chose. The provider receives what you put in the Request. We do not send it your name, email address, API Key or IP address. How long a provider keeps that content is decided by the provider.
  • Our email delivery provider. It receives your email address and the content of the emails we send you: verification, password reset, email change, low Balance and payment confirmation.
  • Cloudflare, on the sign-up page. Cloudflare Turnstile receives your IP address and details of your browser to check that a person is signing up.

The service sends your data to no one else. The companies that host the service for us store it on our behalf.

How long we keep it

We keep your data for as long as your account is open. Nothing is deleted automatically while it is open.

You can close your account yourself in Settings at any time. Closing is immediate and cannot be undone. It deletes:

  • Your name, email address and profile picture. The account record stays, with placeholders in their place.
  • Your password hash, your two-factor secret and backup codes, and every sign-in session with its IP address and browser.
  • CLI logins, password-reset links and the stored copies of API Keys.
  • Your referral code, the notes our staff wrote about your account, and your email address in the audit log entries about your account.

It keeps, because we need them for our accounting:

  • Your Requests, Orders and Ledger entries. They hold IDs, Token counts, amounts and times, and no name, email address or prompt content.
  • Your API Keys as revoked records: the name you gave each key, its prefix and its hash. Past Requests refer to them.
  • The audit log entries about your account, without your email address.
  • Your language, your group and rate limits, when you accepted the Terms of Service, and which account invited you.

After closing, the same email address can sign up again as a new account.

If you cannot sign in to close your account, write to support@centrouter.com.

What you can do yourself

  • Change your name, password and language in Settings.
  • Change your email address in Settings, if your account has a password. The new address must be verified before the change takes effect.
  • See your sign-in sessions and sign them out in Settings.
  • Revoke any API Key on the API Keys page.
  • Export your Activity as CSV.
  • Close your account in Settings.

Changes to this page

When what we store or who receives it changes, we update this page. The date at the top shows when it last changed.

Contact

Questions about your data: write to support@centrouter.com.

Also read: Terms of Service