VI // TIẾNG VIỆT
DATA_GOVERNANCE // GDPR & ZERO-PII PRIVACY • November 2026

VRAMForge Privacy Policy & Zero-Account Sizing Architecture

How VRAMForge calculates GGUF VRAM and RAG server memory client-side with zero user accounts, zero PII collection, and clean partner attribution.

1. 100% Client-Side Sizing & Zero Personal Data Collection on VRAMForge

VRAMForge Editorial Desk operates without user accounts, registration walls, email newsletters, or third-party ad-tech pixels. Every GGUF quantization footprint, parallel KV-cache calculation, and OpenAI API TCO comparison executes directly in your browser.

We never log your model configurations, internal team headcount inputs, or architecture presets on any central database. Privacy inquiries may be directed to https://vramforge.pages.dev/en/contact/.

2. Outbound /go/* Partner Attribution & Vendor Cookies on VRAMForge

When you choose to click an outbound infrastructure link routed via /go/* (marked with rel="sponsored nofollow noopener"), our Cloudflare Edge router processes an anonymized aggregate click event (provider slug, locale, and workload preset tag) and returns an HTTP 302 redirect to the official vendor.

Once you land on Hostinger, UltaHost, Vultr, InterServer, or ChemiCloud, that provider sets its standard referral attribution cookie (typically 30 to 90 days) under its own published privacy policy.

3. TLS 1.3 Edge Security & Strict CSP Isolation on VRAMForge

All pages and static assets on VRAMForge are delivered over HTTPS (TLS 1.3) with Content-Security-Policy (script-src self, frame-ancestors none), Strict-Transport-Security, X-Content-Type-Options: nosniff, and X-Frame-Options: DENY.

Return to VRAMForge Workbench →