What we collect, and what we do not.

[Registered company or sole-trader name], [Street and number, postcode, city, country], registered as [KvK number], decides why and how the data described here is processed. That makes us the controller under the GDPR.

Questions, or a request about your own data: [privacy@your-domain]. We are not required to appoint a data protection officer, and have not.

Your account

Sign-in runs on Clerk. Depending on how you sign in, Clerk holds your email address and, if you use GitHub, the name and avatar it gives us. We store a profile row with your display name, username, avatar URL and role. We never store your password — we never see it.

What you write

Your project, your story, your updates. A draft is visible only to you and to the editors reviewing it. Once published it is public, indexable, and readable by anyone — that is the point of the site, and worth being deliberate about.

Your signals

Reactions, follows and your one backing a week are stored against your account, because each is limited to one per person and that limit cannot be enforced anonymously. Aggregate counts are public. Who reacted is not shown to other makers.

Sponsorship payments

Handled by Stripe. Card numbers never reach our servers. We store which package was bought, for which project, when it runs, and Stripe’s reference for it.

Abuse prevention

We count recent actions per account so nobody can flood the site. That record is your account id, the kind of action, and a timestamp. It is not tied to an IP address.

Server logs

Vercel records the usual request metadata, including IP addresses, to serve pages and catch errors. We do not build profiles from it.

The newsletter box

It stores nothing. The digest does not exist yet, and the form says so rather than implying a subscription that is not there.

We use PostHog to understand which parts of the site work. There are two levels and you pick one.

Our own events are a closed list in the code, and the properties they may carry are a closed list too. There is deliberately no field for revenue, an email address, story text, or what you typed into search — a search box on a site about people’s businesses is sensitive, so we record how long a query was and whether it matched, never the query.

Narrowing your choice takes effect at once: a recording in progress stops and the identifier held for this browser is discarded.

To provide the service — your account, your projects, your signals. Without this data there is no site to use.

Consent — full analytics, and nothing else. Withdrawing is a click and costs you nothing.

Legitimate interests — keeping the site up, stopping abuse, and basic measurement that does not follow you.

Legal obligation — payment records, which tax law requires us to keep.

We do not sell anything to anyone. These are the services that process data for us:

Some of these are in the United States. Transfers there rely on the EU Standard Contractual Clauses, and on the EU–US Data Privacy Framework where the provider is certified under it.

Your account and what you published stay until you delete them. You do that yourself, from your profile page, and it happens immediately rather than as a request we process: the profile, its projects and their stories and updates, every reaction, follow and backing you left anywhere, your rate-limit counters, and the sign-in account itself.

On the way out we ask why you are leaving, and keep the answer. It is stored on its own — no user id, no username, no email, nothing that points back at the account — so it is feedback rather than a record that you were here. The free-text box beside the answers is optional, and we ask you to leave personal details out of it.

Rate-limit records are pruned once their window has passed. Payment records are kept for seven years, because Dutch tax law says so. Analytics follow PostHog’s retention; nothing collected at the basics level survives your tab in the first place.

One honest caveat: a story that was public may live on in search engine caches and in the Internet Archive. We can remove it from here. We cannot remove it from there.

You can ask for a copy of your data, ask us to correct it, ask us to delete it, ask us to restrict or stop a particular use, and ask for it in a portable form. Where we rely on consent you can withdraw it, and where we rely on legitimate interests you can object.

Deletion is the one you do not have to ask for: the button is on your profile page. For anything else, write to [privacy@your-domain]. We answer within a month. If you are not satisfied you can complain to the Autoriteit Persoonsgegevens, or to the authority where you live.

This site is not for children. You need to be 16 or older to create an account. If you believe a child has one, tell us and we will remove it.

We update the date at the top. If a change alters what we collect or why, the cookie choice is reset so you are asked again rather than held to an answer you gave about something else.

The companion document is the terms and conditions.