Privacy
Deft sits between you and the AI tools you already use. That only works if it is obvious what crosses the line and what does not. This page states it plainly, and it describes the system as built — not as intended.
Last updated [DATE NOT YET SET]
Two surfaces, two different answers
The most important thing on this page is that Deft has two places where text reaches us, and they are treated differently. Conflating them is how privacy policies end up untrue.
- Your own AI tools, routed through Deft. When Deft sits in front of Claude, ChatGPT, or Gemini, we do not keep what you write. The content passes through to the provider and is not written to our database.
- Deft’s own chat. When you talk to Deft directly in the app, that conversation is saved so you can return to it later — the same way any chat product keeps your history. You can delete it.
We do not store the content of prompts you send through your own AI tools. Conversations you have inside Deft are stored, because they are the product.
What we collect
| Data | Why | Where |
|---|---|---|
| Account details — name, email, role, team | Sign-in, and matching suggestions to what your role actually needs | users |
| Usage metadata — model used, token counts, timestamp, and a classification of what kind of work the request was | Measuring the gap between how you use AI and what your role needs. This is the product. | prompt_events |
| A 200-character preview, only when our classifier is uncertain (confidence below 0.65) | Reviewing genuinely new kinds of work so the taxonomy can learn them. Confident classifications never store it. | prompt_events.freetext_description |
| Conversations you have with Deft in the app | So your chat history is there when you come back | chat_sessions |
| Integration metadata — calendar and Drive titles and timing, Slack workflow signals | Understanding the shape of your work week when you connect these. Optional. | integrations |
| Error and performance telemetry | Keeping the service working | Sentry |
What we never collect
- The content of prompts or responses passing through Deft to your own AI tools, beyond the uncertain-classification preview described above.
- The bodies of your emails, documents, or Slack messages. Google and Slack integrations request metadata scopes; we do not read message or file contents.
- Anything from your device beyond what your browser sends to load the app.
- Claude Code and Cowork connections never collect prompts, responses, tool inputs or outputs, commands, file paths, or emails (see section 6).
- We do not sell personal data, and we do not use your content to train models.
How long we keep it
| Data | Retention |
|---|---|
| Low-confidence 200-character preview | 14 days, then automatically erased by a daily job. Nothing about it is kept after that except the classification itself. |
| Usage metadata (no content) and the skill evidence derived from it | For as long as your account is active |
| Claude Code / Cowork connection events (no content) | 30 days, then deleted. Only the derived skill evidence above is kept longer. |
| Prompt-ownership records (hashed ids and a date) | 90 days, then deleted. |
| Deft chat conversations | Until you delete them, or until your account is deleted |
| Account details | Until your account is deleted, then removed within 30 days |
| Error telemetry | Per Sentry's retention, currently 90 days |
The 14-day window is enforced in code by a scheduled job, not by policy alone.
What your employer can see
If your organisation provides Deft, your admin sees adoption analytics. By default those are aggregated at team level only. Your individual activity is not visible.
An administrator must turn it on and you must opt in. Either one alone is not enough, and you can withdraw your opt-in at any time.
No employer view exposes prompt content, from either surface, under any setting. Administrators see categories, gap scores, and trends — never what you wrote.
Claude Code and Cowork connections
If you or your organisation connect Claude Code or Cowork to Deft, we collect agent usage metadata only: which kinds of tools were used, whether work ran in the background, and whether skills, MCP tools or subagents were used, plus a one-way-hashed repo context. We do not record the names of skills or MCP servers. The hash cannot be turned back into a repo name or path.
We never collect prompt text, responses, tool inputs or outputs, commands, file paths, or emails. Your email is used once, to match you to a member of your organisation, and is then discarded.
| Data | Retention |
|---|---|
| Normalized connection events (no content) | 30 days, then deleted. |
| Prompt-ownership records — hashed ids plus a date, nothing else | 90 days, then deleted. |
- Pausing collection, per client. You will be able to pause collection for each client from your Deft settings; until that control is available, contact us and we will pause it for you. Pausing Claude Code does not affect Cowork, and the reverse. While a client is paused, its events are dropped and not stored.
- Content capture is rejected. If a host sends prompt content, Deft rejects the whole batch and stores none of it, including any safe records in the same batch.
- Employers see aggregates only. Your employer sees team-level, k-anonymous aggregates, never an individual’s events.
Who else processes your data
| Provider | Purpose |
|---|---|
| Supabase | Database, authentication, file storage |
| Railway | API and AI gateway hosting |
| Vercel | Web application hosting |
| Anthropic | Claude model access |
| OpenAI | Model access and embeddings for search |
| Gemini model access; calendar and Drive metadata if you connect it | |
| Slack | Delivering suggestions and reading workflow signals if you connect it |
| Sentry | Error monitoring |
Where you supply your own AI provider key, requests go to that provider under your own account and their terms apply to that traffic.
Your choices
- See it. Your profile and chat history are visible in the app. Ask us for anything else we hold.
- Delete it. Delete individual conversations in the app, or ask us to delete your account. Deleting an account removes your personal records within 30 days.
- Disconnect. Slack and Google integrations can be revoked at any time in account settings; we drop the stored tokens.
- Opt out of individual analytics. Off by default. If you opted in, you can withdraw it.
Requests go to [privacy@yourdomain]. We answer within 30 days.
Changes and contact
If we change what we collect or how long we keep it, we update this page and the date at the top. Material changes are notified in the app before they take effect.
[LEGAL ENTITY NAME]
[MAILING ADDRESS]
[privacy@yourdomain]