You built a cool side project. Deployed it. Shared it on Twitter.
Then someone asks: "Where's your privacy policy?"
Panic.
Let me help you fix that.
Do You Actually Need a Privacy Policy?
Yes, if you:
- Use Google Analytics (or any analytics)
- Have a contact form
- Use cookies
- Collect emails for a newsletter
- Store any user data
- Show ads
- Use third-party APIs that track users
Basically, if you have any JavaScript from external sources, you probably need one.
What Happens Without One?
Legal risks:
- GDPR fines up to €20M or 4% of revenue (EU users)
- CCPA penalties up to $7,500 per violation (California users)
- App store rejections (iOS, Android, Chrome extensions)
Practical risks:
- Google AdSense won't approve you
- Some APIs require it (Stripe, social logins)
- Users might not trust your app
What Must Be In Your Privacy Policy?
At minimum:
1. What Data You Collect
Be specific:
- Email addresses
- IP addresses
- Browser information
- Usage data
- Cookies
2. Why You Collect It
- To provide the service
- To improve the product
- For analytics
- For marketing (if applicable)
3. Who You Share It With
Third parties like:
- Google Analytics
- Stripe
- Your hosting provider
- Email services (Mailchimp, etc.)
4. How Long You Keep It
- As long as needed for the purpose
- Specific retention periods
5. User Rights
- Right to access their data
- Right to delete their data
- Right to export their data
- How to contact you
A Simple Template
Here's a minimal privacy policy for a typical side project:
Privacy Policy for [Your App]
Last updated: [Date]
What we collect:
- Usage data via Google Analytics
- Email addresses (if you sign up)
- Data you voluntarily submit
Why we collect it:
- To provide and improve our service
- To communicate with you
Third parties:
- Google Analytics (analytics)
- [Hosting provider] (infrastructure)
Your rights:
- Request your data: [email]
- Delete your data: [email]
- We'll respond within 30 days
Contact:
[Your email]
Customize for your actual data practices.
Tools to Generate Privacy Policies
Free options:
- PolicyFree.site — Simple generator for basic privacy policies
- Termly (free tier)
- PrivacyPolicies.com (limited free)
Paid options (for serious businesses):
- Iubenda ($29/year)
- Termageddon ($99/year)
- Lawyer ($$$$)
For a side project, free is usually fine.
Where to Put It
- Footer link on every page
- Sign-up/registration page
- App store listing
- About page
Standard URL: /privacy or /privacy-policy
GDPR vs CCPA vs Everyone Else
GDPR (EU):
- Strictest
- Requires explicit consent for non-essential cookies
- Must offer data deletion
- Apply to all EU residents, regardless of where you're based
CCPA (California):
- "Do Not Sell My Personal Information" link required
- 30-day response time for data requests
- Applies if you have CA users AND meet revenue thresholds
Everyone else:
- Follow GDPR rules and you're mostly covered
- When in doubt, be more transparent, not less
Common Mistakes
- Copy-pasting someone else's policy — might not match your actual practices
- Never updating it — review quarterly
- Claiming you don't collect data when you use Analytics — you do collect data
- No contact information — required by most laws
- Hiding it — must be accessible
Quick Checklist
- [ ] Privacy policy page exists
- [ ] Linked from footer
- [ ] Lists all data you collect
- [ ] Lists all third-party services
- [ ] Includes contact email
- [ ] Has a "last updated" date
- [ ] Matches your actual practices
Action Items
- Audit your site — what data do you actually collect?
- List your third parties — Analytics, CDN, APIs, etc.
- Generate a policy with PolicyFree.site
- Add it to your site footer
- Set a calendar reminder to review quarterly
Don't let legal stuff stop you from shipping. A simple, honest privacy policy takes 10 minutes to create.
Generate yours free: policyfree.site
Top comments (0)