Post Your Build Ideas
Launch

Privacy

Effective 21 October 2026. Last updated 14 November 2026.

Who is responsible

The controller for this site is an independent developer based in Switzerland, reachable at support@postyourbuildideas.com. The full name and postal address are on the imprint.

What is stored, and why

  • Idea posts: the name, idea, category and optional fields you type, and your email address. Everything except the email address is public by design, and permanent. The email address is never shown; it is kept with the post, to verify it and to reach you about it.
  • Launches: the product name, link, tagline, description, category, pricing, your maker name and your email address. Everything except the email address is public once you verify the launch. The email address is never shown; it is used to send you the verification link. The link itself is not stored, only a one-way hash of it.
  • Comments: the name you give, what you write, and an email address if you choose to give one. The name and the text are public; the email address is never shown.
  • Discussion threads: the name you give, what you write, and your email address, which a thread requires. The name and the text are public; the email address is never shown, and is kept with the thread to verify it and to reach you about it.
  • Build links (“Built this?”): the link, the short description, an optional name and the email address you give. The email address is never shown.
  • Newsletter: if the weekly-digest box is ticked when you launch, post an idea or start a thread (the box is ticked in advance on those forms, and you can untick it), or if you use the Subscribe button, your email address, the exact consent text you agreed to, when you agreed, where you agreed (the launch, idea or thread form, or the Subscribe button), when you confirmed, and whether you have unsubscribed.
  • Votes: for launches and threads, a hash of the random pyb_vid cookie (below) made with a server-side salt, plus a salted hash of your IP address. For idea likes and dislikes, a salted hash of your IP address and browser.
  • Salted hashes of your IP address, used for rate limiting and to allow one vote per voter. The raw address is never stored.
  • Idea Checker: not the text you paste. One row per check with its length, the time, a salted hash of your IP address, the number of tokens the call used, what it cost and whether it worked. See the Idea Checker.
  • Emails the site sends, held in a sending queue: the address, the message, and whether it was sent.
  • An admin audit log recording actions taken in the admin panel.

Nothing is sold here. Payment code from an earlier version of the site is still in the codebase but switched off: no payment is taken and no payment data is collected.

Why it is allowed — the legal basis for each purpose

Under the GDPR every purpose needs a basis. These are the ones relied on here, and nothing is processed for a purpose not on this list.

  • Publishing what you post, and running a launch — contract. Showing your idea, launch, comment, thread or build link is the service you asked for. For a launch, your email address is needed to send the verification link, and to answer you about the launch afterwards. For an idea or a thread, it is kept with the post, to verify it and to reach you about it.
  • The weekly digest — consent. You are added only if the box is ticked, and only confirmed when you use the link in the email we send you. You can withdraw at any time with the unsubscribe link in every email.
  • Reading the text you paste into the Idea Checker — contract. It is the service you asked for, and it happens only when you press the button. The text goes to TypeSafe for that and for nothing else.
  • Rate limiting, spam and abuse prevention — legitimate interests. Salted IP hashes and the voting cookie exist so one person cannot flood the board or vote a thousand times. The interest is keeping a public, account-free board usable; the impact is minimal because the raw address is never stored and the cookie holds only a random number.
  • Analytics with Vemetric — legitimate interests. Knowing which pages are read, and publishing honest traffic figures on the stats page. The interest is running the site; the impact is minimal because Vemetric is cookieless, aggregate, and carries no identifier that follows you between visits, so it runs without asking.
  • Analytics with Minilytics — legitimate interests. Understanding how visitors use the site. Minilytics runs for every visitor and sets two first-party cookies on your device; how to stop them.
  • Admin audit log — legitimate interests. Knowing what was changed in the admin panel, and by whom, so a removal or a hidden post can be accounted for.

Where the basis is legitimate interests you can object — see your rights.

How long it is kept

  • Idea posts, comments and threads are permanent by design, so what is stored with them is kept as long as they exist. The operator can hide or remove one, and a post about a real, identifiable person is removed on request.
  • Unverified launches are private and expire 24 hours after they are submitted; expired ones are then deleted, with the email address on them. Verified launches, including the email address, are kept until removed.
  • Newsletter records are kept until removed. When you unsubscribe, the address is kept marked as unsubscribed, so that it is not emailed the digest again.
  • Build links, including the email address, are kept until removed.
  • Votes, and the hashes attached to them, are kept as long as the vote exists. Taking a vote back on a launch or thread deletes it.
  • Rate-limit records for launches, comments, threads and votes — a salted IP hash and a time — are cleared out routinely once they are more than a day old.
  • Visit and page-view records — a salted visitor hash with the hour it was seen, and a per-day view count — are currently kept indefinitely. They are what the published figures are counted from. There is no automatic deletion of them today, and saying otherwise would be inventing a policy that is not implemented.
  • Click and prompt-copy records are kept indefinitely, for the same reason: the counts on the stats page are counted from them.
  • Idea Checker records — length, time, a salted IP hash, token count, cost and outcome, never the text — are currently kept indefinitely. They are how the hourly and daily limits and the daily spending cap are counted, and how the cost of the feature is known. There is no automatic deletion of them today.
  • Admin audit log and emails in the sending queue are kept until removed.

Who processes data for us

These are every third party this site sends data to. There is no advertising network, no data broker, and no one else.

  • Supabase — database and file storage, EU region.
  • Cloudflare, Inc. (United States) — hosting and content delivery, on Cloudflare Workers, with cached pages held in Cloudflare KV and D1.
  • Resend — sending the site’s emails: launch verification links, and anything else the site emails you.
  • Vemetric — analytics, EU-hosted.
  • Minilytics — analytics, with two first-party cookies. Self-hosted by the operator on Cloudflare Workers (Cloudflare, Inc., United States).
  • TypeSafe AI, Inc. (United States) — reads the text you paste into the Idea Checker. What it does with it.

Data leaving Europe

Supabase stores this site’s database and files in an EU region, and Vemetric hosts its analytics in the EU. Others are different: Cloudflare (which hosts this site and runs Minilytics on its global network) and Resend are US-headquartered, and processing or support access outside the EEA and Switzerland has to be assumed — a page is served by whichever region a request reaches, and an email passes through Resend’s infrastructure. The Idea Checker sends the text you paste to TypeSafe in the United States (below).

The safeguard relied on for the Cloudflare and Resend transfers is each provider’s data processing agreement incorporating the European Commission’s Standard Contractual Clauses, with the Swiss addendum recognised by the FDPIC where Swiss data protection law applies. If you want to see the agreement relied on for a particular provider, ask and you will be told which one and where to read it.

For TypeSafe the safeguard is its own data processing addendum, last updated 24 April 2026, which its customer agreement incorporates. It applies the European Commission’s standard contractual clauses (module 2, controller to processor) and the UK addendum, and names the Swiss Federal Data Protection and Information Commissioner as the competent authority for people in Switzerland.

Children

This site is for adults. Nothing here is directed at children, no age is asked for on any form and none is stored, and there is no knowing collection of data from a child. If you believe a child has posted something or that data about a child is held here, email support@postyourbuildideas.com and it will be removed.

The Idea Checker

When you press the button on the Idea Checker, the text in the box is sent over an encrypted connection to TypeSafe AI, Inc., a US company, which reads it and sends back scores. This site does not store that text, does not put it in analytics and does not write it to a log. What it keeps is described under “What is stored” above: one row per check, without the text.

What TypeSafe’s own published documents say — its privacy policy, terms, data processing addendum, customer agreement and trust centre, read on 19 September 2026, with the privacy policy, terms, addendum and customer agreement checked again on 24 September 2026:

  • Where. The service is hosted in the United States. Its subprocessors are Amazon Web Services, which stores and processes customer information for live requests, and Modal, which processes prompts without storing them; both are in the USA. It publishes no EU or Swiss processing option.
  • Training. It says it will not train or fine-tune any model on what you send, and will not disclose it to anyone but its own service providers. Its customer agreement qualifies the training restriction: training on customer data requires the customer’s prior consent.
  • Its role. Under its data processing addendum TypeSafe is a processor acting on this site’s instructions, and the addendum is part of its customer agreement.
  • How long it keeps the text: not published. Its privacy policy says “as long as reasonably necessary”. Its customer agreement also permits ongoing processing to derive telemetry, monitor fraud and abuse, and comply with law. It gives no fixed deletion deadline. Zero data retention is described only as an option for enterprise customers, which this site has not set up. Assume the text may be kept for an unknown time.
  • Usage data. Its customer agreement lets it keep technical logs, hashes, summary statistics, classifications and metrics about how the service is used, to improve its services. Its documents do not say whether any of that can contain what you typed.

So: do not paste anything you would not want a US company to hold for an unknown time. That means personal details, secrets, and any idea you need to keep private. An idea you have not published may still be retained; the training restriction does not establish a deletion deadline.

Posts are public, on purpose

Everything published to the site — an idea, a verified launch, a comment, a thread, and the name you give with it — is public from the moment you press publish, visible to anyone, indexed by search engines, and readable through the site’s own pages and feeds. Email addresses are the exception: they are never shown. There is no setting that makes a post visible to some people and not others.

Do not put anything in a post that you would not put on a public web page: not your address, not your phone number, not somebody else’s details. Ideas, comments and threads are permanent for their authors and there is no self-service delete; a launch can be fixed by its owner only until it is published, and after that only by email to the operator.

The one thing that always overrides permanence: a post about a real, identifiable person is removed on request, from that person, with no justification needed and no argument. Use the report page or email support@postyourbuildideas.com.

Emails and the newsletter

The site emails you only when you ask it to: the verification link for a launch, and the weekly digest if the box for it was ticked. Emails are sent through Resend. The digest box is ticked in advance on the launch, idea and thread forms; you can untick it, and launching, posting an idea or starting a thread works the same without it. When it is ticked, the exact consent text shown next to the box, the time and the source (the launch, idea or thread form) are stored, and the subscription is confirmed only when you use the link in the email we send: the launch email, or for an idea or a thread a confirmation email with one link. Every email carries a one-click unsubscribe link, and unsubscribing takes effect immediately.

Cookies and analytics

When you vote on a launch or a thread, the site sets one first-party cookie, pyb_vid: a random ID, kept for one year, readable only by the server (httpOnly), so that one browser gets one vote per item and can take it back. It contains no name, email or IP address. What is stored is a salted hash of it, never the value itself. If you never vote, it is never set.

Traffic on this site is measured with two tools. Vemetric is cookieless and always on: it sets no cookie, and no identifier follows you from one visit to the next — to tell repeat views apart within a day, Vemetric derives a hash from a salt that rotates daily and is then unrecoverable.

Minilytics and its two cookies

The second tool, Minilytics, is the operator’s own self-hosted analytics, running on Cloudflare Workers. It runs on every public page, for every visitor, and sets two first-party cookies on this domain:

  • ml_vid — a random visitor ID, kept for one year, so a return visit is recognised as the same browser.
  • ml_sid — a random session ID, kept for 30 minutes after your last page view, to group one visit.

Neither contains your name, email or IP address, and neither is used on any other site. Minilytics receives the page address (with personal-looking parameters such as an email removed), the referrer, screen width, browser and device type, an approximate location derived from your IP address, and the same events listed below. Your email is never sent to analytics. To stop these cookies, or the voting cookie, block or delete cookies for this site in your browser settings; the site works the same without them, except that voting needs the voting cookie. You can also object by email, as described under your rights below.

Apart from the cookies above, what is kept in your browser is session storage only: a random number your tab uses to group its own page views into one visit, a marker noting that the post form has already been counted as started, and — if you send an idea to the Idea Checker — its text, so the checker box opens already filled. All of it is per-tab, none of it identifies you, and all of it disappears the moment you close the tab.

What it records is aggregate and about pages, not about people: which page was viewed, the referrer that led there, an approximate country, and the browser and device type. On top of that, the things this site is actually for are counted as events — an idea opened, liked, disliked or shared, a build prompt copied, and a post started and published. None of them carry your name, your email or your IP address.

Searches are recorded. When you search the board, the words you typed are sent as an analytics event together with how many results came back. This is genuinely useful — it shows what people come here looking for and do not find — but it is text you typed, so please treat the search box as public. It is capped at 64 characters, an empty search is never recorded, and the words are not linked to you or to anything else you do.

There is no cross-site tracking, no advertising network, no third-party pixel, no profile, and nothing is ever sold. Your browser does reach Supabase directly — that is this site’s own database and file storage, named above, and it is what makes the counters update live. Analytics never load in the admin area. Vemetric’s servers are in the EU; Minilytics runs on Cloudflare’s network, and the numbers are published on the stats page rather than kept private.

Your rights

Under the Swiss FADP, and under the GDPR if you are in the EU or the UK, you can ask for:

  • Access — a copy of what is held about you, and what it is used for.
  • Correction of anything inaccurate.
  • Deletion, where there is no overriding reason to keep it.
  • Restriction of processing while something is being checked, and objection to anything relied on under legitimate interests, including analytics.
  • Portability of what you gave for a launch, in a machine-readable file.
  • Withdrawing consent, where consent was the basis. The only thing here that relies on consent is the weekly digest, and the unsubscribe link in every email withdraws it in one click.

How to exercise them: email support@postyourbuildideas.com, say which right you are exercising, and give enough for the data to be found — for a launch, an idea, a comment, a thread or the newsletter, the email address you used. There is one person here; you will get a human reply, and the aim is within 30 days. It costs nothing. You may be asked something to confirm the request is really yours, and no more than that.

You can also complain to a supervisory authority. In Switzerland that is the Federal Data Protection and Information Commissioner (FDPIC); in the EU it is the data protection authority of the country you live or work in, or where you think something went wrong; in the UK it is the Information Commissioner’s Office. You do not have to raise it here first, though it is usually faster.

An honest limit: most of what this site stores is a salted hash of an IP address or of a random cookie, kept precisely so that nobody — including the operator — can work backwards from it to a person. That means an access or deletion request usually cannot be tied to those rows at all. For a launch, an idea, a build link, a comment or thread posted with an email address, or a newsletter subscription, which do carry your email address, it can.