Trust & Safety
How TwoHomes protects your family's data
Your custody data is among the most sensitive information you'll ever store digitally. Here's exactly how we protect it — in plain language, not legalese.
Passwords are hashed with bcrypt before storage. We never store plaintext passwords, and our staff cannot recover them. If you forget yours, you reset it via email — we cannot tell you what it was.
All connections to TwoHomes in production are encrypted via HTTPS (TLS 1.2+). Your data is never transmitted over unencrypted HTTP.
Your family data is stored in a managed PostgreSQL database on Render.com with encrypted storage at rest. Document uploads are stored in encrypted object storage.
Sessions use HttpOnly, SameSite=Lax cookies with a 30-day expiry. Sessions are invalidated on password change, and you can sign out of all devices from Settings. Session tokens are cryptographically random and stored as hashed values.
Four roles govern what each account can see: Party (full co-parent access), Lawyer (read-only access to their clients' records), Child (calendar and appointments only — no messages, finances, or legal data), and Admin (family administration).
Messages and exchange check-ins are append-only. Once sent or confirmed, they cannot be edited or deleted. This is intentional: it preserves the integrity of co-parenting records for potential court use.
Each co-parent can only see their own private notes and settings. Shared records (calendar, messages, ledger) are visible to both parents — but side-specific namespaces are isolated at the database level.
Render.com's managed PostgreSQL provides automatic daily backups with point-in-time recovery. Backups are retained for 7 days.
If you discover a security vulnerability in TwoHomes, please report it to us before disclosing publicly. We'll respond within 48 hours, work with you to understand the issue, and credit you in our disclosure (if you'd like).