ElasticRAM Privacy Policy for Browser-Side JVM & OpenSearch Sizing
We architected our ElasticRAM Split-Pane Studio so every JVM heap equation, shard calculation, and downloadable jvm.options or opensearch.yml file executes locally inside your browser session with zero account registration.
ElasticRAM Last Verified Date: 2026-11-12
Browser-Only Calculation Inside the ElasticRAM Config Studio
ElasticRAM requires no user login, email signup, or cloud workspace to generate OpenSearch 2.x and Elasticsearch 8.x configuration files. When you enter daily log ingestion rates (5 GB to 500 GB/day), retention windows, or node counts, our JavaScript engine processes those inputs strictly in local browser memory and constructs downloadable files via the standard Blob API.
We never transmit your cluster names, internal IP ranges, endpoint volumes, or exported opensearch.yml configurations to any backend server.
- 100% local execution for jvm.options and opensearch.yml generation via Blob + URL.createObjectURL
- Zero third-party ad networks, behavioral retargeting pixels, or cross-site tracking scripts
- Strict Content-Security-Policy (default-src 'self') with zero external font or script calls
How ElasticRAM Processes Outbound /go/* Partner Redirects
When you intentionally click an outbound partner link beginning with /go/* (all marked with rel="sponsored nofollow noopener"), our Cloudflare Pages edge function increments an aggregate, non-identifying counter (recording only provider slug, locale code, and workload preset tag) before issuing an HTTP 302 redirect to the vendor.
Once your browser reaches the official vendor domain (Hostinger, Vultr, UltaHost, InterServer, or ChemiCloud), that provider may set a standard affiliate attribution cookie governed by its own published privacy notice.
- Aggregate click counters store zero names, email addresses, or persistent user profiles
- All /go/* endpoints send Cache-Control: no-store and X-Robots-Tag: noindex, nofollow headers
- Upstream vendor cookies apply only after you navigate to an external hosting provider
Privacy Inquiries & Security Headers on ElasticRAM
Every HTML document on ElasticRAM is delivered over HTTPS with Strict-Transport-Security, X-Frame-Options: DENY, X-Content-Type-Options: nosniff, and Subresource Integrity (SHA-384) hashes on local CSS and JS assets. For any privacy questions regarding ElasticRAM, contact ElasticRAM Editorial Desk via https://elasticram.pages.dev/en/contact/.
- Cryptographic SHA-384 Subresource Integrity verified on /assets/elasticram-studio.css and .js
- Permissions-Policy disables camera, microphone, and geolocation APIs site-wide