Privacy Policy
Memodate is made by Ian Magee, an individual developer based in London, United Kingdom. This policy explains, in plain English, what the Memodate iPhone app does with your data. If anything here is unclear, email privacy@memodateapp.com.
The short version
Without an account, everything stays on your device. If you make an account, your email address, your name (if you give one) and your learning progress are stored so the app can restore your progress. There is no advertising, no tracking across other apps or websites, and nothing is sold to anyone.
What is collected
Account details
If you create an account, Memodate stores your email address and your name. You can sign up with email and password, with Sign in with Apple, or with Google. Sign in with Apple may give the app a private relay address instead of your real one, which is fine. Passwords are never stored in readable form.
Your learning progress
The app keeps a save file: the lessons and games you have done, your times and scores, and the numbers you have turned into pictures. With an account, that save is stored in Supabase, an EU-hosted Postgres database, and tied to your account so you can restore it. Without an account it never leaves your phone.
Purchases
Subscription state is handled by RevenueCat. That means Apple’s transaction identifiers and whether your subscription is active. Payment is handled entirely by Apple. Memodate never sees or stores card details.
Crashes and errors
If the app crashes or hits an error, a report is sent to Sentry: device model, operating system version, app version and a stack trace. These reports do not carry your name.
What is not collected
- No advertising and no ad identifiers.
- No tracking of you across other companies’ apps or websites.
- No selling or renting of personal data, ever.
- No contacts, photos, location or microphone access.
Why it is used, and the legal basis
Under the UK GDPR and the EU GDPR:
- Contract. Running your account, syncing your save and honouring your subscription are needed to provide the service you asked for.
- Legitimate interest. Crash and error reports are used to keep the app working. The data is minimal and cannot identify you by name.
- Consent. Creating an account is optional. You give consent by choosing to make one, and you can withdraw it at any time by deleting the account.
How long it is kept
Account details and your save are kept for as long as your account exists, and are deleted when you delete the account. Backups roll off within 30 days. Crash reports are kept for up to 90 days. Purchase records are kept as long as needed for support and for tax and accounting duties.
Deleting your account
Open Settings inside the app and choose to delete your account. That removes the account and the save from the database. You can also email privacy@memodateapp.com and it will be done for you. Deletion is permanent and the save cannot be recovered afterwards.
Your rights
You can ask for a copy of the data held about you, ask for it to be corrected or deleted, ask for it in a portable form, or object to a particular use. Email privacy@memodateapp.com and you will get an answer within 30 days. If you are unhappy with the response you can complain to the UK Information Commissioner’s Office at ico.org.uk, or to your local data protection authority.
Children
Memodate is not directed at children under 13, and accounts are not knowingly created for them. If you believe a child under 13 has an account, email privacy@memodateapp.com and it will be removed.
Who else handles your data
- Supabase — account records and your save file, on EU-hosted Postgres.
- RevenueCat — subscription state, using Apple’s transaction identifiers.
- Sentry — crash and error reports.
- Apple — the App Store, payment, and Sign in with Apple.
Each acts as a processor on the app’s behalf under its own agreement, except Apple, which acts as its own controller for payment and App Store matters. Where data is handled outside the UK or EEA, it is covered by standard contractual clauses.
Security
Traffic between the app and its servers is encrypted in transit, data at rest is encrypted by the hosting provider, and access to the database is restricted so an account can only read its own rows.
Changes to this policy
If this policy changes in a way that matters, the effective date at the top will change and a notice will appear in the app. The current version always lives at memodateapp.com/privacy.
Contact
Ian Magee, London, United Kingdom.
Privacy: privacy@memodateapp.com
Support: support@memodateapp.com