Learn · Try · Make it yours
Permissions
You selected an app, started a block, and it still opens. Check what the feature needs before changing your whole setup.
New to Appcognito? Learn where the main screens are and what the terms mean.
Understand the idea
Test one thing at a time
Selecting an app tells Appcognito what to block. Device permission lets the blocking feature do its job. Keep one test block active, confirm that your app or site is selected, then review the permissions for that feature on your platform.
The key ideaApp blocking and website filtering use different access. Follow the checklist for the feature that is failing.
02 · Make it work on your phone
Check the access a block needs
Your setup
Before you beginStart a short test block for one selected app or website first. Permissions are device approvals that let Appcognito carry out that block.
- Inside Appcognito, open Settings → App settings → Permissions. Use this checklist to open the relevant Android settings.
- For an app-opening block, allow Usage access so Appcognito can detect the app in use, and Display over other apps so it can show the blocking screen. Return to Appcognito after each approval.
- For websites, approve the local VPN filter when requested. This is the device configuration Appcognito uses to filter the sites you select.
- Complete any extra requests for your chosen rule. For example, a location rule needs location access. Return to Appcognito and keep the test block active.
Check it workedOpen the same selected app or website while its block is active. The app should show a blocking screen, or the website should fail to load.
Need help or want to undo?
If the selection still opens, check that the test is active now and includes it. For an app-opening block, also check the Block opening effect; a report permission alone does not start a block.
You can revoke an approval in Android Settings. Features that depend on that access may stop working.
Explore the full referenceMore options, feature details and answers
Only what you use
There is no checklist to clear before the app works. Each ask comes from what the rule you just built actually does.
- A charging rule never mentions alarms. Nothing about it is clock-driven.
- A rule that only cuts internet never mentions the accessibility service.
- A block list with no keywords in it never mentions screen reading.
The trade-off is that you meet permissions gradually. To see them all at once, open Settings, Block settings, Permissions, which lists every one and lets you switch things on early.
The blocking permissions
| Permission | Shown as | What it does | Needed for |
|---|---|---|---|
| VPN | Block apps and sites | Filters traffic on your device so blocked sites do not load and blocked apps get no internet. | Internet blocking and all website blocking. |
| Display over other apps | Block apps you pick | Draws the block screen over a blocked app when you open it. | App blocking, with Usage access. |
| Usage access | App usage | Notices when a blocked app opens, and measures how long apps and the screen are used. | App blocking, plus usage, screen time and open limit triggers. |
| Alarms and reminders | On-time blocking | Wakes the app at the exact moment a block should start or lift. | Clock-driven rules. Without it, blocks run up to ten minutes late. |
| Battery | Run in the background | Stops Android killing the background work that runs your rules. | Every rule, since they all run with the app closed. |
What a trigger needs
Only ever asked for by the rule using it, when you enable it.
| Permission | Used by | Why |
|---|---|---|
| Location | Wi-Fi and Location | Android hides the Wi-Fi network name behind location permission. Allow all the time lets both survive a reboot. |
| Calendar, read only | Meetings | Reads timed events from your phone's calendar. Nothing is written. |
| Physical activity | Movement | Tells walking from running from driving, on device. |
| Nearby devices | Bluetooth | Sees which Bluetooth device is connected, usually your car. |
| Accessibility | Off topic | Reads on-screen text to tell studying from drifting. |
| Accessibility | Tabs | Sees which tab an app is on, so only Shorts or Reels are stopped. Nothing is saved or sent. |
Optional and Pro
| Permission | For |
|---|---|
| Notifications | Blocking alerts, habit reminders, and the small notice while blocking is on. |
| Camera | Scanning your QR tags and a parent's QR code. No photo is taken, and nothing else uses the camera. |
| NFC | NFC tags only. Granted at install, so you are never asked. |
| Device admin | Uninstall protection. Survives a restart. Pro. |
| Accessibility | Keyword blocking. Recommended, not required. See below. |
NFC and tag scanning only matter if you use tags.
Permanently deny a permission and Android stops showing its dialog. Appcognito notices and sends you to the right page in system settings, instead of leaving you tapping a dead Allow button.
About Accessibility
This is the one people are most wary of. Fair enough, so here is exactly where it stands.
App blocking no longer uses it
It used to, because the service was the only way to notice a blocked app opening. That made a screen reader mandatory for the app's core feature, and it had a real cost: banking and payment apps in several regions refuse to run while an accessibility service is on. Blocking your distractions could break your banking.
App blocking now runs on two ordinary permissions instead, the overlay and usage access. Neither is visible to the apps being blocked.
What it is still used for
Off topic guard Required
Its whole job is reading the screen to tell studying from drifting. Without the service it cannot fire at all, so it is not offered without it.
Keyword blocking Recommended
Catching a word needs screen text. But a block list is apps plus sites plus words, and many people want the first two only. So this never blocks you from saving. Apps and sites block anyway, and keywords start working the day you turn the service on.
What happens to what it reads
On-screen text is matched against your own keyword list, in memory, on your phone. Not stored, not logged, not sent. There is no account and no server to send it to.
About the VPN
Android shows a key icon whenever a VPN is active, and Appcognito's filter uses that API, so you will see it while blocking is on.
It is a local filter, not a tunnel. Nothing goes to a remote server, nothing is decrypted, nothing is logged. It exists so a blocked domain can be dropped before it loads, in every browser at once.
If one gets switched off
Android sometimes revokes special access on its own, usually after an OS update or an aggressive battery optimiser. Rather than letting your blocks silently stop working, Appcognito tells you. It names the exact one that is missing and says plainly that blocked apps can be opened again until you turn it back on.
Settings, Block settings, Permissions shows how many are on, and every row can be fixed from there.
New to Appcognito? Learn where the main screens are and what the terms mean.
Understand the idea
Test one thing at a time
Selecting an app tells Appcognito what to block. Device permission lets the blocking feature do its job. Keep one test block active, confirm that your app or site is selected, then review the permissions for that feature on your platform.
The key ideaApp blocking and website filtering use different access. Follow the checklist for the feature that is failing.
02 · Make it work on your phone
Check the access an iOS block needs
Your setup
Before you beginKeep a short block active for one selected app or site. Screen Time is Apple’s approval for restricting selected apps.
- Inside Appcognito, open Settings → App settings → Permissions.
- For apps, allow Screen Time and check the list’s selections in Apple’s picker—the system app-selection window.
- For websites, approve the site filter. For keyword filtering, enable the Safari extensions following the checklist; keywords are checked in Safari.
- If your rule asks for Set up in Shortcuts, follow its instructions in Apple’s Shortcuts app. Return to Appcognito, confirm setup and enable the rule.
Check it workedOpen a selected app: Apple’s blocking screen should appear. Test a selected website in a browser, and keyword filtering in Safari. Only test features you have actually selected and enabled.
Need help or want to undo?
Check the active time, app selections and approvals. For rules that use Shortcuts, test both the event that starts the block and the event that stops it.
You can revoke access in iOS Settings. Any feature that depends on that access may stop working.
Explore the full referenceMore options, feature details and answers
Blocking permissions on iOS
| Permission | Why it is needed |
|---|---|
| Screen Time | Choose apps, show Apple’s blocking screen when they are restricted, and enable supported usage monitoring and reports. |
| Site filter / VPN configuration | Block selected domains locally across the device. |
| Safari extensions | Apply keyword filtering in Safari. |
The local site filter is not a remote VPN service. It handles domain lookups and does not route all your traffic through Appcognito’s servers.
Feature-specific access
- Notifications: reminders and alerts.
- Location: place rules; background behavior depends on the authorization granted.
- Calendar: rules based on calendar events.
- Camera: scanning QR codes in the app.
- NFC: interactive scan sessions on supported hardware.
- iCloud: backup uses the Apple Account signed in on the device.
iOS does not use Android’s Usage access, Display over other apps, exact-alarm, battery-exemption or Accessibility-service setup.
If access is denied or revoked
Open Appcognito’s permissions checklist in Settings, then follow the relevant system-settings instructions. Recheck Screen Time and your app selections for app blocks, the local filter for sites, and Safari extensions for keywords. Shortcuts automations must also remain enabled.
Approving one permission does not approve the others. A backup restore does not restore system permissions.