RANA
Zero Remote Telemetry Standard

Privacy Policy & Zero-Telemetry Guarantee

Last Updated: September 2026Applies to rana.com.bd/utilities

Architectural Guarantee

In-Browser Sandbox

Inputs stay completely in your local browser memory.

Zero Ingestion

No payload endpoints or background upload requests.

Offline Resilient

Functions normally even if your connection drops.

1. Core Philosophy: Client-Side Sandbox

RANA Web Utilities are built upon an unambiguous technical premise: Zero Data Ingestion. Every developer tool (including JSON parsers, formatters, Base64 transformers, hash engines, and regex suites) executes purely in-memory inside your local web browser's JavaScript V8/SpiderMonkey engine.

Your input payloads, files, query parameters, and generated tokens are never dispatched to our origin servers, proxy nodes, or any third-party computing infrastructure.

2. Zero Network Telemetry & Payload Tracking

When you transform sensitive data (such as API keys, environment variables, JWTs, SQL schemas, or code repositories), the computation remains entirely offline-capable after the initial static asset download.

  • No HTTP POST payloads containing raw input bodies
  • No automated remote crash logging for inputs or outputs
  • No behavioral screen recordings or cursor heatmaps
  • No external tracking beacons or advertising identity cross-matching

3. Local State & Ephemeral Storage

Any state preservation—such as remembering active theme preferences, category view selections, or quick scratchpad settings—lives exclusively within your browser's native localStorage or sessionStorage. This data remains on your physical disk and can be purged instantly by clearing browser cache.

4. Edge Distribution & Transient Network Logs

Our static application assets (HTML, CSS, compiled JavaScript bundles, and WebAssembly modules) are cached and delivered via high-speed global edge CDNs. Like any web distribution node, the edge server may process standard ephemeral network protocol headers (such as IP address, requesting browser user-agent, and requested static file path) solely to deliver assets, prevent distributed denial-of-service (DDoS) attempts, and fulfill technical TLS handshakes.

6. Security & Inquiries

If you have questions regarding the underlying client-side security architecture or wish to submit an audit report, direct inquiries may be sent to [email protected].