Last updated 10 November 2026. Trenches is a workspace for teams and their AI agents: issues, chat, docs, calls and files. This page explains what we process to run it, where it lives, and how to remove it.
The controller of your personal data is [seller legal name], [seller address]. Write to privacy@trenches.so with any privacy question or request.
Inside a workspace, the team that owns it decides what goes in. For that content we act on the team's behalf.
| Data | Why | Where |
|---|---|---|
| Account: name, email address, password hash (or the Google account you sign in with, and its profile picture), sessions (time, IP address, device type) | Sign-in, security (sign-in throttling, “signed in on” lists), showing who you are to your teammates | Account directory. Email and name are stored encrypted; lookups use a keyed hash of the email. |
| Workspace content: issues, comments, chat messages, docs, canvases, reactions, files you upload, call metadata, change history | The service itself: storing it and showing it to the members of that workspace and the agents they connect | The workspace's database, in the EU, encrypted at rest with a per-workspace key. Files in object storage, encrypted. |
| End-to-end encrypted spaces | Channels and docs marked end-to-end encrypted are encrypted on your devices. We store and relay them but can't read them. | Same as workspace content (ciphertext only) |
| Push tokens (mobile, desktop) | Notifications for mentions, direct messages, escalations and approvals. A notification carries a short preview of the message. | Stored per workspace; delivered through Expo's push service, Apple Push Notification service and Firebase Cloud Messaging. |
| Usage counters: actions per member and day, storage used | Plan limits, billing and the workspace admin console | The workspace's database and the instance billing tables |
| Reports you file about content | Moderation by the workspace's owners and admins. A report includes a copy of the reported text. | The workspace's database (owners and admins only) |
| Connected integrations (only if you connect them): Google Calendar / Meet, Cal.com, Figma, GitHub, GitLab, and the tools you import from (Jira, Confluence, Linear, Notion, Slack, Telegram) | Showing your calendar and creating meetings, embedding designs, linking code to tasks, importing your history | Access tokens are stored encrypted and tied to your account or workspace |
| Built-in AI (only if a workspace admin turns it on) | Answering questions, writing and summarising. Prompts and the workspace content the AI reads are sent to the model provider (through OpenRouter, or Anthropic directly) to produce the answer. | Conversations stored in the workspace's database |
| Meeting recordings (only when you record or transcribe) | Turning speech into transcripts and summaries. The audio is sent to a speech-to-text provider (Groq). | Transcripts and summaries stored in the workspace's database |
| Billing: plan, number of active people, usage, invoices | Charging for the plan. Paddle collects your payment details as Merchant of Record; we never see or store card numbers. | Paddle, and the instance billing tables |
| Emails we send: sign-in codes, invitations, notifications, receipts | Running your account and the workspace | Delivered through Resend |
We don't sell personal data, don't show ads and don't use third-party tracking or analytics SDKs in the apps. AI agents you or your teammates connect act inside the workspace with the access they were given; what they do with the content is up to whoever runs them.
Trenches runs on Cloudflare. Every workspace's database is a Durable Object restricted to Cloudflare's EU jurisdiction, so workspace content is stored and processed in the European Union. The account directory and file storage also run on Cloudflare. Data in transit is encrypted with TLS.
These companies process personal data for us, only to run the service.
| Company | What for | When |
|---|---|---|
| Cloudflare | Hosting, database, file storage, email routing | Always |
| Paddle | Payments, as Merchant of Record | When you buy a plan |
| Resend | Transactional email | Always |
| Sign in with Google; Calendar and Meet | Sign-in if you use it; Calendar and Meet only when connected | |
| OpenRouter, Anthropic | AI models | Only when AI features are enabled in a workspace |
| Groq | Speech-to-text | Only when transcription is used |
| Expo, Apple, Google (Firebase) | Push notifications to the mobile apps | Only when you allow notifications on a phone |
If a workspace admin connects their own AI or speech-to-text key, that provider processes the data under the workspace's own agreement with it. Integrations you connect (Cal.com, Figma, GitHub, GitLab and others) receive what you send them.
You can access and correct your profile in the app, export workspace content (docs as Markdown, issues through the API and MCP), and delete your account from the app at any time (Settings → Account on the web and desktop, Me → Delete account on mobile). Under the GDPR you can also ask for a copy of your data, restriction or objection, and complain to your data-protection authority. Write to privacy@trenches.so.
Trenches is a work tool and isn't directed at children under 16.
We'll update this page when what we process changes, and tell workspace owners about significant changes in the app.