Ormy · Last reviewed 14 November 2026 (PostHog in the app now counts day-to-day use, anonymously)
These are essential. Ormy cannot function without them.
| Provider | Purpose | Personal data processed | Location | Transfer safeguard |
|---|---|---|---|---|
| Convex Privacy terms |
Database, server functions, scheduled jobs. This is where Ormy's data lives. | Account details, reminders (including the coordinates and radius of any place pinned to one), chat messages, check-ins, activity log, recaps, push tokens, subscription status | United States | SCCs + UK Addendum |
| Clerk Privacy terms |
Authentication, session management, Sign in with Apple. | Name, email address, authentication credentials, session and device metadata, IP address | United States | SCCs + UK Addendum |
| Anthropic Privacy terms · Trust centre |
Asks one question in the heads-ups Ormy sends, and suggests a next step when a reminder is ticked off. Never the reminders themselves. | The title of the reminder involved, and for a heads-up how many days away it is. Never the user’s name or location. Not used to train models. | United States | SCCs + UK Addendum |
| Expo Privacy terms |
Push notification delivery, over-the-air app updates, build infrastructure. | Push notification tokens and the content of notifications sent to a device | United States | SCCs + UK Addendum |
| Apple Privacy terms |
App distribution, Apple Push Notification service, payment processing, Sign in with Apple. | Push tokens, notification content, purchase and subscription records, Apple ID identifiers | United States and global | Apple's own transfer framework |
| RevenueCat Privacy terms |
Subscription state, entitlement checks, purchase receipts. | An app-generated anonymous user identifier, purchase receipts, subscription status. No name, no email, no reminder content. | United States | SCCs + UK Addendum |
| Resend Privacy terms · DPA |
Sends Ormy's emails: the email confirming a waitlist sign-up, later waitlist emails, and feedback sent from the app, passed on to us. | Email address and the content of the email. For feedback, the sender's name, email address and message. | United States | SCCs + UK Addendum; EU–US Data Privacy Framework |
| Provider | Purpose | Personal data processed | Location |
|---|---|---|---|
| GitHub Site policies |
Hosting for these legal pages. | Standard web server logs, including IP address | United States |
| PostHog Privacy terms · DPA |
Visit counts and how the website (getormy.com) is used. In the app, anonymous counts of how Ormy is set up and used day to day, crash details and optional survey answers. | Website: pages viewed, clicks, scrolling, browser and device type, IP address and the approximate location worked out from it. Only with the visitor’s yes (asked first in the UK and Europe; elsewhere on unless they say no): a browser ID and visit recordings, with anything typed hidden. App: the screen, step or tab shown, app opens and closes, the sign-in method and any error code, the notification and AI answers, the plan and whether it renews, the settings new reminders use, ticks, snoozes, skips, edits and deletes, which kind of alert was opened, crash details, any survey answers, a random ID kept on the phone, the app and iOS version, and the IP address any server sees (no location worked out from it). Not linked to an account, never your answers or what your reminders say. Off in Settings → Usage stats. | EU (Frankfurt) |
| Email provider | Support and account correspondence. | Your email address and whatever you write to us | United Kingdom / EEA |
Named explicitly, because their absence is the point:
Before a provider gets access to personal data we confirm that it:
We review this list at least annually, and whenever we change any part of the stack.
Adding or replacing a sub-processor is a change to how your data is handled, so we treat it as one.
To ask about a specific provider, request evidence of a transfer safeguard, or object to a change, email support@getormy.com.