Your shopping list, recipes, and settings live on your own device by default (in your browser's local storage) and never touch our servers unless you choose to sign in with Google.
If you sign in with Google, your list, recipes, and settings sync to a private database (Firestore, part of Google Firebase) tied to your Google account, so they follow you across devices. Only you can access this data — it's locked to your account. We receive your Google account's name and email as part of that sign-in, and use it for nothing beyond identifying which synced data is yours.
Your location is handled deliberately conservatively. If you use "Use my location," your device's GPS coordinates are used only for that browsing session to find your nearest store, then discarded — never stored anywhere. If you type a ZIP code and check "remember this ZIP," that ZIP code (nothing more precise) is saved on your own device so you don't have to re-enter it — it is never sent to us for storage, only used to ask Kroger's API for nearby stores each time you shop.
What you search for — the items and recipes you type or say — is sent to our backend, which forwards it to Kroger's product API to get real prices, and to TheMealDB for recipe search. We don't log, store, or build any profile from your search history.
Shared lists — if you create or join a shared list, its items and name are visible to everyone you've shared it with (and no one else), stored the same way as your personal data, tied to your Google account since collaboration requires knowing who's involved.
Crash reporting. We use Sentry to catch and fix bugs — when something breaks, technical details (what happened, not who you are) are sent to Sentry so it can be fixed. This runs on both our backend and in the app itself.
Basic usage counters. We log simple, anonymous counts of which features get used (e.g. "an item was added," "shopping mode was started") to understand what's actually useful and what isn't. These are just an event name and a timestamp — never tied to your identity, never building a profile of you individually, and never sold or shared. This is different from third-party analytics or ad-tech tracking: it's our own minimal, first-party counting, and nobody but the developer can see it.
We don't run ads, sell data, or use any third-party advertising or behavioral tracking.
Feedback submitted through the in-app feedback button opens your own email app — we only receive what you choose to send us directly. Occasionally, after a shopping session, the app may show a quick optional "how did it go?" prompt — always dismissible, never required, and never shown more than once every few days.
Since most of your data lives on your own device, clearing your browser's site data for blurt.works deletes it completely. If you've signed in with Google and want your synced cloud data deleted too, use the feedback button to ask — it'll be removed by hand, since there's no automated account-deletion flow yet at this stage.
Blurt isn't directed at children and we don't knowingly collect data from anyone under 13.
This is beta software, provided as-is. Blurt is an actively-developed personal project. Things may break, change, or be temporarily unavailable without notice. There's no warranty of any kind.
Not affiliated with Kroger. Blurt is an independent, unofficial tool that uses Kroger's public developer API. It is not affiliated with, endorsed by, or sponsored by The Kroger Co. or any of its banners (Fred Meyer, QFC, Ralphs, and others).
Prices are estimates. Prices shown come from Kroger's API and may not always match what you're charged at checkout — sales, availability, and pricing can change. Always treat the final price at the register as the real one.
No liability. Blurt is provided without guarantees, and the developer isn't liable for shopping decisions, price discrepancies, or any damages arising from using the app.
Fair use. Please don't attempt to abuse, scrape, or overload the service — it runs on a personal, limited-quota backend.
These terms may change as Blurt develops. If you keep using the app, that means you're fine with the current version of them.
Use the feedback button inside the app — it's the fastest way to reach the developer directly.