Privacy at Pairnt
Pairnt handles sensitive family information. This notice explains what the service stores, how it is used, and how visibility works.
At a glance
What this notice covers
Pairnt uses email sign-in, stores the information needed for the service to work, and separates some private records from shared case content.
- Email magic links are used for sign-in.
- Account, case, message, calendar, expense, record, call, and export data are stored as part of the service.
- Some records can remain private to you, while shared case content follows membership and module access.
Sign-in method
Email magic link
Access boundary
Case membership
Private records
Supported
Information we collect
Pairnt 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 we use it
Stored information is used to authenticate sessions, enforce case access, render product modules, and maintain 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.
Visibility and access
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 remain 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 represent itself as HIPAA-certified or SOC 2 certified, and it is not an emergency service.
Some support, export handling, and operational follow-up may involve manual review rather than a fully self-service workflow.
For questions about how a specific signed-in workflow behaves, compare this notice with the explanation on the trust page after signing in.