Privacy Policy

Last updated: 27 October 2026

What the app processes

Notifications from other apps

For Removication to hide a notification, the operating system has to show it to the app. That is what the notification access permission in the Android settings is for. Without it the app has no function.

The following is processed:

• which app sent the notification
• title, text and sub-text of the notification
• for chat notifications, the name of the sender
• the notification category (“channel”) assigned by the sending app
• the time it arrived

Only what was actually hidden gets stored. Notifications that are let through are processed in memory and immediately forgotten.

Hidden notifications go to the Notification Catcher, a list inside the app. In the free version entries are deleted automatically after 24 hours; with Premium after the retention period you set (30 days by default). You can delete any entry, or the whole list, at any time.

What the app learns about your apps

Removication remembers which notification categories your apps use and how often they send. This serves two purposes: the app picker can sort by actual frequency, and you can target rules at individual categories. Only the label and a count are stored — no content.

What the app cannot see

From Android 15 onwards, the operating system marks notifications containing verification codes and one-time passwords as sensitive. Apps like Removication never receive their content. Banking TANs and login codes are technically unreadable to the app.

Advertising (free version only)

The free version shows a banner at the bottom, delivered by Google AdMob. Google processes device identifiers (including the advertising ID), technical details about the device and the IP address in order to select ads, measure their delivery and detect fraud. That data goes to Google and, where applicable, to its advertising partners; Google’s own privacy policy applies in addition to this one.

The ad component never sees your notifications. It runs in the user interface, not in the part of the app that processes notifications. Title, text, sender and the contents of the Notification Catcher are never handed to it.

Consent: Before the first ad, a form asks whether personalised advertising is allowed. The legal basis is your consent (Art. 6(1)(a) GDPR). You can change or withdraw it at any time under Settings → “Ad settings”. Without consent you will see non-personalised ads at most.

Premium switches advertising off entirely. The ad library is then never started, no form appears, and no request goes out to the network.

Sharing with third parties

Apart from advertising there is none. The app includes no analytics and creates no user accounts. Notification content is never transmitted — in neither the free nor the Premium version.

In addition there is the purchase of the Premium version, which runs through Google Play Billing. Removication only learns whether a valid purchase exists. Payment processing lies entirely with Google, under Google’s own privacy policy.

Permissions and what they are for

Permission	Purpose
Notification access	Core function — nothing can be hidden without it
Post notifications	Solely for the neutral placeholder in censor mode
Query installed apps	To populate the app picker
Google Play Billing	Purchase and restore of the Premium version
Internet	solely for advertising in the free version
Network state	part of the ad library: checks whether a connection exists at all
Advertising ID	the resettable identifier Google uses to select and bill ads

The last three come with Google’s ad library. They are present in the Premium package too — Android requires the declaration for the whole app — but go unused there, because the library is never started.

The app requests no permission for location, contacts, camera, microphone or storage. The internet permission serves advertising alone; hiding notifications neither needs nor uses it.

App lock (Premium)

Turning on the app lock means choosing a four-digit code. The app stores that code nowhere. It keeps only a kind of fingerprint of it — a string the code cannot be recovered from. To unlock, it checks whether the code you typed produces the same fingerprint. Anyone reading out the app’s storage will not find the code there.

The code never leaves the device. It protects sets and the Notification Catcher inside the app, and has nothing to do with your phone’s screen lock.

Backup and changing devices

The app’s database is excluded from Android cloud backup and from device-to-device transfer. When you move to a new device you have to create your sets and rules again — a deliberate decision: notification content does not belong in a backup you hand over.

Deletion

All data lives in the app’s private storage. It is deleted completely when you uninstall the app or clear its storage in the Android settings.

Your rights

No data is transmitted to us — we run no server and hold nothing about you. Access, rectification and erasure under the GDPR are therefore exercised directly on your device: the Notification Catcher can be emptied, the app uninstalled.

For the advertising data of the free version, Google is the recipient. You can change or withdraw your consent at any time under Settings → “Ad settings”, and you can reset your device’s advertising ID in the Android settings. For any questions, reach us at the address below.

Changes

Material changes will be announced in the app and in the Play Store listing. This page carries the date of the current version at the top.

This website

This site sets no cookies, loads no fonts or scripts from third-party servers and measures nothing — which is also why there is no cookie banner. When a page is requested, the host GitHub Pages (GitHub, Inc.) processes technically necessary connection data (IP address, timestamp, file requested) in order to deliver the page and defend against attacks. The legal basis is Art. 6(1)(f) GDPR.

Data controller

Gideon Hoja — Nice Developments
Maschstraße 36
38114 Braunschweig
Germany

Email: verynicedevelopments@gmail.com