Last updated: July 2026
This policy explains what information FoodBlurb collects and how we use it. By using foodblurb.com, you agree to this policy.
• Account info — your name, email, and profile details when you sign up.
• Content you create — blurbs, ratings, photos, replies, and reactions.
• Usage & device data — how you use the app, signup source, authentication method, device category, language, and timezone, collected via Firebase Analytics and our account systems.
• Approximate signup area — city, region, and country may be estimated from the signup connection for security and growth reporting. FoodBlurb does not retain the raw IP address in the signup record.
• Location — the location or zip code you use to find restaurants. When available, precise location may be used briefly to confirm that a new blurb was posted near its restaurant; the submitted coordinates are removed after that check.
• Notification tokens — if you enable push notifications.
To run and improve the Service — show your blurbs, personalise your feed, send notifications you've opted into, and keep the community safe. We don't sell your personal information.
Your display name may appear in discovery. Profile details and blurbs are visible according to your profile privacy setting. We use trusted providers — Google Firebase (hosting, database, auth, analytics, messaging), Google Maps/Places, and IPWho (coarse signup-area lookup) — who process data on our behalf. We may disclose information if required by law.
If you turn on notifications, we store a device token to deliver alerts (new followers, replies, likes, and updates from places you follow). You can turn these off anytime in your device settings.
From Account privacy in your profile, you can make your profile private, manage blocked users, download a copy of your account data, or permanently delete your account and blurbs.
FoodBlurb isn't directed at children under 13, and we don't knowingly collect their information.
Privacy questions? Email contactus@foodblurb.com.
This is a general template and not legal advice. Consider having a professional review it for your jurisdiction (e.g. GDPR/CCPA obligations).