TracesHub (traceshub.com) is the hosted application for the open-source agent-trace CLI, operated by Ujjal Sharma ("we", "us"). This policy explains what data we collect when you use the TracesHub website and app, why we collect it, and the choices you have. Questions or requests: support@traceshub.com.
What we collect
Account information
You sign in with GitHub (OAuth scopes read:user and
user:email). We store your GitHub user ID, username, display name, email
address, and avatar URL. We never see your GitHub password.
Content you push
The core of TracesHub is content you explicitly push with the agent-trace CLI. Depending on the push filters you configure, this can include:
- per-line attribution ledgers and commit links (which model and tool wrote which lines);
- prompts, session summaries, and full agent conversation transcripts;
- trace metadata such as file paths, commit SHAs, and timestamps.
Nothing is uploaded automatically — the CLI is local-first and only syncs when you run
agent-trace push. Conversation transcripts can contain anything you typed to
your coding agent, so choose your push filters accordingly.
Repository data
If you install the TracesHub GitHub App, we receive installation and repository metadata from GitHub (repo names, branches, commit information) and webhook events for the repos you grant access to. To compute full-codebase attribution, we clone the repository code into a temporary, short-lived workspace on our servers; these checkouts are ephemeral working copies, not a separate long-term store of your source code.
Collaboration and audit data
- Organization and project membership, roles, and sharing settings.
- Invitation records, including the email address you invite someone with.
- An append-only audit log of consequential actions (who enabled traces, minted or revoked a token, changed collaborators, and similar).
Technical data
- Server access logs (IP address, user agent, requested URL, timestamps), kept for security and debugging.
- API token metadata. Tokens you mint are stored hashed — we cannot recover the secret after showing it to you once.
Cookies
We set a single essential cookie, tracehub_session, to keep you signed in
(up to 14 days, rolling). We use no analytics, advertising, or third-party
tracking cookies on the website or the app.
How we use your data
- To provide the service: store, display, and share your traces with the people you choose.
- To authenticate you and secure the application (sessions, tokens, rate limits, audit logs).
- To send transactional email only — such as project invitations. No marketing email.
- To respond to support requests.
We do not sell your data, show ads, or use your code, prompts, or conversations to train AI models.
Who we share it with
Your content is visible to the people you share it with — organization members and project collaborators, according to the roles and permissions you set. Beyond that, we share data only with the infrastructure providers needed to run the service:
- Amazon Web Services (AWS) — hosting, database, and email delivery (currently in the United States).
- GitHub — sign-in and the GitHub App integration, under GitHub's own terms and privacy policy.
We may disclose data if required by law.
Retention and deletion
- Account data and pushed content are kept while your account or organization is active.
- Server logs are kept for a limited period for security and debugging, then discarded.
- Organization owners and admins can export all of an organization's trace data and metadata as a ZIP archive from the app at any time.
- To delete your account, an organization, or specific content, email support@traceshub.com and we will remove it within 30 days, except where a residual copy must be kept briefly in backups or for legal reasons.
Your rights
Depending on where you live, you may have rights to access, correct, export, or delete your personal data, or to object to its processing. Email support@traceshub.com to exercise any of these rights and we will respond within 30 days.
Security
Traffic is encrypted with TLS, API tokens are stored hashed, and access to data is scoped by organization and project roles. No system is perfectly secure — if you find a vulnerability, please report it responsibly to support@traceshub.com.
Children
TracesHub is not directed at children and may not be used by anyone under 13 (or the higher minimum age required in your country).
Changes to this policy
We may update this policy as the service evolves. We will change the "Last updated" date above and, for material changes, make reasonable efforts to notify signed-in users.
Contact
Ujjal Sharma — support@traceshub.com