# How to redact personal data in Android screenshots: installing and setting up tuomin

> AI Release · @ai_release1 · https://ai-release.org/guides/kak-skryt-personalnye-dannye-na-skrinshotah-android-ust_en.html

## TL;DR

- **Time to complete:** about 15 minutes
- **Difficulty:** Basic
- **You need:** an Android phone with Developer options enabled, a data-capable USB cable, ADB (Android Debug Bridge — a command-line tool that lets a computer send commands to the phone), the tuomin app, and one test screen filled with fake personal data

## Requirements and setup
![Illustration: Requirements and setup](https://ai-release.org/guides/img/kak-skryt-personalnye-dannye-na-skrinshotah-android-ust-en-1.jpg?v=1794992107)


- **Phone:** any Android device that tuomin lists as supported. The minimum Android version is stated on the app's store listing — open the listing and read the "Requires" line before you start. If the listing does not state it, treat the version as unknown and check the app's documentation.
- **Computer:** Windows, macOS or Linux with `platform-tools` unpacked. Any current build of platform-tools works; you do not need Android Studio.
- **Cable:** a data cable, not a charge-only one. Charge-only cables are the most common reason `adb devices` shows nothing.
- **Free space:** at least twice the download size shown on the listing page, so the installer and the extracted files both fit.
- **Screen lock:** a PIN or pattern must be set, because you will test whether tuomin redacts lock-screen and notification previews.
- **Test data:** a note containing a fake name and a fake phone number, e.g. `Ivan Petrov, +1 555 0100`. Never test with your real contacts.

Checklist before you touch the phone:

- [ ] `adb version` runs on the computer and prints a line starting with `Android Debug Bridge version`
- [ ] Developer options and **USB debugging** are enabled on the phone
- [ ] The phone is unlocked and the "Allow USB debugging?" dialog was accepted
- [ ] The fake note from above exists on the phone
- [ ] The tuomin listing page is open so you can read its package name and minimum Android version

```bash
# macOS / Linux — verify platform-tools is on PATH
adb version
```

**Example:** the output begins with `Android Debug Bridge version` followed by a build number. If you instead see `bash: adb: command not found`, add the platform-tools folder to `PATH` or call `./adb` from inside it.

## Step 1. Install tuomin and read its package name

**What to do:** install tuomin from its official listing, then read the exact package name from the phone instead of guessing it.

**Why:** every later command in this guide is addressed to a package name. A wrong name produces `Error: Unknown package` and sends you chasing a permissions problem that does not exist.

**How to check:** connect the phone, confirm it is visible, then list only third-party packages.

```bash
adb devices
adb shell pm list packages -3 | grep -i tuomin
```

**Example:** `adb devices` prints two columns — the serial and the state. The state must be `device`, not `unauthorized` or `offline`. The second command prints one line such as `package:<vendor>.tuomin`; `<vendor>` is whatever prefix the developer used.

If `grep` returns nothing, the app is not installed under a name containing "tuomin". Cross-check the package name from the store URL — the part after `id=` in `https://play.google.com/store/apps/details?id=<vendor>.tuomin` is the package name. Store builds and sideloaded APK builds can differ here, so always trust `pm list packages` over the URL.

Write the value down as `<vendor>.tuomin`; every command below uses this placeholder and you must substitute your real value.

## Step 2. Grant media and notification access, then point tuomin at the screenshot folder
![Illustration: Step 2. Grant media and notification access, then point tuomin at the screenshot folder](https://ai-release.org/guides/img/kak-skryt-personalnye-dannye-na-skrinshotah-android-ust-en-2.jpg?v=1794992116)


**What to do:** grant the runtime permissions tuomin needs, confirm them, and make sure the app watches the folder your phone actually writes screenshots into.

**Why:** since Android 10, apps use *scoped storage* — each app sees only the media it was granted, not the whole filesystem. A redaction app that cannot read the screenshot simply shows an empty list, and a redaction app that cannot see notifications cannot redact their previews. Detection usually runs on the device, which is the same idea as [running an AI model locally on Android](https://ai-release.org/guides/kak-zapustit-ii-model-lokalno-na-android-prilozheniya-i.html?utm_source=tg&utm_medium=channel&utm_campaign=guide_inline&utm_content=guide_to_guide) — nothing leaves the phone, but only if the permissions are correct.

First, find the screenshot directory. It is **not** the same on every vendor:

```bash
adb shell ls -d /sdcard/DCIM/Screenshots /sdcard/Pictures/Screenshots 2>/dev/null
```

**Example:** a Pixel prints `/sdcard/Pictures/Screenshots`; several other vendors print `/sdcard/DCIM/Screenshots`. Whichever line appears is the folder to select inside tuomin.

Grant media read access non-interactively:

```bash
adb shell pm grant <vendor>.tuomin android.permission.READ_MEDIA_IMAGES
adb shell dumpsys package <vendor>.tuomin | grep -A 20 "runtime permissions"
```

**Example:** the `dumpsys` output contains a line `android.permission.READ_MEDIA_IMAGES: granted=true`. If the permission is not declared by the app at all, `pm grant` prints `Exception occurred while executing 'grant': java.lang.SecurityException: Package <vendor>.tuomin has not requested permission android.permission.READ_MEDIA_IMAGES` — that means the build uses a different permission model and you must follow its documentation rather than this command.

Then, in the app itself:

1. Open tuomin → settings → **screenshot folder / watch folder** (label wording varies by build; if you cannot find it, check the documentation) and select the path you confirmed above.
2. Enable the redaction style. A solid fill (black box) is safer than blur, because blur can sometimes be reversed by an attacker; a solid box destroys the pixels.
3. If tuomin offers notification redaction, enable it and grant notification access in **Settings → Apps → Special app access → Notification access**.

```bash
adb shell settings get secure enabled_notification_listeners
```

**Example:** the output lists components separated by `:` — your new entry appears as `<vendor>.tuomin/<vendor>.tuomin.NotificationListener`. If the list does not change after you toggle the switch, the grant failed and you should re-open the toggle.

## Step 3. Verify redaction with an OCR pass
![Illustration: Step 3. Verify redaction with an OCR pass](https://ai-release.org/guides/img/kak-skryt-personalnye-dannye-na-skrinshotah-android-ust-en-3.jpg?v=1794992123)


**What to do:** take a screenshot of the fake note, pull the file, and run OCR (optical character recognition — a tool that turns pixels back into text) over it. If OCR can still read the fake name or number, the redaction failed.

**Why:** this is the only check that proves the data is gone rather than merely covered. Looking at the image yourself confirms nothing about what a machine can extract from it.

Take the screenshot with the phone's hardware buttons, then pull the newest file:

```bash
adb shell ls -t /sdcard/Pictures/Screenshots | head -n 1
adb pull /sdcard/Pictures/Screenshots/<newest-file>.png ./after-redaction.png
tesseract ./after-redaction.png stdout
```

**Example:** `ls -t` prints the newest filename first, for instance `Screenshot_20240115-101500.png`; substitute that exact name into `adb pull`. `tesseract` then prints the text it recovered from the image.

Pass criteria — all four must hold:

- [ ] OCR output does not contain `+1 555 0100`
- [ ] OCR output does not contain `Ivan Petrov`
- [ ] the covered area is a solid fill, not a translucent overlay you can still read through
- [ ] the same two strings are also absent from the notification shade preview after you lock and unlock the phone

If OCR still returns the number, the app either processed a cached copy or your test image was never re-scanned. Delete the cached output file, take a fresh screenshot, and repeat the pull. Do not assume success from the app's own "done" toast.

## Troubleshooting

**Problem. The app lists no screenshots and the log shows a media permission failure**

- Error: `java.lang.SecurityException: Permission Denial: opening provider com.android.providers.media.MediaProvider ... requires android.permission.READ_MEDIA_IMAGES or android.permission.READ_MEDIA_VISUAL_USER_SELECTED`
- Cause: on recent Android versions the media permission has a "selected photos only" mode. If the user picked "Select photos and videos" during the first prompt, the app can read only the items chosen at that moment, and every new screenshot is invisible to it.
- Solution: revoke and re-grant with full access: `adb shell pm revoke <vendor>.tuomin android.permission.READ_MEDIA_IMAGES`, then re-grant it as shown in Step 2 and pick "Allow all" in the in-app prompt.

**Problem. ADB cannot see the phone**

- Error: `adb: device unauthorized. Please check the confirmation dialog on your device.` or `adb: no devices/emulators found`
- Cause: the RSA fingerprint prompt was dismissed, USB debugging was turned off, or the cable carries power only.
- Solution: run `adb kill-server && adb start-server`, unlock the phone, replug the cable, and accept the "Allow USB debugging?" dialog. Confirm with `adb devices`, which must show state `device`.

**Problem. New screenshots never appear inside tuomin**

- Error: no error text — the folder view stays empty while the gallery shows the new image.
- Cause: the app is watching a different directory than the one your vendor writes to.
- Solution: compare both candidate paths with the `ls -d` command from Step 2, then re-point the watch folder in tuomin's settings to the path that actually contains the file.

## Summary and next steps

Repeat the OCR check after every app update, because permission defaults and folder paths can change silently. If you also want your financial screenshots to stay off third-party clouds entirely, the same privacy logic applies to [self-hosting Actual Budget with Android sync](https://ai-release.org/guides/kak-vesti-semeynyy-byudzhet-na-svoem-servere-ustanovka.html?utm_source=tg&utm_medium=channel&utm_campaign=guide_inline&utm_content=guide_to_guide). 

## FAQ

**Does tuomin upload my screenshots to a server?**
This guide cannot verify that. The checkable method is empirical: enable airplane mode, take a test screenshot, and confirm redaction still happens — if it does, processing is on-device. Confirm the rest in the app's privacy policy.

**Which Android versions are supported?**
The minimum version is stated on tuomin's store listing. If the listing omits it, treat it as unknown and check the documentation before installing.

**Is blur good enough for hiding a phone number?**
No. Some blurs can be partially reversed; a solid black box destroys the pixels, so use solid fill where the app offers it.

**Can I redact a screenshot that already exists in the gallery?**
It depends on the build. Import the file through the app's picker and re-run the OCR check from Step 3 to confirm it worked.
