Short answer: no product analytics or telemetry. Your data lives in your own instance, leaves it only for the providers your admin configures, and you can export or delete it at any time.
01Who is responsible
This website: [Legal entity name] is the controller of the little data this site handles.
The hosted Service: your organisation is the controller of the data in its DevHub instance. We are the processor: we host the instance and process the data only on your organisation's documented instructions (these policies, the Terms and the DPA).
Self-hosted installs: your organisation is the controller and the operator. The data stays in your environment and we have no access to it. The software does not call home.
Privacy questions: [Contact email].
02This website
- This site uses cookieless, aggregate page-view analytics from Vercel (pages viewed, referrer, country, device type). It sets no advertising or tracking cookies and does not profile you.
- If you contact us or book a demo, we use your name, work email, company and message to reply and to arrange the demo, and keep them for as long as the conversation is relevant.
03No product analytics or telemetry
The DevHub product has no product analytics, telemetry or advertising trackers. It records its own usage (who used which feature, which provider, what it cost) inside your instance so your admins can see and cap costs. On the hosted Service the licence check receives only whitelisted aggregate counts: no names, emails, code, tickets, URLs or settings.
04What the Service stores
To show your work, an instance stores real content from your tools in its own data store, on your server or your isolated hosted instance:
- a cache of tracker and code-host data (ticket titles, statuses, comments, assignees; PR titles, authors, reviewers);
- a code index (paths and symbols; code chunks only when remote content indexing is on);
- review findings, with snippets masked and secret values never stored;
- pages and incidents, which can hold your end customers' data if you put it there;
- finance and cost data, when you connect those tools;
- encrypted credentials, a usage log, audit logs, preferences, notifications and mentions;
- assistant conversations, private to the person who had them and encrypted at rest.
Secrets (API keys, tokens) are stored encrypted with AES-256-GCM, are never shown back in full, exported or sent to AI.
05Why, and on what basis
Data is used to provide the Service: show plans, code, quality and operations, send the alerts people chose, run the features they start, keep an audit trail and enforce cost caps. The legal bases are performance of the contract with your organisation and our legitimate interest in operating and securing the Service.
06What leaves your environment
Nothing leaves an instance except:
- prompts to the AI provider your admin configured, within the data classes your admin allowed;
- emails and chat messages to the recipients and channels your admin set up;
- reads from your connected tools, and writes to them only after a preview and a confirm;
- dependency names to the public npm registry, for the dependency audit;
- public pages an admin listed for competitor watch or accessibility audits (off by default);
- on the hosted Service only, the licence check and an aggregate heartbeat (counts, nothing identifying).
The third parties involved for the hosted Service are listed on the Subprocessors page.
07AI
AI is optional and can be switched off. Admins decide whether code excerpts, issue text and customer data may be sent; each stays off until an admin allows it, emails are masked when customer data is off, and secrets are always masked. The AI provider's terms decide whether it may keep or train on prompts: choose a provider and plan that does not. Free AI tiers may use what you send to improve their models, so use them for testing and demo data only.
08How long data is kept
| Data | Kept for (default) | Applies to |
|---|---|---|
| Tool cache | 30 days | Cached tracker and code-host data, refetched when needed |
| Alerts and delivery state | 90 days | Bell alerts, digest and delivery records, read marks |
| Proposed actions and runs | 30 days | Actions the assistant proposed, AI review runs |
| Usage and cost log | 400 days | Who used which feature and provider, and what it cost |
| Metric history | 400 days | Daily metric snapshots and uptime history |
| Audit logs | 365 days | Sign-ins, permission and settings changes, writes, data requests |
| Workspace content | Until deleted | Pages, findings, indexes, saved views |
| Configuration and accounts | Kept | Settings, users, encrypted credentials, licence |
Admins can change these periods. A nightly job deletes what is older. Private conversations are kept 90 days by default. When a subscription ends, the remaining data, including backups, is deleted within 30 days.
09Your rights
- See and take your data: in the product, Help, then Your data, then Export my data downloads everything stored about you.
- Delete your data: Delete my data removes your preferences, notification state, proposed actions, private conversations and personal keys, and anonymises your usage records. Audit entries and your terms acceptance are kept as a security record for the audit retention period.
- Your organisation's admins can do the same for any person, and export or delete everything at offboarding.
- You can also ask [Contact email] to correct, restrict or object to processing, or to receive a copy, and you can complain to your data-protection authority. For data in an organisation's instance, we pass requests to that organisation, which decides as controller.
10Where data is hosted and transfers
Hosted instances run on Vercel (application hosting) and Neon (managed PostgreSQL database), in the United States (us-east-1); other regions on request. Transfers outside that region (for example to an AI provider) rely on the European Commission's Standard Contractual Clauses or another lawful mechanism, where required.
11Security
Each customer has an isolated instance with its own data store and encryption keys. Connections are read-only by default, every write is previewed, confirmed and audited, and vendor support access is time-boxed and only with your owner's consent. A personal-data breach is notified without undue delay and within 72 hours of becoming aware of it.
12Changes
When this policy changes materially, we update the date at the top and tell customers in advance.
Questions about this page: [Contact email]. [Legal entity name], [Registered address].