MariaDBBench privacy policy covering local browser execution of InnoDB buffer pool sizing, zero account tracking, and /go/ partner redirect cookies. (Last updated: 2026-11-12)
MariaDBBench executes every InnoDB dataset calculation, connection memory budget, and 50-server.cnf file download locally inside your browser using static JavaScript and Blob URLs. We do not run login forms, newsletter popups, or behavioral ad trackers.
Your entered InnoDB dataset gigabytes, max_connections ceilings, and server RAM selections are never transmitted to any external MariaDBBench database.
When you click an outbound hosting link starting with /go/ on MariaDBBench, our edge redirect endpoint records an aggregate non-identifying click counter (provider slug, language, and workload tag) before issuing an HTTP 302 redirect to ChemiCloud, Hostinger, UltaHost, InterServer, or Vultr.
After landing on the vendor domain, that hosting company may set a standard affiliate attribution cookie governed by its own published privacy statement.
MariaDBBench serves all static pages over HTTPS with strict Content-Security-Policy script-src self rules, Subresource Integrity (SHA-384) asset verification, and zero third-party font or analytics beacons.