Privacy policy

The app asks for no sign-up, email or login. You pair the phone with DCC running on your computer, and that computer is what holds your projects, conversations and the agents' work. The Dev Command Center project keeps no database with information about the people who use the app.

When you send a message or an attachment from the phone, it reaches your computer and is handled by the agent you chose there (for example, Claude or Codex), just like a message typed on the desktop. That agent uses the AI provider and account you set up on your computer, under that provider's terms.

Your computer opens an outbound connection to a relay and the phone joins the same room. The default relay is wss://relay.devcommandcenter.com, run by the project on Cloudflare (Workers). Phone and computer run a Noise handshake with each other, and everything after it is end-to-end encrypted (ChaCha20-Poly1305): the relay only forwards ciphertext.

The relay does not see messages, code, responses, attachments or the notification token. What it does see:

• the room identifier (random, 128 bits);
• the IP addresses of the phone and the computer;
• the time and size of each packet.

The relay logs nothing about content, and a room with no connection from the computer for 30 days is deleted. Cloudflare, as the infrastructure provider, processes this network metadata. If you would rather not depend on the project's relay, you can host your own (the code is open, in apps/relay in the repository) and set its address on the desktop under Settings → Connections.

To pair, you scan a QR code shown by the desktop with the camera. The QR code works once, for 5 minutes, and the desktop only accepts the device after you approve the request by checking that both screens show the same code (fingerprint).

The app creates a cryptographic key of its own for the device. The private part stays in the system's secure storage (Keychain on iOS, Keystore on Android), bound to this device and excluded from backups, and never leaves the phone. The computer keeps only the public part, together with the device name (the name the system gives the phone, or its model) and platform, to show in the approval request and in the list of paired devices.

You revoke a device on the desktop under Settings → Connections → Paired devices (Dispositivos pareados). Revoking drops the connection immediately and the revoked key cannot get back in; using the app again requires pairing again.

• Camera: used only to scan the pairing QR code and, if you choose to, take a photo to attach to a message.
• Photos and files: the app opens the photo library or the file picker only when you attach something, and reads only what you pick.

Photos are resized (up to 2048 px on the longest edge) and re-encoded as JPEG; other files go as they are, up to 10 MB each. The attachment travels encrypted, over the same channel, to your computer, which saves it in the temporary folder where DCC keeps pasted images and hands it to the agent along with the message. No attachment goes to Dev Command Center servers.

Dictation uses the system's own speech recognition: Google's on Android and Apple's on iOS. When the Portuguese model is available on the device, recognition happens on the phone; when it is not, the system may send the audio to Google's or Apple's service to transcribe it, under those companies' policies.

The microphone is used only while you dictate. The audio never goes to your computer or to Dev Command Center: only the recognized text lands in the message field, and nothing is sent until you tap send. Microphone and speech recognition permissions are requested the first time you use dictation.

After pairing, the app asks whether it may notify you when an agent needs you. If you accept, the app obtains a notification token from Expo and hands it to your computer over the encrypted channel (the relay does not see it). The computer keeps the token for 48 hours and renews it on every connection.

When an agent asks for permission, asks a question, or a task finishes or is interrupted, your computer sends the notification straight to Expo's push service, which passes it on to Apple (APNs) or Google (Firebase Cloud Messaging). There is no Dev Command Center server in between. For each notification, the computer sends:

• the device token;
• a generic text: the title DCC and a body such as “my-project needs you” or “my-project: task finished” — that is, the project name and the kind of notice;
• the session identifier, so tapping opens the right conversation;
• and, as with any request over the internet, the computer's IP address and the time.

A notification never carries the conversation, commands, file paths or the text of the permission request. You can turn notifications off at any time in the app (Configurações → Notificações deste aparelho) or in the system settings. Turning them off in the app deletes the token on the computer; so does revoking the device. The app's interface is in Portuguese, so the actual notification text is in Portuguese.

Besides updates through the store, the app uses expo-updates to download new versions of its JavaScript code from Expo's EAS Update service. It checks on launch and, when you come back to the app, at most every 30 minutes.

These checks download app code; they do not send your conversations, projects or personal data. The request carries only technical information: platform, runtime version, update channel, the identifier of the version in use, a random installation identifier generated by Expo's library and, if an update fails to launch, the technical error description — plus the IP address and time, as with any request.

The app includes no analytics, advertising, tracking or crash-reporting SDK, does not use an advertising identifier, and does not sell or share data for advertising. The app's code is open and can be checked in the project's repository.

• On the phone: the device key, the pairing data (relay address, room and the computer's public key) and small preferences (notifications, the access level chosen per project, demo mode), all in the system's secure storage. The app keeps no copy of your conversations; they are loaded from the computer while you use the app.
• On your computer: projects, conversations and attachments, as already happens in DCC desktop, plus the paired device record (public key, name, platform, pairing date and notification token) and a local audit log of pairings and revocations, which is not sent to any service.
• With third parties, only what is described above: network metadata at the relay (Cloudflare), the generic notification text (Expo, Apple, Google), dictation audio when the system uses its online service (Google, Apple) and update checks (Expo).

• In the app, Configurações → Esquecer este computador (forget this computer) deletes the pairing from the phone and asks the computer to forget the notification token.
• On the desktop, revoking the device under Settings → Connections → Paired devices (Dispositivos pareados) blocks its key, drops the connection and deletes the notification token.
• Uninstalling the app removes its data from the device. On iOS, the system may keep Keychain items after the app is uninstalled; they stay bound to the device and, once the device is revoked on the desktop, give access to nothing.
• Conversations and attachments stay on your computer, under your control, like the rest of DCC desktop's data.

Since Dev Command Center keeps no data about the people who use the app, there is no account to close and no copy on our side to delete.

The app is a tool for software developers and is not directed at children.

When the app changes how it handles data, this page will be updated and the date at the top will change.

For questions about privacy or this policy, open an issue on the project's GitHub. To report a vulnerability, do not open a public issue; follow the repository's security policy.

• Email: wharleyornelasjs@gmail.com
• GitHub issues
• Security policy
• App support