The House Rules.

A privacy policy, written like a person actually wrote it.

Last updated · April 24, 2026

"We're a small kitchen. We do not sell your data, share it with advertisers, or feed it to brokers. What we keep, we keep to make the app work.and we throw most of it out as soon as we're done with it."

· Chapter One ·

What we keep on file.

Account, when you sign in with Google

Your Google account email and unique identifier
Your profile display name, if you provided one

Pantry & usage, generated as you cook

Items you add to your pantry.quantities, units, expiration dates
Photos of receipts, fridge contents, and barcodes you submit to scan (extracted, then discarded)
Photos attached to recipe contributions (kept if your recipe is approved, discarded otherwise)
Shopping list, meal plans, recipe swipes (save / skip / cook), reviews, follow relationships

Analytics.coarse, not personal

Screen views, taps, swipes, and button presses, tied to your account ID
Session metadata: app version, device model, coarse timing

Subscription, if you buy one

Google Play purchase token (to verify your tier)
Subscription tier and renewal status

House Rule №1

We do not collect precise location, your contacts, your text messages, your call logs, your health data, or anything biometric. None of that is necessary to figure out what to cook tonight.

· · ·

· Chapter Two ·

Why we keep any of it.

To run the app. Recipe matching, pantry tracking, meal planning, scanning, shopping list.all of it needs the data above to work.
To make it better. We measure which features get used, fix bugs, and improve recipe ranking.
For the community. If you publish reviews or contribute recipes, your display name (not your email) shows on them.
To keep things honest. Detect abuse, enforce rate limits, rotate compromised credentials.

House Rule №2

We do not sell your data. Not to advertisers. Not to data brokers. Not for "marketing partnerships." Not for anything.

· · ·

· Chapter Three ·

Where the data lives.

Account & usage data: Cloudflare Workers + D1 (SQLite), in their global network
Approved recipe photos: Cloudflare R2
OCR & vision processing: Anthropic Claude API.images are extracted, not retained, per Anthropic's terms
Subscription billing: Google Play Billing

· · ·

· Chapter Three & a Half ·

The ads on the wall.

The free tier of brimm shows ads. Pro subscribers do not see ads.

Who serves them

Google AdMob serves all banner, interstitial, and rewarded ads in brimm.
AdMob is operated by Google. Their handling of ad data is governed by the Google Privacy & Terms.

What AdMob may collect

Your device's Advertising ID (a resettable identifier specific to ads, not your account)
Coarse IP address and approximate location derived from it
Device model, OS version, screen size, language
App-package signal that you are using brimm (no other in-app behavior is shared)

What we share with AdMob

Nothing from your pantry, recipes, plans, scans, or account.
The fact that an ad slot fired, and (for rewarded ads) whether you completed it.

Personalized ads & opting out

If you are in a region that requires consent (EU/UK), you will be asked before personalized ads are shown.
You can reset or opt out of ad personalization at any time from your device: Settings → Google → Ads → Reset advertising ID / Opt out of Ads Personalization.
To remove ads entirely, subscribe to Brimm Pro from inside the app.

House Rule №3

We never share who you are, what's in your pantry, or what you cook with our ad partner. Ads are served based on the device, not on you.

· · ·

· Chapter Four ·

How long it sticks around.

Pantry, shopping, plans, interactions: kept while your account exists
Receipt & fridge scan photos: discarded within 24 hours of processing
Unapproved recipe photos: discarded within 30 days
Approved recipe submissions: kept until the recipe is deleted
Analytics events: retained 90 days
Deleted account data: purged within 30 days of deletion

· · ·

· Chapter Five ·

Your cards on the bar.

Export your data.in-app: Settings → Export my data
Delete your account.in-app, or use the deletion form. Your pantry, plans, lists, interactions, and account record are permanently gone within 30 days.
Get in touch about anything in here: schulgenkyle@gmail.com

· · ·

· Chapter Six ·

About the rest.

Children

brimm is not directed to children under 13. We do not knowingly collect data from anyone under 13. If you believe a child has submitted data, contact us.we'll delete it.

Security

TLS in transit for every API request
Certificate pinning in the Android client
HMAC-signed access tokens with rotating refresh tokens
EXIF / GPS metadata stripped from photos before storage
Backend access limited to the operator

No security is perfect. Report vulnerabilities to schulgenkyle@gmail.com and we'll acknowledge within 7 days.

Changes to this policy

We post material changes here with an updated "Last updated" date. If a change affects how we handle data already collected, we notify active users in-app before it takes effect.