01. Data we use
Subs Compiler uses the information needed to provide the features you choose. This can include your Firebase account identity, saved subscription or recurring-payment records, plan and usage state, app settings, limited device or service diagnostics, and information needed for billing, notifications, security, and fraud prevention.
Saved payment records can include merchant name, amount, currency, billing date, recurrence or payment-plan details, source type, and limited source references needed for detection, deduplication, or record integrity.
Subs Compiler does not sell personal data. Personal data and Gmail data are not used for advertising.
02. Optional Gmail access
Gmail access is optional and separate from normal Google sign-in. When you authorize Scan Mail or Auto Scan Mail, Subs Compiler requests read-only Gmail access to look for supported subscription and recurring-payment evidence.
Full mailbox content is not stored as a subscription archive. Only structured information needed for confirmed payment records and limited source references can be saved.
Auto Scan Mail requires authorization that can continue after you close the app. Credentials needed for this feature are protected on the backend and are used only to provide the authorized Gmail feature.
Use and transfer of information received from Google APIs follows the Google API Services User Data Policy, including its Limited Use requirements.
03. Statement imports and local content
You can select supported PDF or CSV bank and card statements for payment detection. Raw statement files and PDF passwords are not stored as subscription records. Only structured payment details you review and confirm are saved.
Custom subscription images stay app-private on your device and are not added to the shared merchant-logo library. Screenshot-style share images are created locally for the Android share sheet.
Budget Me values and certain display preferences are stored locally by the app for the signed-in account. They are not used as a bank transaction history or uploaded solely for those local features. Device or operating-system backup behavior may still apply.
Share Snapshot images are created on your device. If you choose to send a snapshot through another app or service, the copy you share is then handled by that recipient or service under its own privacy terms.
04. Chat Support
When you use Chat Support, Subs Compiler stores the messages, images, issue information, and delivery metadata needed to provide support. Authorized Support administrators can view and respond to the Support content you send.
Support image uploads use protected storage and short-lived upload authorization. Security and abuse-prevention records can be kept separately from visible chat history so deleting a conversation does not reset safety limits.
Do not send passwords, verification codes, full card numbers, or information that is not needed for your support request.
05. Security and service providers
Subs Compiler uses Firebase and Google Cloud services for authentication, database storage, protected file storage, app integrity checks, crash diagnostics, notifications, and backend processing. Google Play processes paid subscriptions and provides purchase status used to verify plan access.
Security controls include authenticated account ownership, Firebase App Check with Play Integrity, backend authorization, Firestore and Storage rules, protected billing verification, bounded upload and request controls, and encrypted credentials where ongoing authorization is required.
No internet service can guarantee absolute security. If you believe your account or data has been exposed, contact us promptly.
06. Retention and deletion
Subscription records remain until you delete them, clear subscription data, or delete your account, subject to limited records that may need to be retained for security, fraud prevention, billing integrity, legal obligations, or dispute handling.
Support content can be removed through the app's chat controls and account deletion process. Temporary uncommitted Support uploads can be cleaned automatically. Billing records controlled by Google Play follow Google's retention and purchase rules.
Clear Subscription Data removes tracked subscription records and local category organization without deleting your account or cancelling Google Play billing.
Deleting an individual tracked record removes that saved record. A later Scan Mail or statement import can detect the same commitment again when new valid evidence is found.
Deleting your Subs Compiler account removes account-owned app data and, where applicable, removes Subs Compiler's Google authorization. It does not delete your Google or Gmail account and does not cancel a Google Play subscription. Cancel paid billing separately in Google Play.
07. Your choices and rights
You can use Subs Compiler without Gmail access by importing supported statements or using Manual Add. You can disconnect Gmail, delete individual records, clear subscription data, change privacy presentation settings, or delete your account from the app.
Depending on where you live, applicable privacy law may provide rights to access, correct, delete, or obtain information about personal data. Contact us to make a privacy request. We may need to verify your identity before acting on a request.
08. Contact and updates
Privacy questions or requests can be sent to contact@subscompiler.com. Signed-in users can also use Settings > Support > Chat Support.
Material changes to this policy will be published here with an updated date and handled as required by applicable law.