Privacy Architecture

Designed for developers who prioritize security. Our zero-log policy isn't just a promise; it's enforced by client-side encryption.

Data Sovereignty

RedisKeeper collects the absolute minimum required to function. We prioritize data minimization in every transaction.

Client-Side Encrypted Credentials — Shipped to us as opaque blobs. We don't hold the keys.
Monitoring Metadata — Basic timestamps used for scheduling the next ping cycle.

Information We Do NOT Collect

Personally Identifiable Info (PII)

Browser Fingerprinting

Interaction Analytics

Credential Plaint-text

Monetization Data

Third-party Cookies

Encryption Standards

Utilizing TweetNaCl.js, we establish a secure enclave in your browser. The PBKDF2 derivative of your manager password stays in your RAM and is never transmitted.

Decryption only occurs in an ephemeral serverless execution environment during the 10-second ping window.

Purge Requests

Autonomous data deletion is available via your Management Dashboard. Deleting an entry results in a hard delete from our primary database and all cache layers.

Manage your data

Audit Our Source

RedisKeeper is open source. You can audits our encryption and storage logic on GitHub.

View Repository