Skip to content

Privacy

Privacy policy

What DevBench collects, why, where it is held and for how long. Written for the people who use the product and the people who buy it.

  • Effective 12 November 2026
  • Last updated 12 November 2026
  • 9 min read

01In short

  • DevBench is a tool for software teams. It processes what it needs to run your workspaces and tell you about them. Nothing is collected for advertising or profiling, and nothing is sold.
  • Two kinds of data, two places. Account data (who you are, which organization you belong to, billing) is held by Vesprr LLC. Workspace data (repositories, chat, notes, recordings, docs, media) is held on the host your organization chose: DevBench compute, or a host you run.
  • Accounts are invite only; a read-only demo needs no account. The product is for organizations and their staff, not the general public, and not for anyone under 16.
  • You can delete your account yourself in any of the apps, ask for a copy of your data, or ask for any of it to be deleted, at any time. See section 10 and Delete your account.

02The mobile and desktop apps

DevBench has an iPhone app, an Android app and a desktop app. They are windows onto the same account and the same organization as the web app; this policy covers all of them. What they reach on your device:

  • Notifications, if you allow them, so a mention, a question from an agent or a finished task reaches you. Your device's notification token is sent to Vesprr LLC for this and deleted when you sign out or delete your account.
  • Camera and photo library, only when you choose to attach a photo or a screenshot to a chat message, and only the pictures you pick. Nothing is read in the background.
  • Files and text you share to DevBench from another app, sent only to the workspace you choose.
  • Your sign-in token, kept in the device's secure storage (Keychain or Keystore).

The apps do not use your location, contacts, calendar or microphone, do not read an advertising identifier, do not track you across other companies' apps or websites, and contain no advertising. To check for app updates, the phone apps contact Expo's update service (section 7), which sees your IP address, the app version and the device platform.

03Who is responsible

The controller for the data described here is Vesprr LLC, 1209 Mountain Road Pl NE, Ste R, Albuquerque, NM 87110, USA, a New Mexico limited liability company. We build and sell DevBench, at devbench.sh.

For anything in this policy, write to hello@devbench.sh. We have not appointed a data protection officer.

When your organization runs DevBench on a host it controls, your organization is the controller for the workspace data on that host and Vesprr LLC is a processor for it, under the data processing agreement.

04Where data lives

DataWhere it is heldWho can reach it
Account data: users, organizations, memberships, roles, invite codes, API keys, billingVesprr LLC's server in the European Union (Germany)You and your organization's owners through the product; Vesprr LLC staff for support and billing
Workspace data: repository clones, branches, chat, notes, task timelines, recordings, docs, media, previews, deploymentsThe host your organization chose: DevBench compute in the EU, or a host you runMembers of your organization by role; Vesprr LLC staff only on DevBench compute, only for support you asked for, and logged
Provider tokens (GitHub, GitLab), cloud credentials, secretsThe same host as the workspace data, encrypted at restNever returned by the API; used by the server to clone, push and deploy on your behalf

On a host you run, your source code, chats and recordings are stored on that host, not on a machineVesprr LLC operates. The processors in section 7 still receive what an agent sends them.

05What we process, and why

Each row is a feature. If the feature is not used, the data is not collected.

WhatWhy
Username, email address, password (as a salted hash)To sign you in and let your team recognize you. The email is for account matters, not marketing.
Your commit email and nameEvery commit a workspace's box makes is authored as the person who asked for it. This is how.
Organization, membership, roleTo decide what you may see and do.
Messages, files and notes in a workspace's chat and timelineTo deliver them to your team and the workspace's agent, and to keep the history.
Repositories, branches, merge requests, tasks, releases, deploymentsTo run the workspaces you create.
Recorded demos and uploaded mediaBecause you or an agent recorded or uploaded them for the workspace.
Photos, screenshots, files and screen recordings you attach to a messageTo deliver them to your team and the workspace's agent. Only what you pick is sent.
Push notification tokens, device platform and nameTo reach the right handset, and to show you which devices are registered.
Error reports from the apps: what failed, where in the app, and the error messageSo a failure in the app reaches the team and gets fixed. They are not used for anything else.
The audit log: sign-ins and actions taken in a workspaceSecurity, troubleshooting, and so a team can see who changed what.
The text on a box's terminal screen, with obvious secrets maskedOnly if your organization turns on box health: to judge whether the agent is stuck and which key frees it. The screen is sent to TypeSafe AI (section 7); DevBench keeps a hash of it, not the text, with what was decided and pressed.
The text and controls of your own preview's pages, when the AgentReview Explorer walks it; a task's description and the agent's note when a finished task is checkedTo judge what a first-time user would run into, and whether a task the agent finished is really done. Sent to TypeSafe AI (section 7); the walk's report stays in your workspace.
Usage: agent spend and compute minutes per workspaceTo show the Usage page and, on paid plans, to bill.
Billing name, address, VAT ID, invoicesTo invoice your organization, as tax law requires. Card details are held by the payment provider, not by us.
An access request from this site: email, name, team size, repositories, where it should run, plan, message, the page it was sent from, a hash of the IP addressTo reply, and to spot one address submitting the form in bulk. The IP is stored only as a salted hash.

We do not collect location, contacts, calendars, microphone audio or an advertising identifier, and we read photos and the camera only as section 2 describes.

06Legal bases

  • Contract (Art. 6(1)(b) GDPR): running the account and the workspaces your organization asked for, and replying to an access request.
  • Legal obligation (Art. 6(1)(c)): keeping invoices for the period tax law requires.
  • Legitimate interest (Art. 6(1)(f)): the audit log, rate limiting, abuse prevention and cookieless site analytics. You can object; see section 10.
  • Consent (Art. 6(1)(a)): only where we ask for it, such as a product update mail. Withdraw it any time.

07Subprocessors

We use a small number of processors, each for one job. None may use your data for its own purposes. The list is kept current here; customers on a data processing agreement are told of changes in advance.

WhoWhat forWhere
Contabo GmbHRuns the servers that hold account data and DevBench compute.Germany (European Union)
Amazon Web ServicesHosts this website and the DevBench web app. It serves pages and files; it holds no account data.United States
StripeCheckout, invoices and card storage for paid plans.United States
Plausible AnalyticsCookieless visit counts for this website, when enabled: no cookies, no personal data, IP addresses not stored.European Union
Expo (650 Industries)Delivers updates to the iPhone and Android apps. Sees the IP address, app version and platform of a phone checking for one.United States
Google (Firebase Cloud Messaging), Apple (APNs)Deliver push notifications to phones. They receive the notification content and the device token.United States
Anthropic (Claude Code)In a workspace that runs Claude Code, the agent sends prompts, and the code it reads, to Anthropic's models, on the account your organization added.United States
OpenAI (Codex)In a workspace that runs Codex, the agent sends prompts, and the code it reads, to OpenAI's models, on the ChatGPT sign-in or API key your organization added.United States
TypeSafe AIA model provider behind three features: box health (only if your organization turns it on; the text on a box's terminal screen, obvious secrets masked), the AgentReview Explorer (your preview's pages as it walks them) and the check of a finished task (its description and the agent's note). It returns a decision; it does not keep or train on what it is sent.Given on request

Your git provider (GitHub or GitLab) and any cloud you deploy to (AWS, Hetzner, DigitalOcean, Vultr) are not our subprocessors. They are yours: you hold the account, and DevBench acts on it with credentials you gave.

08How long we keep it

  • Account data: while the account exists. Deleting your account deletes it at once; backups roll off within 90 days. What you wrote in a team's chat and task notes stays with the team as “Former member” unless you ask for it to be deleted (Delete your account).
  • Workspace data on DevBench compute: while the workspace exists. Deleting a workspace deletes its box, its volume and its media. Organization backups are yours to delete.
  • Workspace data on a host you run: your retention, your backups. We hold none of it.
  • Audit log: 12 months.
  • Invoices: for as long as tax law requires.
  • Access requests from this site: 12 months after the last contact, then deleted.

09Transfers outside the EU

Account data and DevBench compute are in the European Union. Where a subprocessor above is outside the EU, the transfer rests on the European Commission's standard contractual clauses or an adequacy decision, and we can show you the mechanism on request.

10Your rights

Under the GDPR you can ask us to:

  • tell you what data we hold about you, and give you a copy (access, portability);
  • correct it;
  • delete it, where we have no legal reason to keep it;
  • restrict or stop processing it, including any processing based on legitimate interest;
  • withdraw consent you gave.

You can delete your account yourself at any time: in the phone apps under You, Delete my account; on the web and desktop under Preferences, Your account. For anything else, or if you cannot sign in, use the form on Delete your account or write to hello@devbench.sh. We answer within one month. You can also complain to the data protection authority of the EU or EEA country where you live or work, and, if you live in California, you have the rights the CCPA gives you, which we honour the same way. We do not sell or share personal information.

When your organization is the controller (workspace data on its own host), send the request to your organization's owner; we help them answer it.

11Cookies and analytics

This website sets no cookies. When enabled, it counts visits with Plausible, which sets no cookies and stores no personal data. No analytics runs in the product or the apps. If we turn on Google Analytics or Mixpanel, which set cookies and identifiers, we will ask for your consent first and update this section and the date above before they run.

The product sets one session cookie or holds one token to keep you signed in. Signing out removes it.

12Security

Provider tokens and secrets are encrypted at rest and never returned by the API. A person merges by default; an owner can allow self-merge on one workspace, and each one is announced. Pushes to protected branches are refused. Actions in a workspace are in the audit log. The security pagedescribes the hosting model and how to report a vulnerability.

13Changes to this policy

When this policy changes, the date at the top changes with it and the previous version stays available on request. A change that affects what we collect or why is announced to organization owners by mail before it takes effect.

14Contact

Vesprr LLC, 1209 Mountain Road Pl NE, Ste R, Albuquerque, NM 87110, USA.
hello@devbench.sh for anything about your data.
security@devbench.sh for a vulnerability report.