Less managing.
More resolving.

01 · The basics

What we collect

Account details. When you sign in, we receive the account information provided by Firebase Authentication, such as your email address or Google account identifier. We do not support anonymous access in the connected build.

Age band. Chüng is for people aged 13 and over. We store an age band—13–15, 16–17, or 18+—rather than a date of birth.

Team and project content. We store the teams, memberships, invitations, structured responses, votes, outcomes, budgets, and recaps that you create or are authorized to see. Please avoid putting sensitive personal information or unnecessary free text into a project.

Attachments. If a project supports a file, Chüng stores the file behind a short-lived, signed access ticket. The app does not create arbitrary storage paths.

Operational records. Commands generate audit records containing the action, actor, request ID, version boundaries, and affected entity. Privacy-safe analytics may record product events without account identity, age band, payload, or free text.

02 · Purpose

How we use information

We use information to provide Chüng’s core workflow: authenticate an account, enforce age and team membership rules, collect structured input, calculate outcomes, protect project boundaries, deliver authorized attachments, maintain auditability, and improve reliability during the beta.

We do not use your project content to sell advertising. We do not use the product as a messaging or notification-history archive. Budget features are calculation and recording tools; they do not move money or store payment credentials.

03 · Boundaries

When we share information

Project information is shown to the team members and other people who have permission for that project. A file is made available only through a valid, short-lived authorization checked by the service.

We may use infrastructure providers that operate services for Chüng, including Firebase for authentication, database, and backend functions, and Cloudflare for authorized file delivery. They process information only to provide those services and under their own terms and safeguards.

We may disclose information when required by law, to protect the service and its users, or to investigate abuse, security incidents, or requests for support.

04 · Control

Your choices

You can choose what to put into a project, manage team membership where the product allows it, and control notification scope using Chüng’s available settings: all activities, related activities only, or only the result.

You may request access to or correction of account information. You may also request deletion. A confirmed deletion request starts a durable deletion workflow; some operational records may be retained where necessary for security, legal, or audit obligations. The beta deletion workflow is approval-gated while it is being hardened.

05 · Care

Safety and retention

We use authentication, membership checks, server-side validation, optimistic version checks, transaction boundaries, signed file tickets, and audit records to protect the beta. No online service is completely secure, so do not use Chüng for information that requires a regulated or guaranteed environment.

We retain information for as long as needed to provide the service, resolve disputes, maintain security, complete deletion, and meet legal obligations. Retention periods will be made more specific in the final public policy.

06 · Help

Questions about this policy?

For beta questions or a privacy request, use the support channel provided with your Chüng beta invitation. This temporary page does not publish a separate support address yet.