Privacy Policy
Last updated: October 2026
This page explains what Baby Registry collects, why, and how you (or any family using the Service) can see, export, or delete it.
1. What we collect
- Account data: your email, a hashed password (we never store your actual password), and your name if you provide one.
- Registry content: baby name, due date, photos, milestones, journal entries, and anything else a parent chooses to post.
- Guest data: when someone claims a gift, comments, or RSVPs, we store the name/email/message they provide — the same information they're choosing to share with the family.
- Technical data: a hashed (not raw) form of IP address is kept briefly to enforce rate limits against spam/abuse, and standard web server logs.
- Payment data: handled entirely by Stripe — we never see or store your card number. We keep a record of the transaction (amount, date, plan) for your invoice history.
2. What we don't do
- We don't sell or rent any family's data to anyone, ever.
- We don't run third-party ad trackers on tenant registries.
- We don't index tenant registries in search engines — every registry page is marked
noindex, nofollow, noarchive, nosnippet, and is reachable only via its secret link or an authenticated custom domain.
3. Children's data
This Service is designed for parents to post about their own child — the child is not a user of the Service and does not create an account or provide their own information. We understand that photos and details of a minor are still sensitive:
- Only the parent(s) who control the registry decide what's posted about their child.
- A registry is reachable only by its secret link, a custom domain the family controls, or an explicit invite — never discoverable publicly.
- A parent can export or permanently delete their entire registry (including every photo) at any time — see Section 5.
- We do not use any registry's content — including photos or details of a child — for advertising, profiling, or to train any machine learning model.
4. Cookies
We use only functional cookies, not advertising or cross-site tracking cookies:
- A session cookie so you stay logged in as a parent/admin.
- A "recognize me" cookie for guests who've claimed a village profile, so liking a memory is one tap instead of retyping your name/email every time. It only identifies you to the one registry that set it.
5. Your rights: export & deletion
From your billing page, you can:
- Stop the weekly email — if a family switches on the optional weekly village roundup, every one of those emails carries a one-click unsubscribe that needs no login and no registry link. It only goes to villagers who confirmed their email address by clicking a link, and never in a week when nothing happened.
- Export everything — a ZIP of every photo (full resolution) plus a manifest of every milestone, journal entry, gift, and guest, any time, on any plan.
- Permanently delete your registry — removes your tenant's database, every uploaded photo, and its platform records. This cannot be undone, which is why it requires typing your registry's name to confirm. We recommend exporting first.
A guest who wants their own comment/RSVP/claim removed can ask the family (who can hide or delete it from their admin console), or contact us directly and we'll help.
6. Data retention
We keep your data as long as your account exists. If a subscription lapses, your data is kept (read-only) rather than deleted — see the Terms of Service. Backups are retained on a rolling basis (typically 14 days) and age out automatically.