Privacy policy examples for apps: three worked examples

The fastest way to understand what a privacy policy needs is to see a few that fit real kinds of apps. Below are three short, complete examples. The apps and companies are invented, and the details are chosen to show different situations: nothing collected, sensitive data with accounts, and advertising with purchases. Each is followed by notes on why it is written that way. To produce your own, use the app privacy policy generator or the template.

What does a policy look like for a note-taking app with no account?

Margin Notes privacy policy. Last updated: October 25, 2026.

This policy explains how Example Studio ("we") handles information in the Margin Notes app for Android and iOS.

Information we collect. Margin Notes does not collect personal information. There is no account, your notes stay in the app's storage on your device, and the app contains no analytics, advertising or tracking code. Apple and Google collect information through their app stores under their own policies and give us aggregate statistics, such as install counts, that do not identify you.

Device permissions. If you attach a picture to a note, the app opens the system photo picker and receives only the picture you choose. It stays on your device.

Keeping and deleting information. Your notes stay until you delete them or uninstall the app. If you email us, we use your address only to reply and delete the conversation when it is no longer needed.

Children. The app is not directed at children under 13, and we do not knowingly collect information from them.

Changes and contact. We will update the date above if this policy changes. Questions: privacy@example.com.

This policy was prepared with a free privacy-policy tool and is not legal advice.

Why it is written this way:

• Both stores require a policy even when nothing is collected. Saying so plainly, and explaining where the data lives, is enough.
• Using the photo picker instead of full photo access keeps the permission section to one sentence.

What does a policy look like for a fitness app with accounts and health data?

StrideLog privacy policy. Last updated: October 25, 2026.

This policy explains how Example Health Apps LLC ("we") handles information in the StrideLog app.

Information we collect.

• Account details: your email address, name and date of birth.
• Workouts you record: routes, distance, duration and the notes you add, stored on our servers so they sync between devices.
• Health data you allow: steps, workouts and heart rate from Health Connect on Android or the Health app on iPhone, only for the data types you approve.
• Location: precise location while a workout is being recorded, including when the screen is off, to map your route. You can choose approximate location or turn location off in Settings.
• Diagnostics: crash reports with technical details, through Firebase Crashlytics.
• Subscription status from Google Play or the App Store. We do not receive card details.

How we use it. To run your account, record and sync workouts, show your progress, fix crashes and deliver your subscription. We do not use health or location data for advertising or marketing, and we do not sell it.

Third-party services. Google provides crash reporting (Firebase privacy information: https://firebase.google.com/support/privacy). Each provider protects your data at least as well as this policy does.

Keeping and deleting information. We keep your data until you delete your account. You can delete it in the app under Profile > Delete account, or by emailing privacy@example.com without the app. We delete it within 30 days, except records the law requires us to keep.

Security and transfers. Data is encrypted in transit. We store it in the United States; for users in the EU and UK we rely on the Standard Contractual Clauses.

Your rights. You can access, correct, export or delete your data, and withdraw consent for health data at any time. In the EU and UK, our legal bases are contract (your account) and consent (health and location data), and you can complain to your data protection authority.

Contact. Example Health Apps LLC, 1 Example Street, Springfield. privacy@example.com.

This policy was prepared with a free privacy-policy tool and is not legal advice.

Why it is written this way:

• Health data is sensitive under both stores' rules, so the policy says what types are read and promises no advertising use.
• Background location gets its own sentence, matching what Google Play asks you to justify.
• Account deletion is offered in the app and by email, as both stores require.

What does a policy look like for a free game with ads and purchases?

Tile Tumble privacy policy. Last updated: October 25, 2026.

This policy explains how Example Games Ltd ("we") handles information in the Tile Tumble game.

Information we collect. We do not ask for your name or email. The game collects:

• Gameplay and device information: levels played, session length, app version, device model and an installation identifier, through Google Analytics for Firebase.
• Advertising data: your device's advertising ID where your settings allow it, approximate location from your IP address, and the ads you see and tap, collected by Google AdMob.
• Purchase records from Google Play or the App Store: the item, date and order identifier.

How we use it. To keep the game working, balance levels, show ads that keep the game free, and deliver what you buy.

Advertising. Ads may be personalized. On iPhone, we ask permission first through App Tracking Transparency; if you decline, ads are not personalized through tracking. On Android, you can delete or reset your advertising ID in your device settings. How Google uses this data: https://policies.google.com/technologies/partner-sites

Purchases. Coins and ad removal are sold through Google Play and the App Store, which handle payment.

Children. Tile Tumble is not directed at children under 13.

Your rights. Email privacy@example.com to access or delete your data. California residents: showing personalized ads can count as sharing personal information. To opt out, decline tracking or reset your advertising ID, or email us with the subject "Do not sell or share".

Contact. privacy@example.com.

This policy was prepared with a free privacy-policy tool and is not legal advice.

Why it is written this way:

• "We do not collect your name" is true, but the ad and analytics SDKs still collect device data, and the policy says so. Leaving that out is the most common mismatch reviewers find.
• The advertising section tells users how to limit tracking on each platform.
• California's "sharing" rule applies to personalized ads, so the opt-out is spelled out.

How do I turn an example into my own policy?

Start from the example closest to your app, then go through your build: every permission in your manifest or Info.plist, every SDK, and every place data leaves the device. Add or remove sections until the policy matches. Then check it against your Google Play Data safety form and Apple's App Privacy answers; our Google Play and App Store guides list what each store compares.