← Back to HushWall

Privacy Policy

HushWall · Last updated: June 29, 2026

Overview

HushWall is available on Android and iPhone, and is designed with privacy in mind. Your schedules, blocked-app lists, focus scores, and intervention history all stay on your device. We use two analytics providers — Mixpanel and Google (Firebase / Google Analytics) — to collect anonymous, aggregate usage analytics that help us understand how features are used, diagnose problems, and improve the app. This analytics data contains no personal information and is tied only to a randomly generated device identifier, never to your name, email, or any account (there are no user accounts and no cloud sync). On iPhone, for users in the European Economic Area, the United Kingdom, and Switzerland, analytics is collected only if you give your consent when you first set up the app; if you decline, no analytics data is collected and the app works exactly the same. The app also makes a periodic configuration check to a HushWall-controlled server to see if a new version is available.

Data Collection

HushWall does not collect personal information. HushWall collects anonymous usage analytics through Mixpanel and Google (Firebase / Google Analytics) to understand how the app is used and to improve it. On iPhone, in the European Economic Area, the United Kingdom, and Switzerland, this happens only with your consent (see above). This analytics includes:

  • Anonymous in-app events — for example onboarding steps reached, permissions granted, schedules created, and whether an intervention was completed or dismissed
  • Device and app information — such as device model and manufacturer, operating system and version (Android or iOS), app version, screen size, and network type; and on Android, the OEM software skin (e.g. One UI, MIUI, ColorOS) and mobile carrier
  • Approximate location — only your city, region, and country, derived from your IP address by our analytics providers. We do not collect GPS or precise location, and your IP address itself is not stored by us.
  • A randomly generated device identifier used to group events from the same install

We do not collect:

  • Your name, email address, phone number, or any account identifier
  • The advertising identifier (Android Advertising ID or Apple IDFA)
  • The content of your screen, messages, passwords, or browsing history
  • Which specific websites you visit (only that a block occurred)

HushWall also makes a periodic configuration check to a HushWall-controlled server to see if a new version is available. This request contains no body data and no identifiers; your IP address is unavoidably transmitted as part of any HTTPS connection but is not logged or used to identify you.

Permissions

HushWall requires certain device permissions to function, and these differ by platform. No data obtained through these permissions — including app usage, the list of installed apps, and anything read on Android by the Accessibility Service — is ever sent to our analytics providers or transmitted off your device. The analytics described above consists only of the anonymous in-app events and device information listed in the Data Collection section.

On Android

  • Usage Access (PACKAGE_USAGE_STATS)— Used to read which apps are currently in use so HushWall can detect when a blocked app is opened during a scheduled focus window, and to suggest blocking targets during onboarding based on weekly screen-time stats. This data is processed locally and never leaves your device.
  • Query All Packages (QUERY_ALL_PACKAGES)— Used to enumerate the apps installed on your device so you can choose which apps to block. The list of installed apps is processed locally and is never transmitted off your device.
  • Accessibility Service— Used for two purposes: (1) to detect when a blocked app is brought to the foreground so HushWall can show an intervention screen, and (2) to read the URL bar in supported browsers (Chrome, Firefox, Edge, Brave, Opera, Samsung Internet) to detect when a blocked website is opened. The service does not read passwords, form fields, messages, or any other on-screen content beyond the browser URL bar. No accessibility data is stored or transmitted.
  • Display Over Other Apps (SYSTEM_ALERT_WINDOW)— Used to show the block/intervention screen on top of blocked apps.
  • Foreground Service— Used to keep the blocking service running in the background so schedules remain active even when the app is closed.
  • Boot Completed— Used to restart the blocking service after your device reboots, so your schedules stay active.
  • Battery Optimization Exemption— Used to prevent Android from killing the background service, ensuring schedules remain reliable.
  • Notifications— Used to show a persistent notification when the blocking service is active, as required by Android for foreground services.
  • Internet— Used to send anonymous usage analytics to our analytics providers and to fetch configuration from a HushWall-controlled server.

On iPhone (iOS)

  • Screen Time (Family Controls)— Used to detect and block the apps and Safari websites you choose during a focus window, through Apple's own Screen Time system. Your selections are stored as opaque tokens provided by Apple — HushWall cannot see the names of the apps or the websites you pick, and this Screen Time data never leaves your device. Website blocking on iOS applies to Safari only. HushWall does not use an Accessibility Service, does not read your screen or any browser URL, and does not draw over other apps on iOS.
  • Notifications— Used to hand off from the block screen to an in-app intervention (a breath, a quote, or a short game) and for related focus reminders.

Data Storage

All data — including your schedules, blocked-app lists, focus scores, and intervention history — is stored locally on your device (in an on-device database on Android, and in on-device storage on iPhone). This data is not backed up to any cloud service and is deleted when you uninstall the app.

Third-Party Services

HushWall uses two analytics providers: Mixpanel and Google (Firebase / Google Analytics). They process the anonymous usage data described above on our behalf, to help us understand how the app is used and to measure the performance of our app and marketing in aggregate. We do not show ads inside HushWall, we do not use advertising SDKs that build a profile of you, and we never sell your personal data. You can read each provider's privacy policy here: mixpanel.com/legal/privacy-policy and policies.google.com/privacy.

Children's Privacy

HushWall does not collect personal information from anyone, including children under the age of 13. The anonymous analytics described above is not tied to any identity and is not used to profile or individually track users of any age.

Changes to This Policy

If we update this privacy policy, we will post the new version on this page with an updated date. Since HushWall does not collect any contact information, we cannot notify you directly of changes — please check this page periodically.

Contact

If you have any questions about this privacy policy, please contact us at [email protected].