Droidex Privacy Policy

Data Handled

Droidex may handle:

• Pairing credentials, including relay URL, realm id, Mac device id, and pairing secret.
• Project names and paths received from the paired Mac.
• Thread titles, prompts, responses, tool output, settings, and account or rate-limit summaries received from the paired Mac.
• Optional images or project files that the user explicitly attaches to a Codex request.
• Relay routing metadata, including realm id, device id, IP address, connection timing, and encrypted frame sizes.

Google Play may describe data as collected whenever it is transmitted off the Android device. Under that definition, Droidex transmits this data only to provide remote-control features requested by the user. Droidex does not use it for advertising or profiling.

Storage

The Android app stores the saved pairing payload locally with Android Keystore-backed AES-GCM encryption. Background relay status, notification state, and a generated background device id are stored locally in app-private storage. Pairing and relay state are excluded from Android backup and device transfer rules.

The iOS app stores its saved pairing payload in Keychain-backed local storage and app-private preferences. Pairing, relay state, Live Activity state, and local notification state are used only to operate the user's paired Droidex session.

The Mac sidecar stores its relay URL and pairing secret in user-only files when installed as a LaunchAgent. Sidecar project aliases, hidden projects or threads, and per-thread mobile settings are stored locally on the Mac.

Transmission

Prompts, responses, settings, tool output, and attachments are sent between the mobile app and the Mac sidecar inside end-to-end encrypted envelopes. The relay routes these envelopes and does not need access to plaintext Codex contents.

The relay operator may still see operational metadata such as source IP address, connection times, realm ids, device ids, and encrypted message sizes. Users should run the relay themselves or use a relay operator they trust.

The relay can temporarily buffer a limited number of end-to-end encrypted envelopes in memory when a target Mac is offline. Buffered envelopes are removed after delivery, when displaced by queue limits, or when the relay process restarts. The repository relay does not persist plaintext Codex content.

Android Permissions and Background Features

• Camera access is requested only when the user chooses to scan a Mac pairing QR code.
• Notification access is used for active work, approval requests, background relay status, and the optional outside-app Codex pet.
• The remote messaging foreground service runs only when the user enables background relay listening and can be stopped in Droidex Settings.
• Display over other apps access and the special-use foreground service are used only after the user explicitly enables the optional outside-app Codex pet. The pet does not read or interact with content from other apps and can be stopped from Settings or its persistent notification.
• Boot completed access restarts user-enabled background features after a device reboot.

Third Parties

The current app build does not include advertising SDKs or third-party analytics SDKs. Droidex does not sell personal data.

The Droidex website uses Vercel Web Analytics to count page views and visits to the APK download page. These website analytics are used to understand launch traffic and do not include Codex prompts, project contents, or mobile app activity.

Codex requests are ultimately handled by the user's installed Codex environment and whatever model provider or account that environment is configured to use. Those provider relationships are controlled by the user's Codex setup, not by Droidex.

User Controls

Users can:

• Remove the saved mobile pairing with the Forget saved pairing action.
• Disable background relay listening without deleting the saved pairing.
• Rotate the Mac sidecar pairing secret and re-pair the mobile app.
• Stop or uninstall the Mac LaunchAgent.
• Delete the app to remove local mobile app-private data.

Retention and Deletion

Pairing credentials, cached workspace information, preferences, and notification state remain in app-private storage until the user forgets the pairing, clears app data, or uninstalls Droidex. Mac-side settings remain on the user's Mac until removed by the user. The repository relay stores queued encrypted envelopes only in process memory as described above.

Droidex does not maintain a separate cloud account database for the mobile app. Codex conversations, projects, or account data managed by the user's Codex environment must be deleted using that environment's or provider's controls.

Support

Visit droidex.app/support for setup help and issue reporting.