Privacy in practice
A household plan, not a public family page.
When Baby’s Home is built around one household and the people it invites. This page explains the product’s current privacy boundaries in plain language. Formal legal notices will govern where their terms apply.
The household controls the link.
Helpers enter through a household-scoped private link. The organizer controls who receives it and can replace or disable it. There is no public household directory.
Helpers do not create global accounts.
A helper’s contact, interests, on-call choice, suggestions, and commitments stay scoped to that household. A helper cannot use them to browse another family.
People see only what they need.
Helpers can see public activity descriptions and schedule states for the household they entered. They do not see another helper’s name. Organizers can see names where coordination requires them.
Private instructions stay private.
Door codes, addresses, food preferences, and similar instructions are not shown on the shared helper page. They can reach only the person who claimed that task, in the relevant reminder.
The optional photo is app-only.
If a family adds one baby photo, it is rewritten without metadata, stored privately, and shown only inside an authorized launched household session. It is never included in email or served at a public media URL.
Public pages stay household-free.
Public metadata, analytics, logs, previews, and test fixtures must not contain private family content. Product evidence uses bounded, content-free records instead.
Private links still need care.
Anyone who can redeem the household link may be able to view and save what that link permits. Families should share it only with people they trust and replace it if it travels too far.
Retention promises stay literal.
Active household data is not automatically deleted after four weeks. The archive and deletion process is still part of private-beta preparation, so no response-time promise is published yet.
Invite-controlled private beta