Bite.

Bite · Effective October 20, 2026

Privacy Policy

Who is responsible?

Bite is provided by Ava Dazina Thalheim, trading as gugus. Software&Things, Tiefenbach 433, 3555 Trubschachen, Switzerland. Contact support@gugus.software for privacy questions or requests. Further contact details appear in our legal notice.

Local data and optional connections

You can use Bite without creating a Bite account. Profile details, goals, body measurements, food and activity entries, recipes, drafts, meal plans, photos, collectibles, preferences and cooking progress are primarily stored on your device. Device language and region help select language, units and food search results. Network features and connections described below are optional, except purchase verification and app analytics where available.

Food search, barcodes and recipe imports

Online food searches send your search text or barcode, shopping country and language to Bite’s food catalog hosted on Cloudflare. Barcode lookup may also contact Open Food Facts or USDA FoodData Central. These services receive ordinary connection information such as your IP address. Bite does not send your diary, body measurements or health records with food searches. Opening or importing a recipe URL contacts the source website and may download its text, images or public metadata. If you use AI extraction, the selected source content is also sent to your configured AI provider.

Health permissions and sensitive information

If you connect Apple Health or Android Health Connect, Bite reads the health and activity categories you authorize to display measurements and trends and calculate activity adjustments. Body, nutrition and health information can be sensitive. Health connections and their permissions remain device-specific. Health information saved in Bite can be included in a cloud backup when you enable sync. We do not use health information for advertising, sell it, or send it to food-search services or TelemetryDeck. You can revoke health access in the operating system’s health permissions; this does not automatically delete previously imported entries or backups.

Optional Google Drive sync

Google sign-in is used to connect your own Google Drive for backup, synchronization and restore, not to create a Bite account. Bite requests only https://www.googleapis.com/auth/drive.appdata for Drive access. It can read, create and manage Bite’s files in its hidden application-data folder, without access to your other Drive files. The Google account identifier and email are kept locally to identify and reconnect the selected account; the Google SDK manages authorization tokens.

When enabled, Drive sync uploads versioned copies of your Bite data and supported photos, including profile, food, recipe, planning, body and saved health information. Google stores these files in your account. Previous revisions may remain after you change or delete a local entry. Device permissions, AI API keys and purchase entitlements are not included in the Drive backup. Bite uses Google user data only to provide the sync and restore features you request; it is not sold, used for advertising or used to train generalized AI models. Our use of Google user data follows the Google API Services User Data Policy and Google Workspace API User Data and Developer Policy, including their Limited Use requirements.

Optional iCloud sync

On supported Apple devices, enabling iCloud sync sends Bite backup data to your private CloudKit database, with iCloud Drive used where supported as a fallback. Apple processes the data under its own terms and privacy policy. Sync availability depends on the device, account, connection and storage quota. Bite does not add its own end-to-end encryption layer to cloud backups.

Optional AI providers and API keys

AI features use a provider you configure, such as Google Gemini, OpenAI or a compatible endpoint, with your own API key. Your chosen photos, recipe text, prompts, ingredients and reviewed preferences or dietary restrictions are transmitted directly to that provider to fulfil the request. Dietary restrictions may reveal health information. Your full diary or health history is not automatically uploaded. Connection testing uses a synthetic request. Keys are stored using platform-secure storage, excluded from Bite tracker exports and cloud snapshots, and sent to the configured provider for authentication. Disconnecting removes the saved connection key; you can also revoke the key with the provider. Providers control their own retention, international processing, billing and possible use of requests for model improvement, which can differ by provider and free or paid tier. Review their policies before sending sensitive information.

Camera, photos, reminders and sharing

Camera and photo access support barcode scanning, meal photos, recipe images and avatars. Selecting or taking a photo does not by itself authorize an AI upload; an AI request or enabled cloud backup can send selected or saved images as described above. Reminders are scheduled locally through device notification permissions. Exports and sharing send the content you select to the destination or app you choose. External links, including Discord, open services governed by their own policies.

Analytics and purchases

Bite initializes TelemetryDeck on supported platforms for usage and technical analytics. Signals can include app launches, app and operating-system versions, device characteristics, language and region, with identifiers handled by that SDK. We do not attach diary contents, photos, health records, API keys, names or email addresses to analytics. Analytics are not used for advertising or cross-app tracking. Apple or Google Play and RevenueCat process purchase records, app-user identifiers, device information and entitlement status to sell, restore and validate Pro access. We do not receive your full payment-card details.

Retention, deletion and revoking access

Local data remains until you delete entries, reset Bite or remove its stored app data. Device and operating-system backups may retain copies. Turning off sync stops future synchronization but does not delete existing cloud files or historical revisions. You can revoke Bite’s connection in your Google Account’s third-party connections and delete Bite’s hidden app data through Google Drive’s Manage apps settings where available. Manage iCloud app data through Apple’s storage settings. Deleting a cloud backup does not delete local copies or copies on other devices; a device with sync enabled may upload data again. Disable sync on your devices before removing all backups. AI providers, purchase services and support correspondence have their own retention requirements. We retain support messages only as needed to address your request or meet legal obligations.

Your choices, rights and international services

We process information to provide requested app functions and purchases, respond to support requests, maintain reliability and meet legal obligations. Optional health, cloud and AI connections require your action and relevant permissions; you can stop using or revoke them. Where applicable law requires consent, you may withdraw it for future processing. Third-party providers may process information outside Switzerland or your country, including in the United States; their policies describe locations and safeguards. Depending on applicable law, you may request access, correction, deletion or portability, object to or restrict processing, and complain to the Swiss FDPIC or your local supervisory authority. Contact us using the details above. We cannot retrieve device-only information or erase independent provider records we do not control.

Children and policy updates

Bite is not directed to children under 13. We do not sell personal information or use it for advertising. We may update this policy as the app changes and will revise its effective date. Material changes requiring new consent will be subject to that consent.

Provider policies

Google · Apple · Cloudflare · TelemetryDeck · RevenueCat · OpenAI · Gemini API · Google API Services User Data Policy · Google Workspace API User Data and Developer Policy