Privacy: what Steakpedia keeps about you

Privacy

You can read all of Steakpedia without an account. If you create one, we keep very little, we never sell it, and you can delete all of it with one button. Last updated Nov. 1, 2026.

What we keep if you create an account

You sign in with Google. Google tells us only three things: your email address, your name and your Google account ID. We receive nothing else from Google: not your contacts, your files or your password.

We store:

your email, your name and your Google ID;
the language of the page you signed in from;
whether you ticked the newsletter box (it is never ticked for you) and when you ticked or unticked it;
the date you joined and your last visit;
your steak log, the doneness notes you save in the Steak log tool, copied from your device so it follows you to your phone and computer;
a record of your open sign-in (see cookies below).

Waiting list, city editors and suggestions

Member spots are limited at first. If they are full when you sign in, we keep your email address, your name, your Google ID and the language of the page on a waiting list, only to tell you when more spots open. You are not a member until then and nothing else is stored. Write to hello@steakpedia.com and we delete the entry.

You can apply to be the editor of one city. We keep what you wrote in your application (up to 280 characters) and the city you chose until we answer; you can withdraw it from your account menu at any time. If you are approved, a “City editor” badge appears in your menu. We never show your name or email publicly.

Approved editors can send suggestions about their city. We keep the text of each suggestion, and the restaurant name if you add one, so we can review it. Nothing is published until we check it against sources.

Deleting your account with the button also deletes your application and your suggestions.

Where it is kept

In a database on Cloudflare (D1), the service that also hosts Steakpedia. Cloudflare processes the requests to the site, including your IP address, to deliver it and to protect it from abuse. Google handles the sign-in itself, on its own page.

Cookies and the sign-in

Signing in sets one cookie, __Host-sp_s. It is HttpOnly (page scripts cannot read it) and lasts 60 days; each visit renews it, and signing out removes it. It holds a random code, and our database keeps only a scrambled copy of that code. A second cookie lasts 10 minutes while you are in the middle of signing in with Google and then disappears.

There are no advertising cookies. Steakpedia uses Google Analytics to count visits and see which pages are read; it sets its own cookies, and we do not send it your email, your name or anything from your account.

Without an account

The Steak log, the passport and your settings live in your browser and stay on your device. The doneness photo checker sends the photo to an AI model on Cloudflare to read the doneness, does not store it, and does not need an account.

Who else gets it

No one. We do not sell or rent your data, we show no ads and we do not share it with restaurants, brands or other companies. The only services involved are the ones named above, to run the site: Cloudflare and Google. Steakpedia is independent and is not connected to any restaurant.

Only if you tick the box. We use your email for the newsletter and for nothing else. Untick it in the account panel at any time and it stops.

Delete everything

Open the account panel (the person icon in the header) and press Delete my account. It removes at once your email, name, Google ID, steak log on our servers and every sign-in, on every device. The log on the device you are using stays there; you can clear it in your browser. You can also write to us and we will do it.

Questions and your rights

To ask what we hold about you, to correct it or to have it deleted, write to hello@steakpedia.com. If we change this page, the date at the top changes. For what you may do with the site’s content, see Using Steakpedia.