Notices  ·  Pinhold

Privacy

Last updated 26 September 2026

Pinhold is run by Sword in Board Workshop. This page says what the site keeps, why, who else sees it, and how long it lasts. It is short because the site itself does little.

What the site keeps

What you put on a board. Titles, writing, pictures, where things sit, which strings connect what. Whatever you pin up is stored as you wrote it.

Board passphrases. Stored encrypted, but reversibly — the owner of a board can look up its keys to pass them on, and that only works if the site can decrypt them. So they are not hashed the way a login password normally is, and in principle we can read them too. Do not reuse a password you use anywhere else.

A recovery email address, only if you give one. Optional, stored encrypted, and used for emailing you a way back into your board if you lose the passphrase, and confirming a refund when applicable. Never for anything else. You can leave it blank.

Submissions. If you send something to a board, the site keeps the name you typed, the note, any pictures, and a contact detail if you gave one, until the board's owner accepts or discards it.

Reports. If you report a board, the site keeps the reason, whatever you typed in the box, which board it was, when, and which key you were holding at the time. It also keeps a copy of the board itself as it looked at that moment — including its pictures — separate from the live board, so a report can be reviewed even if the board is edited or deleted afterward. Reporting does not lock the board or affect anyone using it. That same copy also goes out by email to the moderator at the time of the report, so it is not held in one place alone.

A sign-in cookie. One cookie, set when you enter a passphrase. It is a signed token saying which board you are allowed into and what you are allowed to do there. It is not an identifier, it follows you nowhere, and the site does not work without it.

A record that you agreed to this. A second cookie noting the date of the notices you agreed to and which boards you agreed for. It is there so you are not asked the same question every time you open the site — only when you open a board you have not been on before, or when these notices change in a way that matters. It holds no name and no identifier.

Counts of failed sign-in attempts. To stop somebody guessing their way into a board, the site counts wrong answers against a hashed IP address. The raw address is not written down anywhere by Pinhold itself.

What the site does not keep

• Your name, unless you type it into something.
• Your location.
• Any advertising or cross-site identifier.
• Anything at all from people who never sign in.

Pinhold is not directed at children, and we do not knowingly collect information from anyone under 13 — see the age requirement in the User Agreement. If we learn that someone under 13 has given us information anyway, we will remove it.

Who else sees it

Two companies, and only because the site runs on them:

• Netlify hosts the site and stores its data. Like every web host, their servers log requests, and those logs include IP addresses. That is Netlify's logging, not ours, and it is governed by their policies.
• Resend runs the site's email features including the recovery message and notices to us when something is reported. The message contents pass through them.
• Stripe takes the payment if you buy Supporter. Your card details go to Stripe, never to Pinhold's own servers. Certain info remains accessible to Sword in Board, such as name and billing info, provided so that we may process refunds. See payment & refunds for what that covers.

We do not sell data, share it, or hand it to advertisers. We will hand something over if a valid legal order requires it, or if we believe it is needed to stop someone being seriously hurt.

How long it lasts

• Boards: 180 days after the last time anyone looked. Then the board, its items and its pictures are deleted automatically, with no warning and no undo. Opening a board resets its clock.
• Submissions: until the board's owner accepts or discards them.
• Reports: kept while we look into them, and afterwards as a record.
• The sign-in cookie: until it expires or you sign out.
• The agreement cookie: six months, or until these notices change enough to be worth agreeing to again.

How safe is it, honestly

The site is served over HTTPS, passphrases are never shown in a URL, failed guesses are counted and refused, and sessions are signed so they cannot be forged.

What that does not add up to is secrecy. Boards are not end-to-end encrypted. Anyone with the passphrase reads the board, passphrases are shared freely by design, and we can open any board on the site when needed for moderation purposes. Please read the first section of the User Agreement before deciding what to put on a board.

Your rights

Pinhold has no accounts, so most of what follows works differently here than on a site where you'd log in to manage your data: the passphrase to a board or the recovery email on file for it is what proves it's yours to ask about, the same way it's what proves it's yours to edit.

You can ask us to tell you what a board holds, correct it, or delete it — though because access is the identifier for a board, you can already do all three yourself by opening it. For anything Pinhold holds outside a board itself — a recovery email address, a submission you sent, a report you filed — write to swordinboard@gmail.com and say what you're asking for. We aim to respond within 30 days. If you're in the EU or UK, this also covers the right to receive your data in a portable format and to object to or restrict how it's processed; if you're in California or a state with a similar law, it covers the same ground under that law's own terms — either way, the practical answer is the same because the site keeps so little to begin with.

Why we process what we do: running the board you asked for (the board's own content, the sign-in cookie), something you explicitly opted into (a recovery email address), or keeping the site from being guessed into (the hashed failed-login counts). None of it is used for advertising or profiling by Sword in Board.

Where it goes: Netlify, Resend, and Stripe, named above, each process data outside the country you're in if you're outside the United States. All three participate in the EU-U.S. Data Privacy Framework, the UK extension to it, or rely on Standard Contractual Clauses for the transfer — the mechanisms the law recognizes for moving data across that line.

Sword in Board Workshop is who's responsible for that processing and who you're asking. If you're not satisfied with how a request was handled, EU and UK residents can complain to their own country's data protection authority; other jurisdictions have their own equivalent, usually through a state or national consumer-protection office.

If something goes wrong

Most breach-notification laws are written around specific categories of data — Social Security numbers, driver's license numbers, financial account numbers with the code to use them — and Pinhold doesn't collect any of that, by design. That doesn't change what we'd do if the data described on this page were ever exposed: we would tell affected users at the address on file, and anyone we can otherwise reach, as soon as we reasonably could after finding out, and say plainly what happened and what we know.

Changes

If this page changes, the date at the top changes with it. If the change is significant, we will put a notice on the sign-in screen.

Getting hold of us

Sword in Board Workshop — swordinboard@gmail.com