Privacy statement

Exactly one event per device, the first time it connects to a MoliSync server, and never again afterwards. It contains:

• an opaque id derived from the deployment id and a salted device key (SHA-256, truncated to 128 bits);
• the platform (windows, android or other);
• the server version;
• a timestamp.

• no device name, certificate fingerprint, IP address or hardware identifier;
• no text, file names, file contents, clipboard history or record metadata;
• no cookies, advertising ids, fingerprinting scripts or analytics SDKs;
• no account, e-mail address or contact information.

Your own server sends the event to statistics-api.molirain.com, a Cloudflare Worker backed by D1.

The counter stores only that opaque id, the platform, the version and the timestamp. The id is scoped to a single deployment, so the same device cannot be linked across installations. Only aggregate numbers are ever published.

Cloudflare is the infrastructure provider and may process request metadata such as the connecting IP under its own policies; the counter code itself does not store it.

Set MOLISYNC_TELEMETRY_ENABLED=false, or leave telemetry.endpoint empty. Sync, P2P and relay keep working exactly the same.

Each server also exposes its own local counters at GET /api/v1/stats; those never leave your deployment.

Text records and files are stored in your SQLite database and blob directory. The project maintainer has no access to them.

Clients keep certificate private keys in the operating system store or Android KeyChain; they are never uploaded.

Update checks read the public GitHub Releases API. They use a separate HTTP client without your MoliSync certificate, so your device identity is never presented to GitHub; GitHub simply sees a request like any other visitor.

This website is static and self-contained: fonts, styles and scripts are served from this domain only.