Privacy

Usage data comes from two places, the CLI on your machine and the website and dashboard; neither reads what is inside your box. How a box is reached and what the control plane holds about it are on Security and trust.

The Privacy Policy is the full statement: what Prized collects, who processes it, how long it is kept, and your rights.

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, the in-browser terminal included
• Secret values and environment variable values
• CLI arguments, flags, and paths

The output of a command you run with prized exec or the edge is kept for you to read back, in its command history, never for analytics.

Website and dashboard

The site records page views, clicks, and these named product events:

• Signing up (which sign-in provider, and where you came from)
• Creating a box, the box reaching running, or waiting for capacity
• Opening the browser terminal; signing in from the CLI
• Using the CLI, at most once a day per workspace (the first command's name, the CLI version, and your OS), from its usage telemetry
• Pausing, resuming, resizing, and deleting a box; changing auto-pause
• Copying a CLI command; the onboarding steps you view
• Starting checkout (with the plan amount); activating a plan; paying for a top-up (with its amount)
• On a campaign page: the sections you scroll to, and how much of its film you watch

Events also note whether the page is open inside a social app's built-in browser (Instagram, Facebook, Threads, TikTok, LinkedIn, Snapchat), read from the browser's user agent.

Once you sign in, events are tied to your account, including the pages you viewed before signing up in the same browser, so a broken flow can be traced to the account that hit it.

"Where you came from" is one first-party cookie, prized_src, set on the first page you land on and kept 30 days: the referring site's hostname, the landing path (invite and install tokens removed), and any campaign tags (utm_source, utm_medium, utm_campaign, ref) on the link you followed. It holds no identifier and is never rewritten by a later visit. With Do Not Track on, it is not set, a stored one is removed on your next page load, and a sign-up callback is not recorded.

The New box form and the onboarding tour pick the region nearest you from your approximate location, which our host derives from your network address for each request; it is used for that page and not stored. To show round trips, your browser also sends a few empty requests to each region's AWS endpoint (dynamodb.<region>.amazonaws.com/ping); they carry nothing about you beyond the request itself, and the times stay in your browser.

Each sign-in records its time, network address, and browser, kept 90 days to investigate abuse and account takeover (Data retention); Settings → Sessions shows the address of each of yours.

prized login registers your computer's SSH public key with each workspace it signs in to, so desktop apps can reach your boxes. If one computer signs in to several new workspaces, we keep a one-way fingerprint of that key and those workspaces' identifiers, to investigate abuse of the free credit. We keep them for 90 days after we last added a workspace to that computer's record (we add one when the pattern is detected, within minutes of the use that completes it; the uses it counts can be up to a day older) and delete them in the hourly cleanup after that, so a later addition restarts the 90 days for the whole record. A workspace held because of it keeps the same fingerprint and identifiers in its hold record for 90 days after the latest use of that computer's sign-ins the hold counted (Data retention).

Before an analytics event leaves your browser, its URL is cut to the path: query strings and fragments are dropped, and tokens in private links (invites, install links) become a placeholder. Pages also tell your browser not to send their address as a referrer when loading resources or following links.

Session replay

While you are signed in, the dashboard records a replay of the interface, 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 record as empty placeholders.

Signed-out visitors are never recorded, so the marketing pages and these docs produce no replay.

Turning it off

• Browser. The site respects Do Not Track: with it on, the site records nothing, no page views, events, or replay.
• CLI. A separate switch, under CLI: usage telemetry.

How long it is kept

Retention windows for box metrics, process snapshots, and CLI usage aggregates, and how zero data retention shortens them, are on Data retention.

Where it goes

• PostHog holds the product events, the account they belong to, session replay, and error reports when a page throws, in its US cloud.
• Vercel Web Analytics, run by the platform that hosts the site, holds aggregate page-view counts (visits per page, by country and browser). It is never told who you are, sets no cookie, and sees the same cut-down URL.

An ad blocker may block the analytics requests; that affects our telemetry, never the dashboard.