Launch terms for a durable co-parenting workspace
These launch terms explain how Pairnt may be used today. They are intentionally plainspoken: Pairnt is a premium co-parenting workspace for durable communication, scheduling, expenses, records, and export requests, and some later-stage features remain works in progress.
Launch posture
Built around the release that exists
Pairnt is a launch-stage product. These terms are written to match the current shipped shell, not a future roadmap.
- The live product centers on messaging, calendar events, expenses, records, exports, sign-in, and onboarding.
- Some workflows already save durable history, while others currently log requests or operational facts ahead of full automation.
- You should not rely on Pairnt for emergency communication, legal advice, or time-critical crisis response.
Authentication model
Magic link
Primary promise
Durable records
Emergency coverage
Not provided
Using the service
You may use Pairnt only for lawful case coordination, caregiving logistics, documentation, and related collaboration tied to your role in a case.
- You are responsible for the accuracy of what you enter, upload, or request through the workspace.
- You may not use Pairnt to harass, threaten, impersonate, or interfere with another person's access to a case.
- You may not probe, copy, scrape, or bypass access controls for cases, records, or users you were not invited to view.
Accounts and access
Access is currently based on email sign-in and case membership. Sessions are server-validated and authenticated routes redirect back to sign-in when the session is not available.
- Keep control of the email address you use for Pairnt, because magic-link authentication depends on that inbox.
- You are responsible for activity taken through your account until you lose access and notify the Pairnt team through available support channels.
- Role-based access may limit which modules a given case member can view inside the authenticated shell.
Availability and scope
Pairnt is evolving quickly. Some surfaces already perform the underlying workflow, and some currently capture durable requests, logs, or history ahead of full file delivery, media handling, or automation.
- Export requests and call logging should be understood according to the behavior shown in the product today, not as a promise of automatic downstream delivery.
- Features described as upcoming, eventual, or future-facing are not commitments to ship on a specific timeline.
- Pairnt may change or remove features, limits, or visual structure as the product matures.
By accessing or using Pairnt, you agree to these terms. If you are using Pairnt on behalf of a firm, coordinator, or other organization, you represent that you have authority to do so for that organization.
Pairnt is not a law firm, mediator, therapist, emergency dispatcher, or payment processor. The service helps organize communication and records. It does not replace professional advice or mandatory emergency channels.
If you believe a case invitation, export request, or record was created in error, stop using that flow and review the current guidance on the support page. Continued use after terms updates means you accept the revised version once it is posted here.
Keep reading Pairnt honestly
Use Pairnt with the current release in mind
Pairnt works best when the ground rules are clear: use it for accountable coordination, keep your login secure, and avoid assuming a feature exists just because a future-facing concept appears in product language.