SupaScale Privacy Policy & Client-Side Supabase Sizer Data Rules
Last updated on SupaScale: 2026-11-12
| Data Controller | SupaScale Editorial Desk |
|---|---|
| Privacy Contact | https://supascale.pages.dev/en/contact/ |
| User Accounts / PII Forms | None (100% Stateless Browser Execution) |
| Third-Party Ad Pixels | Zero External Tracking Scripts or Fonts (CSP script-src self) |
1. Zero Personal Data Collection in the SupaScale Supabase Docker Workbench
SupaScale (maintained by the SupaScale Editorial Desk) runs without user registration walls, newsletter popups, or behavioral ad pixels. Every 12-container Supabase Docker toggle, MAU tier selection, PostgreSQL buffer calculation, and downloadable docker-compose.override.yml file executes locally inside your browser.
We never transmit or store your project MAU estimates, database gigabyte inputs, or generated Compose YAML configurations on any remote database.
2. Outbound /go/* Partner Redirects & Upstream Vendor Cookies on SupaScale
When you click an outbound /go/* partner link on SupaScale, our edge redirect endpoint logs an anonymized aggregate counter (target provider slug, page language, and workload tag) and returns an HTTP 302 redirect with Cache-Control: no-store to Hostinger, Vultr, UltaHost, InterServer, or ChemiCloud.
Upon landing on the vendor domain, that hosting company sets its standard affiliate attribution cookie governed by its own published privacy policy.
3. Strict Content-Security-Policy & Privacy Inquiries for SupaScale
SupaScale enforces strict Content-Security-Policy (default-src self, zero external font or analytics requests), HSTS preload, and X-Frame-Options: DENY headers across every static document. For privacy questions, contact SupaScale Editorial Desk via https://supascale.pages.dev/en/contact/.