Private beta community

A private feedback space for approved beta testers.

BiteBalance community spaces are meant to keep beta feedback useful, privacy-safe, and connected to product improvements. Access is private during closed beta and shared directly with approved testers when community participation is available.

Purpose

Feedback should help the app get better.

Community conversations focus on real logging workflows, install friction, catalog quality, scanner results, simpler-mode feedback, and the parts of nutrition tracking that feel confusing or too heavy.

Access model

Private during closed beta.

Community links are not public signup links. When community participation is available, invites are shared directly with approved beta accounts and may be reviewed if beta status, account status, or moderation status changes.

1
Approved testerUses an assigned iOS or Android beta channel and can share app feedback.
2
Helpful feedbackShares focused bug, catalog, workflow, or quality notes that help improve the beta.
3
Support routingAccount, privacy, deletion, and sensitive reports move to support or in-app reporting.
Expectations

Good beta feedback is specific and privacy-safe.

Community spaces are not the primary support queue. They help testers compare notes, share context, and surface product issues without exposing private account or health details.

Be concreteShare the screen, flow, platform, version, expected behavior, and what actually happened.
Stay privateDo not post passwords, one-time codes, raw health exports, account tokens, or private medical documents.
Use support for sensitive issuesAccount, privacy, deletion, billing, and security questions should go to support.
Keep it constructiveNo harassment, spam, credential sharing, false reports, or unsafe nutrition advice.
Expect moderationAccess can change for safety, beta eligibility, account issues, abuse, or security concerns.
Feedback may be summarizedUseful details may be summarized so the team can track patterns and follow up.