A privacy notice grounded in the Pairnt shell that ships today
Pairnt is designed for durable co-parenting coordination, so it necessarily handles sensitive family and case information. This launch privacy notice explains what the shipped product appears to collect and how that information is used inside the current shell.
Launch posture
What the current product handles
This page is deliberately specific about the app that exists today: Pairnt uses Supabase-backed auth and app data, stores case information needed for the shell to function, and separates some private records from case-visible ones.
- The sign-in flow uses email magic links.
- The app stores case, profile, message, calendar, expense, record, call-log, and export-request data that users create inside the shell.
- Some records can be marked private to the current user, while shared case content is visible according to membership and module access.
Auth provider pattern
Supabase
Access boundary
Case membership
Private-note support
Partial today
Information Pairnt collects
The app collects the information needed to authenticate you, place you in the right case, and display the records you create.
- Account and profile data such as your email address, display name, and avatar information when available.
- Case data such as memberships, child profiles, messages, calendar events, expenses, journal entries, documents, moments, call logs, and export requests.
- Operational metadata such as timestamps, actor identifiers, and workflow status fields that keep the case timeline understandable.
How Pairnt uses that information
The current release uses stored information to authenticate sessions, enforce case access, render product modules, and maintain durable context across the workspace.
- To sign users in, validate sessions, and redirect unauthenticated visitors away from protected routes.
- To determine which case a user belongs to and which modules that role can access.
- To preserve message history, read receipts, records, expenses, scheduling context, and other accountability-oriented case activity.
How visibility works today
Not every piece of information in Pairnt is visible the same way. Some content is shared as part of the case record and some content can be stored as private to the current user.
- Case-visible messages and other shared records are intended to remain visible in context for the members who can access that module.
- Some records flows include a private visibility option so personal notes do not automatically become part of the shared case view.
- Role-aware module access means not every member necessarily sees the same navigation or data surface.
Pairnt does not describe itself in this repo as HIPAA-certified, SOC 2 certified, or fit for emergency response. You should not infer those claims from the product’s tone or design system alone.
Because Pairnt is still in an early release, some support, export fulfillment, and operational follow-up may involve manual handling by the Pairnt team rather than a self-service workflow. When that changes materially, this page should be updated to match.
For questions about how a particular workflow behaves in the current release, compare this notice with the in-product explanation on the trust page after signing in.
Keep reading Pairnt honestly
Read Pairnt as a boundary-setting product
Privacy in Pairnt is about boundaries as much as storage: understanding what is visible to the case, what stays private to you, and where the current release still relies on manual handling rather than automated fulfillment.