PGSizer Privacy Policy for Browser-Based postgresql.conf Generation
PGSizer executes PostgreSQL 17 memory equations and pgbouncer.ini exports locally in your browser with zero user registration and zero schema logging. (Revision: 2026-11-12)
Local Browser Execution Inside the PGSizer PostgreSQL 17 Studio
-
PGSizer computes shared_buffers, effective_cache_size, work_mem, and pgbouncer.ini connection limits strictly within local JavaScript inside your web browser. PGSizer never transmits your PostgreSQL dataset volume, connection concurrency slider values, or downloaded .conf files to any backend database.
Readers can inspect, copy, and download postgresql.conf and pgbouncer.ini artifacts on PGSizer without creating an account or submitting personal identifiers.
How PGSizer Handles Outbound /go/* Redirects & Partner Attribution Cookies
-
When a visitor clicks a sponsored /go/* infrastructure link on PGSizer, our edge redirect handler logs non-identifying route metadata (target provider key, language code, and workload preset slug) before issuing an HTTP 302 redirect to Hostinger, UltaHost, Vultr, InterServer, or ChemiCloud.
Upon arrival at the external hosting merchant domain, that vendor applies its own referral attribution cookie under its respective privacy notice. For privacy questions regarding PGSizer, contact PGSizer Editorial Desk via https://pgsizer.pages.dev/en/contact/.
PGSizer Content-Security-Policy & Subresource Integrity Controls
-
Every static page on PGSizer enforces HTTPS transport, strict Content-Security-Policy (script-src self, frame-ancestors none), and cryptographic SHA-384 Subresource Integrity hashes on local PGSizer CSS and JavaScript bundles.