Privacy

DRAFT — NOT LEGAL ADVICE. This is a working draft for the tracebin beta, written by the product team, not by a lawyer. It has not been reviewed by counsel. It exists so that beta users know, plainly, what we collect and what we do with it.

Last updated: 2026-07-21

What we collect

Account data. Your email address and a bcrypt hash of your password, held by our authentication provider (Supabase). We have no plaintext access to your password.

Bins and manifests. Bin titles, descriptions, and collection specs; team and membership records; and for every run, the manifest: file names, sizes, SHA-256 hashes, source paths, container name, command text and exit codes, and timestamps.

Collected files. The files and command output a customer approves for upload. In transit they go directly from the customer's machine to object storage over HTTPS via short-lived signed URLs — file contents do not pass through tracebin's application servers. At rest they live in object storage (see below).

Operational data. Collection token records and expiry, run progress events, per-token rate-limit counters, and aggregate statistics (bin counts, storage totals). We run no third-party analytics and no ad tracking.

From customers running a collection link: no account, no name, no email. The script sends only the run's files, manifest, and progress events.

Where it is stored

• Database and authentication: Supabase (Postgres).
• Collected files: Cloudflare R2 by default. If your team has connected its own S3/R2 bucket, files for team bins are stored there instead, under your agreement with that provider; tracebin stores that bucket's secret access key encrypted (AES-256-GCM) and decrypts it only to sign upload and download URLs.

The "we don't read your files" posture — stated honestly

tracebin's systems do not open, parse, scan, or analyze the contents of collected files. Contents transfer directly between the customer and storage; the product's features operate entirely on the manifest.

The honest carve-outs:

• We do store and display metadata about every file — its name, size, hash, and source path — to the bin's owner and, for team-scoped bins, their team. File names and paths can themselves be sensitive; the customer sees every name before approving upload.
• Command output collected by a spec is a file like any other: we store it and show it to the bin owner without inspecting it.
• Operators with storage-level access could technically access stored objects, as with any hosted service. Policy is that we access customer file contents only if required to debug a specific problem with your explicit permission, or if legally compelled.

Retention

During the beta, there is no automated retention: collected files and manifests persist until deleted. The announced 30-day retention for the free tier is a forward-looking policy that is not yet enforced by the system — when automated retention ships, it will be announced before it deletes anything. To have files, bins, or your whole account deleted now, email us and we will do it manually.

Collection tokens expire on their configured schedule (24 hours to 30 days) and expired tokens are refused permanently.

Sharing

We do not sell data or share it with third parties, except the infrastructure providers named above acting as processors, and legal compulsion. Team features share data exactly as described in the product: team-scoped bins and their runs are visible to active team members.

Contact

Questions, deletion requests, corrections: support@tracebin.dev