Privacy Policy
Privacy Policy
# Privacy Policy for SubSave
Effective date: 7 November 2026
SubSave is a subscription and recurring-payment tracking app provided by Physics Infotech. This Privacy Policy explains how information is processed when you use SubSave. For privacy questions or account and data deletion requests, contact physicsinfotech.tech@gmail.com.
## 1. Information you provide
SubSave processes information you choose to enter, including subscription or merchant names, amounts, currencies, categories, billing cycles, payment dates, trial details, renewal settings, notes, and payment history. Depending on the features you use, records may also include optional payer, bank, payment-method, or billing-provider details.
Please do not enter passwords, one-time passwords (OTPs), UPI PINs, CVVs, full card numbers, or other authentication secrets into notes or support messages. SubSave does not require your banking credentials and does not connect directly to your bank or email account.
## 2. Guest use and account information
You can use SubSave as a guest without creating an account. Guest tracking records are stored locally on your device and are not synchronized to our Firebase account storage.
If you create an account or sign in, Firebase Authentication processes your account information. This can include your account identifier, email address, display name, profile photograph URL, and authentication information provided through your chosen sign-in method. Google or Apple may process information when you choose their sign-in options.
For signed-in users, subscriptions, renewal and payment records, saved subscription-detection candidates, and dismissed savings-insight settings are stored using Cloud Firestore. The service can maintain a local cache for offline access. Not every device-local preference or record is synchronized.
## 3. Optional Android SMS access
On supported Android devices, you can choose to scan your SMS inbox for possible recurring financial payments. SMS access is optional. SubSave displays a disclosure and requests Android SMS permission only after you choose to continue. You can decline permission and continue using manual tracking or pasted-payment-text features.
A user-initiated scan examines inbox messages from the previous 180 days, checks up to 10,000 messages, and analyzes up to 1,000 financial-looking messages. Financial keyword filtering and OTP/security-code exclusion take place on your device. Filtering can be imperfect; scan results require your review.
Raw SMS bodies are used temporarily for local analysis and are not saved to SubSave storage or uploaded by the scan. Sender metadata is not passed to the app's subscription-detection engine. SubSave does not send SMS, read SMS continuously in the background, or use SMS information for advertising.
Scan suggestions stay on the scan screen until you choose to review and track one. When you save a subscription, its confirmed fields are stored locally in guest mode or in your account storage when signed in. Review the merchant, amount, billing frequency, and next billing date before saving. A suggestion does not establish that a subscription or payment mandate is currently active.
You can revoke SMS access at any time in your device's Android permission settings.
## 4. Pasted payment text and Smart Passbook
Text you paste into supported features is parsed on your device. Subscription-detection features can save extracted merchant, amount, currency, date, source, confidence, and sanitized-reference information for review. Saved candidates use local guest storage or signed-in account storage. Newly generated candidates do not retain full pasted messages.
Smart Passbook stores extracted transaction details and a message fingerprint used to identify repeated imports. Passbook records remain on the device, separately for each account or guest profile, and are not included in cloud synchronization or subscription exports. Full raw messages, sender details, and account numbers are not intended as Passbook fields. You can delete individual entries or clear Smart Passbook.
## 5. How information is used
SubSave uses information to provide subscription tracking, spending calculations, recurring-payment suggestions, savings insights, payment history, local reminders, account access, optional cloud synchronization, and requested exports. Information you send to support is used to respond to your request and, where necessary, verify account ownership.
SubSave does not sell your personal information. The current app does not integrate advertising SDKs, AdMob, Firebase Analytics, Firebase Crashlytics, or in-app purchase SDKs. Spending analytics shown inside the app are calculations based on your tracking records.
## 6. Notifications and device authentication
Renewal reminders and smart alerts are generated locally. Depending on your settings, service names and amounts may appear in notifications, including on a lock screen. You can adjust reminder privacy settings in the app and notification permissions in device settings. In-app notification history is stored locally, with up to 200 entries.
App Lock uses the device's authentication system. SubSave receives an authentication result; it does not receive or store your biometric templates or device passcode.
## 7. Exports and external links
When you export or share a CSV or PDF report, it can contain subscription and payment information. You decide where to send or store the file. Files already shared with other services or people remain subject to their handling and cannot be recalled by deleting your SubSave account.
Provider billing links, cancellation guides, support links, and public privacy links may open an external app or website. Those services operate under their own privacy policies. Deleting a SubSave record or account does not cancel subscriptions or payment mandates held with other providers.
## 8. Service providers and disclosures
SubSave uses Google Firebase Authentication and Cloud Firestore for account and cloud functions. Google and Apple sign-in are used when selected. These providers may process network, device, service, and authentication metadata needed to operate and secure their services. Data processing locations depend on the service configuration and provider practices and may be outside your country.
Google Privacy Policy: https://policies.google.com/privacy
Apple Privacy Policy: https://www.apple.com/legal/privacy/
Information may also be disclosed where necessary to comply with applicable law, respond to a valid legal request, prevent abuse, or protect users and the service. We do not provide raw SMS messages to these providers through the SMS scan.
## 9. Storage and security
SubSave uses device storage and, for signed-in account records, Firebase services. Cloud access rules are designed to restrict account records to the authenticated account. Device security, account security, and service-provider protections also affect the security of your information. App Lock adds an access check; it does not make every local record encrypted by SubSave.
No storage or transmission method provides absolute security. SubSave does not claim end-to-end encryption or guaranteed backup and recovery. Protect your device and sign-in credentials, and share exported files carefully.
## 10. Retention and your choices
Tracking records are retained until removed through available controls or through an account/data deletion request. Some subscription deletions use a soft-delete mechanism for synchronization; removing a record from the interface does not necessarily immediately erase every stored copy. Signing out does not delete your cloud records. Uninstalling the app does not delete cloud account records, exported files, or copies on other devices.
Device-local preferences, notification history, and Passbook records remain until cleared, replaced, removed with app data, or otherwise removed by your device. Operating-system backup and restore behavior may affect device-local data. You can edit tracking records, delete available entries, clear Passbook, change notification settings, revoke SMS permission, use guest mode, and request account or personal-data deletion.
## 11. Request account and data deletion
To request deletion from inside the app, open Settings → Privacy Center → Request account and data deletion. This opens an email draft. You must send the email to submit your request.
You can also request deletion without installing or opening the app: email physicsinfotech.tech@gmail.com with the subject “SubSave account deletion request”. Include the email address associated with your SubSave account and state that you want your account and associated cloud data deleted. For a more limited data-deletion request, describe the records concerned.
We may ask you to verify account ownership before acting. Never send your password, OTP, full card number, or banking credentials. Account deletion covers the Firebase Authentication account and associated SubSave cloud subscriptions, payment/renewal history, saved detection candidates, and cloud settings. Device-only Passbook records must be cleared on the relevant device. Remove app data on your other devices and delete any exports you no longer need.
If information must be retained for a legal or security obligation, or a service-provider retention limitation applies, we will explain the applicable limitation in our response. Request processing is handled by support; opening an email draft does not automatically delete an account or confirm completion.
## 12. Children
SubSave is a financial organization tool intended for people managing their own subscriptions. We do not knowingly seek personal information from children. If you believe a child has provided personal information, contact physicsinfotech.tech@gmail.com so we can review and address it. Applicable age and consent requirements depend on the user's location.
## 13. Changes to this policy
We may update this policy when app features, processing practices, or applicable requirements change. The updated policy will show its effective date. Material changes to permissions or data use will also be reflected in relevant in-app disclosures where appropriate.
## 14. Contact
Developer: Physics Infotech
App: SubSave
Android package: com.subsave.subtracker
Privacy, support, and deletion requests: physicsinfotech.tech@gmail.com