Privacy policy

1. Your note is public, permanently

The moment a payment clears, everything on your note is published: site name, link, description, logo or monogram, note tone, serial number, and the fact that it was drawn as #1 in any given window.

It's a public page, so search engines, scrapers and archives can copy it, and we can't un-publish those copies later even after your note comes down. Don't put anything on a note that you wouldn't put on a billboard.

2. Payments

Payments run through Stripe Checkout, on Stripe's own pages. Card numbers never touch our servers and we never see them. Stripe collects your email address for the receipt, along with whatever it needs for fraud checks and tax. That part is Stripe's processing, under Stripe's privacy policy.

What we store on our side is only:

• the Stripe checkout session id and payment intent id;
• whether the entry is pending, paid, refunded or removed;
• when it was created.

We can see the email address you gave Stripe in our Stripe dashboard, and we use it for two things: replying if you write to us, and sending the notices these pages promise — a shutdown notice, or a material change to the terms. No newsletter, no marketing, and we don't sell it or hand it to anyone.

3. Logos you upload

An uploaded logo goes into our storage bucket and is served from a public URL, the same as any image on a public page: anyone with the link can fetch it. Uploads are limited to PNG, JPEG or WebP under 512 KB, and we check the file's actual bytes rather than trusting what it's named. A logo uploaded for a checkout that was never completed gets deleted.

4. The counters, and what a “session” means here

The online count, the visit count, and the click tally on the current #1 all work off a random UUID your browser generates and keeps in sessionStorage.

It is not an identity. It's tied to no name, no email, no note, and no other site, it can't follow you anywhere, and it's gone when you close the tab. A new tab is a new id and counts as a new visit. We keep one row per id with a last-seen timestamp; a row goes cold after 90 seconds and is deleted after an hour. A click row records that one id clicked through to the #1 during one fifteen-minute window, so the tally counts people rather than refreshes.

None of that uses cookies. The id sits in sessionStorage, which the browser clears when the tab closes and never attaches to a request. We set no cookies of our own anywhere on this site — the only cookies here are Google Analytics', which is the next section.

There is no advertising pixel, no session recording and no fingerprinting. The fonts are served from our own domain, so the text renders without fetching anything from Google.

5. Google Analytics

Every page here loads Google Analytics 4 (measurement id G-THG49F1Q9R). It is what tells us whether anyone is finding the wall and where they came from; the counters in section 4 only say who is looking right now.

Through it, Google receives:

• which pages you view here, when, and in what order;
• the site, search or link that sent you;
• your browser, device type, operating system, language and screen size;
• an approximate location — country, region, usually city — worked out from your IP address;
• a randomly generated client id that lets Google tell a returning browser from a new one.

Google Analytics sets cookies — _ga and _ga_THG49F1Q9R. They are Google's, not ours. Google gets no name, no email address, and nothing you typed into the submission form, and we don't use any of it for advertising, remarketing or Google Signals.

Google uses your IP address to work out that approximate location and doesn't store the address itself in the property afterwards. What Google does with the rest is covered by its own privacy policy and its note on how it uses data from sites that use its services.

If you'd rather not be counted, Google publishes a browser opt-out add-on, and any ordinary content blocker stops the script loading. Nothing on this site breaks if you use either — the wall works exactly the same.

6. IP addresses

When you submit a note or upload a logo, the server holds your IP address in memory for up to an hour so it can rate-limit abuse. It is never written to the database and never attached to your note.

Our host and Stripe keep their own request logs, which include IP addresses, under their own policies. We don't control those and don't use them for anything.

7. Who else touches any of this

• Stripe — payments, receipts, and the email address you give it.
• Supabase — the database holding entries and counters, and the bucket holding logos.
• Vercel — hosting, and the server logs that come with it.
• Google — Analytics, as set out in section 5.

That is the whole list. There is no fifth party.

8. How long things are kept

• Your note — for as long as it's on the wall. Ask us to remove it and it comes off.
• The payment record — the amount, the date, and the Stripe ids. We keep these after a note comes down, because tax and accounting rules require it and because a refund or dispute months later has to be traceable to something.
• Presence rows — deleted an hour after the tab that made them went quiet.
• Click rows — kept with the draw they belong to; they are what the click count is.
• Analytics data — held by Google, not by us, under the retention setting on the property. Event- and user-level data is kept for at most 14 months; the aggregate reports built from it last longer.

9. What you can ask us for

Get in touch to get a copy of what we hold about you, correct something on your note, take your note down, or ask anything about this page. We'll reply within 30 days and usually much sooner.

Depending on where you live you may have stronger rights than that — the GDPR in the EU and UK, the DPDP Act in India, and the CCPA in California all give you specific ones. We'll honour them; say which you're relying on and we'll handle the request under it.

If you need it in those terms: we process your submission and payment to perform the contract between us, and we run the counters, the abuse rate-limit and the analytics in section 5 on the basis of our legitimate interest in knowing whether the wall works and keeping it free of spam.

10. Children

This isn't a site for children and we don't knowingly collect anything from them. If a note was submitted by a child, tell us and it comes down, with the dollar refunded.

11. Changes to this page

If what we collect changes, this page changes with it and the date at the top moves. If the change is a significant one, we'll say so rather than let you find it by re-reading.