Use the app first. Use the web when you cannot.
Signed-in beta users manage account, privacy, and data requests from the iOS or Android app. This page explains the same workflow and provides a web fallback for access, export, correction, deletion, and support requests.
Account controls live behind sign-in.
Open BiteBalance, sign in with the beta account, then go to Account → Privacy & data. Sensitive actions may require recent verification before the request is accepted.
Cannot access the app?
Use support or the public deletion pages. Include only the details needed to locate the account and confirm request scope.
The email tied to the beta account, if one exists.
Apple, Google, or email, plus iOS or Android if the issue is platform-specific.
Access help, data export, correction, app data deletion, or full account deletion.
Do not send passwords, one-time codes, access tokens, raw health exports, or private medical documents.
Choose the account action that matches the outcome.
App controls are preferred when you are signed in. Public web pages stay available when you cannot use the app or arrive from a store listing.
Request account data
Ask for an archive of eligible account-linked data when export controls are not available in the beta app.
Correct account details
Request review of profile, access, sign-in, or account details after ownership is verified.
Delete app data
Remove eligible logs, saved foods, goals, preferences, or other app data while keeping the account open.
Delete account
Request deletion of the account and associated eligible app data through the app or public web fallback.
Support verifies ownership before sensitive changes.
Verification protects account data and helps prevent someone else from changing or deleting a beta account.
Support may ask for account email, sign-in provider, app platform, app version, or request context.
Never send passwords, one-time codes, authenticator codes, session tokens, or raw private health documents.
Fallback requests receive a status or completion update after ownership and request scope are reviewed.