Privacy

The short version

DevTee is a measurement tool. To measure your computer use it captures your computer use — including the keys you press and the text those keys produce. If that's not a trade you want to make, DevTee is not the product for you. The rest of this page spells out exactly what leaves your machine, where it goes, and how to turn it off or scope it down.

What the desktop client captures

On a Mac you've installed DevTee on, the client may capture all of the following and send it to DevTee's servers:

• Keystrokes. The key code, the canonical key name (e.g. KeyA, Enter), modifier flags, key-down vs. key-up, the millisecond offset within the capture interval, and — under the default capture mode — the literal UTF-8 text the keystroke produced. That includes prose you type into editors, chat windows, search bars, terminals, and password fields.
• Active app and window. The foreground application's name and bundle identifier, and the title of the active window. Window titles routinely contain URLs, document names, email subjects, message recipients, terminal commands, and (for tools like Claude Code) the description of the task you're currently working on. DevTee does not strip these.
• Mouse activity. Cursor position in screen coordinates, clicks, scroll deltas, and modifier flags.
• Device and session metadata. A stable per-machine identifier generated on first run, the OS version, and the DevTee client version. A new session identifier is generated each time the app launches.
• Liveness heartbeats. Periodic timestamps so the dashboard can tell when a device is online.

DevTee does not capture screen contents, the clipboard, the contents of files you open, microphone, camera, or network traffic. It does not run keystroke or screen capture on machines you have not installed the client on.

Capture modes and redaction

Every event the client emits carries a capture mode. There are three:

• Full. Keystroke text, window titles, and mouse positions are sent as captured. This is the default.
• Count only. Only the per-interval keystroke count is sent. Individual keystrokes and their text are dropped on the device before upload. Window titles and app context are still sent.
• Ignore. The event is reduced to a placeholder. Keystroke counts are zero, the keystroke array is empty, and the window title is replaced with <redacted> before upload.

You can scope down capture per app (by bundle identifier) or per window title (by regular expression). The most restrictive matching rule wins. Resolution happens on the device, before the event is sent — DevTee never receives the redacted content.

You can also pause capture entirely from the menu bar at any time. Quitting the app stops all capture.

Where data lives

Events are uploaded over TLS to DevTee's API and stored on infrastructure operated by Center Pixel, Inc. in the United States. Storage and compute run on Center Pixel-managed Kubernetes and Postgres — not on a third-party hosted database. DevTee does not sell your data and does not share it with advertisers or data brokers.

Who can see your data

You can see your own data. If you've joined a Team, the team owner can see the data of members they administer; that is the entire point of joining a Team and you should not join one if you don't want the owner to see what you're working on. Center Pixel employees can access stored data when required to operate the service, investigate abuse, or comply with legal process; access is logged.

Your data, your control

From the dashboard you can export your account's data, delete specific time ranges, or delete the account in full. Deletion propagates to backups within 30 days. Team owners can do the same for members they administer.

What we ask of you

Don't install DevTee on a machine you don't own or aren't authorized to monitor. Don't deploy it on a teammate's machine without their informed consent — the desktop client is designed to be visible (menu bar icon, capture indicator) precisely so that consent is observable. Treat passwords and sensitive prose accordingly: if you'd rather DevTee not see them, configure a per-app or per-window rule before you type them.

Contact

Questions about privacy go to hello@devtee.com. DevTee is operated by Center Pixel, Inc., in San Francisco.