Privacy
Last updated 31 July 2026
The short version
There are two groups of people involved, and they are treated very differently. You, the account holder, have an account with an email address and a password. Your visitors, the people whose browsers call the API, have no account and are never identified. We resolve their approximate location, return it to you, and drop their IP address.
Your visitors
When a request reaches the API, the caller's IP address is used in memory to
determine a location and is then discarded. It is returned to you in the
response if your plan includes the ip field, and it is written
nowhere: not to a database table, not to a log line, not to an error report.
That is not a policy we intend to follow, it is a check that runs on every build. A commit that puts a visitor address into a table or a log fails CI.
The same applies to an address you send us yourself. If you use the
ip parameter to ask about somebody other than the caller, that
address is looked up in memory, returned to you, and discarded. It is not
recorded either.
Those lookups use the DB-IP Lite City database, made available by DB-IP under the Creative Commons Attribution 4.0 licence. It is a static file we hold a copy of. Nothing about your request is sent to DB-IP or to anyone else.
What is kept about a request, and for how long:
| What | Where | Kept for |
|---|---|---|
| Count of requests per key | Database | Indefinitely, as billing history |
| Country, calling site, status code | Redis | 24 hours |
The response body sent back, with ip removed | Redis | 24 hours |
The 24-hour records exist so you can debug your own integration on your project page, and so we can answer a support question with what actually happened. They expire on their own.
Your account
We store what an account needs and nothing beyond it:
- Your email address and the name you gave at sign-up.
- A hash of your password. We never see the password itself.
- Your active sessions, including the IP address and browser you signed in from. This is the one place an IP address is stored, it is yours rather than a visitor's, and it is there so you can see where your account is signed in.
- Your projects, API keys and their origin allowlists.
- Your plan, subscription status and billing period.
- A log of significant account actions, such as revoking a key.
Payments
Payments are handled by PayPal. We never see or store card numbers or bank details. What we keep is the identifier PayPal gives us for your subscription, so we know which plan you are on. PayPal's handling of your payment details is covered by their privacy policy.
Who else touches the data
- Cloudflare sits in front of the API and provides the country and city estimate.
- PayPal processes payments.
- Resend delivers account email, such as usage warnings.
- Sentry receives error reports when it is enabled. Reports carry a key prefix, never a full key and never a visitor address.
We do not sell data, and there is no advertising or analytics tracking on the API.
Cookies
The dashboard sets a session cookie so you stay signed in, and a preference for light or dark theme. That is all. There are no tracking or advertising cookies on this site or in the dashboard.
Your rights
You can see everything we hold about your account in the dashboard. Email [email protected] to request a copy of your data or to delete your account. Deleting an account removes your projects, keys and account record; billing records are kept where we are required to keep them.
Where it runs
The service runs on servers in a single region, behind Cloudflare. If you need to know the specific location for a data protection assessment, ask and we will tell you.
Changes
If this page changes in a way that affects what we collect, we will email account holders rather than quietly updating the date at the top.
Contact
Get in touch or email [email protected].