Protok

Privacy Policy

Protok Studio — telemetry & data handling

Overview

Protok Studio sends anonymous usage statistics to help us understand which features matter, where the IDE struggles and what to build next. Telemetry is strictly opt-in — nothing is collected until you explicitly enable it in the first-run dialog or in Studio Settings, and it can be turned off at any time — disabling stops all further collection immediately.

What we collect (when enabled)

Session & environment

  • Studio version, operating system and CPU architecture
  • License tier (Community / Pro / Enterprise)
  • Total session time and active editing time

Feature usage

  • Which low-code node types are created, deleted or connected
  • Aggregate graph size (node/link counts — never the structure itself)
  • Widget types added to screens

UI design statistics

  • Aggregate counts of LVGL widget types, style properties, parts, states and flags used across your screens
  • Aggregate color usage (hex values and counts only — not where or on which widget)
  • Layout system usage (flex/grid) and style transition counts
  • Screen and widget counts per project

AI assistant (MCP)

  • Names of invoked tools, success/error status and transport (in-IDE vs external client)
  • Ratio of changes made manually vs via the AI assistant

Simulation, debugging & code generation

  • Simulator start/stop events and durations
  • CAN log playback, TRDP Lab sessions, hardware debug connections (flags and durations only)
  • Code-generation runs with success/failure status

Collaboration sessions

  • Session start/end events with role (host or guest) and join method (invite code, invite, hosting)
  • Session duration, peak participant count, and reconnect count
  • Aggregate counts of synced edits and project files transferred (counts and sizes only)
  • Failed join attempts (method only — never the invite code itself)

Stability

  • Anonymized crash reports and unhandled errors, tagged with the Studio version

What we never collect

  • Source code, generated code or project files
  • Signal names, DBC contents, TRDP telegram structures or network addresses
  • Project names, file paths or the structure of your node graphs
  • Widget labels, text content, object names or screen layouts — only aggregate type/style/color counters
  • Collaboration content — room IDs, invite codes, chat messages, cursors or edits themselves (only aggregate counts)
  • Keystrokes, screen contents or anything outside Protok Studio

How you are identified

Events are tagged with a random per-installation identifier and, if you are signed in, your account ID. Both are hashed (SHA-256) on our servers and are never stored or displayed in raw form. We use them only to count distinct installations and group metrics — not to profile individual users.

Live collaboration

When you host or join a collaboration session, your project files and edits are exchanged with other participants through our relay server and direct peer connections. This content is transmitted to deliver the feature — it is not part of telemetry and is not retained on our servers beyond what the session requires. Only the anonymous usage counters listed above (durations, participant and edit counts) are collected.

Product announcements

Studio periodically fetches published product announcements (release notes, important notices) to display them in the IDE. This is a read-only request — it carries no identifiers and is unrelated to telemetry.

Website analytics

This website uses cookieless, self-hosted analytics. We record page views, the referring site, UTM campaign tags and a handful of product events (such as a download click or a registration). No cookies are set and no raw IP addresses are stored: visitors are counted via a SHA-256 hash of IP address, browser user-agent and the current date, which rotates daily — so we can count unique visitors per day but cannot follow anyone across days. Requests that honor Do Not Track or Global Privacy Control are not tracked at all.

Your choice

On first launch Studio asks whether you want to share anonymous statistics — collection does not start until you agree. You can change this at any time via Menu → Studio Settings → "Share anonymous usage statistics". Turning it off stops all further collection immediately; previously sent anonymous events remain in aggregate statistics.

Contact

Questions about this policy or your data: contact@protok.tech. See also the changelog for what ships in each release.