Subham — Privacy Policy

Last updated: 1 October 2026

This Privacy Policy explains how HyperZeta ("we", "us") handles your information in the Subham Android app (package com.hyperzeta.subham, "the app"). Subham helps families plan weddings and related ceremonies — rituals, tasks, budgets, vendors, and moi (gift) records. The app is intended for users aged 13 and older.

Summary

Signing in is required, by phone OTP or Google, through Google Firebase Authentication.
Everything you plan in the app — events, rituals, tasks, budget, vendors, guests, and moi entries — is stored on your device. No server of ours holds it, and there is no cloud sync.
Optional Google Drive backup: if you turn it on, the app saves a copy of your planning data to a hidden app folder in your own Google Drive. It is off until you turn it on, and we cannot see it.
We do not sell your data.
There are no ads. The app is free today; paid subscription features may be added later, billed through Google Play.
Crash reports and basic usage analytics are collected through Google Firebase so we can fix faults.
You can delete your account and wipe all app data from Profile → Account → Delete account.

Data we collect and why

Data	Purpose	Service
Your phone number (phone sign-in), or your Google account email, display name and profile photo URL (Google sign-in), plus an account identifier.	Create and authenticate your account, and keep you signed in.	Google Firebase Authentication
Crash and error reports: stack traces, device model, Android version, app version, and a Crashlytics installation identifier.	Diagnose crashes and fix bugs. We do not attach your account identifier, phone number or email to crash reports.	Google Firebase Crashlytics
App usage events (screens opened, app opens), device and app information, the Android advertising ID, and approximate (IP-derived) location.	Understand which parts of the app are used, and app stability and performance. Not used for advertising — Subham shows no ads.	Google Firebase Analytics
The verification SMS sent to you at sign-in, read automatically to fill in the code.	Auto-fill the 6-digit OTP so you do not have to switch apps. Uses the Google SMS Retriever API: the app holds no SMS permission and receives only the single message that matches its own signature. The message is read in memory, never stored or sent anywhere.	Google Play services (SMS Retriever)
A reference (URI) to the profile photo you pick, if you set one.	Show your photo in the app. Chosen through the Android photo picker, so the app holds no storage or gallery permission and sees only the one image you pick. The image is never copied out of your gallery and never uploaded.	On-device (Android photo picker)
Your planning data: profile details (name, surname, role, hometown, gothram, kuladeivam, display language), events and dates, rituals, tasks, budget categories and expense amounts, vendors and payment schedules, your guest and vendor contact lists, moi (gift) entries, and app preferences such as the app-lock setting.	Run the planner. Never transmitted — it stays in the app's private storage on your phone.	On-device (Android Room & DataStore)
A copy of the planning data above (except app preferences such as the app-lock setting), only if you turn on Back up to Google Drive. Your profile photo itself is not included, only its on-device reference.	Let you restore your plans on a new or reset phone. Stored in the hidden `appDataFolder` of your own Google Drive, which only Subham can read. We never receive it.	Google Drive (your account), via the `drive.appdata` permission

We hold no copy of your planning data and we cannot see it. The only information that reaches a server of a service we use is your sign-in identity (held by Firebase Authentication), the crash/analytics data described above, and — only if you turn it on — the Drive backup, which goes to your own Google account, not to us.

Google Drive backup

Drive backup is off by default. Turning it on in Profile → Account asks Google for permission to use Subham's hidden app folder in your Drive (the drive.appdata scope). That permission is limited to files Subham itself creates: the app cannot see, read or change any other file in your Drive. It is separate from how you sign in, so a phone-number account can use it too.

Backups run on the schedule you choose (daily, weekly, monthly or only when you tap Back up now), optionally on Wi-Fi only. The app keeps the 7 most recent backup files and deletes older ones.
Restore from backup replaces the planning data on the phone with the chosen backup.
Backup files count toward your Google storage and are governed by Google's terms and privacy policy, as is everything else in your Drive.
Turning backup off stops new backups; it does not delete existing ones. To delete them, open Google Drive on the web → Settings → Manage apps → Subham → Delete hidden app data. You can also remove Subham's access from your Google Account connections.

Information about other people

Subham lets you record details of other people — guest and vendor contacts (name, phone, email, city, address, notes) and moi entries (a family name, place, occasion, and the gift given or received). You enter this yourself and it is stored only on your device. You are responsible for having a proper basis to record another person's details, and for handling any request they make about that record. Because we never receive this data, we cannot access, export, or delete it for them — you can, inside the app.

Permissions

The app uses INTERNET and ACCESS_NETWORK_STATE for sign-in, crash reporting and analytics; POST_NOTIFICATIONS for task and ritual reminders (off until you allow it); SCHEDULE_EXACT_ALARM so reminders arrive on the minute rather than batched; RECEIVE_BOOT_COMPLETED to re-arm reminders after a restart; and USE_BIOMETRIC for the optional app lock. The app requests no storage, gallery, contacts or SMS permission: profile photos come through the Android photo picker and the sign-in code through the SMS Retriever API, neither of which needs one. The Firebase Analytics SDK also declares the advertising ID permission (AD_ID); you can reset or delete your advertising ID in Android Settings → Privacy → Ads.

Biometrics never reach the app. The app lock asks Android to confirm your fingerprint, face or screen lock and receives only a yes/no answer. No biometric data is read, stored or transmitted by Subham.

Third-party services

We use Google Firebase to operate the app: Firebase Authentication (sign-in), Firebase Crashlytics (crash reports) and Firebase Analytics (usage and stability). If you turn on backup, Google Drive stores the backup in your own account. Google Play services supports sign-in and Drive authorization on the device. Google's handling of this data is governed by Google's Privacy Policy: https://policies.google.com/privacy. See also Firebase's privacy and security information. To verify a phone number, Firebase sends an SMS through its carrier partners and may use your phone number and device information for abuse prevention.

Paid subscriptions. Subham is free today and contains no in-app purchases. If paid features are introduced, they will be billed through Google Play Billing. In that case we would receive your purchase and subscription status so the app can unlock what you paid for — never your card number or bank details, which Google handles. This policy will be updated before any such feature ships.

Data sharing

We do not sell your data. Your planning data is never shared with anyone; if you turn on Drive backup it is stored in your own Google Drive, which is not sharing it with us. Sign-in, crash and analytics data is shared only with Google as the provider of the services listed above. Everything sent over the network, including backups, is encrypted in transit.

Data retention and deletion

Your planning data lives on your device, and in your own Google Drive if you turned on backup, so you control it completely:

Delete individual items — any event, task, expense, vendor, contact or moi entry can be deleted inside the app.
Delete your account — Profile → Account → Delete account deletes your Firebase account and then wipes every table and preference on the device. This is permanent and cannot be undone. It does not delete Drive backups, which live in your Google account — delete those as described under Google Drive backup.
Sign out — Profile → Account → Sign out deliberately keeps your data on the device so you can sign back in and resume planning.
Uninstall — removes all app data from the device. Note that uninstalling alone does not delete your Firebase account; use Delete account for that, or email us.

Firebase Authentication keeps your account record until the account is deleted. Crashlytics retains crash reports for up to 90 days; analytics data is retained for the period set in our Google Analytics configuration. Drive backups stay in your Google Drive until you delete them (the app itself keeps only the 7 most recent). Since we hold no copy of your planning data, there is nothing for us to delete on our side. For any data request, contact us at the email below and we will respond within 30 days.

Security

App data is kept in Android's private per-app storage, which other apps cannot read. You can turn on App lock (Profile → Account) to require your screen lock or biometric before Subham opens. Drive backups are protected by your Google account's own security, so keep that account secure. No method of storage or transmission is perfectly secure, but keeping your planning data off any server of ours removes most of the risk.

Your rights

Depending on where you live — for example under India's Digital Personal Data Protection Act, 2023, the EU/UK GDPR, or the California CCPA — you may have the right to access, correct, or delete data relating to you, to withdraw consent, and to object to or restrict certain processing. We do not sell personal information. Your planning data is on your device (and, if you chose, in your own Google Drive) and not held by us; for your account identity and crash/analytics data, use Delete account in the app, or contact us at the email below.

Children and teenagers

The app is intended for users aged 13 and older. It is not directed to children under 13, and we do not knowingly collect personal information from them. If you believe a child under 13 has provided us information, contact us and we will delete it and the associated account.

If you are between 13 and the age of majority where you live, please use Subham with a parent or guardian's involvement — they should review this policy with you, and their consent is required for any paid subscription. Where local law sets a higher minimum age for consenting to data processing (for example 16 in parts of the EU), that age applies instead of 13.

Changes to this policy

We may update this policy as the app changes. The "Last updated" date above reflects the current version.

Contact

Questions or data requests: hyperzetaz@gmail.com.