Privacy policy

Local filtering

On Android, bouncy uses a local VPN interface to block traffic from apps you select. It does not send your internet traffic through a PENTAGHOST VPN server. On Windows, filtering uses Windows Filtering Platform rules on your computer.

Your installed-app list, blocking rules, profiles, and app usage statistics are used on your device. The app does not upload those lists, statistics, browsing history, packet contents, or DNS queries to our backend. Android app backups are disabled in this release.

Optional Android online services

Before making online requests, the Android app asks whether you want to enable online services. If you agree, it sends a hashed device identifier derived from Android ID and the app package, device manufacturer/model, Android version, and app version to our backend. The hash is a persistent device identifier, not anonymous data.

We use this information to register your device, provide a trial, associate payments with your device, and verify or restore your subscription. Registration and access checks record first-seen and last-seen times. Subscription records contain the plan, expiry, platform, and associated transaction references.

You can choose Continue offline or change your choice in Account → Privacy & online services. Offline mode stops new backend and update requests and keeps free controls and any valid saved license available. Trials, payments, subscription refresh, and automatic update checks require online services. Turning online services off does not erase records already held by the backend.

This consent choice is provided by the Android app. The Windows client also registers device and license details when using its online licensing features.

Payments

If you initiate a mobile-money payment, we process your phone number, MTN or Airtel selection, chosen plan, amount, payment status, and transaction references. This data goes to our backend and Yo! Uganda, which communicates with the selected mobile-money network. bouncy does not request or store your mobile-money PIN.

Updates and permissions

With Android online services enabled, bouncy checks our website for version information. You choose whether to download an update and approve installation through Android. Before offering installation, the app checks the official HTTPS download source, file checksum, package name, version, and signing certificate.

VPN access is used for filtering. Installed-app visibility lets you choose apps to block. Optional usage access supports local usage displays. Notifications show filtering and update status. Battery-optimization exemption supports background filtering. Installation permission allows you to install a downloaded update. You control these permissions in Android settings.

Website and service providers

Our backend uses Supabase for device, subscription, payment, and download-event records. The website and backend are hosted using Vercel. These services and their infrastructure providers receive IP addresses and standard connection/request information when you connect; operational logs may contain that information.

The landing page uses ipapi.co to determine a country from your IP address and choose regional content. APK download clicks are counted by our backend with the platform and event time. These website events do not contain your app usage or filtering rules.

Google Analytics loads only if you accept optional website analytics. It uses cookies and connection/device information to measure website use. You can refuse analytics or change your choice using Analytics preferences. Essential preferences are saved in your browser. Opening this website from the app makes a separate browser connection.

Storage and your choices

Network requests use HTTPS. Android stores access tokens in encrypted preferences when the device keystore is available; a private, unencrypted preference fallback exists if the keystore is unavailable. Filtering preferences and usage records are stored locally. Device, subscription, and payment records are retained to operate licensing, restore access, investigate payment issues, and maintain transaction records.

You can revoke Android permissions, stop filtering, disable online services, and clear the app's local data or uninstall it. Clearing local data does not delete backend device, subscription, or payment records. Re-enabling online services can reconnect your device with those records.