Privacy Kit

byChar0n · Root & System

Verified safeOpen sourceExclusive

Download APK

—

No reviews reviews

downloads

8.0

android

AI summary

LSPosed module for per-app Android identifier spoofing, letting you assign controlled fake identities to individual apps to reduce cross-app tracking. Version 2.0.5 fixes a sandbox fingerprinting leak where containerized apps could detect Privacy Kit and list your other isolated apps, migrates containers to hashed folder names, and preserves sessions through atomic moves.

Generated by AI. May contain inaccuracies.

About this app

Privacy Kit is an LSPosed module for per-app Android identifier spoofing.

It is designed for users who want more control over the identifiers that apps can read from their device. Instead of changing identifiers globally, Privacy Kit lets you manage spoofed values on an app-by-app basis so each selected app can receive its own controlled identity.

What Privacy Kit Does

Privacy Kit hooks supported Android identifier access paths through LSPosed and returns configured spoofed values to selected apps. This can help separate app profiles, reduce cross-app tracking based on stable identifiers, and test how apps behave when device identity values are changed.

This module does not make a device anonymous by itself. Apps can still use many other signals, including account login, IP address, network metadata, browser state, app-specific storage, sensors, permissions, and server-side behavior.

Key Features

- Per-app identifier spoofing for selected target apps. - LSPosed/Xposed module integration. - One-tap AI Auto Profile and Maximum Privacy profile flows. - Isolated browser account sessions using Android System WebView on supported Android versions. - Hotfix WebView compatibility for commerce, checkout, login, and payment flows in release 7-1.6. - Live in-process updates (as of release 10-1.8) so location, Build fields, and identifier changes apply to an already-running target app without a relaunch. - Region Preset, per-app walk/jog and drive Activity Simulation scheduling, saved Favorite Locations, and a map-based coordinate picker for location spoofing (as of release 10-1.8). - Hook Diagnostics, an in-app hook log viewer, and history views for troubleshooting LSPosed scope, profile, and hook activity. - Package name: com.sal.privacykit. - Release-only public repository for LSPosed distribution. - Official APK releases published through GitHub Releases. - Public checksum information for release verification.

Requirements

- Android device with root access. - Magisk or another supported root environment. - LSPosed installed and working. - A compatible Android version for your LSPosed setup. - Basic understanding of Xposed module behavior and app compatibility risks.

Enabling the Module in LSPosed

1. Open the LSPosed manager app. 2. Go to the Modules section. 3. Select Privacy Kit. 4. Enable the module. 5. Select the apps you want Privacy Kit to affect. 6. Reboot the device if LSPosed asks you to, or force stop and restart selected target apps when appropriate.

Only enable the module for apps you intend to manage. Keeping the scope narrow usually makes troubleshooting easier and reduces unexpected behavior.

Disclaimer

Use Privacy Kit only on devices and apps where you understand and accept the privacy, compatibility, legal, and policy implications. You are responsible for how you use this module. Some apps and services may restrict access, enforce integrity checks, terminate sessions, or behave unexpectedly when device identifiers are changed.

License

The application source, build project, signing material, and private tooling are maintained privately by the developer.

lsposed module privacy root identifier spoofing system open source

What's new

v2.0.5Sep 19, 2026

Apps could see they were being sandboxed — and list your other sandboxed apps The isolated-container mounts were visible to the app inside them. Any containerized app could read its own /proc/self/mountinfo and find 133 lines naming Privacy Kit, along with the package name of every other app you isolate and how many profiles each one had. An app that wants to know whether it is being sandboxed only had to read a file about itself — and knowing you isolate that particular set of apps is a fingerprint in its own right.
Containers now live outside the app's data directory, in a place that names neither the product nor your apps (each app's folder is named by a hash of its package).
Measured on device, before and after: 133 → 0 lines naming Privacy Kit, 6 → 0 app names exposed.
Your data is moved for you The first time you use a profile after updating, your containers are migrated automatically. Sessions are preserved: mounts are torn down first, each app's data is moved with a single atomic rename, nothing is ever deleted, and if anything goes wrong the old copy stays where it was and keeps working. Verified by migrating a live, signed-in Instagram profile — it stayed signed in.
Two things come along with the move: your apps' session data no longer counts against Privacy Kit's storage, and containers now survive clearing Privacy Kit's data or reinstalling it.
Fixed
The Apps screen showed â In scope but not seen loading â open it instead of ⚠ In scope but not seen loading — open it. Encoding damage across four UI files, 28 occurrences. Includes everything from 2.0.4 Per-profile keystore isolation (the fix for Instagram logging you out when you switch profiles), per-profile app_* stores, the pm clear fix so creating a profile no longer logs out your existing ones, and the five defects an adversarial review found in that work.