Verified 2026-08-11
How ManageSubs handles data
ManageSubs is designed around records you enter yourself, but “private” does not mean that no service ever receives data. This overview explains the current data flows on iOS and Android in plain language. The English Privacy Policy is the controlling legal document.
Your subscription records
Names, prices, currencies, billing cycles, renewal dates, categories, family members, notes, cancellation information, and budget settings are stored in the app’s on-device database. ManageSubs does not connect to your bank or read your financial transactions, and it does not operate a server that keeps a complete copy of your subscription database.
Backup and sync differ by platform
On iOS, if you enable iCloud sync those records are also stored in your private CloudKit database so they can sync across your Apple devices. You can disable sync. If the CloudKit-backed store cannot load, the app can continue with a local-only store and flags that sync is not active. This is private CloudKit storage, not a promise that all app-related data stays only on the device.
On Android, there is no ManageSubs cloud sync. The app’s database can be included in Android Auto Backup or a device-to-device transfer into your own Google account — and only when the device supports backup encryption. On Android 8.0 and 8.1 the app’s data is excluded from backup altogether. You can turn backup off in your Android system settings.
Receipt scanning stays on your device
When you scan a receipt or screenshot, the text recognition runs on the device itself — Apple’s Vision framework on iOS, Google’s on-device ML Kit on Android. The image is not uploaded to us or to a third-party recognition service. Only the values you confirm are saved.
Product analytics: PostHog EU
Where enabled, the app sends events to PostHog’s EU endpoint under a random installation identifier. That identifier is pseudonymous, not anonymous. Events can cover lifecycle activity, screens, feature actions, counts, billing-cycle categories, import source and count, paywall actions, Pro status, share-card settings, and purchase product identifiers.
Purchases: the app stores and RevenueCat
Apple processes in-app payments on iOS; Google Play Billing does on Android. ManageSubs uses RevenueCat on both to retrieve products, complete and restore purchases, and determine whether a Pro entitlement is active. The app does not receive your full payment-card number, billing address, Apple ID password, or Google account password. RevenueCat processes purchase history, receipt or transaction information, an SDK-generated customer identifier, and technical information needed for that service.
Exchange-rate requests
For multi-currency totals, the app can request a public USD exchange-rate table from ExchangeRate-API at open.er-api.com. The request does not include your subscription records, prices, or currency selections. The app stores the latest successful rate table locally, uses it when offline, and has an approximate bundled fallback. As with any internet request, the rate provider can process connection data under its own policies.
The website and optional email
This website uses a separate PostHog EU project for website analytics. If you choose to submit an email form, MailerLite processes the address and delivery activity. These website and email flows are separate from the subscription records you store in the app.
Check the details and your choices
Read the Privacy Policy for providers, retention, requests, and contact details. For the calculations behind the dashboard, including rate caching and fallbacks, see how ManageSubs calculates subscription spending.