Privacy policy

An email address and a password hash when you create an account. API key identifiers and their last used time. A metering record for every tool call, holding the account, the source, the tool name, the outcome and the timestamp. Billing identifiers from Stripe if you subscribe. Standard server logs.

We do not store the arguments you pass to a tool, and we do not store the data a source returns to you. Metering records what was called and whether it succeeded, not what you asked for or what you received. The one exception is the response cache, which holds upstream responses so they can be served again, and which is never associated with your account.

To authenticate you, to enforce the quota your plan provides, to show you your own usage, to bill you correctly, to diagnose faults, and to keep one customer from degrading the service for others.

One session cookie, set when you sign in, marked http only and same site. It is required for the dashboard to work. There are no advertising cookies and no third party analytics on this site.

Stripe processes payments, so billing details go to Stripe. Our infrastructure provider hosts the servers. We do not sell personal data, and we do not share it with the government sources we proxy beyond what is necessary to make an upstream request, which never includes your identity.

Some government sources publish records that contain personal information, such as contact details on award records or named individuals on filings. We suppress those fields at the gateway before returning a response, so the data we serve is reduced rather than passed through whole.

Metering records are kept so you can see your usage history. Account records are kept while the account exists. Ask us to delete your account and we will remove your personal data, keeping only what we must retain for tax and accounting.

You can export your usage, rotate or revoke keys, or close your account from the dashboard. For anything else, use the contact page.