Effective date: September 11, 2026
This Privacy Policy explains what data Клац ("the App", "we", "us") collects, how it is used, and who it is shared with. We wrote this policy to describe exactly what the App does — no more, no less.
Food photos: When you take or select a photo of food to log a meal, the photo — along with any note you type about the meal — is sent to Google's Gemini API to identify the food. The identified food name (not the photo itself) is then sent to the USDA FoodData Central API to look up its calories and macronutrients (protein, carbs, fat), and Gemini may be called a second time to translate that food name. These requests are routed through our own server-side proxy (hosted on Cloudflare) so that our API credentials are never embedded in the App itself; the proxy's own code does not store, log, or retain your photos, notes, food names, or API responses beyond fulfilling your request. Cloudflare's infrastructure may separately retain basic technical request logs — which can include a food name from a USDA lookup — for a short period (typically a few days) for operational diagnostics, independent of anything we do.
Barcode scanning: When you scan a product barcode, the barcode is sent directly from your device to Open Food Facts, an open, crowdsourced food-products database, to retrieve the product's name, nutrition information, and image. Unlike the food-photo flow above, this request does not go through our proxy — it goes directly to Open Food Facts, so Open Food Facts receives your device's IP address. The product image shown for that diary entry continues to be loaded directly from Open Food Facts' servers each time you view it.
Diary and profile data: Your food diary entries and profile details (name, age, height, gender, weight, activity level, goal, and nutrition goals), along with a profile picture you choose from your photo library, are stored only on your device, using local device storage. We do not operate a server or account system that stores this data — it never leaves your device except for the specific requests described above (food-photo analysis and barcode lookups). Uninstalling the App or clearing its data permanently deletes this information; we have no copy of it.
Anonymous app identifier: The App uses Firebase (a Google service) to generate an anonymous identifier for your app installation — specifically, an anonymous authentication ID (no sign-in, no password, nothing you provide) used to rate-limit AI recognition requests so no single installation can exhaust the shared quota, and a Firebase Installation ID that the Firebase SDK creates automatically for basic operation. Neither identifier contains or is linked to your name, email address, diary contents, or photos — see "No Accounts" below.
Crash and error reports: If the App encounters an unexpected error, a report is sent to two places: our crash-reporting provider, Sentry, and a private Telegram channel that only the developer can access.
The report sent to Sentry contains: the anonymous app identifier described above, the device platform (iOS/Android) and app version, standard technical device information collected automatically by Sentry's SDK (OS version, device model, locale, available memory), a short trail of your recent in-app navigation (e.g. "camera opened", "saved meal to diary" — screen/action names only, never their content), the error message, and stack trace. In rare cases where an error occurs while looking up or translating a food name, a short fragment of that food name may also be included as technical context.
The report sent to Telegram contains: your device's platform (iOS/Android), the App version, a timestamp, the error message, and a portion of the technical stack trace. It does not include the anonymous app identifier or diary contents. In both cases, we do not deliberately collect your name, diary contents, or photos through these reports — though, as with Sentry, a malformed AI response could rarely cause a small fragment of recognized food text to appear in an error message.
Permissions: The App requests access to your camera and photo library to let you photograph or select food images for meal logging, and to let you choose a profile picture. You can revoke these permissions at any time in your device's system settings; doing so will only prevent photo-based meal logging and profile-picture selection.
Security: All network requests made by the App use HTTPS/TLS encryption in transit. We do not store your photos, diary, or profile data on any server we operate.
We do not sell your data, and we do not share it with advertisers or data brokers. We currently do not use any analytics or advertising services.
Клац does not require or offer account creation, sign-in, sign-up, or a password. We do not ask for and cannot identify you personally — by name, email, or otherwise — from App usage. The App does automatically generate the anonymous app identifier described in Section 1 (an anonymous Firebase authentication ID and a Firebase Installation ID) for every installation. This identifier is a random technical value, not tied to any personal information you provide, and exists solely to rate-limit AI requests per installation and to let us debug crash reports (see Section 4 for how long it's kept and how to have it deleted).
We do not retain food photos, diary entries, or profile data on any server we control. Your diary and profile data persist on your device only until you delete the App or clear its data.
Crash and diagnostic reports sent to Sentry, including the anonymous app identifier attached to them, are automatically deleted no later than 90 days after they're received — after that point they no longer exist anywhere, even to us. Crash reports sent to our private Telegram channel are retained for as long as needed for debugging purposes; unlike the Sentry reports, they carry no identifier at all, so they cannot be linked back to any specific installation or person. Basic technical request logs kept by our hosting provider (Cloudflare), which can briefly include a food name, are automatically deleted after a short retention period and are not used for any purpose beyond diagnostics.
Because the Sentry identifier is anonymous and never shown to you inside the App, we generally cannot look up "your" specific crash reports from a deletion request alone — in practice, the 90-day automatic deletion above is what actually removes that data. If you'd like us to delete a specific report sooner (for example, one you can describe by approximate date and device), contact us using the details in Section 8 and we'll do our best to locate and remove it.
Клац is not directed at children under the age of 13, and we do not knowingly collect personal information from children under 13. If you believe a child has provided us with personal information, please contact us at the email below so we can address it.
If Клац later introduces a paid subscription, purchases will be processed directly by Apple's App Store or Google Play using their own in-app purchase systems — we do not receive or store your payment details. This Privacy Policy will be updated if that changes what data we collect.
We may update this Privacy Policy as the App changes. Updates will be posted at this same URL, with a revised effective date at the top.
Клац is developed and operated by an independent developer, reachable at the email below. You may contact us at any time to ask what data we hold about you or to request its deletion — though as described above, we generally don't hold any of your personal data ourselves, since your diary and profile stay on your device and we don't operate accounts.
If you have questions about this Privacy Policy, contact us at: grebni2006@gmail.com