Privacy

• Your email address, because signing in needs one. We also use it to mail you about your own grills: when one finishes, and once, a day later, when its re-grill opens. That reminder can be turned off on your account page. If you use Google, we get your email and nothing else from them.
• The URLs you grill, and what we captured from them: the page text, a screenshot of the first screen, a screenshot of the whole page, and the site’s favicon. If you download a launch brief from a grill, we also keep the taglines and descriptions drafted for it from that text; the name you type for the brief goes into the file and is not stored.
• The grill itself — scores, findings, the verdict.
• How you arrived: whether you came from a shared grill, a public grill page, an AI assistant such as ChatGPT, or directly. Two cookies, lg_src and lg_ref, hold that for 30 days.
• How you heard about us, if you answer the one question we ask while your first grill runs. One choice from a list, or that you skipped it; it stays with your account.
• Feedback you send us from the Feedback tab: the message, the page you sent it from, and your email address only if you add one. It is kept until you ask us to delete it.
• Product events: that a grill was created, finished, failed, viewed or shared. Enough to know whether the product works, not enough to follow you around. To count a grill’s readers as people rather than page loads, each view carries a short code made from your IP address, your browser and the date. The IP address itself is never stored, nothing is put on your device, and the code changes every day, so it counts one day’s visits, never you over time.
• Takedowns: if someone asks for a grill of their page to come down, we keep their email address, the address they claimed, whether it matched that page’s domain, and what each side said. We use it to tell them what was decided, and to see when the same address asks repeatedly.
• Grills I start for someone: the link to where they asked for it. Only I see it; it is the record that they asked.
• Claims: if you claim a launch I grilled for you, we keep your account email, whether it is at that page’s domain, what you wrote, and what I decided. We use it to tell you the answer.
• Removed grills: if I remove a grill, the reason, its score and its address stay in our event log. Nothing else about it does.
• The wait before a re-grill, and the launch slot: for each page you add we keep the address, and — if you grilled it — when you last did and how many times. It survives removing the launch, so removing and re-adding a page cannot be used to grill sooner or to free one of your ten launch slots. We keep the address of a launch you removed without ever grilling it for that second reason alone. Nothing else about the grill survives.
• Why you made your account: the button that led to it — grilling a launch, seeing a launch plan, adding a directory to one, a PDF and which, claiming a grill, done for you, or the sign-in page — and when. It stays with your account.
• Whether you agreed to hear from us: the sign-up box beside the launch plan, the PDFs and “Add to my plan” says we will email you about launching and the Launch Kit now and then. If you signed in from it, we keep the date. Every such email has a one-click unsubscribe, and unsubscribing clears it.
• Your launch plan: what you are launching, the directories in it and what you marked submitted or live, with the dates. Deleting your account deletes it.
• If you buy the Launch Kit: your email address and the GitHub username you gave at checkout, kept with the order so we can send the invite and answer a refund request. Stripe holds your payment details, not us.
• If you buy done for you: the page you gave, which account bought it, and, while I work, the mail directories send to the address you forward to me (sign-up confirmations and replies). I use it only to submit your product and mark your launch plan; you stop the forward when I am done.

This is the part worth reading twice. Every grill gets a public permalink, appears in the record, and can be indexed by search engines. There is no private option and nothing you can pay for one — the product runs on grills being readable.

If someone grilled your page and you did not run it, the link at the bottom of that grill takes it down — immediately if you write from an address on that page’s own domain, and otherwise by hand within a day.

• Supabase — where your account and your grills are stored, and where you sign in. On servers in London, in the UK.
• Google (AI Studio), whose model reads the page text and screenshots and writes the critique. Your page content goes to them, and on the free tier we use, Google may use what it receives to improve its models. Your email does not go to them.
• OpenRouter, only when Google’s model does not answer: it passes the same page text and screenshots to a second model (NVIDIA’s Nemotron) on a free tier, whose provider may keep and use what it receives. Your email does not go to them.
• Google (Analytics) — counts visits to this site, only if you allowed it. It then receives your page views, your rough location, and your device and browser, on Google’s servers, which may be outside the UK. It never receives your email address or anything from your grills.
• Microsoft (Clarity) — shows us how pages are used, only if you allowed it. It records the page you are on as you use it: what you scroll to, where you click, how the mouse moves, plus your rough location, device and browser. It does not record anything you type into a box, and it never receives your email address or the contents of your grills. Microsoft holds it on their servers, which may be outside the UK.
• Sentry — tells us when the site breaks. Our server sends it the error and the page it happened on, which can include your browser and your IP address, on servers in the EU; your browser does not contact it. It does not receive what you typed, the contents of your grills, or your email address.
• Stripe — payments. It sells the Launch Kit to you as merchant of record (through Link), so it holds your card, your billing address and the tax it charges; we receive your email, the GitHub username you typed and the amount.
• GitHub — if you buy the Launch Kit, we ask GitHub to invite the username you gave, so GitHub learns that it has access to our kit repository.
• Resend — the emails we send you.
• Telegram — how Said is told what happens on the site. It receives feedback you send, word for word, and short notices when you sign up or sign in, a grill starts, finishes, waits for a retry or fails, you download a brief, buy the Launch Kit (with the GitHub username you gave), report a grill, claim or remove a launch, or a mail to you fails. Those messages include your email address — the one you sign in with, or the one you typed into the feedback form — and, for grills, the address of the page being grilled.
• Cloudflare — every visit to this site passes through it on the way to our machine. It sees your IP address, your browser and the page you ask for, keeps short-lived logs, and protects the site from attacks; it does not receive what you type into a box beyond what the page sends, and it sets no cookies of its own here.
• A machine we rent ourselves, in Nuremberg, Germany. It runs this site, opens the page being grilled, takes the screenshots, and keeps a nightly backup of the database.
• Directories whose badges are in the footer (Aura++, Dang.ai, NavFolders, Fazier, Huzzler, Shipybara, SubmitHunt, Launch Llama, DailyPings, AI Agents Directory, SaaSBison, Neeed, FastLaunch, Altern, ShowMeBest, MarketingDB, AI Tools for Marketers, LaunchPanda, Launch Vault, Buildlist, Deeplaunch, DodoDirectory, Findly, SaaSGrow, Postmake, TinyLaunch, Startup Fast, Hunt0, SaaSHub, ScoutForge, ShipyardHQ) — the “Featured on” badges in the footer are images loaded from their servers, so your browser asks them for the image and they see your IP address and browser. They are not told which page you are on, and they receive nothing else.

Visits, clicks on our own buttons and links, and how fast pages load are counted by self-hosted Umami on that same server, which sets no cookies, is never told who you are, and keeps what it collects on our machine. Google Analytics and Microsoft Clarity run only if you allowed it when asked — say no, or never answer, and neither script is loaded at all. You can change your mind from “Cookies” in the footer. No advertising pixels, and nothing here follows you to other sites.

Four unless you allow analytics, all first-party: the sign-in cookie that keeps you logged in; lg_src and lg_ref, which remember where you came from for 30 days so we can tell whether shared grills actually bring people in; and, only when you ask for a sign-in link, lg_sent_to, which holds the address you typed for ten minutes so the “Check your inbox” page can show it. Allow analytics and up to four more are set. Google Analytics adds _ga and _ga_<id>, which count you as one visitor rather than several, for up to two years. Microsoft Clarity may add _clck, which does the same job for a year, and _clsk, which ties one visit’s pages together and lasts a day — depending on how it is set up it records without either. Your answer itself is kept in your browser’s own storage, not in a cookie. We set no advertising cookies. Clarity will read two of Microsoft’s advertising cookies, _uetvid and _uetmsclkid, if something else has already put them on your machine — it never creates them here, because that needs an advertising-consent signal this site does not send.

• Grills and screenshots: until you remove the launch they belong to, or delete your account.
• After you remove a launch we keep one line about it: the address, the date you last grilled it, and how many times. No score, no findings, no screenshot. It is there so removing and re-adding a page cannot be used to skip the wait between grills, and it goes when your account does.
• Demo credentials for a human read: removed from the database the moment the grill is delivered. If you start a purchase and never finish paying, they go with the abandoned order — email us and we will clear it sooner.
• Product events: while your account exists; deleting it removes them.
• Backups: a nightly copy of the database, kept 14 days on that same machine. What you delete leaves them within 14 days.
• Payment records: as long as tax law requires. That is Stripe’s clock, not ours.

One launch. Your grills lists your launches, and removing one destroys it and every grill of it — the scores, the findings, the screenshots and the public pages, whose links stop working. It cannot be undone. It is all-or-nothing per launch on purpose: you cannot delete a low score and keep a high one on the same page.

Everything. Your account page exports everything we hold about you as one file you can download and open elsewhere, and deletes your account. Deletion removes your grills, your launches, the screenshots, your events, the re-grill waits and your sign-in. It cannot be undone, and any public grills you ran disappear with it.

You can also email [email protected] and I will do it by hand.

There is no security team to escalate to — there is me. Write to [email protected] and you will get a person, usually the same day. If you are in the EU or UK you can also complain to your local data protection authority.