Ethical Considerations in Co-Parenting Apps: Striking a Balance Between Convenience and Privacy Rights

What you are actually signing up for with co-parenting apps

If you have been ordered by a family court in the United States to use one of the major co-parenting apps, or if you are weighing one as a way of taking the heat out of high-conflict communication with an ex, the most useful thing to understand before you choose between them is what these apps technically are. They are court-grade communication and scheduling platforms whose business model is built on creating a permanent, time-stamped, unalterable record of what two co-parents say to each other and to their lawyers. OurFamilyWizard, the category leader, is now accepted by courts in all fifty US states and has over one million co-parents and family-law professionals using the platform (OurFamilyWizard). That is not a marketing detail. That is the load-bearing feature of the entire category.

The reason these apps exist, and the reason judges like them, is the same reason data-privacy researchers worry about them: every message you send goes into a court-admissible archive. The same property that makes the app useful for documenting a non-cooperative ex makes it useful for the app provider, the opposing attorney, a subpoena-empowered third party, and — in some configurations — your own future cross-examiner. This is not a hypothesis. It is the design.

Most parenting press on this topic treats the apps as straightforwardly helpful technology and skips the privacy mechanics. This piece does the opposite. I am going to walk you through what you are actually signing up for when you choose one of these apps, name the five major ones and what they each do with your data, name the regulations that do and do not apply, and close with one concrete data-minimisation move you can make this week regardless of which app you are on.

A practical note before we begin. As of 2026 the "truly free" co-parenting-app landscape has narrowed: AppClose ended its free tier in January 2025, and TalkingParents ended its free plan in March 2025 (LakeMunro Law, 2025 Co-Parenting Apps review). Most older "best free co-parenting apps" listicles you will find on a Google search are out of date on this. Plan on paying.

HIPAA does not protect what you send in a co-parenting app

This is the single most important fact about co-parenting apps and it is missing from almost every existing guide on the SERP. So I am going to put it in plain English.

HIPAA — the Health Insurance Portability and Accountability Act — protects health information that is held by a "covered entity": doctors, hospitals, health plans, healthcare clearing-houses, and their business associates. Co-parenting app providers are not covered entities under HIPAA. They are SaaS communication platforms. The protected-health-information protections you would expect at a pediatrician's office do not transfer when you type the same information into a co-parenting app message. As the Pittsburgh Lesbian Correspondents reporting put it in March 2026, court-ordered users may have "signed away" PHI and PFI the moment they accepted the app's terms of service — HIPAA "would not protect anything disclosed in the app texts" (Pittsburgh Lesbian Correspondents, March 2026).

What this means in practice: the message you sent your ex about your child's ADHD medication, the therapy session timing you coordinated via the app, the mental-health diagnosis you described to explain why an exchange needed to be rescheduled — none of those have the legal protection they would have if you had said them at the doctor's office. They are subpoena-accessible. They are court-admissible. They can be shared with opposing counsel. In some configurations they can be reviewed by the app's own customer-support staff during a dispute.

This is true for all of the major apps. OurFamilyWizard is not HIPAA-covered. TalkingParents is not HIPAA-covered. AppClose is not HIPAA-covered. The security features each of them advertises — encryption in transit, password protection, multi-factor authentication — protect the data from third-party interception. They do not give it HIPAA protection, because HIPAA does not apply to entities outside the statutory definition. This is not a flaw the apps have. It is a feature of where the apps sit in the statutory map.

The practical move that follows: treat every message you write in a co-parenting app as if it could be read in open court by a hostile attorney. Because, structurally, it can be.

What the five major apps actually do with your data

Here is a side-by-side comparison of the five most commonly court-ordered co-parenting apps, on the privacy dimensions that most of the SERP listicles skip. I have built this against the Safety Net Project's nine-dimension framework from the National Network to End Domestic Violence's tech-safety arm, which is the most rigorous neutral third-party assessment available (techsafety.org — Co-Parenting Apps).

A few things this table makes visible that the listicle versions hide.

First, the HIPAA column is uniform across every US app. There is no "more HIPAA-compliant" choice in this category in the US. If the data you are coordinating is health data and you need HIPAA protection, you have to share it outside the app or accept that the app archive does not carry that protection.

Second, the retention defaults are mostly "indefinite unless you actively request deletion." That is the default for OurFamilyWizard, TalkingParents, AppClose, and coParenter as of the most recent published reviews. When your custody case ends, the messages do not automatically disappear. Most app archives persist on the provider's servers until you export and request deletion — and even then, the provider may keep backups for some period under their data-retention policy.

Third, 2houses is the European outlier. As an EU-based service it is subject to GDPR Article 8, which sets a higher baseline for child-data processing than US federal law. That is a real advantage for child-privacy. The trade-off is that 2houses has less established US court recognition than OurFamilyWizard, so if you anticipate a contentious custody hearing, the court-admissibility floor is lower.

Fourth, the "court admissibility" column matters as a feature, not just a property — every US-led app in the table actively markets itself on this. The trade you are making, in choosing any of these apps, is privacy for evidence. There is no version of the trade that gives you both at maximum.

Loading image...

The legal frame, in plain English

Three regulations come up across this topic and are worth knowing by name and number.

COPPA — the Children's Online Privacy Protection Act, 16 CFR Part 312. Applies to operators of websites and online services directed at children under 13, and requires parental consent before collecting personal information from children in that age range. For co-parenting apps, COPPA's relevance is narrower than parents often assume — the apps' direct users are the parents, not the children. Where COPPA does bite is when the app collects information about children (custody schedules, medical notes, location data) in ways the FTC has begun to treat as in-scope for the child-protection rules. The 2023–2025 FTC enforcement actions in adjacent child-data categories should be read as the direction this is travelling, even where current co-parenting-app practice has not yet been formally challenged.

California Consumer Privacy Act (CCPA), as amended by California AB 1394 for child users. If you live in California, AB 1394 strengthens the consent and data-handling requirements for services collecting information from California minors. This is the strongest US state-level child-data protection currently in operation. If your co-parenting app holds data about your California-resident child, your child has rights — at and after age 18 — to know what data the app holds and to demand its deletion under the CCPA framework. The app's compliance with this varies; check the app's CCPA disclosure page.

GDPR Article 8 (European Union). Sets the consent threshold for child users at 16 by default (member states may lower it to 13). This is the regulation that makes 2houses meaningfully different from the US-led options in privacy terms, because the EU regulatory floor is simply higher than the US federal one for child data.

A useful mental model: regulation in this category is built for an industry that mostly does not yet exist as a regulated industry. Co-parenting apps sit in the gap between communication platforms (lightly regulated), legal-evidence services (regulated by courts not statutes), and child-data services (regulated unevenly across jurisdictions). The gap is where the real privacy risk lives, and the regulations above name the edges of it without filling it.

When you cannot refuse the app

Most readers of this piece are not weighing whether to use a co-parenting app. They are using one because a judge ordered them to. The question of whether is settled. The question of how to use it well is open.

Data-minimisation is the move. The principle, borrowed from data-protection practice generally, is this: do not put information into the app that you do not need to put into the app for the purpose the app is serving. The purpose is documented co-parenting communication. The purpose is not your full medical history, your therapist's name, your child's diagnosis verbatim, your immigration status, your work schedule in granular detail, or your home address (the app typically already has it through registration, but you do not need to re-state it in messages). Anything that you can say in less specific terms, you should say in less specific terms.

Concrete examples of minimisation. Instead of "Need to reschedule because Ben has an appointment with Dr. Cassandra Reyes at the trauma clinic for his PTSD follow-up" — "Need to reschedule for one of Ben's healthcare appointments on Thursday." Instead of "I'm at my therapist's office until 2pm" — "I'm unavailable until 2pm." Instead of describing a child's behavioural episode in clinical detail — "Difficult day, can we move pickup to 6pm." The first version of each is normal human communication. The second version is the same coordination work, with significantly less material that could be subpoenaed, screenshotted, or quoted in an opposing brief.

Two practical add-ons. Strip metadata from photos before you upload. Most phones embed GPS coordinates in photo files. When you upload a photo of your child to the co-parenting app, the location data goes with it unless you remove it. On iPhone, Settings → Privacy & Security → Location Services → Camera → Never. On Android, the photo-edit screen typically has a metadata-strip option in the share menu. This is a thirty-second change and it materially reduces the location-data surface area of every photo you ever send through the app.

Export and request deletion when the case ends. Most apps keep your data on their servers indefinitely unless you actively ask them to delete it. When your custody case is closed, export the archive you may need for your own records and then file a written deletion request with the app provider. Their data-retention policy will tell you how long the deletion takes and what backups persist. Do not assume the data goes away on its own.

If you are in a high-risk situation

This section is for a smaller readership, but it is the readership for whom the stakes are highest, so it has to be said plainly.

The 2026 Pittsburgh Lesbian Correspondents reporting on co-parenting app risk raised the issue, explicitly, that data inside these apps can be subpoenaed not only by family courts but by federal authorities under recent executive orders — and that immigrant families, trans youth, families with mental-health diagnoses, and survivors of intimate-partner violence may face categorical risks that the average co-parenting-app user does not. The reporting did not frame this as a reason to refuse the app — most people in these categories cannot refuse a court order. It framed it as a reason for those readers to make their use of the app informed.

The relevant resource for a survivor of intimate-partner violence is the National Network to End Domestic Violence's Safety Net Project at techsafety.org, which maintains specific guidance on stalkerware risk, account-takeover risk, and the use of monitoring software by abusers (Safety Net Project). If you are in a current safety-planning situation, the Safety Net Project's resources and the NNEDV hotline are designed for exactly this conversation; a co-parenting-app guide cannot replace them, and this piece should not pretend otherwise.

For readers in the other named categories, the practical implication is that the data-minimisation principles above apply with additional weight. The fewer specifics about immigration status, gender identity, mental-health treatment, or medication you put into the app archive, the smaller the surface area for a subpoena to reach. None of this is a reason to refuse what a court has ordered. It is a reason to be deliberate about what you say inside what the court has ordered.

Loading image...

What to do this week

If you are about to choose a co-parenting app, the move that is most useful is to read the app's current data-retention and subpoena-policy pages — not the marketing pages, the legal pages. They are usually at the bottom of the app's website in small print. The thirty minutes you spend on those pages now is worth more than any number of "best of" listicles, because the listicles are mostly six months out of date and the legal pages are the actual contract.

If you are already on a co-parenting app and you have been using it without thinking much about the archive, the move that is most useful is the one that takes ten minutes tonight. Open the app. Look at the most recent fifty messages you sent. For each one, ask whether the level of specificity in the message was needed for the coordination work — or whether you were, as most people in high-conflict communication are, performing for the imagined record. Most readers will find at least a third of the messages can be re-written, in their own internal style, with less specificity for the same coordination effect. The next fifty messages you send can use the trimmed style. The app archive is a long horizon. The version of you that sends a tighter message today is the version your future self will be glad you were.

The co-parenting app category is, on balance, a real improvement over the era of text-message dispute and screenshot wars that preceded it. The category also genuinely does carry privacy trade-offs that the marketing material softens. The honest reader of this article is the one who uses the apps clearly, names the trade-offs, and gives the data archive the kind of attention they would give any other document that might be read aloud in court. That is, in 2026, the most useful relationship to have with the tool you may not be able to refuse.