Privacy Policy
Updated 11 October 2026
We added Sign in with Google (what we receive from your Google account, and that we never see your Google password), explained how long you stay signed in and where your sign-in tokens are stored, and clarified what happens when you delete your account.
01 Scope
This policy covers the JamExams Android app and the jamexams.sc.tz website (landing page and admin tools). It applies to anyone who uses either as a guest or as a registered account holder: students, teachers, and administrators.
It does not cover third-party sites you reach by following a link out of JamExams, or services you use independently of JamExams (for example, your phone's own settings).
02 Information we collect
2.1 What guest browsing needs
You can open the app, browse subjects and classes, and search for exam papers without creating an account. For this, we don't collect anything that identifies you personally - only standard technical data your device sends automatically (see 2.3).
2.2 What an account adds
| Category | Examples | Why we need it |
|---|---|---|
| Account details | Name, email address, password (stored as a salted hash, never in plain text) if you register with email, role (student/editor/admin) | To create and secure your account, and to show the right tools for your role |
| Sign in with Google | If you choose it: your Google account email address, name, profile picture and Google's unique account identifier. We never receive your Google password. | To create or sign you in to your JamExams account without a separate password, and to recognise you when you come back |
| Content activity | Papers you've downloaded, bookmarked, or recently viewed | So your downloads and bookmarks are there when you come back, and so we can show relevant "recently updated" suggestions |
| Device & push token | An Expo push token tied to your install of the app | To deliver notifications you've asked for - e.g. a new paper added to a subject you follow |
| Session & auth tokens | Access and refresh tokens, kept in your device's encrypted secure storage (Android Keystore) | To keep you signed in without re-entering your password constantly. You stay signed in while you keep using the app; if you don't open it for about 7 days, or you log out, you'll be asked to sign in again |
2.3 Technical & diagnostic data (everyone, including guests)
| Category | Source | Examples |
|---|---|---|
| App usage analytics | Firebase Analytics (Google) | Screens viewed, features used, general device/OS info, approximate region |
| Crash & error reports | Firebase Crashlytics (Google) | Stack traces, device model, OS version, app version at the time of a crash |
| Advertising data | Google AdMob | Advertising identifier, ad interaction data, approximate location for ad relevance (see Section 5 - this is limited for users we know or suspect are minors) |
We don't currently use website cookies for tracking on jamexams.sc.tz beyond what's strictly needed to keep you signed in to the admin panel. See Section 6.
03 How we use it
- Operate the core service: showing you papers, remembering bookmarks and downloads, keeping your session signed in.
- Verify your identity when you sign in, including checking with Google that a Sign in with Google request is genuine.
- Send you notifications you've opted into (new papers, marking schemes, account/security notices).
- Understand which subjects, classes, and features are actually used, so we know what to build or fix next (Firebase Analytics).
- Find and fix crashes before they affect more people (Crashlytics).
- Show ads that help keep JamExams free to use (AdMob) - see Section 5 for the limits we apply here.
- Respond to support requests you send us directly.
We do not sell your personal data. We do not use your data to build advertising profiles outside of the ad network described in Section 5.
05 Advertising & children
JamExams is used heavily by secondary school students, many of whom are under 18. We take that seriously in how ads are configured:
- We do not knowingly target personalized advertising at users we know to be children under the age applicable in their country.
- Where the app or a specific account is flagged as likely to be used by a child, ad requests are tagged accordingly so AdMob serves only non-personalized, contextual ads rather than ones based on behavioral profiling.
- We don't knowingly collect more data than necessary from an account used by a child, and we don't knowingly allow a child to make in-app purchases (JamExams currently has none - see Terms of Service, Section 7).
If you are a parent or guardian
If you believe your child has given us personal information beyond what's needed for the account features described above, contact us at the address in Section 12 and we'll review and delete it as appropriate.
07 Data retention
We keep account data for as long as your account is active. If you delete your account, we remove your personal details (name, email, stored password hash, and the Google account identifier and profile picture if you signed in with Google) and your bookmarks/download history within 30 days, except where we're required to keep limited records for legal, security, or dispute-resolution purposes. Aggregated analytics that no longer identify you may be kept longer.
08 Your rights
Depending on where you live, you may have rights to access, correct, export, or delete your personal data, and to object to or restrict certain processing. If you're in Tanzania, these rights are recognized under the Personal Data Protection Act, 2022.
To exercise any of these, email us at the address in Section 12. We'll respond within a reasonable time and may need to verify your identity first.
- Access & correction - most of your account details can be edited directly in the app's Settings.
- Deletion - request account deletion at any time; see Section 7 for what happens next.
- Notification opt-out - turn off push notifications in the app's Settings, or in your device's notification settings.
- Ad personalization opt-out - use your device's "Opt out of Ads Personalization" setting (Android: Settings → Privacy → Ads).
09 Security
Passwords are stored as salted hashes, never in plain text. If you sign in with Google, we don't store or see a Google password, and we verify Google's sign-in proof on our server before creating your session. Sign-in tokens on your phone are kept in encrypted secure storage. Sign-in uses token-based authentication (JWT) over encrypted connections (HTTPS/TLS). Access to the admin panel is role-restricted. No method of transmission or storage is perfectly secure, so while we work to protect your information, we can't guarantee absolute security.
10 International data transfers
JamExams's backend is hosted on servers outside Tanzania, and providers like Google (Firebase, AdMob) and Brevo process data on infrastructure located in other countries. By using JamExams, you understand your information may be processed outside the country you're in, under that provider's own safeguards.
11 Changes to this policy
We may update this policy as JamExams changes - for example, if we add a new feature that collects different data, or change service providers. We'll update the effective date above, and for material changes, we'll post a notice in the app or on the website before they take effect.
12 Contact us
Questions, requests, or concerns about this policy or your data:
support@jamexams.sc.tz
Jamjicho Media - operator of JamExams (jamexams.sc.tz)