Privacy Policy

Built to protect attention, not collect your life.

Last updated: May 2026

GameBrek is designed to be local-first. Core focus protection, app selection, session controls, and on-device guidance are built to run on your device.

Local-first protection No personal sign-in required for core use Accessibility used only for protection Early release email only if you submit it

What stays on your device

Protected apps, session settings, active session state, local session history, blocked attempt events, and recommendation signals are processed on your device for the core experience.

What may be uploaded

Where backend telemetry is enabled, GameBrek may upload limited processed session-level telemetry for reliability, diagnostics, and model evaluation readiness.

What we do not intend to collect

GameBrek is not designed to read messages, passwords, keystrokes, screen text, contact content, precise location, or personal content from other apps.

1. Who we are

GameBrek is a digital wellbeing and focus app designed to help users manage access to mobile games and other distracting apps during intentional focus sessions.

GameBrek is currently operated by Md Abir Hossain. In this Privacy Policy, “GameBrek”, “we”, “us”, and “our” refer to the current operator of the GameBrek app and related services.

2. What GameBrek does

GameBrek lets users create focus sessions, choose protected apps, and receive protective prompts or interventions when a protected app is opened during an active session. It may also provide on-device duration or mode guidance based on local behavioural patterns.

3. Permissions we use

Accessibility Service

GameBrek uses Android’s Accessibility Service to detect when a protected app is opened so it can present a focus prompt or intervention during an active session.

GameBrek is designed to use accessibility only for protection and intervention functionality. It is not intended to read screen content, keystrokes, passwords, personal messages, or other text entered by you.

Usage Access

GameBrek may use Usage Access as a secondary signal to improve foreground app detection and maintain more reliable protection behaviour on some devices.

Notifications and battery settings

GameBrek may request notification permission for session reminders and status updates. It may request battery optimisation exemption so protection remains more reliable during active sessions.

4. Information processed on your device

GameBrek stores and processes local app data including protected and essential app selections, focus session settings, active session state, session history, blocked attempt events, recovery-related events, emergency unlock events, local recommendation signals, and diagnostic state used to monitor protection reliability.

This local-first design means core runtime behaviour does not depend on constant server access.

5. Information that may be uploaded

Where backend telemetry is enabled, GameBrek may upload limited processed session-level telemetry to secure backend services. This may include selected duration, actual protected minutes, completion outcome, blocked attempt count, session mode, recommendation metadata, model and feature version metadata, threshold and sync version metadata, a pseudonymous backend identifier, and limited backend sync or diagnostic status information.

GameBrek is designed not to upload raw accessibility event streams, screen text, keystrokes, passwords, personal messages, contact content, or unnecessary fine-grained content from other apps.

6. Early release email signups

If you choose to join the early release list on this website, we collect the email address you provide, the signup source, consent version, signup status, and timestamps. We use this only to send occasional GameBrek launch or early access updates.

You can ask to be removed from the early release list at any time by emailing [email protected].

7. What we do not intend to collect

GameBrek is not designed to collect your name, phone number, contact list, personal messages, email content, typed text, passwords, payment card details, financial account credentials, camera content, microphone content, photo library content, precise location data, advertising identifiers for ad targeting, or raw screen content from the apps you use. The website only collects your email address if you choose to submit the early release form.

We do not sell personal data or sensitive user data.

8. On-device guidance

GameBrek uses an on-device model to support session recommendations. The model is packaged with the app and runs locally on your device. Where backend telemetry is enabled, uploaded data is used to support diagnostics, evaluation, and retraining readiness rather than moving live inference off your device.

9. Service providers

GameBrek may use third-party infrastructure providers to operate secure backend functionality. These may include Firebase Authentication, Cloud Firestore, Firebase App Check, and Firebase Crashlytics. Depending on the service used, permitted telemetry may be processed in countries outside your own, with appropriate safeguards where required.

10. Data retention, deletion, and your choices

Local app data remains on your device until you delete it, clear app storage, or uninstall the app. To remove local app data, use Android Settings → Apps → GameBrek → Storage → Clear Data, or uninstall GameBrek.

If backend telemetry has been enabled and uploaded, or if you submitted an early release email, you may contact us to request deletion of uploaded telemetry or early release signup information associated with you, subject to any legal, security, fraud-prevention, or record-keeping obligations.

Depending on where you live, you may have rights to request access, correction, deletion, restriction, objection, or withdrawal of consent for certain processing.

11. Contact

If you have questions about this Privacy Policy or GameBrek’s data practices, email [email protected].