Blokkere Privacy Policy

Last updated: October 20, 2026

This policy describes the Blokkere Android app, package com.blokkere, with app open ads provided by Google AdMob and no in-app feedback form. Blocking features do not require a Blokkere account.

Your blocking rules

Blokkere uses the names and identifiers of selected apps, websites, keywords, group names, schedules, days, time limits, and network conditions to enforce the rules you configure.

The app list is retrieved on your device. Rules and usage counts are saved in the app's private storage. You don't need to register an account to set up blocks, and rules aren't synced with a Blokkere server. Android backup and device transfer are described below.

Identifying apps and websites

With your permission, usage access identifies the app in the foreground. For website and keyword rules, the accessibility service reads window information and the address bar of supported browsers, including while you use other apps. A foreground service runs the blocking monitor with a status notification while groups are enabled.

URLs may contain searches and personal information. Addresses are compared with your websites and keywords on your device: observed addresses aren't saved or sent to servers. Screen time mode stores group identifiers and their daily durations, without a URL history.

This feature doesn't capture screenshots or read messages or passwords. In Chrome, it may replace a blocked address with a blank page in the same tab; this doesn't prevent a connection that has already started. Identification depends on supported browsers. When you close the blocking screen, accessibility lets you return to the home screen.

Permissions and your control

Accessibility: identify websites and keywords in URLs and return to the home screen. Not required for app-only blocking. Before opening Android settings, Blokkere explains this access and asks for your agreement. You can turn off the service at any time in Android settings.

Usage access: identify open apps and measure usage while the monitor is running. The count resets daily and doesn't include usage before the monitor was enabled.

Display over other apps: show the blocking screen over other apps.

Network and Wi-Fi: check the connection type and network name for Network mode. Android may require precise location permission and location to be turned on to read the Wi-Fi name. Blokkere doesn't access coordinates or track your geographical location; you can also enter the network name yourself.

Battery: removing background restrictions is optional and helps keep the monitor available. You can deny or revoke permissions in Android settings, but the corresponding feature may stop working.

Notifications: with your permission when required by Android, Blokkere shows a silent summary of enabled groups and selected apps when you leave the app, plus a few reminders during the day while your phone is in use. It uses no sound, vibration, or alarms. The summary is generated on your device, without sending names or rules to servers. Details are marked private on the lock screen, respecting Android settings. You can dismiss or disable these notifications without turning off your blocks.

Optional review invitation

The app stores the blocking-screen dismissal count and your response to the optional review invitation on your device to control when it appears and stop further invitations once answered. No response is sent to Firebase or a Blokkere server. Love it opens Google Play; leaving a review is optional and handled by Google Play. Blokkere does not know whether you post a review.

Google Play purchases

Payments are processed by Google Play. Blokkere checks products and purchases on the store account, verifies the receipt's digital signature, and acknowledges the purchase. It doesn't receive full card details or ask for your Google account password.

Receipts and purchase tokens are used in memory by the store integration, without being sent to our own server or included in rule storage. Premium access is checked again when you open the app. Rules and observed URLs aren't sent to process payments.

Storage, backup, and deletion

You can remove groups and rules from their respective screens. Daily usage tracking removes references to deleted time groups in the monitor's next cycle. Clearing app data removes local content and the accessibility authorization recorded by Blokkere.

Android automatic backup and device-to-device transfer are enabled. Rules, preferences, and other eligible private data may be copied or restored by the system, depending on your settings and Android version. Local accessibility authorization is excluded from backup and transfer. Blokkere doesn't control the retention or deletion of copies kept by the system.

Deleting data on your device does not delete Android backups, Google Play purchase records, or statistics and diagnostics already sent. External services follow their own retention and security terms.

Statistics and diagnostics

In production releases, Blokkere uses Firebase Analytics to measure sessions and visits to modes, plans, and information screens. The service processes installation identifiers, usage events, and technical information about the app and device. In Firebase Analytics, advertising identifier collection and ad personalization signals are disabled.

Firebase Crashlytics receives crash and app-not-responding reports, including stack traces, app version, device characteristics, technical identifiers, and the area of the main navigation.

Events and logs added by Blokkere do not include group names, selected apps, websites, keywords, network names, observed URLs, satisfaction responses, or purchase receipts. Automatic crash reports may include technical exception messages. Google/Firebase processes the data, potentially outside Brazil; retention follows those services' settings and terms. Clearing app data does not delete records already sent.

Advertising and privacy choices

Blokkere displays app open ads with Google AdMob. The SDK collects and shares with Google IP addresses, device and advertising identifiers, ad interactions, and technical data for ad delivery, measurement, and fraud prevention, subject to your privacy choices and applicable settings.

The IP address may be used to estimate the approximate location of the device. Blokkere does not send group names, selected apps, websites, keywords, networks, or observed URLs for advertising.

Google presents consent options when required; you can revisit them on the privacy screen. Analytics advertising identifier collection and ad personalization signals remain disabled. Debug builds use test ads. For questions about your data, use the contact in this policy.

Responsibility, rights, and updates

Blokkere is responsible for the app and for processing data for the purposes described in this policy.

For privacy questions and requests about your data, email contact@blokkere.com.

We assess requests under applicable law and may ask for the information necessary to locate the data and verify the request, without asking for passwords.

Depending on applicable law, you may request information about personal data processing, access, correction, and deletion, and exercise other rights. Android permissions can be revoked at any time. Reading this policy doesn't authorize the accessibility service or replace your specific agreement.

Material changes to this policy will have a new update date and will be communicated in the app when applicable.

Security and external services

Communications with Google services use encrypted connections in transit. Local data is kept in app-private storage, subject to Android controls and the backup described above. We do not sell personal data.

Google processes service data under its applicable policies and terms. Support may also receive information you choose to send by email.