DrivePass Nepal — Privacy Policy

Advertising and privacy information for the DrivePass Nepal Android app.

App: DrivePass Nepal (Android package com.drivepassnepal.drivepass) Last updated: [TO BE PROVIDED — set the publication date] Policy version: 1.0 (draft for review)

Draft status. This policy is prepared for publication but is not yet published. It becomes effective only once it is hosted at a public URL and that URL is entered in Google Play Console. Placeholders marked [TO BE PROVIDED] must be completed before publishing.

1. Who we are

DrivePass Nepal is an independent educational application that helps people in Nepal prepare for the driving-licence written examination (“likhit”) and the practical trial.

Developer / data controller: [TO BE PROVIDED — your legal name or registered business name]
Contact for privacy questions: [TO BE PROVIDED — a working privacy contact email address]
Country of establishment: Nepal [TO BE CONFIRMED]
Public policy URL: [TO BE PROVIDED — the public URL where this policy will be hosted]

DrivePass Nepal is not affiliated with, endorsed by, or operated by the Department of Transport Management (DOTM) or any government authority.

2. Summary

The app itself has no account, no login and no developer-operated server. Your learning data (progress, results, bookmarks and preferences) is stored only on your device.
The app shows advertising through Google AdMob (the Google Mobile Ads SDK). That SDK collects certain data on its own behalf to deliver and measure ads and to prevent fraud, as described in section 4.
Where the law requires it, you are asked for consent through Google’s official consent form (User Messaging Platform, UMP) before any ad is requested. You can review or change that choice at any time from Settings → Privacy → Ad Choices.
Ads are shown on learning and examination screens. No ad is ever shown on the main dashboard.

3. Information that stays on your device

DrivePass Nepal stores the following locally, in the app’s private storage. It is not transmitted to us and we cannot access it.

What	Why	Where
Mock-exam attempts and results (score, date, duration)	To show your progress history	Local SQLite database
Practice answers	To show what you have answered and your accuracy	Local SQLite database
Bookmarked questions	To let you revisit saved questions	Local SQLite database
App preferences — language (English/Nepali), light/dark theme, first-launch and notice flags	To remember your choices	Android `SharedPreferences`
Bundled study content (questions, traffic signs, rules, colour-vision plates)	To let the app work offline	App assets (read-only)

None of this is uploaded. Deleting the app, or clearing its storage in Android settings, removes all of it permanently.

Permissions: the app requests only android.permission.INTERNET. It does not request location, camera, microphone, contacts, phone, SMS, storage or notification permissions.

Network use: the app checks whether the device can reach the internet (a TCP connection test to port 443) to decide whether to enable the online learning sections, and it can open official websites (for example dotm.gov.np and edlvrs.dotm.gov.np) in your browser or your email app when you tap a link. All app-initiated traffic is HTTPS; plain HTTP is disabled.

4. Information collected by third-party SDKs

The app includes the following Google SDKs. They collect data independently of us, under Google’s own terms and privacy policy.

4.1 Google Mobile Ads SDK (AdMob)

Bundled through the google_mobile_ads Flutter plugin; the underlying Android library is Google Play services Ads (play-services-ads).

Per Google’s official Google Play data disclosure guidance for the Mobile Ads SDK, the SDK automatically collects and shares:

Data type (as Google describes it)	Notes
IP address	May be used to estimate the general (approximate) location of the device. The app does not request Android location permission and does not collect precise location.
User product interactions	App launches, taps and video views, including interactions with ads.
Diagnostic information	Performance information about the app and the SDK, such as app launch time, hang rate and energy usage.
Device and account identifiers	The Android advertising ID (ad ID) and the app set ID, plus other identifiers related to signed-in accounts on the device where applicable.

This data is used for advertising or marketing, analytics, and fraud prevention / security / compliance, and is shared with Google and its advertising partners as part of delivering ads. Google states that all user data collected by the Mobile Ads SDK is encrypted in transit (TLS).

Google’s guidance: developers.google.com/admob/android/privacy/play-data-disclosure

4.2 Google User Messaging Platform (UMP)

Used solely to collect and store your advertising consent choices and to present Google’s consent and privacy-options forms. It stores the consent state on the device so you are not asked again on every launch.

4.3 What is not used

The app contains no analytics SDK, no crash-reporting SDK, no social login, no cloud sync and no other third-party advertising network.

Note on “no data collected”. Statements such as “this app collects no data” would be inaccurate. DrivePass Nepal operates no backend of its own, but the advertising SDK bundled in the app does collect and share the data listed above.

5. Advertising in this app

Advertising is how DrivePass Nepal is kept free.
Banner ads may appear at the bottom of learning and examination screens — including question practice and mock exams — always separated from the question text, options, timer and controls.
Full-screen (interstitial) ads appear only at two points: immediately before a mock exam starts, and occasionally after every 50 answered questions in Full Question Bank practice. They are never shown between individual exam questions.
No ad is shown on the main dashboard.
Ads are requested only when the device is online, when your consent allows it, and when the advertising SDK is available. An ad failing to load never blocks learning and never interrupts an exam.

6. Consent and your privacy choices

At each launch the app refreshes your consent status through Google’s UMP and displays Google’s consent form when the law in your region requires it.
The app requests an ad only if UMP reports that ad requests are permitted (canRequestAds()).
You are never required to accept personalised advertising to use the educational content. Declining, or ignoring the form, does not lock any learning feature; it simply means fewer or no ads are shown.
When UMP indicates that a privacy-options entry point is required, Settings → Privacy → Ad Choices re-opens Google’s form so you can change or withdraw your choice at any time.
You can also reset or delete your Android advertising ID in your device settings; see Google’s page: support.google.com/googleplay/android-developer/answer/6048248

7. Data retention and deletion

Data held by us: none. We operate no server and store nothing about you.
Data on your device: kept until you delete it. Uninstalling the app or clearing its storage in Android settings removes the local database and all preferences.
Data collected by Google’s advertising SDK: retained by Google under Google’s own retention rules. The privacy contact below can help you with questions, but deletion requests for SDK-side data must ultimately be handled through Google’s controls (for example resetting your advertising ID) or Google’s privacy tools: myadcenter.google.com

8. Children’s privacy

DrivePass Nepal is intended for people preparing for a Nepali driving licence — generally teenagers and adults — and is not directed at children. It does not knowingly collect personal information from children. The app has no account, no user-generated content and no social features.

[TO BE CONFIRMED] Confirm the intended minimum age of your audience and, if any part of the app should be treated as child-directed, whether the advertising SDK must be configured for child-directed treatment (Google Play Families requirements and the “tag for child-directed treatment” / “tag for users under the age of consent” settings in AdMob).

9. Security

All app-initiated network traffic is HTTPS. Cleartext (plain HTTP) traffic is disabled through an Android network security configuration.
Study content stored on the device is public educational content, not personal data.
The app requests no sensitive permissions and keeps personal information off any server.
No method of transmission or storage is perfectly secure. Since we store nothing on a server, the main risk to your information is limited to data held by the advertising SDK, which is encrypted in transit.

10. Changes to this policy

This policy may be updated when the app, its SDKs or the law change. The “Last updated” date will be revised and, where the change is significant, it will be described in the app’s release notes on Google Play.

11. Contact

Name: [TO BE PROVIDED]
Email: [TO BE PROVIDED]
Postal address: [TO BE PROVIDED — optional, but helpful for store review]

12. Sources used to prepare this policy

Google Mobile Ads SDK — Google Play data disclosure: developers.google.com/admob/android/privacy/play-data-disclosure
Google Play — Data safety section: support.google.com/googleplay/android-developer/answer/10787469
Google Play — Advertising ID: support.google.com/googleplay/android-developer/answer/6048248
Google Play — User Data policy: support.google.com/googleplay/android-developer/answer/10144311

Information in this policy reflects the following components actually bundled in the app at the time of writing: google_mobile_ads 7.0.0 → Google Mobile Ads SDK (play-services-ads) 24.9.0 and Google User Messaging Platform 4.0.0. Google periodically changes its SDK data practices — re-check the official page above, and review this policy, whenever the SDK is upgraded.