Privacy Policy — MyRelations
Effective date: April 28, 2026 Last updated: April 28, 2026
MyRelations ("MyRelations", "we", "us", "our") is a private relationship journaling app. This v1 of the app is local-only — your journal entries never leave your device. This Privacy Policy explains the limited data the app touches, why, and your rights over it.
If anything is unclear: hello@my-relations.app.
1. Who we are
My Relations is the operator of this app. The app is distributed via Google Play, the Apple App Store, and at https://my-relations.app.
Contact: hello@my-relations.app
2. Plain-language summary
- Your journal stays on your device. Names of partners, session types, ratings, moods, notes, locations you type, tags, dates — all stored locally in an SQLite database on your phone. We never see it. It never leaves your device. There is no cloud sync, no account, no email, no password.
- The only data that leaves your device is what's required for in-app purchases (subscription / lifetime purchase) and a single read of a public counter showing how many lifetime promo slots are left. Both are detailed below.
- No tracking. No ads. No data selling. No third-party analytics.
3. What data we touch
3.1 Stored locally on your device
- Journal content: partners you add, session logs, ratings, moods, notes, tags, dates, locations you type, durations, your chosen name. All in a private SQLite file inside the app's sandboxed storage. Other apps cannot read it.
- App preferences: notification toggle, default privacy toggle, appearance choice (light/dark/system), Pro entitlement flag. Same SQLite file.
- Pro entitlement cache: a boolean mirrored from RevenueCat (see 3.3) so the paywall doesn't re-check on every launch.
This data is not transmitted anywhere. If you uninstall the app, this data is deleted by the OS as part of the standard sandbox cleanup. You can also wipe it manually from the in-app Settings → Delete all data.
3.2 Data you can export
Settings → Export my data writes a JSON file containing all the data above to your device's documents folder and opens the system share sheet so you can save it to Files, email it to yourself, or move it elsewhere. The export is a copy — the original stays in the app.
3.3 Data sent to third parties (only when needed)
RevenueCat (in-app purchases) — when you tap a purchase button on the paywall, RevenueCat receives your Apple/Google purchase event and sends back the entitlement status. RevenueCat sees an anonymous device-generated user ID (no email, name, or PII), the product you purchased, and the purchase receipt validated by Apple/Google. We use this to know whether you're a Pro user. RevenueCat's privacy policy: https://www.revenuecat.com/privacy
Apple App Store / Google Play Billing — payments are processed by Apple or Google. We never see your card or billing details. Their privacy policies apply: Apple https://www.apple.com/legal/privacy/ — Google https://policies.google.com/privacy
Lifetime promo counter — on app launch and when you open the paywall, the app makes a single GET request to a public counter endpoint we operate, which returns a number (e.g. { "remaining": 847 }) to drive the "Only N lifetime slots left" scarcity message. This request includes nothing about you — no user ID, no device ID. Standard server access logs (your IP address + timestamp) may be retained briefly by our hosting provider (Supabase) per their default retention.
That is the entirety of the data leaving your device.
3.4 Data we do NOT collect or transmit
- No email, name, password, or account credentials (there are no accounts in v1)
- No journal content (sessions, partners, notes, ratings) — never
- No precise GPS or location services — locations you type are local strings
- No contacts, camera, microphone, or photo library access
- No biometric, health, or financial data
- No analytics SDK (no PostHog, no Amplitude, no Mixpanel, nothing)
- No advertising IDs, no IDFA, no ad tracking
- No crash reporting that includes your data (none in v1)
4. Why we touch what we touch
| Purpose | Data touched | Legal basis (GDPR) |
|---|---|---|
| Run the app you installed | local-only journal content | Contract |
| Sell you a subscription or lifetime | RevenueCat purchase event | Contract |
| Show "N lifetime slots left" | counter GET request | Legitimate interest |
| Reply to support email | your message | Contract |
5. Storage and security
- Your journal is stored in the app's iOS / Android sandboxed storage, protected by the OS at rest. We do not store it on any server.
- The lifetime counter is served from Supabase Edge Functions over HTTPS. The counter endpoint is read-only and contains a single integer.
- RevenueCat communications are HTTPS.
- We have no production database of user content. There is nothing for us to be breached on.
6. Sharing your data
We share your local journal data with no one. It never leaves your device unless you export it.
The narrow third-party data described in §3.3 is shared only with the specific processors named there (Apple, Google, RevenueCat, Supabase) and only for the specific purpose described.
We may disclose data we hold (which is essentially: nothing about your journal, plus minimal RevenueCat purchase records you've consented to via store purchases) if legally required (subpoena, court order). We will push back on overbroad requests.
7. International transfers
Our hosting provider (Supabase) may process the lifetime counter request in the US or EU. The counter contains no personal data, so transfers are not a meaningful risk. RevenueCat operates globally.
8. How long we keep data
- On your device: as long as you keep the app. Wiped on uninstall or via Settings → Delete all data.
- RevenueCat purchase records: retained per RevenueCat's policy and tax-law requirements (typically 7 years).
- Lifetime counter access logs: standard hosting-provider defaults (typically 30-90 days).
9. Your rights
Under GDPR, CCPA, UK GDPR, and similar laws, you have rights to access, correct, delete, export, restrict, object to, and withdraw consent for processing of your data.
In v1, almost all of these rights are self-served from inside the app:
- Access: open the app — you have it all
- Correct: edit any partner or session in-app
- Delete: Settings → Delete all data (instant, complete)
- Export: Settings → Export my data (JSON)
For RevenueCat purchase records, contact RevenueCat directly (https://www.revenuecat.com/contact) or email us at hello@my-relations.app and we will help.
For complaints, you can lodge with your local data protection authority.
10. Children
MyRelations is not intended for children under 16. The "intimate" session category means the app is rated 17+ on the App Store and Mature on Google Play. We do not knowingly process data from children. If you believe a child has installed the app and you're a parent or guardian, you can wipe data from inside the app or uninstall.
11. Security
The app uses iOS and Android's standard sandboxed storage, which is encrypted at rest by the OS when device-level encryption is enabled (default on modern devices with a passcode). All third-party network calls are HTTPS. We have no servers storing your journal content; there is no production database of user content to be breached.
12. Third-party links
The app may link to our homepage (my-relations.app), Apple's App Store, or Google Play. Their privacy policies apply.
13. Changes to this policy
We may update this policy. Material changes will be announced in-app or by a banner on my-relations.app at least 14 days before they take effect. Continued use of the app after changes means you accept the new version.
14. Contact
Questions, requests, or complaints: hello@my-relations.app https://my-relations.app