Security Overview

The Mollify app is designed to help co-parents share sensitive scheduling and communication data. This page summarizes how Mollify family protects that information.

1. Transport security

Communication between the Mollify app and our API uses HTTPS (TLS). Do not use the Mollify app on networks you do not trust when handling personal information.

2. Authentication

Accounts are protected with industry-standard authentication. You may sign in with email and password or supported OAuth providers (Google, Facebook, Apple). Keep your device and account credentials secure.

3. Access control

Household data is visible only to accounts linked within the same co-parent household. API requests require valid authentication tokens. We review access patterns to reduce unauthorized use.

4. Data storage

Application data is stored on secured infrastructure operated by our hosting providers. Passwords are stored using strong one-way hashing. Mollify family applies reasonable technical and organizational safeguards appropriate to the data we process.

5. Messaging integrity

Co-parent messages are retained as a shared record and cannot be deleted after sending. This supports accountability between co-parents but means you should send messages carefully.

6. Third-party services

We rely on vetted providers for hosting, analytics (PostHog, in-app only), subscriptions (RevenueCat, Apple, Google), and email. Each provider is used only for its intended purpose, as described in our Privacy Policy.

7. Reporting issues

If you discover a security vulnerability or suspicious activity, contact us promptly at lewisl@mollifyfamily.com. We will investigate and work to address verified issues.

8. Your responsibilities

Use a strong device passcode, keep the app updated, and do not share invite codes with anyone other than your co-parent. Log out on shared devices when finished.

Last updated: June 16, 2026