Privacy Policy

Overview

Clex ("we", "us", "our") is a browser-based file workspace that helps users prepare and share files. This Privacy Policy explains how we collect, use, and protect information when you use our service at clex.in.

Our core design principle is privacy-first. For direct P2P and local network transfers, your files never leave your browser and are never stored on our servers. We believe your files are your business.

What We Don't Collect

Let's start with what we don't do. This is the important part:

• We do not store your files on any Clex server during P2P or local transfers
• We do not read, scan, analyze, or inspect the content of your files
• We do not require you to create an account for core file transfer functionality
• We do not sell or share personal data with third parties for advertising
• We do not use tracking cookies for behavioral advertising
• We do not retain file metadata after your transfer session ends

What We Do Collect

To keep the service running and improve the experience, we may collect:

• Signaling data: Temporary session identifiers used to establish P2P connections. These are ephemeral and discarded after the connection is established.
• Basic analytics: Page views, feature usage counts, and error reports — anonymized and aggregated. We use this to understand which features are used and fix bugs.
• Google Account data (Drive transfers only): When you choose to use Google Drive as a fallback, we request access to your Google Drive to upload files. We do not store your Google credentials — authentication is handled by Google's OAuth flow.

How P2P Transfer Works (Privacy Perspective)

When you share files via P2P, Clex uses WebRTC to create a direct browser-to-browser connection. Here's what happens:

• A lightweight signaling server helps the two browsers discover each other (this is the only server involvement)
• The signaling server sees only connection metadata (session IDs, network information) — never file content
• Once the P2P connection is established, the signaling server is no longer involved
• File data travels directly from browser to browser, encrypted via DTLS
• When the transfer completes or either browser tab closes, the data is gone

Google Drive Transfers

When you choose to use Google Drive as a fallback transfer method:

• Files are uploaded to your personal Google Drive account, not to any Clex-controlled storage
• We use Google's OAuth 2.0 for authentication — we never see or store your Google password
• We request only the permissions needed to upload files to your Drive
• File management (deletion, sharing settings) is under your control in Google Drive
• Google's own privacy policy applies to data stored in your Drive

File Processing Privacy

All file processing tools (image compression, PDF operations, DOCX conversion, ZIP bundling) run entirely in your browser. Your files are processed using client-side JavaScript and never sent to any server for processing. This is by design — it's core to our privacy architecture.

Cookies & Local Storage

We use browser local storage to save your preferences (theme, settings). We do not use cookies for tracking or advertising. No third-party tracking scripts are loaded.

Changes to This Policy

We may update this policy from time to time. Changes will be reflected on this page with an updated "Last updated" date. Significant changes will be communicated through the application.

Contact

Questions about this privacy policy? Contact us at hello@clex.in.