Security, privacy and data
A plain summary of what Truly Shipped collects, how it's protected, how long it's kept, and how to get it back or have it deleted. The policies themselves are linked at each step.
What we collect
- GitHub: pull requests, reviews, review comments, commits and deployments, as GitHub's API returns them. Review comments arrive with the few lines of code they point at, and we store them as sent. To measure rework we read which commit last changed each line, never the lines themselves. We never fetch your repository's files or full diffs.
- Jira: issues, epics and sprints from the projects you pick. We store webhook events as Jira sends them, which can include descriptions and comments. Never attachments.
- Claude Code and GitHub Copilot: daily usage counts per person. Never prompts, responses, suggestions or code.
- Your account: name, work email, role and sign-in times. There are no passwords.
The full table is in the Privacy policy.
What we do with it
We turn it into your teams' dashboards and weekly digests, and show them only to the people your workspace allows; see Roles and visibility. To write each digest, a summary of the team's week goes to Anthropic's API: team name, issue keys and types, story points, epic and initiative names, and computed metrics. No one's name or email is sent, and Anthropic doesn't train on API data. We never sell your data, use it to train models, or combine it with another customer's.
How it's protected
- Every connection is read-only. We can't change anything in GitHub or Jira.
- Everything is encrypted in transit and at rest, and connection credentials are encrypted again inside the app.
- Every request is limited to your workspace, and your workspace has its own telemetry token and webhook secret.
- Sign-in links are single-use and expire in 15 minutes.
The details are on Security.
Where it's kept, and who processes it
In the United States, in Amazon Web Services' Ohio region. Anthropic writes the digests from the summary above. The full list, with what each one receives, is on Subprocessors; we'll email workspace admins 30 days before adding one.
How long we keep it
| What | Kept for |
|---|---|
| Workspace data | While the workspace is active |
| After you close the workspace | Deleted within 30 days |
| Database backups | 7 days, so deleted data is gone from backups within a further 7 days |
| Application logs | 30 days |
Getting your data, or having it deleted
- A copy of your workspace's data: an admin writes to chris@trulyshipped.com and we send it within 30 days.
- Closing your workspace: an admin writes to us. We delete its data within 30 days and confirm when it's done.
- One person's data: someone who wants to see, correct or delete their own data asks their workspace admin, or writes to us directly. We answer within 30 days.
- Stopping a connection: Disconnect on Connections stops new data straight away. What's already synced stays until you ask us to delete it.
- Removing a member: Deactivate on Members signs them out everywhere and stops their email.
Security reviews and questions
We're not SOC 2 audited yet. If your security review needs more than these pages, write to chris@trulyshipped.com and we'll answer your questionnaire. To report a vulnerability, use the same address; we acknowledge within 2 business days.
Stuck? Write to chris@trulyshipped.com and we'll help.