Last updated: 2 October 2026
This policy explains what the DeveloperCards iOS app collects, why, who handles it for us, how long we keep it and what you can do about it. It replaces the version dated 4 December 2025, which no longer described the app correctly. Since then, DeveloperCards has added optional accounts, cloud sync, in-app purchases, crash reporting and optional anonymous usage counts.
DeveloperCards is made by TimeAwake Limited, a New Zealand company in which one developer builds and runs the app and its servers ("we", "us"). Our contact details are at the end of this policy.
Summary
- You don't need an account. You can study, collect cards and set reminders without signing up. Without an account, your progress, review history and collection stay on your phone.
- Accounts are optional. If you create one, we store your email address and an account ID. We also back up your study progress and review history, your card collection and draw balance, your Premium status and any card reports you send, so you can restore them on another device.
- Some data is sent with or without an account. This covers crash and performance reports (Sentry), update and settings checks, deck downloads and Premium checks with RevenueCat. If they are switched on, it also covers anonymous usage counts, which carry no account or device ID.
- No ads, no tracking, no selling. The app contains no advertising code. It never asks to track you and does not use Apple's advertising identifier. We do not sell or rent your information, and we do not share it with advertisers or data brokers.
- You can delete your account in the app under Me › Settings › Account › Delete account. Some copies outlive deletion, such as backups and logs. See "How long we keep data".
- Our servers are in Amazon Web Services' Sydney region in Australia. Some service providers are in the United States or other countries.
What we collect and why
Using the app without an account
Your decks, progress, collection, draw balance, Mistake Book and settings are kept on your phone (see "What stays on your device"). The app still connects to a few services so that it can work:
- Deck downloads. Free decks come from our content delivery network, Amazon CloudFront. Premium decks are downloaded directly from our file storage (Amazon S3, Sydney) through a short-lived link our server creates. These download requests contain no account or personal details. As with any web request, the server sees your IP address and the app's user-agent string. We have not switched on access logs for these downloads.
- App settings check. At every launch, the app downloads a small settings file from GitHub (raw.githubusercontent.com). The file tells the app whether an update is required and which features are on. The request contains no identifiers, but GitHub sees your IP address and user agent.
- App updates. At launch, and when you return to the app (at most every 10 minutes), the app asks Expo's update service (EAS Update) whether newer app code is available. The request includes:
- a random ID that Expo's library creates for this installation
- the platform, the app version, the update channel and the update IDs
- if the previous launch ended in a fatal error, the text of that error (up to 1,024 characters)
- Premium checks with RevenueCat. The app contacts RevenueCat when you open the Premium screen (to show prices), when you open a premium deck (to check whether you have Premium), and when you sign out or delete your account, whether or not you are signed in. See "Purchases (Premium)".
- Crash and performance reports and anonymous usage counts, described below.
Creating and using an account
You need an account only for cloud backup and sync, buying or restoring Premium, and reporting a problem with a card.