What the app may access
FocusForge uses Android Accessibility to detect the foreground app so selected app rules can be enforced. In supported browsers, it may also process visible browser text that looks like a domain or URL so exact website blocking can work.
Outside that blocking flow, FocusForge is not intended to capture passwords, analyze messages, record media, or perform general-purpose screen recording. It does not use Accessibility to build advertising profiles.
Usage Access is optional. If enabled, FocusForge can read Android app-usage duration statistics for app-time insights, projections, and related in-app summaries.
To help users choose what to protect, FocusForge may also read locally available app metadata such as launchable package names and app labels on the device.
What stays on the device by default
FocusForge is local-first by default. Blocking rules, website rules, schedules, blocked attempts, session activity, progression state, recent events, and most settings remain on the device unless the user signs in and enables cloud-backed features.
The app may also store local setup data such as birthdate or age-derived configuration used for onboarding defaults, age-appropriate protections, and account-mode behavior.
What may sync if cloud features are used
If a user signs in or enables cloud-backed features, FocusForge may sync account and service data through configured Firebase services.
- Account and auth data such as email address, username, display name, account role, verification status, and sign-in provider.
- Subscription and entitlement data such as tier, billing product identifiers, shared seat state, and related account eligibility.
- Optional social, accountability, and family data such as friends, partner relationships, public profile settings, journal posts, comments, direct messages, leaderboard entries, linked parent-child records, and remote child control rules.
- Device and notification routing data such as installation ID, push token, app version, notification status, and whether protections like Accessibility or device-admin based tamper controls are active.
- Optional media chosen by the user such as custom profile photos, custom block-screen media, or custom block sounds when those features are synced.
Diagnostics and reliability
If backend services are active in the app build, FocusForge may send crash reports and ANR diagnostics to Firebase Crashlytics so stability problems can be fixed.
Those reports may include technical context such as app version, build type, backend mode, subscription tier, auth provider, and whether the account is local or remote. Crash diagnostics are separate from the in-app product analytics toggle.
Who processes data
FocusForge does not sell personal data. Data is shared only with the providers needed to run the features the user chooses.
- Firebase, for sign-in, cloud database storage, optional file storage, push notifications, and crash diagnostics.
- Google Play, for subscription billing, renewals, and subscription management.
- Authorities or other parties where disclosure is required by law, to respond to legal process, or to protect users, the service, or the public.
User controls and deletion
Users can revoke Accessibility, Usage Access, notification permission, and other Android-level permissions in device settings at any time.
The in-app Privacy screen includes local export and local deletion controls, along with cloud sync settings and account-deletion guidance. Cloud-backed deletion requests are handled through the Delete Account page and support email. Canceling a subscription is separate and must be managed through Google Play when Google Play billing is used.
On-device data remains until the user deletes it, clears app storage, or uninstalls the app. Cloud-backed records are retained only as long as needed to operate the requested features, comply with law, resolve disputes, prevent abuse, or support legitimate billing and security workflows.