Privacy.
What Prized records about how you use the product, and what it never records.
Prized collects two kinds of usage data: what the CLI does on your machine, and how you use the website and dashboard. Neither one reads what is inside your box.
What is never collected
Nothing from inside your box is sent anywhere for analytics:
- Source code, files, and anything else on the box filesystem
- Terminal output and shell history, including the in-browser terminal
- Secret values and environment variable values
- CLI arguments, flags, and paths
Website and dashboard
The site records page views, clicks, and a short list of named product events: creating, pausing, resuming, resizing, and deleting a box, and copying a CLI command. Once you sign in, those events are tied to your account, so a broken flow can be traced to the account that hit it.
Session replay
While you are signed in, the dashboard records a replay of the interface, which is how a confusing or broken flow gets diagnosed without a support call. Replay is masked in your browser, before anything is sent:
- Every input and every piece of text is masked. A replay shows layout, clicks, and navigation, never the words on the page.
- The terminal, the secrets panel, and the environment variables panel are blocked outright. They record as empty placeholders, so nothing rendered inside them can be recovered from a replay.
Signed-out visitors are never recorded, so browsing the marketing pages or these docs produces no replay at all.
Turning it off
The site respects your browser's Do Not Track setting. With Do Not Track on, the site records nothing: no page views, no events, no replay.
The CLI has a separate switch, covered in CLI: usage telemetry.
Where it goes
Usage data goes to PostHog, which Prized uses for product analytics and for error reports when a page throws. Events are sent directly to PostHog's US cloud. No analytics code is ever fetched at runtime: the PostHog SDK and all of its extensions are pinned into our reviewed build. An ad blocker may block the analytics requests themselves; that affects our telemetry, never the dashboard's functioning.
Something unclear or out of date?