Legal

Data Safety

Last updated 6 September 2026 · Mirrors the Data Safety section BeastBook declares on Google Play

The short version: BeastBook collects your workout, nutrition, and (if you opt in) Health Connect data — all of it stays on your device. Nothing is shared with advertisers or data brokers. The only network calls are per-feature lookups (AI food search, AI photo estimate, barcode scan) and subscription billing, each sending only the minimum needed for that one request.

Data types collected

Health info

Steps, heart rate, weight, body fat %, and active calories burned (via Health Connect); age, height, weight, and fitness goal you enter directly.

Collected Yes Shared No Processed ephemerally No — stored on device Required Optional

Fitness info

Workouts, exercises, sets, reps, and weights you log.

Collected Yes Shared No Required Optional

App activity

Meals logged, calorie entries, and other in-app actions.

Collected Yes Shared No Purpose App functionality

Personal info — Name

An optional profile field, stored locally only. Can end up in a workout you export or share as a QR code / social card — see the Privacy Policy.

Collected Yes Shared No third party Required Optional

Photos

A photo you take or choose of a meal, for the AI photo-estimate feature. Sent to Google's Gemini API to identify the food and judge portion size; not stored by us afterward.

Collected Yes Shared Yes — sent to Google Required Optional Purpose App functionality

Not collected

Personal infoemail address, physical address, phone number, race/ethnicity, political or religious beliefs, sexual orientation

Videos, messages, audio, files & docs, contacts, calendarnot collected. The camera is also used separately to scan a barcode live — that specific use never captures, stores, or transmits a photo, only the decoded barcode number; see Photos above for the separate meal-photo feature, which does send an actual photo

Financial info, location, web browsing, device or other identifiersnone of these are collected

Where data goes when you use specific features

Feature	What's sent	Sent to
AI food search / estimate	The food text you type	Google (Gemini API), or Anthropic if you've added your own key
AI photo estimate	A photo you take or choose of a meal	Google (Gemini API) — never Anthropic
Barcode scan	The scanned barcode number only	Open Food Facts
Subscription purchases	Subscriber ID, purchase/subscription status, device identifiers	RevenueCat, and Google Play for payment processing

None of these are advertising or analytics partners — each is triggered only when you actively use that specific feature, and receives only the minimum data that feature needs.

Encryption and deletion

In transit: every network request (Gemini, Anthropic, Open Food Facts, RevenueCat) uses HTTPS.

Deletion: handled in-app, immediately — there's no account and no server-side copy. Delete an entry and it's gone; uninstall the app and everything goes with it. The one exception is subscription/purchase records, which Google Play and RevenueCat retain separately for billing and legal record-keeping — see the Privacy Policy for how to request deletion of those.