What we keep, what we don't.
Plain English, no dark patterns. We're a pre-launch waitlist — this is short on purpose.
What we collect right now
If you join the waitlist, we collect the email address you give us. That's the only thing we keep.
The site itself uses Cloudflare Web Analytics to count visitors — it tells us things like "30 people visited the privacy page this week" without setting any cookies, fingerprinting your browser, or tying any of it back to you personally. No tracking pixels, no third-party advertising, no cross-site tracking.
What we use it for
We'll send you one email when the app is ready to open. You can reply with anything — feedback, questions, requests to be removed. We may send a maximum of one update before launch if something material changes (e.g. timeline shift). That's all.
Who we share it with
Nobody. We use Formspree to receive form submissions and Netlify to host the site — both are bound by their own privacy policies and act as processors. We don't sell your address, ever. We don't run ads.
The promise. No data resale. No social feed. No nudges. The product itself is built around the same principle: your story is yours. We just use it to find you a good match.
Cookies & tracking
This site sets no cookies. Cloudflare Web Analytics (mentioned above) is cookieless on purpose — it counts visits server-side without storing anything in your browser, and it never combines this data with data from other sites or with your identity.
The fonts are loaded from Fontshare's CDN; check their privacy policy for what they log on font requests (typically just standard CDN access logs).
Your rights
- Removal. Email us and we delete your address within seven days.
- Access. Email us and we'll tell you everything we have on file (it'll be: your email).
- Portability. Same as above — we'll send you the one row.
When you use the iOS app
The actual product (where you'll write prompts and meet matches) collects more data than this waitlist site does — because it has to, to work. Specifically:
- Firebase Analytics (a Google service) records how you use the app: when you complete signup, when you submit your narrative, when you swipe, when you match, when you send a message. We log counts and categories, not content — never your words, never the AI's read on your archetype, never who you matched with, never what you wrote in chat.
- Each event is tagged with a scrambled version of your account ID (a one-way hash with a project-specific salt) so we can see things like "people who finish the narrative are 3× more likely to come back day 2." We can't reverse the hash to your phone number or any other identifying info, and Google doesn't share it with advertisers.
- Firebase Crashlytics logs app crashes so we can fix them. Includes device model and OS version, never your content.
- You can opt out of analytics at the iPhone-system level: Settings → Privacy & Security → Tracking. The app honors that toggle.
- When you delete your account, we also delete your Firebase Auth identity — which severs the link between you and any historical analytics events. Existing event records auto-purge per Google's retention policy (event-level data is kept up to 14 months).
The full app privacy policy (covering what you write, how matching works, retention, and AI processing) will be linked from inside the app itself before you create an account, and you'll have to accept it separately. Joining this waitlist does not create an account in the future product.
When the app launches
We'll publish the full app privacy policy before opening signups. It'll cover everything in the section above plus details on how your trauma narrative is encrypted, who has internal access, what the AI providers (OpenAI, Anthropic) see, and how matching works mechanically.
Contact
Questions, deletion requests, or anything else: hello@mybaggage.app.
Changes
If we update this page before launch, we'll bump the date at the top. Material changes (e.g. new processors) get an email to everyone on the list.