WHAT WE COLLECT

With your permission through Google Health, we read Steps, Active Zone Minutes, sedentary duration, daily heart metrics needed for maximum heart rate, resting heart rate, and heart-rate variability, and sleep-session duration. We use a main sleep session ending on each local day to record whether that night fell in the 7–9 hour target; we do not retain raw sleep-session timelines.

We also store your Google subject identifier, verified email address, Google display name, optional battle alias, IANA time zone, squad memberships and roles, generated squad codes, application sessions and their security metadata (IP address and user-agent), and encrypted Google access credentials. We do not retain the beta invite code you enter at sign-in.

We do not collect location, contacts, nutrition, ECG, irregular-rhythm notifications, or any Google Health data outside the three readonly scopes used by the app. We use no advertising, analytics, or tracking tools. Cookies are limited to signed account sessions and short-lived public-board access sessions.

HOW WE USE IT

We use this data only to operate the visible Sweat Warfare features: pre-season comparison, current weekly standings, archived final results, and the shared battle board. We do not sell, rent, advertise with, train AI models on, or use health data for credit, insurance, employment, research, medical-device, or other unrelated purposes.

Choosing Continue with Google opens Google's consent flow for the listed readonly scopes. You may disconnect Google Health or delete your account at any time. Disconnecting stops new imports; deleting the account removes the data described below.

WHO CAN SEE IT

Signed-in members of your squad can see the health-derived values and standings for that squad. A person with that squad's code can also open its current public live board without signing in; that access lasts only until the round closes and does not expose the archive, Profile, or other squads. The same code can be used by a private-beta participant to join the squad. Squad codes are credentials: share them only with people you intend to give this access to.

Kalibr Pte. Ltd. and its hosting provider, Render, process the data only to run the service. We do not permit routine human review of health data. If a support request requires access to a particular person's data, we seek that person's specific permission first, except where access is necessary for security or required by law.

STORAGE AND SECURITY

Production data is hosted by Render in its Frankfurt, Germany region. Render is a service provider processing data on our behalf. We use HTTPS in transit, encrypt Google OAuth credentials at rest, restrict production-system access to the developer, and store only the normalized daily data needed for the battle features.

RETENTION AND DELETION

We retain account and battle data while your account exists so your squads can use the live board and archive. Deleting your account from Player File permanently deletes your Google connection, normalized health readings, pre-season imports, sessions, memberships, and your entries from squad-facing battle records. If your departure leaves a squad empty, that squad is deleted; otherwise ownership transfers to the longest-standing remaining member.

You may also request deletion at the contact address below. We will complete a verified request within 30 days. You can revoke Google access separately at myaccount.google.com/permissions; revocation stops new Google Health imports but does not itself delete existing app data.

YOUR RIGHTS AND CHILDREN

You can view your current data in the app, update your alias, disconnect Google Health, and delete your account. You can request a copy or correction of account information by email. If you are in the EU, you may also lodge a complaint with your local data-protection authority.

Sweat Warfare is not intended for anyone under 16. We do not knowingly collect data from children. Contact us if you believe a child has used the service and we will delete the account.

GOOGLE HEALTH POLICY

The use of information received from Google Health API and Developer Tools adheres to the Google Health API Developer and User Data Policy, including its Limited Use requirements, and the Google API Services User Data Policy.

We will update this policy's effective date when it changes. If a change would use health data in a new way, we will ask for consent before doing so.