Mute ("we", "us", "our") provides the iOS app Mute (the "App"). This policy explains how the App handles your information.

Last updated: September 6, 2026

1. Overview

The App uses Apple's Screen Time framework to make apps you choose unavailable during times you choose. We collect only what the App needs in order to work. We show no advertising, we do not use the advertising identifier (IDFA), and we never sell your information to anyone.

2. Screen Time data

This is the most important part of this policy, so it comes first.

Your usage history never leaves your device. We never send records of which apps you open, when you open them, or how long you use them to our servers. This is our policy, and it is also a constraint of iOS: Screen Time totals are computed and displayed only inside Apple's privacy boundary, and the App itself cannot read them as numbers.

The apps you choose to block are stored as opaque tokens issued by Apple. When you pick apps inside the App, iOS hands us a token that points at an app without telling us which app it is. We store these tokens, but as iOS works today, we cannot turn them back into app names. What we store is that block of bytes, and how many apps you selected.

We store them so that your rules and the apps they cover can be restored if you reinstall the App.

Some counts stay on your device only. How many times a shield appeared, how many rules you completed, and your session history are kept on the device and are never sent to us. If you delete the App and install it again, these counts start from zero.

3. Information we handle

Category What it is Where it is stored
Anonymous user ID An identifier the App issues automatically. It is not linked to your name, email address, or phone number Your device (Keychain) and our servers (Google Firebase)
Device information Device model, model identifier, iOS version, App version Our servers
Your settings Rule names, rule type (schedule or daily limit), times, days of the week, whether a rule is on, whether Lockout is on, the token identifying the apps a rule covers, and how many apps that is Your device and our servers
Setup answers The answers you give during first-run setup: what you want to change, how many apps, your occupation, what you are aiming for, your own estimate of your screen time, how you heard about the App, and the rule type you chose Our servers
Activity records Focus session start, end, and outcome; when an emergency pass was used and for which rule Your device and our servers
Usage statistics Screen views, taps, rule creation, edits and deletions, blocks starting and ending, and purchases started, completed, failed, or restored. These never include which apps you blocked Google Analytics for Firebase
Diagnostics Technical records produced when the App stops unexpectedly (where it happened, device state) Firebase Crashlytics
Information attached to statistics An identifier Google Analytics for Firebase assigns automatically (one per installation), and an approximate region inferred from your IP address. This is not your address or a precise location Google Analytics for Firebase
Purchase information Your subscription status (whether it is active, and which plan). We never receive your card number or other payment details RevenueCat and Apple
Ad attribution If you installed the App from an ad on the App Store (Apple Ads), the App sends an Apple-issued attribution token to RevenueCat and receives which ad campaign the install came from. This does not use the advertising identifier (IDFA) and is not used to track you RevenueCat and Apple

The App never asks you for your name, email address, postal address, phone number, or date of birth.

4. Why we handle it

  1. To provide the App's features — storing your rules, and restoring them when you reinstall the App
  2. To determine your subscription status and provide paid features
  3. To find and fix defects
  4. To understand, as statistics, which features are used and how much, in order to improve the App
  5. To measure our own advertising (which ads bring people who keep using the App)

5. Service providers