RedisVault Privacy Policy & Client-Side Calculation Governance
| RedisVault Governance Document | Privacy Policy (/en/privacy/) |
|---|---|
| Publisher & Editorial Contact | RedisVault Editorial Desk — https://redisvault.pages.dev/en/contact/ |
| Last Verified Date | 2026-11-12 |
-
1. 100% Browser-Local Execution on RedisVault
RedisVault operates without registration walls, newsletter popups, or third-party behavioral ad pixels. Every dictEntry/jemalloc overhead equation, POSIX fork() Copy-on-Write projection, and downloadable redis.conf / valkey.conf file is computed locally inside your browser.
RedisVault never transmits or stores your key counts, payload sizes, or generated daemon configurations on any backend database.
-
2. Outbound /go/* Affiliate Redirects & Upstream Cookies on RedisVault
When you intentionally click an outbound vendor CTA routed via `/go/*` on RedisVault (all marked `rel="sponsored nofollow noopener"`), our redirect endpoint forwards non-identifying campaign parameters (`lang`, `src`, `app`) to the official hosting provider (Vultr, Hostinger, UltaHost, InterServer, or ChemiCloud).
Once you arrive on the vendor website, that provider may set its own referral attribution cookie (typically 30 to 90 days) governed by that vendor’s published privacy policy.
-
3. RedisVault Data Controller & Privacy Inquiries
RedisVault is published by RedisVault Editorial Desk over HTTPS with strict Content-Security-Policy (`script-src 'self'`, `frame-ancestors 'none'`) and zero external font trackers. Direct any privacy questions to https://redisvault.pages.dev/en/contact/.