Protection questions

It cannot, and it should not claim to. New domains appear constantly, a person may own several devices, and phones move between networks. Browsers can use their own encrypted DNS, and other VPN apps can displace a filter. A home-built blocker is best understood as friction on the devices and paths it covers. That friction is still valuable, because it creates a pause at the moment a decision is made. Combine it with payment blocks, operator self-exclusion and support, and list its gaps clearly. Scoping the app helps set those expectations early.

Start with the method your platform documents and supports for filtering, and with the device you use most. On a computer, a hosts file or a filtering DNS setting is a simple first layer to learn from. On a phone, the system's content filter or local VPN interface usually gives wider coverage across apps, at the cost of more permissions and background-task limits. A browser extension is easy to build but covers only one browser. The mechanism comparison sets out where each one acts and what it misses.

Only when that person is an adult who understands what the app does and has asked for it, or clearly agreed to it. Installing restrictions or monitoring on another adult's device without their knowledge damages trust and may break the law, depending on where you live and what the software records. Parents managing a child's device are in a different position, and platforms provide their own family controls for that purpose. If you are unsure about the legal side, speak to a qualified adviser; this is general information only.

Use domains reserved for testing and documentation, such as names under .test or .example, and serve a simple page from your own machine. Add those names to the blocklist and check whether the blocker stops them in different conditions: after a restart, on mobile data, with encrypted DNS turned on and so on. The mechanism does not care whether the domain belongs to a casino or a test page, so nothing is lost. The failure-testing checklist lists the conditions worth trying.

Yes, but slowly. A blocker with no exit tends to be uninstalled the first time it blocks something legitimate, and then nothing is protected. A good override is narrow, so it unblocks one domain rather than everything; delayed, so an urge has time to pass; and temporary, so the barrier returns on its own. Plain, calm wording during the process matters as much as the timer. The safeguards guide sets out an override path step by step.

As little as possible. A blocker can see which domains a person tries to reach, and that is sensitive. Keep the blocklist, settings and any history on the device, avoid analytics and advertising libraries, and never upload browsing data by default. If an accountability partner is used, share only the fact that a change was requested. Give the user a way to view, export and delete their local data. If you plan to publish the app, data protection law may apply, and qualified advice is worth getting.

Mobile operating systems limit background work to save battery. A filter service may be paused, restarted with a delay or stopped entirely, depending on the platform, the manufacturer's settings and the app's permissions. Use the background and network features the platform provides for filtering, follow its documented rules for long-running services, and check how the app behaves after long idle periods. Tell the user if a setting, such as excluding the app from battery optimisation, is needed, and show a clear status when the filter is not running.

Often, yes. Network filtering and device restriction features usually sit behind user-granted permissions, and some require developer programme membership, specific entitlements or review before an app can be distributed. Store policies for apps that handle network traffic also tend to be strict. The details differ between platforms and change over time, so read the current developer documentation and store guidelines for your platform before you design around a feature. For a personal build on your own device, the requirements are usually lighter.

Begin with your own list of the specific sites and apps that matter to you, because personal entries are often the most important. Community-maintained domain lists exist, but before using one, check its licence, how often it is maintained, how false positives are handled and whether it is too broad for your needs. Avoid scraping or crawling gambling sites to build a list, as that means interacting with them directly. Store whatever you use as versioned data, as described in the blocking layers notes.

Usually not. A blocker can reduce access in certain moments, but gambling harm often involves money worries, stress, mood and relationships, which software cannot address. Free and confidential help is available, and talking to someone is a reasonable step at any stage, not only in a crisis. In the UK, the National Gambling Helpline offers support, and a GP can explain NHS options. Family members affected by someone else's gambling can seek support too. Nothing on this site is personal, medical or professional advice.