Badger should feel private because the product is built that way.

Badger uses account information like email, username, and birthdate to create accounts, protect the 13-18 age boundary, and keep each user connected to their own data.

Birthdate is used for age eligibility. We should avoid asking for more personal information than the product needs.

Journal entries are designed to be private to the user. They are not community content.

Meli chat messages are saved to support continuity, product safety, abuse prevention, and user experience. Crisis-related signals can create separate review events for safety handling.

Community posts can appear anonymous to other users. They are still linked internally so Badger can moderate abuse, reports, and safety issues.

Replies, reactions, reports, follows, and moderation actions may be stored so the app can work reliably and safely.

The current product direction is data minimization, private journals, anonymous user-facing community identity, backend traceability for safety, and clear account deletion support.

Before a larger launch, the privacy language should be reviewed with the same care as the product and safety systems.