Privacy

• Your account. Your name, your email address, and a hash of your password. We never store the password itself.
• Your session. A cookie that keeps you signed in.
• Your API keys. The name you gave each key, when it was created, and when it was last used. Keys themselves are stored only as hashes — we cannot read one back to you, which is why a new key is shown once and only once.
• How much you use the API. For each key, a count of requests and errors per endpoint per day. Counts, not requests: we do not store the parameters you sent or the recipes you got back.

Our servers keep short-lived request logs, as any web server does.

We use Guvnor, a monitoring service, to find out which requests are slow and which are failing. It receives the path of each request, how long it took, the status code, and the details of any error. On the website it also records which pages you moved between, and stores a random session id in your browser so the steps of one visit line up. If you are signed in, API requests are tied to your account and to the key you used.

Query strings are stripped before any of this leaves our servers, so what you typed into a search is not part of it. Paths are not stripped: a request for a single recipe includes that recipe's id.

On the website this is off until you agree to it. We ask the first time you visit, and you can change your mind whenever you like — see below. API requests are measured either way; there is no browser to ask, and we cannot run the service without knowing what it is doing.

• No advertising, and no trackers that follow you to other sites.
• No profile of what you search for. Search terms stay on our servers.
• No payment details. The API is free.

Nobody buys it and nobody is sold it. Your data sits in our database and on the servers that run this site, both with infrastructure providers who process it on our behalf and under contract. The performance data described above goes to Guvnor on the same terms.

We disclose data otherwise only where the law requires it.

One cookie keeps you signed in. A second is set when you press Run in the documentation: it holds the API key that page created for you, so the request is made with your own key. Both are necessary for the site to work.

A third remembers whether you agreed to the monitoring above, so we only ask once. There are no others.

If you did agree, that monitoring keeps a random session id in your browser's local storage. It identifies a visit, not you, and it is not used for advertising. Change your choice.

We keep your account for as long as you have one, and usage counts for 30 days.

You can revoke any API key yourself from your dashboard, which takes effect immediately. To get a copy of your data, or to have your account and everything attached to it deleted, write to chris@pullpanda.io.

The recipes the API serves are gathered from public recipe pages and are not personal data about you. Each one links back to the page it came from. If you publish recipes and want your site excluded, write to the same address — see about.

If this policy changes in a way that matters, we will say so here before it takes effect.