Privacy Notice

1. Data controller

2. Data-processing principles of the current beta

• BrainFreeze is restricted to users aged 18 or older.
• No mandatory user account is required for the current beta.
• The user may enter a nickname; beta game data and history may primarily be stored locally on the device.
• The application does not use the camera, microphone, GPS or health sensors to automatically assess physical condition.
• No advertising profiling or personalised advertising is used.

3. Firebase Analytics

BrainFreeze may use Firebase Analytics to understand product operation and public beta usage. Analytics collection is disabled by default in the current beta design and is enabled only after the user's consent.

Custom Analytics events may include categories such as:

• application and session start;
• selected language and platform;
• steps and interruption points in the game flow;
• success or failure of result saving;
• retry, share, multiplayer and feedback usage signals;
• beta version, score version and technical campaign/cohort/wave labels.

BrainFreeze's own Analytics contract does not send exact CRI values, exact duration, exact intensity/pain values, nicknames, email addresses, phone numbers or other direct contact data. Where needed, categorized or bucketed technical values may be sent instead.

Firebase/Google may also process technical information required to provide the service, such as device, browser, operating system and application version data, under its own terms.

4. Local game data

The current beta may store nickname, game responses, results, history and statistical data locally on the device. A complete in-app data deletion function is not available in the current release. Local application data may also be affected by the application/site-data controls of the operating system or browser.

5. Feedback

The feedback feature may open an external Google Forms page. The user provides feedback data only if they open the external form and submit information. The handling of data entered in the form is also affected by Google's service and the current settings of the form.

6. Sharing

Result sharing may start after a user action. If content is shared to another application or social service, that third party's privacy rules apply.

7. Support/payment data

Payment functionality is not active in the current public beta release. If voluntary development support is introduced later, updated privacy information will be provided.

8. Retention

• Local game data: may remain on the device until removed by the user or the platform.
• Firebase Analytics: according to the current retention settings of the Firebase project. The exact retention value must be recorded in the final legal version.
• Contact/privacy correspondence: for as long as needed to handle the request and any related legal claims.

9. Withdrawal of consent

Analytics consent can be changed in the application's privacy/Analytics settings. Withdrawal does not affect processing that was lawful before withdrawal.

10. Data security

The operator seeks to limit access, use secure authentication, encrypted transmission, appropriate Firebase security settings and data minimisation. Absolute security of an internet service cannot be guaranteed.

11. Data subject rights

Subject to applicable data-protection law, users may request information, access, rectification, erasure or restriction, object to processing and, where applicable, request data portability. Consent may be withdrawn at any time.

Requests: cs.aisalessystem@gmail.com.

12. Complaints

The user may contact the controller, the competent data-protection supervisory authority or a court. Authority details and the final remedies section will be specified in the final lawyer-reviewed version.

13. Amendments

This notice may change when new features, SDKs, data flows, service providers, laws or platform requirements are introduced.