Take a break from gambling with a timed self‑exclusion you can’t pause or shorten. Once you start an exclusion, access to gambling sites and related services is blocked until the timer ends.

How it works

Uses Android’s on‑device VPN (VpnService) to enforce device‑wide blocking locally on your phone. Filtering happens on‑device; no traffic is routed to external servers.
Runs as an ongoing foreground service with a clear, persistent notification while the exclusion is active.
Starts immediately after you confirm and stays active until the timer expires. Only one VPN‑based app can be active at a time on Android.
Controls

You can’t pause, restart, or shorten an active exclusion. To end the block, wait for the selected time to expire.
Exact timing is used to end the exclusion at the time you chose.
Privacy

No browsing traffic is sent to external servers for analysis.
The app does not access your location, camera, or microphone.
Notes and limitations

Blocking focuses on gambling domains from a maintained blocklist. New sites appear frequently; effectiveness can vary.
On Android 13+, you may need to allow notifications so the ongoing service notification can be shown.
This tool supports healthier habits but can’t guarantee every source is blocked. Consider combining it with your device’s other restriction features.

GamblePause uses Android's AccessibilityService API to support users in voluntary self-exclusion from gambling. Its primary function is to monitor the foreground app in real time and detect when a known gambling or betting app is launched during an active exclusion session, immediately returning the user to the home screen to enforce the block the user configured. As a secondary, opt-in safeguard, the same detection recognizes when the user navigates to GamblePause's own uninstall or force-stop screen while an exclusion session is active, and applies the same home-screen redirect, to help the user follow through on a commitment they set for themselves. This behavior is disabled outside of active exclusion sessions and is presented to the user as an optional toggle with in-app disclosure before being enabled. No data is collected, stored, or transmitted; all detection is local and momentary.