Privacy
What the website, the CLI, the verifier and job sponsors can see. Each item is marked as live today or planned for launch.
This website
Describes how this site is built today.
No analytics, tracking pixels or advertising scripts
LiveThe site ships no third-party analytics or ad code.
No cookies or accounts
LiveThe site sets no cookies and has no sign-in.
Fonts are served from this site
LiveTypefaces are bundled at build time. Your browser does not request them from a font service.
Job brief form stays in your browser
LiveThe brief on the For teams page is not submitted anywhere. It is only copied to your clipboard when you ask.
Hosting logs
At launchLike any website, the hosting provider may record standard request logs such as IP address and user agent. The provider and its retention period will be listed here before launch.
The probe CLI
Implemented in the probe CLI. Not yet published to a package registry.
Runs cases on your machine
BuiltCases run in a sandboxed copy of the job workspace with ffi and file access off and your environment variables removed. Nothing outside the case file is uploaded.
Sends only what a submission needs
BuiltA submission contains the case source, your operator address and a signature over both. Results are computed by the verifier, not reported by the CLI.
Sensitive results are sealed to the sponsor
BuiltThe verifier seals each accepted case and its full trace to the sponsor's X25519 key before publishing anything. Only that key can open it.
The verifier
The verifier needs enough to reproduce a result, and no more.
Sees submitted cases and traces
BuiltIt needs the case source to replay it on the snapshot and give a verdict. It stores the source, and stores reports only in sealed form.
Publishes verdicts, not exploits
BuiltThe public job feed shows each case's title, verdict and fingerprint, never its source or trace.
Runs unreleased code in an attested environment
LaterTesting code that is not yet deployed, with proof of what ran. A later capability.
The job sponsor
The team that funded the job.
Sees accepted results and full failure traces for its own jobs
BuiltOnly a request signed by the job's sponsor wallet can download the sealed reports, and only the sponsor's report key can open them.
Decides on disclosure
At launchThe sponsor decides when, or whether, details of a failure become public.
Questions
Ask @probecli on X. For how encrypted reports work, read Private reports.