Data Use

Last updated 2026-07-01

The goal is simple. Use less data. Less data is better. Keep private work safe. Tell users what happens. Keep it plain.

We collect only the data needed to run the service, protect users, and improve launch.

Data We May Collect

Account data can include email, sign-in method, account status, and account choices.

Founder work can include ideas, saved work, proof data, choice logs, and shared-pack settings.

Program data can include setup, entrant status, packs, review tasks, reviews, and cohort reports.

Safety data can include audit events, request data, browser details, and logs that help protect the service.

Site stats can include safe events, page type, CTA ID, consent state, campaign fields, persona choices, and product steps.

We do not send raw saved-work text, chat text, proof notes, uploads, passwords, secrets, or raw secure-link tokens to GA4 or GTM.

We also do not send names, emails, phone numbers, or private startup content.

Site tools should get safe event facts, not the founder's work.

We use data to:

A founder may share one pack through a secure review link.

People should see only what the founder or program shared.

Shared access is not a public post of the founder's full workspace.

Users can ask for help with access, delete requests, or data questions.

If you cannot sign in, use the contact page. Include enough detail to find your account.

Do not send passwords, raw tokens, or secret files through public contact forms.

We keep data only as long as we need it.

Our site-stats tool keeps visit data for about 14 months.

Campaign context that is not linked to an account is deleted after 90 days.

Campaign context that is linked to an account is removed within 24 months, or sooner when you ask us to delete your data.

Site stats and campaign data should stay bounded and content-safe.

Use the contact page for privacy questions or data requests.