DOKPLOYHUB · DATA GOVERNANCE · CLIENT-SIDE RUNBOOK STORAGE · 2026-11-12
DokployHub Privacy Policy: Client-Side Sizing & Zero-Account Runbooks
Read the DokployHub Privacy Policy covering browser-local PaaS RAM calculations, localStorage checklist persistence, and /go/ affiliate redirect handling.
This DokployHub governance and compliance document (privacy) was last reviewed on 2026-11-12 by the DokployHub PaaS Repatriation Collective.
-
1. Browser-Only Calculations & LocalStorage State on DokployHub
DokployHub, maintained by the DokployHub PaaS Repatriation Collective, requires zero user accounts, newsletter signups, or ad-tech tracking pixels. Every Dokploy, Coolify v4, Kamal 2, and SQLite WAL memory calculation executes locally inside your browser.
Interactive migration checklists on DokployHub save your checked verification steps exclusively in your own browser localStorage under the dkp_runbook_v1_* key prefix. Submissions voluntarily sent through the form on /en/contact/ are used solely to verify technical errata and pricing updates.
-
2. Outbound /go/* Partner Redirects & Vendor Cookies from DokployHub
When you click a sponsored infrastructure link under /go/* on DokployHub (marked with rel="sponsored nofollow noopener"), our redirect endpoint sends an HTTP 302 response to the official vendor website (Hostinger, Vultr, UltaHost, InterServer, or ChemiCloud) with non-personal campaign parameters.
Once you land on the external vendor domain, that hosting provider governs any session or referral attribution cookies under its own published privacy policy. Privacy questions for DokployHub may be submitted anytime via the form on /en/contact/.
-
3. DokployHub Transport Security & Subresource Integrity
All pages on DokployHub are served over HTTPS with strict Content-Security-Policy headers (script-src self; frame-ancestors none), SHA-384 Subresource Integrity hashes on local CSS/JS assets, and X-Robots-Tag: noindex, nofollow on /go/* routes.
DokployHub Pre-Cutover Verification Principles (Privacy Policy)
Across our deterministic DokployHub runbooks, the DokployHub PaaS Repatriation Collective advises rehearsing a full pg_dump or Litestream SQLite WAL restore from off-site S3 storage onto a staging container before lowering DNS TTLs to 60 seconds for Privacy Policy.
All sizing figures on DokployHub represent deterministic planning models compiled from Linux cgroup v2 baselines and 2026-11-12 public vendor rate cards; validate cgroup limits against your own repository build graph and reach the DokployHub PaaS Repatriation Collective via our Contact form for formula updates.