Privacy and transparency

Telemetry

Vivipilot uses three separate forms of measurement. They have different purposes and controls, and none includes your local project content or AI-provider key.

Website

Traffic analytics

Page and product interactions help us improve the website.

Downloads

Aggregate requests

Successful package requests are counted without a visitor identifier.

Desktop

Easy to disable

Minimal first-launch and weekly signals can be turned off in Settings.

Website analytics

The website uses Google Analytics. We may record the page path without query parameters, the section viewed, scroll depth, video label, and interactions such as opening documentation or selecting a download. Download-button events may include the public filename, platform, package format, link text, and link domain.

We do not place advertising tags, enable advertising personalization, send project content, or send form-field values through this analytics integration. Google receives the ordinary network and device information involved in an analytics request. Read the Cookie Policy for controls and provider details.

Download request metrics

When the download service returns a complete Desktop package, it increments an aggregate daily counter containing the platform, package format, release version, request count, and object size. HEAD requests, metadata files, installer scripts, checksum files, and byte-range requests are not counted as package downloads.

Stored	Not stored in metrics
UTC day, platform, package format, version, aggregate request count, aggregate object bytes	IP address, user agent, referrer, cookie, account, visitor ID, installation ID

A request count is not a unique person, completed transfer, or successful installation. Browsers and package managers may retry, so the number can be higher than actual installations.

Desktop activity metrics

Release builds enable minimal Desktop analytics by default. You can disable or re-enable it under Desktop Settings → General without losing any feature. Debug builds do not send these events unless a telemetry endpoint is explicitly configured.

An enabled installation sends one first_launch event after its first successful report, then at most one heartbeat every seven days. Each event contains only:

{
  "event": "first_launch | heartbeat",
  "eventAt": "UTC timestamp",
  "os": "operating system",
  "arch": "processor architecture",
  "appVersion": "application version",
  "channel": "distribution channel"
}

The payload rejects extra fields. It does not contain a random or persistent installation ID, hardware ID, account, project or workspace ID, filename, prompt, source code, media, crash dump, or provider credential. Because no identifier is sent, Vivipilot cannot reconstruct a per-user history or connect an activity event to a particular download.

Processing, security, and retention

Download and Desktop counters are processed through Cloudflare and stored as aggregate daily totals. Network infrastructure may process ordinary request metadata temporarily for delivery, abuse prevention, and operational security, but that metadata is not copied into Vivipilot’s aggregate telemetry tables.

Aggregate counters without a visitor or installation identifier may be retained for long-term product and release analysis. Administrative sessions and failed-login rate-limit records are separate security data with short expirations. Website analytics retention follows the configured Google Analytics property settings.

Your controls

Website: use your browser’s cookie and tracking controls, or a Google Analytics opt-out mechanism.
Desktop: open Settings → General and turn usage analytics off or on.
Questions or privacy requests: email [email protected].