Tracekit Cloud
Tracekit Cloud: privacy notice
Cygnux Labs runs Tracekit Cloud, where a team's signers send their signed runs and the team's people see what its agents did. This notice says what it keeps, for how long, who can read it, what each of the two permissions an owner gives a signer allows, and what a share link shows. It last changed on 2026-11-15.
What a signer sends
- A connected signer sends its bundles: Tracekit's signed records of what its agents did, and its checkpoints.
- Records commit to prompts, files and tool output with hashes and never carry them, and Tracekit Cloud has no way to receive them: a signer sends it only its key, a name for its machine, its bundles and its checkpoints.
- Tracekit Cloud never gets a signing key: an approval pins the signer's public key, and the token it gives can only send that key's bundles and list its runs.
The two permissions
- When an owner approves a signer, Tracekit Cloud asks two permissions, separately, each off until the owner ticks it.
- Permission 1, "Use this signer's data to serve me", covers Tracekit Cloud's analyses of the signer's data for the team, and its full content when the signer asked to send it.
- Permission 2, "Cygnux may use this data for its own work", covers benchmarks, research, training our verifiers and judges, and comparisons across customers, aggregated or de-identified.
- Tracekit Cloud does neither yet: whatever an owner chooses, it keeps, checks and shows the signed records only, and the choices are only stored, shown on Connect and told to the signer.
- An owner can revoke either permission on Connect at any time, and turning permission 1 off turns full content off with it.
- Every choice and every revocation is kept, with who made it and when, while the service runs.
Share links
- An owner can share chosen runs through a link: anyone who has it sees those runs' signed records' metadata and downloads their bundles, trust.json and witness proofs, until it expires or an owner revokes it.
- A share link reaches nothing else in the space, and it shows no arguments or outputs: Tracekit Cloud has none.
- Each share keeps its name, the runs it holds, who made it and when, when it expires and whether it was revoked, while the service runs.
- Each view of a share and each download through it is logged with its time and what was opened, never who opened it or from where; the newest 200 are kept with exact counts, and the space's people see them on Shares.
What we keep, and for how long
- Each bundle as it was sent, Tracekit Cloud's check of it and what it shows of its runs, while the service runs.
- Each checkpoint Tracekit Cloud's witness cosigned or refused for a space's signers, with the time and its cosignature, while the service runs.
- Each pinned key, with who pinned it and when, and each push token as a hash, with who made it, when, and when it was revoked.
- Each space's name, and each person's name and role in it; sign-in tokens and links are kept as hashes, a link works once, and a session is a signed cookie, not a stored row.
- A connect waiting for approval keeps the signer's key, the name its machine reports, whether it asked for content and its checkpoint, with its device code as a hash; once decided, it also keeps who decided and the permissions chosen.
- The first connect started an hour or more after a code expired deletes that code's connect.
- Each fix an owner marks done, with who marked it and when, while the service runs; its figures are worked out from the signed records above whenever Fixes is opened, and only kept in memory.
- The console writes no request log and no IP address: rate limits count addresses in memory, per minute.
Who can read it
- A space's runs, bundles, keys and permissions are shown only to its own people, each signed in as themselves, and the runs an owner shares to whoever has the link.
- In the console, only an owner approves a signer, pins or removes a key, makes or revokes a push token or a share link, or revokes a permission.
- A push token reads only the list of its own log's runs, never a page.
- Cygnux Labs staff with access to the host can read everything above.
Deleting
To have a space's data deleted, an owner writes to research@cygnuxlabs.com, and a person deletes it by hand. Tracekit Cloud's witness keeps each log's latest checkpoint size and root even then, so it never cosigns a rewritten history.
Contact
Questions about this notice: research@cygnuxlabs.com. The terms: /terms.