Privacy Policy
Last updated: 16 October 2026
This Privacy Policy applies to the Android app
MP Sub Engineer Vyapam PYQ
(package name com.vyapam.pyq)
(“we”, “the app”). The app helps students practice Madhya Pradesh Vyapam / Sub Engineer–style previous-year questions across
Civil, Electrical, and Mechanical disciplines.
Developer / support contact:
ajconstruction8827@gmail.com
Initial testing release note:
This build ships with advertising disabled at compile time
(ADS_ENABLED=false). The Google Mobile Ads (AdMob) SDK is present in the app binary and wired in code for banner, interstitial, and rewarded ads, but the app’s ad code paths do not call AdMob initialization, load ads, or show ads while this flag is false. If a later release turns ads on, this policy will be updated before that change is treated as live.
1. Information we collect
1.1 Account & authentication
- Phone number (primary sign-in): Sign-in uses Firebase Phone Authentication for +91 numbers (OTP). Your phone number and Firebase Authentication UID are processed by Google Firebase Auth.
- Optional guest path: The app also offers a “Continue as Guest” option. That path may create a Firebase anonymous session or, if Firebase anonymous sign-in fails, a local guest identifier stored only on the device. Guest use does not require a phone OTP.
- Account profile in Cloud Firestore: For signed-in Firebase users we store (or update) fields such as phone number, display name, premium status, max devices, created-at, and last device-swap time under your user document so we can maintain your account across devices.
1.2 Device binding
- To enforce free / Premium device limits, we store a device identifier based on Android’s
Settings.Secure.ANDROID_ID, a device name (manufacturer + model), last-active time, active flag, and app version under your account in Firestore.
- You can manage devices in-app (subject to current product rules and swap limits).
1.3 Optional leaderboard
- Leaderboard participation is opt-in (off by default in preferences).
- If you opt in, we publish weekly XP, your Firebase UID, and display name to a Firestore leaderboard collection so other opted-in users can see rankings (for example top entries).
1.4 Referrals
- If you use referral codes, the app may store referral ownership and claim records in Firestore (for anti-abuse) and may write a pending reward flag to the referrer’s user document. Local bonus state may also be kept on-device.
1.5 Purchases
- Premium subscriptions are processed by Google Play Billing. Google handles payment details.
- We receive purchase / entitlement status needed to unlock Premium features and may sync a premium flag (and related device-limit fields) to Firestore.
1.6 Cloud messaging (FCM)
- When Firebase is configured for the build, the app uses Firebase Cloud Messaging to subscribe to topics (for example
all_users and discipline topics) and to receive push messages.
- FCM may involve a device messaging token managed by Google’s messaging services. The app uses this so we can deliver study / product notifications when we send them.
- Separate from FCM, optional local study reminders use on-device alarms (without the exact-alarm permission). Those reminders do not require uploading your reminder schedule to our servers.
1.7 Local on-device data
- Preferences and progress (language, theme, freemium counters, bookmarks, streak / XP-related state, reminder settings, leaderboard opt-in, referral bonus state, and similar) are stored locally using Android DataStore and Room.
- Some auth-related values may be stored using Android EncryptedSharedPreferences on the device.
- Clearing app data or uninstalling removes local storage on that device (cloud account data may remain until deleted — see below).
1.8 Advertising (currently disabled)
- This testing release: ads are disabled (
ADS_ENABLED=false). The app does not call AdMob initialization from its ad manager, and does not load or display banner, interstitial, or rewarded ads.
- If ads are enabled in a future build: free users may see Google AdMob banner, interstitial, and/or rewarded ads. AdMob / Google advertising libraries may then collect advertising identifiers and related device / usage data under Google’s policies. Premium is intended to be ad-free when ads are enabled.
1.9 Analytics & crash reporting
- Firebase Analytics: Not included as an app dependency in the current build. In-app event helpers write to local device logs; Firebase Analytics event collection is not active in this release.
- Firebase Crashlytics: Not implemented / not included in the current build.
- Other Google / Firebase SDKs that are active (Auth, Firestore, FCM, and Play services used for billing / updates / review) may still process operational data as described in Google’s own documentation and privacy policies.
1.10 Google Play services (non-ads)
- In-app updates (flexible Play App Update checks) and optional In-App Review prompts may communicate with Google Play services on your device.
2. How we use information
- Authenticate you and maintain your account
- Enforce device limits and restore Premium entitlement
- Provide practice features, freemium limits, referrals, and optional leaderboards
- Send push notifications (FCM) and local reminders you configure
- Operate billing-related unlocks
- When ads are enabled in a future release: show ads to free users
We do not sell your personal information.
3. Third-party services
Depending on features you use and build flags, the app relies on:
- Google Firebase Authentication (phone OTP; optional anonymous guest when used)
- Google Cloud Firestore (account, devices, premium sync, referrals, leaderboard)
- Google Firebase Cloud Messaging (push topics / messages)
- Google Play Billing (subscriptions)
- Google Play In-App Review and App Update APIs
- Google Mobile Ads / AdMob (SDK packaged; inactive in app ad flows while
ADS_ENABLED=false)
Those providers process data under their own terms and privacy policies.
4. Data sharing
- We share data with the service providers above only as needed to run the listed features.
- Leaderboard display names and XP are visible to other users when you opt in.
- We may disclose information if required by law or to protect users and the service against abuse.
5. Security
We use standard platform and provider protections where available (for example HTTPS to Google / Firebase services, and encrypted local storage for some auth-related values).
No method of transmission or storage is completely secure. We do not claim immunity from unauthorized access, and you should protect access to your phone and OTP codes.
6. Children
The app is for exam preparation by adults and older teens. We do not knowingly collect personal information from children under 13. The app is not directed at children under 13.
7. Data retention
- On device: Local data remains until you clear app storage or uninstall.
- In Firebase: Account, device, referral, leaderboard, and related cloud records remain until you request deletion or we remove inactive / abusive accounts under our operational practices.
- Uninstalling the app does not automatically delete your Firebase account data.
- Signing out ends the local session but does not by itself delete your cloud account.
8. Your choices
- Sign out or clear app data in Android Settings
- Opt in or out of leaderboard sharing in app Settings (where offered)
- Disable reminder notifications in app Settings and/or system notification settings
- Manage Google ad personalization in your Google Account / device settings (relevant when ads are enabled)
- Upgrade to Premium for expanded access and (when ads are enabled) an ad-free experience, per current product rules
- Request account / data deletion by email (see below). The current app does not include an in-app “delete account” button.
9. Data deletion
There is currently no in-app account-deletion control.
To request deletion of your Firebase account and associated cloud data that we control (user profile, device binding records, and related referral / leaderboard records tied to your account), email
ajconstruction8827@gmail.com
from a reachable address and include the phone number used to sign in (or enough detail for us to identify a guest / anonymous account if applicable).
We will process verified requests within a reasonable period, subject to legal retention needs and abuse-prevention records that may need limited retention.
Google Play Billing purchase history remains with Google under Google’s policies.
10. Contact
Questions or deletion requests:
ajconstruction8827@gmail.com
11. Changes
We may update this policy when features or data practices change (for example if ADS_ENABLED is turned on, or if Analytics / Crashlytics are added).
Material changes will be reflected in this document and, where practical, called out in-app or on the hosted policy URL.
Continued use after an update means you accept the revised policy.
Legal home · Terms of Service
App: MP Sub Engineer Vyapam PYQ · Package: com.vyapam.pyq · Contact: ajconstruction8827@gmail.com