Privacy Policy — TwoNest

Last Updated: April 22, 2026

TL;DR TwoNest is a co-parenting app. Because both parents need to see the same calendar, messages, and expenses, your family's data is stored in Google Cloud Firestore under a family document that only the two paired parents can read and write. We do not sell data. We do not show ads — on either tier. Messages and expenses are deliberately permanent: once written, they cannot be edited or deleted, even by us. Subscriptions are processed by Apple, Google, and RevenueCat. Analytics and crash reports are anonymized and opt-out.

Important: permanence Unlike most apps, TwoNest enforces immutability on messages, expenses, and swap-request history at the database level. That is a feature of the product, not a technical limitation. "Right to erasure" requests can still be honored for your account (see Section 8), but specific messages and expenses in a shared family record cannot be unilaterally scrubbed from the other parent's view — they would have to be pseudonymized instead.

This Privacy Policy describes how Monsware ("we," "us," or "our") handles information in relation to your use of the TwoNest mobile application (the "App") across iOS and Android. It is written to be compliant with the EU General Data Protection Regulation (GDPR), the UK Data Protection Act, the California Consumer Privacy Act / CPRA, and Turkey's KVKK.

1. Who We Are (Data Controller)

Monsware is the controller of any personal data processed through the App.
Contact: [email protected]
Address: Turkey.
For users in the EU/UK, you may contact the same address for data-protection queries.

2. Information We Collect

2.1 Account Data (Required — You Sign In)

Unlike most of our apps, TwoNest requires an account — the two parents have to authenticate as the same family to share data. At sign-up or sign-in we collect:

Email address (email sign-in) or authentication token (Sign in with Apple, Sign in with Google)
Display name and, optionally, a profile photo you provide
A Firebase Authentication UID (a random identifier unique to your installation)
Your locale, theme preference, default currency, notification preferences, and receipt threshold

2.2 Family & Child Data (Shared Between the Two Parents)

When you create or join a family, you and the other parent share one family document in Cloud Firestore. Everything below is visible to both paired parents and only to them, enforced by Firestore security rules:

Family metadata: the invite code (expires after 7 days), custody pattern type and schedule
Child profiles: name, date of birth, photo (optional), blood type, allergies, current medications (name / dosage / frequency / time of day), height, weight, shoe/clothing size, emergency contacts (name / phone / relationship), and school info (school name, teacher name, teacher phone)
Calendar events: title, type (school / medical / activity / birthday / holiday / other), date, optional start/end time, optional child link
Day-swap requests: who requested, for which date, reason (optional), status, response, timestamps — history is immutable
Messages: sender, text, attachments (up to 10 MB each — photos or PDFs stored in Firebase Storage), read receipts, timestamps — immutable
Expenses: payer, amount, currency, title, optional description, category, optional child link, split rule and shares, receipt photo (if attached), verification status — immutable, corrections are new entries referencing the original
Server-computed balance between the two parents

2.3 Push-Notification Tokens

For handoff reminders, swap requests, and new-message alerts, the App registers a Firebase Cloud Messaging (FCM) token tied to your device and account. You can disable specific notification types in Settings → Notifications and revoke notification permission at the OS level.

2.4 Anonymous Analytics & Crash Reports

We collect anonymized, non-personally-identifying analytics and crash data through Firebase Analytics and Firebase Crashlytics. This includes:

Device model, OS version, app version, screen language and region
Which screens you visited and which features you used (event counts, not contents)
Crash stack traces and non-fatal error logs
Approximate country-level location derived from your IP (not precise GPS)

This data never includes the contents of your messages, expenses, receipts, child profiles, or custody schedule. You can disable analytics at any time from Settings → Privacy → Analytics.

2.5 No Advertising

TwoNest does not show ads on the free tier or any other tier. We do not integrate with ad networks. We do not collect your advertising identifier. Monetization is subscription-only.

2.6 Subscriptions & In-App Purchases

TwoNest Premium is processed by Apple App Store or Google Play, and verified through RevenueCat, Inc.. We never see your payment card, billing address, or store email. RevenueCat stores an anonymized user ID and the purchase receipt issued by the stores for entitlement verification; our backend webhook receives a purchase event and flips a server-only isPro flag on your user document.

2.7 Support Emails

If you email us for support, we receive your email address and the contents of your message. We use them solely to respond and keep the thread for a reasonable period for follow-up.

3. What We Do Not Collect

We do not sell your data. Full stop.
We do not run ads or collect your advertising identifier.
We do not use third-party analytics pixels, cross-site cookies, or fingerprinting.
We do not collect precise location (GPS) — only the approximate country implied by your IP for anonymized analytics.
We do not access your device contacts, photos beyond what you explicitly attach, microphone, or calendar (except when you opt into calendar sync, which writes to your device calendar; it does not read it).

4. How Data Is Shared Between the Two Parents

The core premise of a co-parenting app is that both parents see the same record. When you and the other parent are paired into a family:

Both accounts can read the full family document, child profiles, messages, expenses, calendar events, and swap requests.
Both accounts can create new messages, expenses, events, and swap requests.
Neither account can edit or delete existing messages, expenses, or swap-request history — this is enforced in the database, not just the UI.
A user's private Settings (default currency, receipt threshold, notification toggles) are stored under that user's own document and are not visible to the other parent.
Family membership is capped at two parents. Extended-family read-only access may be added in a future release; it will not change existing sharing rules without your explicit action.

5. Legal Bases for Processing (GDPR)

Purpose	Legal basis
Providing core App functionality (family, messaging, expenses, calendar)	Contract (Art. 6(1)(b))
Keeping an immutable record of shared activity	Legitimate interest — integrity of a shared co-parenting record (Art. 6(1)(f))
Crash reports	Legitimate interest — app stability (Art. 6(1)(f))
Analytics	Consent (Art. 6(1)(a)) — shown at first launch, revocable anytime
Push notifications	Consent (Art. 6(1)(a)) via OS prompt; legitimate interest for transactional alerts once enabled
Subscription processing	Contract (Art. 6(1)(b))
Responding to support emails	Legitimate interest (Art. 6(1)(f))

6. International Data Transfers

Our primary infrastructure provider, Google (Firebase Authentication, Firestore, Firebase Storage, Firebase Cloud Messaging, Firebase Analytics, Firebase Crashlytics), may process data in the European Union, the United States, and other regions where Google operates data centers. Subscription processing with RevenueCat and the app stores may involve US transfers. When data leaves the EU/UK, transfers are covered by the EU–US Data Privacy Framework and/or the Standard Contractual Clauses adopted by the European Commission.

7. Data Retention

Family data (messages, expenses, calendar, children): retained for as long as at least one paired parent keeps an active account. If both parents delete their accounts, the family document is scheduled for deletion 30 days later to allow for accidental-deletion recovery.
Attachments (receipt photos, message attachments): retained alongside the family data they belong to; deleted on the same schedule.
Analytics & crash data: Firebase defaults (up to 14 months for analytics; 90 days for crash logs).
Subscription records: retained by the App Store / Google Play / RevenueCat for the duration required by tax and consumer-protection law (typically up to 10 years).
Support emails: up to 3 years, then deleted, unless needed for an open matter.

8. Your Rights

Depending on where you live, you have the right to:

Access the personal data we hold about you
Correct inaccurate data
Request deletion ("right to be forgotten")
Restrict or object to processing
Receive your data in a portable format
Withdraw consent at any time (for analytics, notifications)
Opt out of the "sale" or "sharing" of personal information (California: CCPA/CPRA) — note we do not sell or share data
Lodge a complaint with your local data-protection authority (EU/UK)

Most rights are exercisable directly inside the App. To delete your account, open Settings → Account → Delete Account; you will be asked to confirm. Because family data is shared with the other parent, deletion removes you from the family but preserves the shared record for the other parent. If both parents delete their accounts, the family document is purged 30 days later.

For other requests (analytics history, subscription records, support emails), send a request from the email associated with your inquiry to [email protected]. We will verify your identity and respond within 30 days (or as required by your local law).

9. Children's Privacy

TwoNest is used by adults to coordinate care for their children — children themselves are not the users of the App. We do not knowingly create accounts for people under 18. Child profiles (name, medical info, school) are created and managed by the paired adult parents under their own account responsibility. Please do not share your login credentials with your child.

10. Security

We follow industry best practices: authentication via Firebase Auth (Google Sign-In / Sign in with Apple / email+password); Firestore data encrypted in transit (TLS 1.2+) and at rest; security rules gate every read and write to a family document on membership; server-only fields (isPro, aggregated balance, server-computed timestamps) cannot be written from the client. No system is perfect — use a strong password or a passkey, and do not share your device passcode with people you do not trust.

11. Sub-Processors

Provider	Purpose	Region
Google LLC (Firebase Auth, Firestore, Storage, FCM, Analytics, Crashlytics, Cloud Functions)	Authentication, cloud storage of family data, push notifications, analytics, crash reporting, backend automation	EU, US
RevenueCat, Inc.	Subscription receipt verification and entitlement sync	US
Apple Inc. / Google LLC	App distribution & payment processing	Worldwide

12. Changes to This Policy

We may update this Policy. When we do, we will revise the "Last Updated" date above and, for material changes, show an in-app notice on next launch.

13. Contact Us

Privacy questions or requests: [email protected]
General support: [email protected]