The first on-device consent enforcement engines. Zero network-layer blocking, total architectural integration directly within your application code.
Blocks tracking SDKs at initialization using deep class loading analysis.
Enjoy a 30-day open trial using key TRIAL-12345678.
Validating zero-latency tracing constraints within fast-refresh rendering frames to prevent operational lag while intercepting advertising packages.
CookiePrime engine integrated directly into Google's official Sunflower code build alongside Firebase Analytics, Facebook SDK, and Mixpanel.
Real ADB logcat output tracking the complete operational scanning and whitelisting loops inside our test container.
Package Whitelisting prevents accidental runtime drops by explicitly configuring trusted internal modules.
Explicitly mark your private corporate tracking classes as safe. The compilation signature analysis engine completely bypasses runtime blocking for any matching entries.
Assign unique custom authorization groups directly to unknown matching classes right inside your initialization loop, bypassing strict default drop actions completely.
Drop the lightweight archive into your local build project's library tree directory.
implementation(files("libs/cookieprime...aar"))
Trigger a safe single-line check sequence directly within your primary initialization class.
CookiePrime.init(this, "TRIAL-KEY")
Query state variables at runtime to safely gate commercial modules based on user parameters.
CookiePrime.isConsentGiven("analytics")
Consent that actually prevents tracking. Third-party SDKs literally never run until the user grants permission.
CookiePrime is built on a simple idea: third-party SDKs should not run until the user says yes.
Not wrapped. Not filtered after the fact. Literally not executed.
SDKs are safely held in a queue at the architecture level. They only initialize and run after explicit user consent is granted.
Tracking blocks are rigorously checked at the call site before execution, ensuring absolute zero overhead on your app's performance.
Audit logs are maintained via secure local storage and encrypted sync to your own backend. Complete data sovereignty.
One line of code. Zero pre-consent data collection. Zero runtime overhead. Stop fighting with complex adapter configurations and massive interception penalties.
Provable compliance. SDKs don't initialize, tracking calls don't execute, and you completely own the audit trail. True immunity from third-party data breaches.
| Aspect | Typical Approach | CookiePrime Approach |
|---|---|---|
| SDK Initialization | SDKs start immediately at app launch | SDKs only start after user grants consent |
| Tracking Prevention | Runtime interception or adapter wrapping | Gated at call site — block never runs |
| Performance Impact | 50–100ms interception penalty per call | ~0ms dictionary lookup |
| Integration Complexity | 50+ lines, multiple config files | 1 line |
For commercial use, partners can request a custom build redirected to their own dedicated Database and VM.