Overview
BiteBalance is operated by CipherChow LLC. BiteBalance provides nutrition logging, macro tracking, barcode scanning, user-selected targets, tracking insights, reminders, non-medical in-app guidance, and account services. This Privacy Policy explains how BiteBalance collects, uses, stores, and protects information when you use the website, mobile app, closed beta, support, and account services.
Public sign-up is not available right now. BiteBalance is not a medical provider and does not provide medical advice, diagnosis, treatment, or emergency services.
Data we collect
| Category | Examples | Purpose |
|---|---|---|
| Account and authentication information | Name, email, authentication provider, account identifiers, verification activity, account status | Account access, security, support, verification, and account controls |
| Profile and preferences | Nutrition goals, units, guidance settings, notification preferences | Personalized tracking, reminders, and plan configuration |
| Nutrition, profile, and optional activity data | Food logs, servings, barcode scans, macro targets, weigh-ins, profile details, and optional activity or device-health data when a permission-based integration is enabled | Logging, analysis, user-selected targets, progress insights, and user-selected sync features |
| Recipes, reviews, and saved content | Recipe content, ratings, review text, saved foods, notes, tags, and related user content | App features, saved content, support, moderation, and service improvement |
| Device, session, and security data | App version, device type, platform, diagnostics, crash reports, IP-derived metadata, authentication events, abuse-prevention signals | Reliability, security, troubleshooting, fraud prevention, and product improvement |
| Support and bug report communications | Messages, requests, attachments, screenshots, report category, app version, platform, device, screen, repro steps, expected behavior, actual behavior, account deletion requests | Support, privacy requests, beta review, account verification, and operational follow-up |
| Catalog and item contributions | Submitted foods, barcode corrections, item names, nutrition facts, ingredient notes, serving updates, review notes, and contribution metadata | Catalog quality, abuse prevention, moderation, support, and product improvement |
| Beta access and safety records | Invite status, beta-user role, account-gated access state, moderation notes, rule reports, and access-review records when those programs are offered | Beta access, safety, support, moderation, and access review |
How data is used
- Provide account access and secure authentication.
- Save nutrition logs, serving choices, goals, preferences, and app settings.
- Generate macro targets, progress signals, reminders, and non-medical tracking insights.
- Improve search, barcode matching, app reliability, security, and support quality.
- Review in-app bug reports, catalog or item contributions, and beta safety reports.
- Use support reports, diagnostics, screenshots you choose to send, and catalog contributions to troubleshoot issues, improve data quality, protect the service, and follow up with beta testers.
- Detect abuse, protect accounts, comply with legal obligations, and enforce terms.
HealthKit, Health Connect, and device integrations
HealthKit, Health Connect, and similar device-health integrations are optional and permission-based. When enabled, BiteBalance requests only the data types needed for the selected user-facing feature, such as nutrition, wellness, activity, profile, or progress context shown inside the app.
BiteBalance does not sell HealthKit or Health Connect data and does not use it for advertising. Access depends on user permission and device settings, and permissions can be changed or revoked through Apple Health, Health Connect, or device settings.
Beta reports and catalog contributions
In-app bug reports and support messages may include app context such as category, app version, platform, device, screen, repro steps, expected behavior, actual behavior, diagnostics, and screenshots you choose to send. BiteBalance uses this information to reproduce issues, prioritize fixes, and follow up with beta testers.
Catalog and item contributions may be reviewed, edited, merged, rejected, or retained to improve food search, barcode matching, nutrition data quality, and abuse prevention.
If BiteBalance offers account-gated beta community or feedback programs, access may be reviewed, moderated, changed, suspended, or revoked based on beta status, account status, safety reports, or these terms.
Retention
BiteBalance keeps personal information for as long as reasonably needed to provide the services, maintain security, meet legal obligations, resolve disputes, prevent abuse, enforce agreements, and support beta reports. Account deletion requests remove or de-identify eligible account-linked data from active systems after verification, subject to lawful retention requirements, security needs, dispute handling, fraud prevention, issue history, moderation records, and backup cycles.
BiteBalance aims to confirm deletion requests submitted by email within 7 days and complete eligible deletion within 30 days after verification unless legal, security, fraud-prevention, dispute, enforcement, or backup requirements require more time. Backup copies are isolated from active use and expire through the backup lifecycle.
Your choices
- Use Account → Privacy & data in the signed-in iOS or Android app to request full account deletion. The same area provides account access, correction, export, and data-only controls as they roll through beta builds; if a control is not available in your build, use the public request pages or contact support.
- Manage notifications through app settings and device settings.
- Disconnect optional health data permissions through device settings.
- Request access, correction, or deletion of account data.
- Use Account deletion for full account removal, or Data deletion when you want eligible app data removed while keeping the account open.
- Avoid sending passwords, one-time codes, private medical documents, or unnecessary sensitive information in support emails.
Security and children
BiteBalance uses technical, administrative, and organizational safeguards designed to protect personal information. No method of transmission or storage is completely secure, and BiteBalance cannot guarantee absolute security.
BiteBalance is not directed to children under 13 and does not knowingly collect personal information from children under 13. Beta access is intended for users who can consent to these terms, or who use BiteBalance with parent or guardian involvement where required. If BiteBalance learns that it has collected personal information from a child under 13, it will take appropriate steps to delete it.
Contact
Privacy requests and account questions can be sent to support@bitebalance.net.