01
The short version
- We only ask for information we actually need.
- We never sell it and we never trade it.
- One thing here asks your permission first, and that is counting your visit. It is off until you press yes. Ignore the question and it stays off for good.
- You can email us any time and ask what we hold, or ask us to erase it.
- The store is open and takes real payments. Customer accounts and personalised video requests are not open, and parts of this page describe what will happen when they are.
02
What we collect right now
Today the site is simple, so there is very little.
- The contact form. Whatever you type into it. That is normally a name, an email address and a message.
- Newsletter signups. Your email address, so the newsletter has somewhere to go.
- Arcade scores, if you post one. After a game you can type a display name and put your score on the public leaderboard. That name and that score are saved and shown to other visitors. Play as much as you like without typing one and nothing that says anything about you is kept. Starting a run does write a line in our database, and all it holds is a random ticket number, the number the game used to build the level, and the time.
- Ordinary web traffic. The site is hosted by Cloudflare. Like every web host, Cloudflare handles the request your browser makes, which includes your internet address, so the page can reach you and so the site can defend itself.
- Counting your visit, if you agreed to it. Google Analytics records which pages you read, in what order and roughly for how long, what kind of device and browser you used, whatever site sent you here, and the country and usually the city Google works out from your address. None of it happens until you press the button that says count me.
- Buying something. The checkout collects the email address you type and the delivery address the parcel has to go to, and we keep a record of what you ordered, what it cost, and the identifiers we need to find the payment again. It is written down only after Stripe confirms the money moved.
That is the whole list. No account and no password, because there is nothing to sign in to. And no card details, because those are typed on a page Stripe serves from Stripe's own site and they never reach this one. If anybody ever emails you asking for a card number in our name, it is not us.
03
Every single thing, one at a time
The sections above are the summary. This is the whole of it: every piece of information this site handles, what happens to it, why we are allowed to, and how long it stays. Nothing is left out to keep the page short.
It is generated from the same file the code reads, so it cannot quietly fall behind what the site actually does. If a form starts asking for something new, it appears here on the same day.
When you send a message through the contact form
So a real person can read what you wrote and reply to you.
What is collected
- Your name, as you typed it
- Your email address
- The topic you chose from the list
- Your subject line, if you wrote one
- The message itself
Where it goes
A row in our own database, which is Cloudflare D1. The columns are name, email, subject, message, topic, a status the owner updates as it is dealt with, and the time it arrived.
Not your IP address, not your browser, not your device, not the page you came from. None of those are written down.
Why we are allowed to
We need it to run the site sensibly, and it does not override your rights.
A message about buying something is handled under Article 6(1)(b) instead, because answering it is a step you asked us to take before a purchase.
Article 6(1)(f), legitimate interests
How long it is kept
No period has been decided yet, and we would rather say so than print a number nobody has agreed to.
Also seen by Resend and Google LLC, each of which is doing a job for us and none of which may use it for anything else.
When you join the mailing list
So we can email you when there is something worth emailing about.
What is collected
- Your email address
- A note of which form you used, so we know where people are joining from
Where it goes
A row in Cloudflare D1 holding your address, a lowercased copy of it used to stop the same address joining twice, a one time confirmation token, a permanent unsubscribe token, and the times you joined, confirmed and left.
Not your IP address and not your name, because the form never asks for either.
Why we are allowed to
You asked for it, and you can change your mind at any time.
The list is double opt in. Your address is stored the moment you submit the form, and nothing is sent to you as marketing until you open the link in the confirmation email. You can withdraw consent at any time from the link in any email.
Article 6(1)(a), consent
How long it is kept
No period has been decided yet, and we would rather say so than print a number nobody has agreed to.
One part of this is decided. If you unsubscribe, the row is kept rather than deleted, with the date you left recorded on it. That is not us hanging on to you: a deleted row would let the same address be added again by mistake, and keeping it is what makes the opt out stick. Ask us to delete it outright and we will.
Also seen by Resend, each of which is doing a job for us and none of which may use it for anything else.
The bot check on both forms
To tell a person apart from a script, without making you solve a puzzle.
What is collected
- Your IP address
- A token the bot check widget creates in your browser
Where it goes
Nothing. We do not write either of these down. They are sent to Cloudflare, which answers with a yes or a no, and that answer is all we keep long enough to act on.
Why we are allowed to
We need it to run the site sensibly, and it does not override your rights.
Without it both forms fill up with automated submissions within days, and the newsletter becomes a way of sending confirmation emails to addresses that never asked for them.
Article 6(1)(f), legitimate interests
How long it is kept
No period has been decided yet, and we would rather say so than print a number nobody has agreed to.
Nothing to keep, because nothing is stored on our side.
This is the only place where we take your IP address and hand it to somebody else. It goes to Cloudflare as part of the check and nowhere else. Your browser gives its own address to any server it talks to, including ours and, while the analytics tag is on the page, the ones at Google, and that is a fact about how the internet works rather than something we do with it.
Also seen by Cloudflare, Inc., each of which is doing a job for us and none of which may use it for anything else.
Stopping one person from flooding a form
So one script cannot send ten thousand messages and bury the real ones.
Where it goes
A one way hash of it, never the address itself. The address is combined with the name of the form, run through SHA 256, and cut to the first 128 bits. What is written down is that string and a count, in Cloudflare KV, and it deletes itself once the time window has passed.
The IP address itself is never written to storage anywhere on this site.
Why we are allowed to
We need it to run the site sensibly, and it does not override your rights.
A hash cannot be turned back into an address. It exists so that two submissions from the same place can be recognised as the same place, which is the whole of what a rate limit needs to know.
Article 6(1)(f), legitimate interests
How long it is kept
Minutes. The counter is given a lifetime slightly longer than the window it guards, and Cloudflare removes it automatically when that expires.
When we send you an email
To send the confirmation, acknowledgement or newsletter you asked for.
What is collected
- The address we are sending to
- What the email says
Where it goes
A line in our own log recording the address, which template was used, the subject, whether it was sent or failed, the id our email provider gave it, and when. It exists so the owner can tell whether a message you were expecting actually went out.
No open tracking, no click tracking, no tracking pixel. We do not know whether you opened anything.
Why we are allowed to
We need it to run the site sensibly, and it does not override your rights.
For marketing email the basis is your consent, and the unsubscribe link in every one of them is how you take it back.
Article 6(1)(f), legitimate interests
How long it is kept
No period has been decided yet, and we would rather say so than print a number nobody has agreed to.
Also seen by Resend, each of which is doing a job for us and none of which may use it for anything else.
When you put a score on the arcade leaderboard
So there is a real leaderboard with real people on it rather than invented names.
What is collected
- The display name you type into the box, if you choose to type one
- Your score and a summary of the run it came from
Where it goes
A row in Cloudflare D1 holding the name as you typed it, a lowercased copy of it used to group your entries together, the score, how long the run lasted, how many things were wrecked, how many treats were caught, how many secrets were found, and the time you posted it. There is also a row recording that a run was started, which holds only a random identifier, the number the game used to build the house, and the time. Neither table holds an IP address, a device identifier, or anything else about you.
Not your IP address, not your browser, not your device, and no account of any kind, because there is nothing to sign in to.
Why we are allowed to
You asked for it, and you can change your mind at any time.
Nothing is posted unless you type a name and press submit. Playing the game sends nothing at all beyond asking for a run to be started, and you can play as much as you like without ever appearing anywhere. If you agreed to be counted, the fact that a score was accepted, which game it was, the score and how long the run lasted are also sent to Google Analytics, tied to the same analytics identifier as the rest of your visit and to nothing else. Not your display name, not the run id. Say no and none of it is sent.
Article 6(1)(a), consent
How long it is kept
No period has been decided yet, and we would rather say so than print a number nobody has agreed to.
The board is public and meant to stay, so a score is kept until somebody asks for it to go. Write to us with the name and roughly when you posted it and it will be removed.
This is the only place on the site where something you typed is shown publicly to other visitors. Choose the name accordingly.
Also seen by Google LLC, each of which is doing a job for us and none of which may use it for anything else.
Counting your visit, but only if you said yes
To find out which pages people actually read, so effort goes into the ones that are worth it rather than the ones that felt important.
What is collected
- Which pages you looked at, in what order, and for roughly how long
- Whether you had been here before, which is what the cookie is for
- Your rough location, worked out by Google from your IP address, at the level of a country and usually a city
- What kind of device and browser you are using, and what size the screen is
- The site or search that sent you here, if there was one
Where it goes
Nothing on our side. It goes to Google Analytics and lives in their system, and what we see there is counts and charts rather than a list of people. Two cookies are set in your browser to make the counting work, and they are named on the cookie page.
Not your full IP address. Google truncates it before it is stored and we never see it at any point. No name, no email address, and nothing you typed into a form. Advertising features are switched off, so nothing here follows you to another site.
Why we are allowed to
You asked for it, and you can change your mind at any time.
This is the only thing on the site that asks. Nothing is stored and your visit is not counted until you press the button that says count me. Until you do, the tag runs with every kind of storage denied, and the only thing it tells Google is that the answer is no. Ignoring the question is the same as saying no, permanently. You can change your mind either way from the cookie page.
Article 6(1)(a), consent
How long it is kept
No period has been decided yet, and we would rather say so than print a number nobody has agreed to.
Set inside Google Analytics rather than here. The property retains individual event records for a fixed period and then keeps only the aggregate counts, and the owner has to choose that period in the Google console. Until that choice is recorded here, this page will not state a number it cannot back.
Everything else on this list reaches another company because you asked us for something: a reply, an email, a form that works. This is the only one that tells another company you were here when you asked us for nothing, which is exactly why it is the only one that asks your permission first. Say no and the site behaves identically.
Also seen by Google LLC, each of which is doing a job for us and none of which may use it for anything else.
When you buy something
To take the payment, send you the thing, and be able to sort it out afterwards if it goes wrong.
What is collected
- The email address you give at the checkout
- The delivery address the parcel has to go to
- What you ordered, how many, and what it cost
Where it goes
A row in our own database, which is Cloudflare D1, written only after Stripe confirms the payment. It holds your email, the delivery address exactly as Stripe passed it to us, the items and the amounts, an order reference, and the Stripe identifiers we need to find the payment again if something goes wrong.
Your card number, expiry date and security code. None of them reach this site at any point. They are typed on a page Stripe serves, and what comes back to us is the fact that a payment succeeded. We also do not store your IP address against an order, and there is no account and no password.
Why we are allowed to
You bought something, or asked about buying something, and we cannot do it without this.
Article 6(1)(b). We cannot send you a parcel without an address, and we cannot answer a question about your order without a record of it. Some of it is also kept because the law says a business must keep records of what it sold.
Article 6(1)(b), performing a contract with you, or taking steps you asked for before one
How long it is kept
No period has been decided yet, and we would rather say so than print a number nobody has agreed to.
An order record has to outlive the order. The records used to defend a payment dispute, meaning the order itself, the delivery address, the evidence that it arrived and the emails about it, are kept for 540 days from the payment and are then deleted, which is exactly what the chargeback policy commits to. Where tax law requires a sales record for longer, that part is kept for longer, and how much longer depends on where the business is registered, which is not settled yet. You can ask what we hold about you at any time.
The single most useful thing to know here is that the card details are not ours to lose. If you are ever asked for a card number by email, by anyone claiming to be us, it is not us.
Also seen by Stripe, Inc., Resend and Cloudflare, Inc., each of which is doing a job for us and none of which may use it for anything else.
Simply visiting the site
To serve you the page, and to keep the site up.
What is collected
- The usual things any web server receives: your IP address, the page you asked for, the time, and what your browser says it is
Where it goes
Nothing by us. Cloudflare handles these as part of hosting and applies its own retention, and we do not have a copy of them in any database of ours.
Why we are allowed to
We need it to run the site sensibly, and it does not override your rights.
A web server cannot answer a request without knowing where to send the answer.
Article 6(1)(f), legitimate interests
How long it is kept
No period has been decided yet, and we would rather say so than print a number nobody has agreed to.
Set by Cloudflare, not by us. Their policy is linked below.
Also seen by Cloudflare, Inc., each of which is doing a job for us and none of which may use it for anything else.
And here is what we never collect
- No advertising, no ad networks, no retargeting, no conversion pixels. Google Analytics is here, but every advertising feature of it is switched off and the ad click identifiers are stripped from anything it sends.
- No profiling, and no automated decision making that has any effect on you.
- No location data beyond the IP address that any web server receives, and the country and city that Google Analytics works out from it if you agreed to be counted.
- No special category data. We never ask about health, beliefs, politics, ethnicity, sex life or anything similar, and you should not put any of it in the message box.
- No payment details. Your card number, expiry and security code are typed on a page Stripe serves from their own site. They never touch this one, they are never sent to us, and we could not store them if we wanted to.
- No account and no password, because there is no way to sign in. You can buy something here without registering for anything.
- No social media buttons or embeds, so no other company learns which pages you read here. The four platform icons are drawings served from this site and they load nothing.
- No fonts loaded from anybody else. Every typeface here is served from this site.
- Nothing at all is counted unless you press the button that says so. Ignore the question and analytics stays off permanently.
04
Your IP address
Every device on the internet has an address, and yours is sent to any website you visit, because otherwise the page has nowhere to go. That much is unavoidable and true of every site you have ever opened.
What matters is what a site then does with it, so here is exactly what this one does, in all four cases.
- When you submit either form, your address is sent to Cloudflare as part of the check that tells a person apart from a script. This is the only time this site itself takes your address and hands it to somebody, and it goes to Cloudflare and nowhere else.
- To stop one person flooding a form, your address is scrambled with a one way hash the instant it arrives, and only the scrambled version is written down, alongside a count, in storage that empties itself within minutes. The scrambling cannot be undone.
- Simply loading a page, your address reaches Cloudflare because it is the server answering you. We keep no copy of it.
- The analytics tag, whatever your answer is. The tag file comes from Google, so your browser fetches it from Google, and every server a browser talks to sees the address it is talking from. We are not the ones sending it and we never see it. Until you agree, all the tag says back is that the answer is no: no cookie, and nothing about your visit. If you do agree, Google turns your address into a country and usually a city, cuts the address short before storing it, and hands neither back to us.
Your IP address is never written into any database of ours in a form we could read back. Not against your message, not against your subscription, not anywhere. There is no column for it, which is a stronger promise than a sentence in a policy: there is nowhere to put it.
05
Where that information lives
Messages and newsletter signups are saved in a small database run by Cloudflare, called D1. It sits behind the website and is not open to the public. A copy of each contact message is also sent to us by email through a company called Resend, so a person actually sees it.
Orders are written to the same Cloudflare database after Stripe confirms a payment. A row holds the email address you gave at the checkout, the delivery address, the items and amounts, an order reference and the Stripe identifiers. No card details of any kind, because none of them ever reach this site.
Both forms are protected by Cloudflare Turnstile, a bot check. Its job is to tell a person apart from a script, which is what stops the inbox filling with junk.
We do not sell your information. There is no version of this where we do.
06
What we would collect later
Two of these were plans until the shop opened, and they are described for real in the section above rather than here. What is left below is genuinely not happening yet.
- Custom video requests, if they open. The details that make the video make sense: names, how to say them, the occasion, and the message you want in it.
- Customer accounts, if they open. An email address and a way to sign in. There are none today, and you can buy something here without making one.
On the day any of this becomes real, this page changes first.
07
Why we collect it
Only to do the thing you asked for. A message so we can reply. An email address so the newsletter arrives. Nothing is gathered because it might be handy one day.
There is one exception and it is worth naming. Counting visits is for us rather than for you: it tells us which pages people actually read, so the work goes into the ones that are worth it. That is exactly why it asks first, why the answer starts as no, and why saying no changes nothing else about the site.
We do not sell your information. We do not trade it. We do not hand it to advertisers.
08
How long we keep it
We keep information for as long as it is useful for the reason you gave it, and then we let it go. If you ask us to delete something sooner, we will.
Owner suppliedThe exact length of time contact messages and newsletter records are kept. No number is written here, because none has been decided, and a guessed retention period is a promise waiting to be broken.
09
Who else touches it
A few companies help run the site. Each one gets only what it needs, and each publishes a privacy policy of its own that you are welcome to read.
- Cloudflare. Hosts the site, serves the pages, runs the D1 database the forms write to, and runs the Turnstile bot check.
- Resend. Delivers our email. Mail from us arrives from info@potatoandhash.com.
- Google. Runs the inbox a contact message lands in, so a person can read it. Also runs Google Analytics, which counts your visit if, and only if, you agreed to be counted.
- Stripe. Takes the payment when you buy something, and collects the delivery address it needs to send it to. Stripe is the only party that ever sees your card details: they are typed on a page Stripe serves, not on this site, and what comes back to us is the fact that a payment succeeded.
10
Information leaving your country
Everyone who helps run this site is a company in the United States, so information about you reaches the United States. That is worth saying plainly rather than burying, because if you are in the United Kingdom or the European Union it is something you have a right to know before you type anything in.
- Resend, in the United States. Delivers the emails this site sends. Their privacy policy.
- Google LLC, in the United States. Runs the inbox that receives messages sent through the contact form, and provides Google Analytics, which counts visits if you agreed to be counted. Their privacy policy.
- Cloudflare, Inc., in the United States. Hosts the site, serves it, runs the database, and provides the bot check. Their privacy policy.
- Stripe, Inc., in the United States. Takes the payment when you buy something, and collects the delivery address it needs to be sent to. Stripe is the only party that ever sees your card details. They are typed on a page Stripe serves, not on this site. Their privacy policy.
Each of them publishes terms covering transfers of this kind. The agreements have not been signed yet, and until they are, this page will not claim a safeguard that is not in place. It is listed under still to be supplied, further down, so it cannot be quietly forgotten.
11
Analytics, only if you say yes
This page used to say there was no analytics here at all. That was true and it is not any more. Google Analytics was added on 9 August 2026, and this page changed on the same day, because a policy that says one thing while the site does another is worse than no policy.
Here is how it works. The first time you arrive, a bar at the bottom of the page asks whether we may count you. It has two buttons, both the same size, and one of them says no. Until you press one, every kind of storage the tag could use is denied, no cookie is written, and your visit is not counted.
One honest detail, because it is the sort of thing a policy usually leaves out. The tag itself does load either way, so Google knows a browser asked for it. While the answer is no, the only thing the tag reports back is that the answer is no. Nothing about which pages you read goes with it and nothing is kept on your device.
Ignoring the question counts as no, and it sticks. There is no second ask, no countdown, and no version of this where scrolling past the bar is treated as agreement. A visitor who never answers is never counted, on this visit or any other.
It is switched off by default everywhere, not only in the countries whose law demands it. Asking politely in some places and counting quietly in the rest is the usual arrangement, and it is not one we wanted to be part of.
If you do say yes: two cookies, which pages you read and in what order, roughly how long for, your device and browser and screen size, whatever site or search sent you here, and the country and usually the city Google works out from your address. Google cuts the address short before storing it and we never see it. Every advertising feature is switched off, so none of this follows you to another site.
You can change your mind either way, at any time, with the button on the cookie page. It takes one press and nothing else about the site changes whichever answer you give.
12
Cookies and the bot check
A cookie is a small note a website leaves in your browser so it can remember something later. This site sets two, both of them Google Analytics cookies, and neither one is written until you agree to be counted. Say no, or say nothing, and neither ever exists. There are no advertising cookies at all.
The Turnstile bot check on our two forms is run by Cloudflare and looks at signals from your browser to decide whether you are a person. The arcade also keeps a few small values in your browser, which are not cookies and are never sent anywhere, and your answer about being counted is kept in the same way. That answer is the only reason you are asked once rather than on every page.
The cookie page goes through all of this properly, names every cookie and every stored value, and is where you change your answer about being counted.
Read the cookie page
13
Seeing it, or deleting it
These are yours under United Kingdom and European Union data protection law. In practice we will do all of them for anybody who asks, wherever you live, because sorting people by jurisdiction before deciding whether to respect them is not a way we want to run anything.
- See it. Ask for a copy of everything we hold about you.
- Fix it. Tell us something is wrong and we will correct it.
- Delete it. Ask us to erase it. We will, unless a law says we have to keep it.
- Pause it. Ask us to stop using it while something is being sorted out.
- Take it with you. Ask for it in a form you can hand to somebody else.
- Object. Tell us to stop using it where we rely on legitimate interests.
- Change your mind. Withdraw consent at any time. It does not undo anything already sent, and it stops everything after.
- Complain. Take it to your data protection authority. In the UK that is the Information Commissioner. In the EU it is the authority where you live.
To use any of them, write toinfo@potatoandhash.com. There is no form to fill in and no fee. We may need to check that the request really comes from you, which for an email address usually means replying from it.
We will answer within one month. If a request is genuinely complicated we may take longer, and if we do, we will tell you why before the month is up rather than after.
14
If you live in California
California law gives you a specific set of rights and asks for a specific set of disclosures. Here they are. Most of this section is short, because most of what the law exists to control is not happening here.
We do not sell or share your information
Not for money, and not for anything else of value. We have not in the twelve months before this page was written, and we have no plans to. That is why there is no Do Not Sell or Share link on this site: there is nothing behind it to switch off.
It is easy to say and worth explaining why it is still true now that there is analytics here. Sharing, in the sense the law means, is handing your information to somebody so they can advertise to you somewhere else. Google Analytics is on this site and counts you only if you agree to it, and every advertising feature of it is switched off: Google Signals is off, the ad click identifiers are stripped out of anything the tag sends, and advertising storage is denied outright rather than merely by default. The button that says count me changes exactly one setting, and advertising is not it. Nothing measured here can be used to reach you on another site, which is the whole of what the definition covers. Nothing is exchanged for money or for anything else of value either.
What is collected, in the categories the law uses
Identifiers
Your name and email address, if you use a form. Your IP address, which reaches our host on every request.
Where it comes from: You, directly. The IP address comes from the connection itself.
What it is used for: Answering you, sending what you asked for, and keeping the forms usable.
Who else sees it: Service providers only: our host, our email provider, and the inbox provider.
Internet or network activity
The page requested and the time, handled by our host as part of serving it. If you agreed to be counted, also which pages you looked at, what browser and device you used, and where you came from, all of it held by Google Analytics rather than by us.
Where it comes from: The connection itself, and the analytics tag if you allowed it to run.
What it is used for: Serving the page, keeping the site up, and finding out which pages people read.
Who else sees it: Our host and Google, both as service providers.
Geolocation data, approximate only
The country and usually the city that Google works out from your IP address, if you agreed to be counted. Never a precise location, and never from your device.
Where it comes from: Worked out by Google from the connection. We never ask your device where it is.
What it is used for: Knowing roughly where people are reading from.
Who else sees it: Google, as a service provider.
No sensitive personal information is collected. We never ask for it, and there is no field on this site that requests it.
What you can ask for
- Know what is collected, used and disclosed, and get a copy.
- Delete what we hold, with the narrow exceptions the law allows.
- Correct anything inaccurate.
- Opt out of the sale or sharing of personal information. There is nothing to opt out of here, because none of it is sold or shared, and that is why you will not find a Do Not Sell link on this site.
- Limit the use of sensitive personal information. Also nothing to limit, because none is collected.
- Be treated no differently for exercising any of these.
15
Children and families
Plenty of our visitors are kids, and we are glad they are here. Two silly dogs are for everyone.
We do not go looking for information about children and we do not need it. Accounts are not open. If a child has sent us a message and a parent or guardian would like it removed, email us and we will take it out. No explanation needed.
Grown ups: if your child wants to send a drawing or a note, we love it, but please send it from your own email address.
16
Keeping things safe
We keep the pile small on purpose, because the safest information is the information nobody collected. No card number ever reaches this site. We can tell you what the site does, but nobody can honestly promise that any website anywhere is perfectly secure, so we will not pretend otherwise.
17
Changes to this policy
If how any of this works changes, this page changes with it. For a big change, such as opening the shop, the change is written down in this section in plain words and mentioned in the newsletter.
The last change was on 11 August 2026, when the shop opened and started taking payments through Stripe. What we collect, where it lives, who else touches it and this page's account of card details all changed with it.
Before that, on 9 August 2026, Google Analytics was added. It went in behind the consent bar described above, and this page, the cookie page and the inventory of what is collected all changed in the same breath rather than weeks later.
18
Still to be supplied
This page is honest about being unfinished. These are the pieces only the owner can fill in, gathered in one place so none of them gets quietly forgotten.
Who is legally responsible for your data
A privacy policy has to name the person or company that decides what happens to your information. That name has not been supplied yet, so this page names the site and the email address to write to, and nothing more. Until it is filled in, treat the contact address as the way to reach whoever it turns out to be.
How long each kind of record is kept
No period has been set for contact messages that are not attached to an order, for subscriber records, or for the email log. We would rather say that than print a number nobody has agreed to. Ask us to delete something and we will, whatever period is eventually written here.
The paperwork behind sending data to the United States
Everyone who helps run this site is a United States company, so information reaches the United States. Each of them publishes terms covering that, and the agreements have not been signed yet. This will say which safeguard is relied on once they are.
Which country’s law applies
A policy has to say whose rules govern it and where a disagreement would be settled. That follows from where the business is registered, which has not been decided, so it is not stated. In the meantime this page gives you the rights that United Kingdom, European Union and California law describe, whichever of them you happen to be covered by.
The date this takes effect
There is no effective date on this page yet. The site is live, so this one is overdue rather than early, and any later change gets its own date beside it so you can see what changed and when.
How quickly a request is answered
One month is the legal maximum and it is what this page commits to. Whether the owner wants to promise something faster than that is a decision nobody has made, so nothing faster is promised.
Which switches are set inside the analytics account
Two things this page tells you about analytics are settings in a Google console rather than code in this site: that Google Signals is off, and that every advertising feature of the account is off. The half that lives in the code is real and anybody can read it, and it denies advertising storage outright and strips the ad click identifiers out of whatever the tag sends. The other half is a screen nobody here can show you. Both of those settings are off unless somebody turns them on, and nobody has, but until the owner has opened the console and confirmed it, this stays on the list rather than being presented as checked.
Which Cloudflare features are switched on
Some of Cloudflare’s security settings store something on a visitor’s device, and which of them are enabled is a dashboard setting rather than anything in this code. This has now been checked against the live site and nothing is being set, which is why the cookie page says none rather than saying maybe. It stays on this list because it is a setting somebody could change without touching the code, and the page would then be wrong until it was checked again.
Not legal adviceThis page was written to be clear and truthful, not to be a finished legal instrument. It has not been reviewed by a lawyer, and nothing on this site claims to be certified or compliant with any privacy law.