Your clipboard is one of the most vulnerable data vectors on your smartphone. Every time you copy a password, a two-factor authentication code, a private message, or a tracking link, malicious or overly intrusive applications can silently read that data the moment you open them. Clipboard Whitelist, engineered by the renowned developer Kr328, puts a definitive stop to this privacy leak. By hooking into the core Android framework via Riru or Zygisk, this module intercepts all clipboard read requests, ensuring that only the applications you explicitly trust can access your copied data.
Core Privacy Capabilities
Discover how this module isolates your clipboard environment to provide an impenetrable layer of data security.
Absolute Read Blocking
By default, the module treats all applications as untrusted. If an unwhitelisted app attempts to query the system clipboard, the module spoofs the response, returning an empty string instead of your private data.
Framework Injection
Instead of running a heavy background service that drains your battery, this module injects directly into the Zygote process. It intercepts the ClipboardManager API calls at the lowest possible level.
Dual Framework Support
The developer provides two distinct builds. You can choose the modern Zygisk implementation for Magisk v24+ and APatch/KernelSU, or the legacy Riru implementation for older rooted devices.
Custom Whitelisting
You retain full control over which apps can read your clipboard. By managing your trusted list, you ensure that essential apps (like browsers, note-taking apps, and keyboards) function normally while locking out trackers.
Technical Breakdown: How Clipboard Interception Works
In the Android architecture, any application can utilize the ClipboardManager API to get or set text in the global clipboard buffer. While Google introduced restrictions in Android 10 to prevent background apps from reading the clipboard, foreground apps (apps currently on your screen) still retain full, unrestricted access to read whatever you copied last.
Clipboard Whitelist solves this by utilizing the Zygisk (or Riru) framework to intercept the initialization of every app on your device. When an app requests to read the clipboard via getPrimaryClip(), the module intercepts the request. It checks the package name of the requesting app against your predefined whitelist. If the app is not on the list, the module drops the true clipboard data and feeds the app a null or empty response. This happens in microseconds, completely transparently, ensuring your data is never leaked.