Privacy Policy

FileXShare operates on a local-first, client-only architecture. When you paste sensitive text, format JSON, inspect JWT headers, decode Base64, generate cryptographic keys, or compress images, all computation is executed entirely within your browser's sandbox using:

• Standard Web Workers: Background thread processing for intensive tasks.
• WebAssembly (WASM): Compiled high-speed execution for codecs, linters, and parsers.
• Web Crypto API: Native window.crypto.subtle for AES, RSA, SHA, and HMAC cryptographic operations.
• HTML5 Canvas API: Local image resampling and conversion without cloud uploads.

At no point are your inputs, files, or processed results transmitted to, processed by, or saved on servers operated by FileXShare. (The explicitly labeled network tools in §4 send only the requests you choose to make, directly from your browser to your chosen destination.)

Unlike conventional developer sites that route requests through centralized API gateways, we maintain an absolute zero-payload policy:

• We do not track or log clipboard contents or user input.
• We do not retain history of transformed data on any server.
• We do not perform behavioral profiling, and we never share your tool inputs with advertisers — see Display Advertising below.
• We do not sell, rent, or trade your data to third parties.

To enhance your developer workflow, our application stores non-sensitive UI settings directly in your browser's localStorage:

• mango:tool-store: Bookmarked favorite tools and recently visited tool slugs.
• mango:workspace:customizer: Preferred theme accent color, editor font size, font family (mono vs sans), and line wrapping mode.
• theme: Light/dark mode selection.
• mango:api-history: Request history saved by the API Request Tester, including URLs, HTTP method, headers (which may include Authorization tokens), and response metadata. Stored only in your browser — never transmitted.
• mango:sql-history: SQL query history saved by the SQL Playground.
• mango:totp:*: TOTP/OTP secret keys saved by the JWT & Auth Studio tool. These keys are sensitive — clear them via browser developer tools if using a shared device.
• mango:flashcards:*: Flashcard decks created in the Academic Productivity Studio and Flashcard tool.
• mango:prefs:<slug>: Per-tool preference overrides (e.g. indent size, output format) keyed by tool slug.
• mango:cookie-consent:v1: Stored status for acknowledging the cookie and privacy notice banner.

This data never leaves your device. You can clear this data at any time through your browser's developer tools, site settings, or the “Reset” button in the workspace customizer.

A small subset of tools require external network connectivity by definition. For these specific utilities:

• Network requests are only triggered when you explicitly press the Execute or Send button.
• These tools are clearly labeled with a Direct Browser Network badge.
• DNS Lookup — queries Cloudflare's public 1.1.1.1 DNS-over-HTTPS resolver. Only the domain name you type is sent.
• API Request Tester — sends your configured HTTP request directly from your browser to the URL you specify. Headers (including Authorization tokens) travel only between your browser and your target server.
• Python Runner — downloads the Pyodide WebAssembly runtime and any packages you install (import X) from the Pyodide CDN on first use. Subsequent runs use the browser cache. Your Python code and its outputs are never transmitted.

FileXShare is distributed globally over HTTPS via Cloudflare's Content Delivery Network (CDN). When you request the site, standard HTTP connection metadata is processed by the CDN to deliver static HTML, CSS, and JavaScript bundles:

• Client IP address, User-Agent, and browser version (for rate limiting, DDoS defense, and bot prevention).
• Encrypted transport via TLS 1.3 to guarantee that code loaded into your browser cannot be tampered with in transit.
• Aggregate, cookieless page-view analytics via Cloudflare Web Analytics — it measures overall traffic and performance without cookies, cross-site tracking, or collecting what you type into tools. Human visitors only; crawlers never receive the analytics script.

FileXShare is free forever and has no accounts, paywalls, or usage limits. To keep it that way, our pages show display advertising served through our ad partner, Monetag. An ad tag loads on our pages (including tool workspaces) for human visitors; automated crawlers and inspection tools never receive ad scripts.

• What the ad provider may process: standard ad-delivery data such as IP address, user agent, and cookies used for frequency capping and fraud prevention, governed by Monetag's own privacy policy.
• What we never share: your tool inputs — pasted text, keys, files, and computed results — are processed locally in your browser and never transmitted to us or to any advertiser.
• You can block ads with any reputable content blocker; every tool keeps working with zero loss of functionality.

FileXShare is designed for software engineers, students, and technology practitioners. Because we do not require account registration or collect personally identifiable information (PII), we do not knowingly collect personal data from anyone under the age of 13 (or under 16 in the European Union).

We may update this Privacy Policy from time to time to reflect new tools, features, or legal standards. The date at the top of this document indicates when the policy was last revised. We encourage you to review this page periodically.

If you have questions, concerns, or responsible security disclosures regarding this policy or our in-browser tool architecture, please reach out to us at privacy@filexshare.com.