Privacy Policy

Last updated: 12 August 2026

Subs Compiler is an Android application published by Manzil Studio. This Privacy Policy explains how Subs Compiler accesses, uses, stores, protects, and deletes information when you use the app.

1. Summary

Subs Compiler helps users detect, add, organize, and track subscriptions and recurring-payment commitments.

Depending on the features you choose to use, the app may process:

• your Google/Firebase app-account information;
• subscription and recurring-payment records you create or confirm;
• Gmail data when you explicitly authorize Scan Mail, Auto Scan Mail, or a selected Gmail statement attachment;
• statement files you explicitly select for import;
• Google Play subscription and purchase-verification information;
• Support Chat messages you intentionally send to Manzil Studio Support;
• notification tokens and limited operational/security data needed to run and protect the service.

Subs Compiler does not sell your personal information or Gmail data. Gmail-derived data is not used for advertising, credit scoring, lending, or data-broker purposes.

2. App account information

Subs Compiler uses Firebase Authentication with Google sign-in.

When you sign in, the app may receive and store information such as:

• Firebase user ID (UID);
• Google account email address;
• display name;
• profile photo URL;
• app initialization/account metadata;
• plan, usage, and entitlement metadata.

This information is used to authenticate your account, keep your data separated from other users, provide plan features, and support account management.

3. Subscription and recurring-payment records

The app stores subscription/payment records that you add manually or that are detected and confirmed through supported features.

A record may include information such as:

• merchant or subscription name;
• amount and currency;
• billing or renewal date;
• monthly, yearly, instalment, or reminder type;
• category;
• source type;
• limited source identifiers or merchant evidence needed to maintain the record;
• created, updated, or last-detected timestamps.

The app does not intentionally invent payment details that were not provided or supported by the source evidence.

4. Gmail access

4.1 Scope and user control

Subs Compiler uses the Google Gmail API with the restricted readonly scope:

https://www.googleapis.com/auth/gmail.readonly

Gmail access is requested only when you choose a feature that needs it, such as:

• Scan Mail;
• connecting Gmail for Auto Scan Mail;
• importing a statement attachment from Gmail.

Google sign-in to the Subs Compiler app account does not by itself grant Gmail read access.

4.2 What Gmail data is used for

When authorized, Subs Compiler may read Gmail messages, headers, metadata, and attachments as needed to identify evidence of subscriptions, renewals, recurring payments, instalments, or user-selected statement attachments.

Unrelated messages are skipped.

4.3 What is stored

Subs Compiler does not store your full Gmail mailbox or full email bodies as subscription records.

The app stores only the resulting subscription/payment information and limited source evidence needed to support the saved record.

For Auto Scan Mail, a Gmail OAuth refresh token may be stored in protected backend credential storage so scheduled scans can run while the app is closed. The refresh token is encrypted before backend storage and is not placed in public user documents.

Disconnecting an Auto Scan Gmail account removes its stored connection/credential state and makes a best-effort request to revoke the related OAuth token.

4.4 Google API Limited Use

Subs Compiler's use of information received from Google APIs complies with the Google API Services User Data Policy, including its Limited Use requirements.

Gmail data is used only to provide or improve user-facing Subs Compiler features that require that access. It is not sold, transferred to advertising platforms or data brokers, or used to determine creditworthiness or for lending.

Manzil Studio does not routinely allow humans to read Gmail data obtained through the API. Human access would occur only where permitted by Google's Limited Use requirements, such as with the user's affirmative agreement for specific data, for security purposes, or where required by law.

5. Statement file imports

Subs Compiler lets you select supported bank or card statement files, or select a supported Gmail statement attachment, to look for recurring-payment candidates.

Current supported file types are PDF and CSV, subject to the app's file-size and parser limits.

Statement processing is performed for the purpose of detecting subscription/payment candidates.

Subs Compiler does not save the following as subscription data:

• the full statement file;
• raw statement text;
• PDF passwords;
• full card or bank account numbers;
• postal addresses;
• full original filenames.

A short sanitized source label may be kept with a saved record, for example a bank or credit-card statement label.

PDF passwords are used only for the current parsing operation and are not stored.

6. Google Play billing and subscriptions

Paid Lite and Pro plans are purchased through Google Play Billing.

To verify entitlement and prevent duplicate or unauthorized claims, Subs Compiler may process and store:

• Google Play product ID;
• purchase/subscription state;
• order and billing-cycle information;
• auto-renewal state;
• expiry information;
• purchase-token hashes;
• private raw purchase tokens in backend-only billing storage;
• purchase-claim, verification, and lifecycle metadata.

Raw Google Play purchase tokens are not exposed in the normal public user billing document.

Google Play remains the payment and checkout provider.

7. Auto Scan Mail

Auto Scan Mail is a Pro feature that can run scheduled Gmail scans after the user explicitly connects one or more Gmail accounts and activates a schedule.

Auto Scan may store:

• schedule configuration;
• connected Gmail account metadata;
• encrypted Gmail refresh-token material in protected backend storage;
• run status and timestamps;
• per-account scan result metadata;
• quota/idempotency information needed to prevent duplicate charging of usage.

If you enable the Auto Scan start-email option, your Subs Compiler login email is used to send the start notification.

Cloud Tasks scheduling metadata does not contain Gmail message bodies, Gmail refresh tokens, or full subscription payloads.

8. Support Chat and push notifications

If you use Support Chat, Subs Compiler stores the content you intentionally send so Manzil Studio Support can read the conversation and reply.

Support Chat data may include:

• message text;
• authenticated sender UID;
• sender type (user or support admin);
• thread owner UID;
• email and display name on thread metadata where available;
• server timestamps;
• last-message/status metadata;
• unread/read counters and timestamps.

Support Chat does not automatically copy Gmail messages, statement contents, or Google Play purchase tokens into the conversation.

For Support Chat notifications, Subs Compiler may store a Firebase Cloud Messaging (FCM) registration token and platform information in a backend-only token registry. The token is used to address notifications to the relevant app installation.

On normal Sign Out, the app attempts to unregister the current Support Chat push token before completing logout. Invalid or expired tokens may also be removed automatically.

When you delete your Subs Compiler account, the account-deletion flow deletes the user's Support Chat thread/messages and Support Chat push-token records as part of the account cleanup.

9. Crash diagnostics, security, and abuse prevention

Subs Compiler uses Firebase and Google security/operational services, including Firebase App Check, Play Integrity, Firebase Crashlytics, and backend logs/monitoring.

These services may process limited device, app, integrity, error, diagnostic, or request metadata needed to:

• protect the app and backend from abuse;
• verify genuine app requests;
• diagnose crashes and operational failures;
• maintain service reliability;
• enforce plan and usage rules.

Subs Compiler does not use this information for advertising.

10. Local device data

Some preferences are stored locally on your device, such as:

• theme choice;
• default currency;
• reminder preferences;
• custom category organization;
• notification read-state or similar local UI state;
• locally cached app/subscription presentation data where supported.

Local settings may remain on the device until cleared by the app, account actions, or device/app storage controls.

11. Merchant logos and exchange rates

Subs Compiler may use a shared merchant catalog and Firebase Storage to display merchant logos.

The app may also use a shared exchange-rate cache to convert dashboard totals into the display currency selected by the user. Exchange-rate requests are for public currency-rate data and do not require your Gmail messages or Support Chat content.

12. Service providers

Subs Compiler relies on service providers and infrastructure needed to operate the app, including Google/Firebase/Google Cloud services such as:

• Firebase Authentication;
• Cloud Firestore;
• Firebase Storage;
• Cloud Functions;
• Firebase App Check / Play Integrity;
• Firebase Crashlytics;
• Firebase Cloud Messaging;
• Google Cloud Tasks;
• Gmail API;
• Google Play Billing and Android Publisher services.

These providers process data as necessary to provide their services and are governed by their own applicable terms and privacy documentation.

Subs Compiler does not sell personal data to these providers.

13. Data sharing

Subs Compiler does not sell user data.

User data may be processed or disclosed only as necessary to:

• provide the features the user requested;
• operate Firebase/Google Cloud/Google Play/Gmail services;
• provide Support Chat and notifications;
• maintain security and prevent fraud or abuse;
• comply with applicable law or valid legal process;
• protect the rights, safety, or integrity of users, Manzil Studio, or the service.

Gmail API data is subject to the additional Limited Use restrictions described above.

14. Data retention

Data is kept only for as long as reasonably necessary for the purposes described in this policy, subject to operational, security, fraud-prevention, payment, dispute, and legal requirements.

Subscription records, Support Chat data, Auto Scan state, and normal account-owned data are associated with the user's Subs Compiler account until deleted through the applicable app controls or account-deletion flow.

Certain minimal hashed identifiers or transaction/security records may be retained after account deletion where reasonably necessary for:

• preventing repeated Free-plan or installation-level abuse;
• fraud prevention and security;
• Google Play purchase ownership/verification and payment disputes;
• compliance with legal obligations.

Such retained records are not used to recreate or continue the deleted Subs Compiler account.

15. Your controls and deletion choices

Individual subscription deletion

Deleting an individual subscription permanently deletes that selected saved record. A later scan or import may detect the payment again if matching evidence still exists.

Clear Subscription Data

Settings → Privacy | Data → Clear Subscription Data

This removes saved subscription records and local category organization but does not delete the Subs Compiler account. It may keep account/authentication, billing, Auto Scan setup, and Support Chat data.

Delete Account

Settings → Privacy | Data → Delete Account

Delete Account removes the normal Subs Compiler app account and associated account-owned data, including:

• saved subscriptions;
• account-owned logo requests/meta data;
• Auto Scan account/configuration/credential state;
• private Google Play account-linked app state as handled by the deletion backend;
• Support Chat thread and messages;
• Support Chat push-token records;
• Firebase Authentication user.

Some minimal records may be retained only for the legitimate purposes described in Section 14.

Deleting the Subs Compiler account does not by itself cancel a Google Play subscription. Google Play subscriptions must be managed or cancelled through Google Play.

External account deletion request

If you cannot access the app, you may request deletion of your Subs Compiler account and associated data through the public account-deletion contact method on this page:

[shafie.code@gmail.com](mailto:shafie.code@gmail.com)

Include enough information for Manzil Studio to identify the Subs Compiler account you want deleted. Do not send passwords, one-time passwords, full card numbers, or Gmail content.

16. Security

Subs Compiler uses technical and organizational safeguards appropriate to the service, including authenticated access, Firestore security rules, App Check, backend-controlled sensitive mutations, encrypted Auto Scan refresh-token storage, server-side billing verification, and access controls for Support Chat.

No system can guarantee absolute security. Users should protect their Google account and device credentials.

17. International processing

Google/Firebase/Google Cloud infrastructure may process information in locations where their services operate. Where applicable, data handling is subject to the protections and contractual arrangements provided by those service providers and applicable law.

18. Changes to this Privacy Policy

Manzil Studio may update this Privacy Policy when the app, legal requirements, or data practices change.

The current version will be published on the Subs Compiler public privacy page with an updated date. Material changes to Google user data practices will be disclosed as required before new or changed uses are applied.

19. Contact

For privacy questions, account deletion requests, or data-handling concerns, contact:

Manzil Studio

[shafie.code@gmail.com](mailto:shafie.code@gmail.com)

Signed-in users may also use Settings → Support → Chat Support inside Subs Compiler.