This Privacy Policy describes how MyNotes (“MyNotes”, the App) collects, uses, stores, and shares information when you use it on Android.
Throughout this Policy, “we”, “us”, and “our” refer to Prasta Apps Studio, the operator of MyNotes.
Contact for privacy requests
Prasta Apps Studio — reach us via the Google Play developer page or the support option on the MyNotes listing on Google Play.
— Summary
- Notes and notebooks are stored primarily on your device.
- If you choose to sign in with Google, the App may sync notebooks and notes to Google Firebase (Firestore) for optional backup and restore, tied to your Google account via Firebase Authentication.
- Advertising (free tier): the App uses Google AdMob, including native-style placements while you browse notes.
- Optional rewarded ads: you can start a rewarded interstitial (full-screen) only from Menu (☰) → Ads & support → Watch ad after an on-screen disclosure with Continue / Skip. Watching is not required for note-taking.
- Optional one-time purchase (ad-free): the App offers Remove ads through Google Play Billing (
com.android.vending.BILLING). The in-product ID isremove_ads(a non-consumable, one-time item; approximate list price often around US $4.99—Google Play shows the exact price for your currency/region). When Play confirms entitlement, native ads and rewarded support ads are disabled until entitlement changes (e.g. refund/revocation by Play or clearing app storage—see §1.4). - Payments for that purchase are processed by Google; we do not receive your full card or bank credentials.
- Firebase Analytics may be active per our SDK configuration—see the Firebase Privacy Policy for categories of data Firebase products may collect.
01 Information the App processes
1.1 Information you enter or create
| Data | Typical use |
|---|---|
| Note content (titles, bodies, checklist text, reminders metadata, notebook names, styling/metadata) | Note-taking, search, reminders, trash/archive |
| Account choice | Optional Google Sign-In for cloud backup |
1.2 Device and usage data
| Data | Why |
|---|---|
| Identifiers and telemetry from Firebase / Google Play Services | Firebase configuration, Authentication, Analytics (if enabled), and installation/app instance identifiers as described by Google |
| Advertising-related identifiers and telemetry | Deliver and measure ads through Google Mobile Ads / AdMob, only when ads are enabled (typically until Remove ads is active for your Play account/device install as described below) |
| Purchase / entitlement signalling from Google Play Billing | The App asks Play whether remove_ads is owned and acknowledged so it can honour ad-free mode (see §1.4) |
| Technical logs on your device | Debugging when you share logs—third-party SDKs may log according to their policies |
Exact categories depend on SDK versions. See the Google Privacy Policy and Firebase disclosures.
1.3 Optional cloud backup (Google Sign-In + Firestore)
If you sign in:
- Firebase Authentication may process identifiers associated with your Google account (such as UID and optionally email for display inside the App) solely to authenticate you.
- Cloud Firestore may store structured documents describing your notebooks and notes keyed to your Firebase user ID so backups can be restored across installs.
Signing out on the device stops new authenticated access from this installation until you sign in again. Permanent delete and empty trash flows generally remove matching documents from Firebase when you are signed in.
1.4 In-app purchases — Remove ads (remove_ads)
The App integrates Google Play Billing Library:
- What you buy: a single, one-time (non-renewing, non-consumable) SKU with product ID
remove_adsto unlock ad-free mode: native AdMob placements and the voluntary rewarded “Watch ad” flow do not appear once Play confirms the purchase (subject to revocation/refund handled by Play). - What we don’t promise here: wording on your actual Play Console product title/description controls marketing; this Policy summarizes technical behaviour. Subscriptions other than
remove_adsare not offered in the current app version as described here. - Payment details: handled by Google under Google Play / Google Payments terms; we receive confirmation of entitlement from the Billing API, not your full payment card number.
- Local cache: whether you are treated as ad-free is mirrored in private app preferences (
SharedPreferences) on your device for responsiveness; that flag is updated when Billing reports changes (for example restore on launch/resume via Restore purchases). Clearing app data may reset the local cache; opening the App while online reconnects Billing so Play can reload ownership for the signed-in Play account. - Refunds / chargebacks: if Google revokes entitlement, ads may resume after the App syncs—see Google Play Help — refunds and your region’s purchaser rules.
1.5 Exports and files you control
You may export or import notes as files you choose to save or share. Those files leave the App under your control (Downloads, messaging apps, cloud folders, USB, etc.). We do not receive them unless you send them to us externally.
02 How we use information
We use information only:
- To provide notes, notebooks, reminders, archive/trash, search/templates (as implemented), and export/import
- To offer optional cloud backup / restore (Firebase, when you authenticate)
- To show ads (AdMob) when
remove_adsis not currently recognized for your install, measure ads where permitted, and honour consent/CMP or age-based restrictions where we configure supported SDK paths—see AdMob programme policies - To deliver and remember
remove_adsentitlement via Google Play Billing plus local prefs aligned with Play - To operate/improve Firebase-related tooling as configured (Analytics, etc.)
We do not sell your note text as a product. Advertising and analytics partners may process certain data under their own notices—see section 04.
03 Legal bases (EEA / UK users)
Where GDPR / UK GDPR applies, we rely on:
- Contract / steps prior to contract — providing the App features you requested, including fulfilment of
remove_adsthrough Play Billing where applicable - Legitimate interests — securing the App, fraud/abuse mitigation where proportionate, product improvement supported by aggregated or minimised telemetry—you may have rights to object where applicable by law
- Consent — where consent is required under platform rules or applicable law (for example certain ad personalisation scenarios on device or consent frameworks when used)
04 Third-party services
| Provider | Purpose | Further reading |
|---|---|---|
| Google Firebase (Auth, Cloud Firestore, Analytics as configured) | Optional backup; telemetry | firebase.google.com/support/privacy |
| Google Mobile Ads (AdMob) | Native ads when not ad-free; optional rewarded ads when started by you | policies.google.com/privacy · AdMob policies |
| Google Play / Play Billing | App distribution; remove_ads one-time purchase; payment processing by Google |
Play Terms |
| Google Play Services / Android | APIs used by Firebase, Ads, Sign-In, Billing | Platform / manufacturer policies |
Those services may act as processors in some relationships and as independent controllers in others, depending on context and law—see each provider’s documentation.
05 Data retention
- On device: notes and preferences (including
remove_adscache) persist until you uninstall, clear app data, or delete content in the App, subject to trash / retention rules in the App. - In Firebase (if you use backup): until overwritten by backups, deleted through App flows that remove cloud copies, or your Google / Firebase relationship changes as applicable.
- With Google Ads / Firebase / Play: retention is largely governed by Google per their policies and your account controls.
06 Children
The App is not directed to children under 13 (or the minimum age required in your jurisdiction for unsupervised consent to online services). If you believe a child has supplied personal information that should not be retained, contact us via the Play listing—we will help as required by applicable law.
07 Security
We rely on industry-standard transport security (HTTPS/TLS) for Google APIs that the Firebase, Ads, and Play Billing SDKs use. Your note content isn’t routed through a bespoke “MyNotes server” we operate—but it may be stored in Firestore when you opt in to backup. No method is 100% secure; protect your device, lock screen, and Google account.
08 International transfers
Google may process data in multiple countries. See the Google Privacy Policy and Firebase disclosures.
09 Your choices
You can:
- Use the App without Google Sign-In (local note-keeping; ads may still show unless
remove_adsis active for your Play account on this install). - Sign out of cloud backup in the App.
- Buy
remove_adsonce (when listed in your region) to disable native and voluntary rewarded ads as implemented, or decline and keep the free ad-supported experience. - Tap Restore purchases in Menu (☰) → Ads & support (or equivalent) to re-sync
remove_adswith Google Play after reinstall or device change for the same Play account. - Adjust Google ad personalisation, reset advertising ID where available, or use platform settings that limit ad tracking—see Google Help for your Android version / account.
- Skip rewarded ads: use Skip on the disclosure before an ad plays, or do not tap Watch ad.
- Manage Play orders and refunds in Google Play.
- Request Firebase / Google account export or deletion via Google Account tools, or contact us via the Play listing.
10 Permissions and Play capabilities (Android)
| Permission / declaration | Why |
|---|---|
INTERNET, ACCESS_NETWORK_STATE |
Network: ads, Firebase, optional backup, Billing |
com.android.vending.BILLING |
Google Play Billing for remove_ads (no access to contacts or SMS) |
POST_NOTIFICATIONS |
Reminders / notifications (Android 13+ where runtime permission applies) |
SCHEDULE_EXACT_ALARM, USE_EXACT_ALARM |
Exact-time reminders where the OS allows |
VIBRATE |
Gentle notification/reminder cues |
11 Changes to this Policy
We may revise this Privacy Policy when features change (for example billing or ad formats). When we do, we will update the “Last updated” date on this page, update the Google Play listing link where appropriate, and show a short in-app notice for material changes when we can.
12 Disclaimer — not legal advice
This document reflects implemented MyNotes behaviour as of the Last updated date: local notes, optional Firebase backup, AdMob (native + optional rewarded), one-time remove_ads via Play Billing, and local entitlement caching. It is not legal advice. Qualified counsel should review disclosures for GDPR, CPRA, LGPD, children’s privacy, COPPA jurisdictions, institutional use, Google Play Data safety accuracy, and any region you target.
This Policy is hosted at a stable HTTPS URL. Link it from your Google Play store listing and keep it aligned with your Data safety form.