Founder Triage

Legal

Privacy policy

Last updated 2026-10-02

Founder Triage is built so the free tools do not need your data on our servers unless you choose to share a copy. This page states what the code actually does. We do not sell your data.

Free funnel diagnosis

The free diagnosis runs in your browser. No account is required. Your numbers stay in this browser and are not stored in our database unless you tick the box to let us keep a copy. A copy of the last diagnosis (and, if you fill it in, the paid-report context form) can stay in this browser’s localStorage so the form can be reopened. Starting checkout also sends that copy, because the purchase needs it.

If you tick the box, we store the diagnosis inputs, the result and your product name as entered in the diagnosis when you run the check, until you ask us to delete it. We do not store your email, IP, or browser details with that copy. Only the site owner can see it, on a private admin page. There is no automatic expiry. Email hello@alexworks.app to have a copy deleted.

We do send a first-party analytics ping when a diagnosis starts or finishes. That ping is an event name and, if you arrived with a campaign link, the utm labels stored in this browser’s sessionStorage. It does not include your funnel numbers. We keep an anonymous daily count of those event names — the UTC date, the event name, and a number — and a log of the UTC time at which each free check started or finished, with the event name and nothing else. No personal data and no funnel numbers.

Calculators and guides

The conversion calculators run in your browser. The numbers you type there are not sent to our servers and are not saved in localStorage.

When you start checkout

Checkout is another time funnel answers leave the browser (the other is if you tick the box on the diagnosis form). Clicking through to pay POSTs the diagnosis and the context form to our Worker, then creates a private report row in Cloudflare D1 before Stripe confirms payment. If checkout is abandoned or Stripe fails after that insert, the row can remain unpaid.

The row stores: funnel numbers and product details (including product URL, name, type, business model, activation definition, acquisition sources and areas you said you already changed); founder-context answers (one-line description, ideal customer, pricing, competitor names, alternatives, biggest concern, and any free-text notes); a SHA-256 hash of the private-link token (not the token itself); payment and generation status; timestamps; and later a Stripe checkout session id. Our forms do not ask for your name, email or phone. Free-text fields can contain whatever you type.

Checkout is rate-limited. We store a SHA-256 hash of the connecting IP in a separate rate-limit table, not the raw IP. A Cloudflare Turnstile check runs before that insert. The Turnstile token is sent to Cloudflare to verify, with the connecting IP when present; we do not keep the token in the database.

Payment

Stripe processes the payment. We send Stripe the report id, the product name and amount, and the success and cancel URLs. The success URL is the private report link, including the token. We do not send Stripe your funnel answers. Stripe’s checkout page collects payment details (typically an email for the receipt). Stripe keeps payment records as tax and accounting law requires.

Paid report generation

After Stripe confirms payment, we generate the report. We fetch a few public pages of the product URL you provided (home, pricing, features, when reachable) and send OpenAI: those page texts, the submitted funnel numbers, the founder-context answers, and a summary of the free diagnosis. The OpenAI request setsstore: false. We do not make claims about OpenAI’s own retention. We do not send OpenAI your Stripe payment details or the private token.

Research notes and the finished report are stored on the same D1 row. Worker logs may include the report id, generation status and a short error message. They are not a copy of the funnel form.

The report URL is private. Anyone who has the full link can open the report, so keep it private. Pages for that report ask browsers not to index them and not to send a referrer. Access is checked by hashing the token in the link. The database keeps only that hash. The private link, including the token, is also held by Stripe as part of the success URL, and may appear in request logs of our hosting provider (Cloudflare).

If we cannot finish a report you paid for, reply to your Stripe receipt with the report ID or email hello@alexworks.app. We will re-run it or refund the payment. A retry is not a second charge.

Analytics

Page views: we load Umami Cloud (cloud.umami.is, posting to gateway.umami.is) on marketing and tool pages. It counts pageviews, uses no cookies, and only checks theumami.disabled opt-out flag. We set Umami’s data-exclude-search so URL query strings (including private report tokens) are not sent. Umami is not loaded on report pages. Cloudflare Web Analytics is not in our HTML; if this host has it enabled, Cloudflare may inject its cookieless beacon (static.cloudflareinsights.com, reporting to cloudflareinsights.com or this origin’s/cdn-cgi/rum).

First-party events (for example that a diagnosis started, that checkout started, or that a report was viewed) are first-party logs plus an anonymous daily count; for the free check we also keep the UTC time of each start and finish. The ping is an event name and, if you arrived with a campaign link, those campaign tags. It does not include funnel numbers. A report-viewed ping does not include the report id or token.

What leaves this browser: that analytics ping (event name and campaign tags); your diagnosis when you start checkout to buy, or if you tick the box to keep a copy; and page-view counts (Umami, plus Cloudflare Web Analytics only if Cloudflare injects it). We do not use advertising cookies or third-party marketing pixels.

Hosting

The site is hosted on Cloudflare. Like any web host, Cloudflare processes standard request data (such as IP address and user agent) to deliver and protect the site.

Free promo-code runs

If you use a free promo code, we save what you entered and the report we generated, along with your email from checkout. We use it only to improve Founder Triage and to follow up with you if you want feedback. We keep it for up to 90 days. Email hello@alexworks.app and we'll delete it sooner. Runs without a promo code are not saved this way.

Retention

Funnel numbers that stay in this browser are only in this browser, until you clear site data — unless you tick the box to keep a copy.

Server-side, we keep checkout report rows (including unpaid rows created when checkout starts), Stripe event ids we record to ignore duplicate webhooks, hashed checkout rate-limit counters,daily_event_counts (a UTC date, an event name, and a number — no personal data),event_log (an event name and a UTC time for each free-check start or finish — no personal data), any report copies you opted in to share (inputs, result, and your product name as entered in the diagnosis), andfree_runs (the promo code, the email from checkout, and a link to that report — kept up to 90 days). Free promo-code runs are deleted automatically after 90 days. There is no automated deletion job and no time-to-live in the code for the other rows listed here: those rows stay until they are deleted by hand. Only the site owner can see opted-in copies and free promo-code runs, on a private admin page. Email hello@alexworks.app to ask for deletion of data we hold. Stripe payment records are kept by Stripe as tax and accounting law requires.

Contact

hello@alexworks.app. For a paid report you can also reply to your Stripe receipt with the report ID.

Changes

If this policy changes, we'll update the date at the top of this page.