· 5 min read · Naveen · Privacy
Do I Need a Privacy Policy? The 5-Minute Test
Run this quick five-minute test to know whether your side project needs a privacy policy, and what to do next if it does.
Every few days, the same question lands in a Discord server: "Do I actually need a privacy policy, or is that just for big companies?"
The answers are always wrong in both directions. Half the thread says every website needs one, no exceptions. The other half says you are fine until you make money.
Both sides are overcomplicating it. What your app does with user data decides this, whatever your revenue. And you can answer it in five minutes.
Here is the test.
Why a wrong answer costs you
Before the test, a quick look at what happens when you guess:
- The platform decides for you. App Store and Google Play require a privacy policy URL the moment an app collects any data. Account creation, contact forms, and most analytics all count. You do not get to argue your app is too small.
- Silence is worse than a rejection. Shipping no policy rarely brings real trouble to a solo builder. Instead, it blocks you at review, fails a security check when a bigger customer wants to buy your product, or shows up in a Reddit thread as "this dev did not even have a policy page."
- The fix is cheap now, annoying later. Writing a policy from your data inventory takes an afternoon. Adding one after a launch, a store submission, and a paying customer means doing it under pressure, while checking everything that changed.
Set a timer now. Five questions. "Yes" to any single one means you need a privacy policy before your next launch milestone.
The 5-minute test
1. Can a person be identified through your app?
An email address at signup is identification. So are a name, a username, an account ID linked to a person. Purely anonymous tools where no identity ever exists (a client-side color picker, a static site) answer "no."
2. Do you collect any data from visitors or users?
Form submissions, email addresses, local storage, cookies, device information, analytics of any kind all count as yes. Most analytics scripts, even "privacy-friendly" ones, collect something, which is why almost every interactive product answers yes here.
3. Do you use third-party services that touch user data?
Your database host, email provider, payment processor, error tracker, analytics tool: if any of them receives user-related information, you have data practices to describe. This question alone catches most side projects. Stripe and Resend are enough.
4. Are you submitting to an app store or payment provider?
Apple and Google require a privacy policy URL before a store will review an app that collects any data. Payment providers such as Stripe, Lemon Squeezy, and Gumroad ask for a policy link during onboarding. The account does not open without that link, whatever your answers to questions 1 to 3 were.
5. Do users create content or accounts in your app?
User-generated content, saved projects, settings, messages. Anything stored on your side creates data you must describe: what you store, how long you keep it, how a user deletes it.
Scoring:
- All five "no": You are likely a static site or a pure client-side tool. That is rare. You can probably skip the policy for now, and re-run the test after your first feature that stores anything.
- Any one "yes": You need a privacy policy. One page, seven sections, an afternoon of work.
- "Yes" to question 4 or 5: You need a privacy policy and terms of service. Payments and user accounts are where the rules between you and your user have to exist in writing. Publish both before your next store submission or payment integration.
If you answered yes, and that is nearly everyone reading, the next section is the actual work.
What to do next (the one-afternoon version)
The test says yes. Here is how you get from "yes" to "policy live" without any special knowledge. You need three things: an inventory, a document, and a URL. The work splits into four steps.
Step 1: Inventory (30 minutes). List every piece of data your app touches: what you collect, why, which third party sees it, how long you keep it, and whether you ever share or sell it. If you do not sell data, write that sentence down. This inventory is the document. Do not skip it in favor of a template.
Step 2: Write seven sections (60 minutes). Collection, use, sharing, how long you keep it, user rights and deletion, children (13+ is standard), and changes. Use "we" and "you." No fancy wording you do not understand. If you cannot explain a sentence, delete it.
Step 3: Publish on a real URL (10 minutes). Public page, stable link, linked from your footer and signup form. A PDF or a Notion page whose share settings change someday will break the day a reviewer clicks it.
Step 4: Mark it done everywhere it is asked. Store listing, payment sign-up, signup footer. A policy that exists but is not linked might as well not exist at review time.
That is the whole fix. Most readers finish steps 1 to 4 today and never think about it again until their data practices change.
Common mistakes
- Confusing "no policy needed" with "no stakes." Even when the test comes back all-no, your first stored user record flips question 1 to yes. Re-run the test when you add signup, analytics, or payments.
- Letting a generator answer for you. Generators guess at your inventory. If your app does not run ads and does not sell data, stock text claiming otherwise is a problem you typed yourself. Generate the structure. Write the facts.
- Publishing without links. A policy with no footer link and no signup link fails the only test that matters: could a real user find it before they hand you their email? If not, it is not done.
The test says you need one. The inventory tells you what to write. All that is left is putting the document on a permanent URL, the part solo builders skip because their site has no good place for documents.
Get started with appsite.page: create a project, write or paste your policy in the editor with live preview, and publish it at a permanent public URL your footer, store listing, and signup form can all point to. See pricing.
Publish your own privacy policy and terms in about two minutes.
Get started