NexusCode Privacy Policy
Effective November 23, 2026
NexusCode sends no usage statistics, analytics or error reports to its developer. The app works without signing in, and then it does not talk to any server the developer runs, except to list the ways to sign in when you open Settings → Remote; that request carries nothing about you or your device. Only when you sign in to a NexusCode account to use remote, voice input, note recording or the mobile app does the information under NexusCode account go through the developer's server (the "server").
What stays on your device
App state such as settings, the workspace list and open tabs, and your notes (text, files, drawings and recordings), are stored only in the app's data folder on this device and in the .nexus-code folder in your home folder. Your sign-in token and account key are encrypted with your operating system's key store (the macOS Keychain, the Windows Data Protection API, a Linux keyring) and stored only in the app's data folder on this device. On Linux without a keyring they are not stored, and are remembered only until the app quits. When you uninstall the app installed from the Microsoft Store, its data folder is removed with it.
Connections made only when you ask
- SSH workspaces: the app connects to the hosts you name and copies the NexusCode agent that remote work needs to your home folder there (
~/.nexus-code). Passwords and key passphrases are used to connect and are not stored. - Git: fetching, pushing and similar operations talk to the remotes you configured. Git (and Git Credential Manager) handles the sign-in.
- Browser tab: the app loads the web pages you open. A search term typed in the address bar, rather than a URL, goes to Google Search.
- Links: links and buttons such as "Download Git" open in your default browser.
NexusCode account
What the server handles when you sign in and use account features.
- Sign-up requests: your first sign-in does not make an account; it leaves a request to join. The request keeps the service you signed in with, your account's identifier at that service, your email address, your name if provided, when you asked, and how many times and when you last tried. If the developer approves it, your next sign-in makes your account. A pending request is deleted 90 days after your last try. A declined request is kept for 30 days, and until then you cannot ask again. An approved request is deleted if you do not sign in within 30 days of the approval, or 30 days after your account is made.
- Sign-in with Google, GitHub or Apple gives the server your email address, your name if provided (on the first sign-in with Apple), and your account's identifier at that service. The server uses these to make your account and keeps them until you delete it. If you choose Hide My Email with Apple, the server stores the relay address as your email address. It keeps any Apple refresh token so it can request revocation when you delete your account. It also keeps your account's status (active or suspended), when it was approved and when it was last used (to the hour) until you delete it.
- Devices: for each device signed in, the server keeps its name (your computer's or phone's), its operating system, when it signed in and when it was last seen (to the hour). A sign-in ends after 30 days unused or 180 days after it was made, and the device's details go with it. A name you gave the device yourself is kept for 180 days after its sign-in ends, so that it comes back if the same app signs in again. Sign-in tokens are stored only as hashes.
- Account password and end-to-end encryption: your account password is never sent to the server. The account key your devices share is locked with it on your device before the server keeps it, and the server cannot open it.
- Remote: what passes between your devices (agent sessions, terminal screens, files, photos) is end-to-end encrypted and relayed by the server. The server can tell only which device it goes from and to, its size and its time; it cannot read it and does not store it.
- Voice input: while you speak, the sound goes through the server to the speech-to-text service Soniox, which transcribes it as you speak. The server does not store the sound or the transcript. It records how long you used voice input. The server keeps the speech recognition words you add until you delete your account. It sends the list to Soniox along with the audio for transcription.
- Note recording: while you record, the sound goes to Soniox and is transcribed as voice input is, with voices told apart so the text is split by speaker (it does not identify anyone). The app also tells the voices apart on your computer by how they sound: it works out a voice print of each line there, which never leaves the computer, is kept in memory only while you record, and is not saved. After the recording, its file may go once more through the server to Soniox for a more accurate text. The file is deleted as soon as its text is ready, the text once the app has it, and both within a day of the file being sent at the latest. Until then the server keeps only the recording's length and how far its transcription is.
- Usage: the time you used voice input and note recording is recorded each month.
- Mobile app: it reads only the photos you choose to attach to chats and notes and sends them end-to-end encrypted to your computer. It uses the camera only to scan QR codes when you link devices. It reads the QR code on the device without saving or sending the camera image. It uses the microphone for voice input. The audio goes through the server to Soniox, as it does on a computer.
- When you turn on push notifications in the iOS app, the server keeps the push token, notification language and kinds with your device's details. When an agent is waiting for approval or an answer, the server can send a notification through the Apple Push Notification service (APNs). It shows only a fixed message such as “A request is waiting for your approval.” Notifications contain no session titles, computer names, commands, paths or conversation content. To prevent duplicates, the server keeps a random identifier for each notification for a day and deletes it at the next cleanup. The server deletes the registration when it processes a request to turn notifications off, a sign-out, device removal or account deletion. It also deletes tokens Apple reports as invalid.
- Operational logs: the server runs on Cloudflare. The app connects to Cloudflare through a relay on AWS Lightsail in Seoul, which keeps no access logs. Records of the requests the Cloudflare server handles (time, path, result and connection details such as your IP address) are used only to find faults and stop abuse, and stay with Cloudflare for a few days. To stop excessive sign-in attempts, the server briefly counts requests from each network.
Soniox does not use the sound or text it receives to train its models.
Admin console
The developer approves or declines sign-up requests and manages accounts in an admin console.
- What it shows: for requests and accounts, the email address, name, sign-in method, status, when the request, account and approval were made, when the account was last used (to the hour), each device's name, operating system and sign-in and last-seen times, the month's voice usage, and states such as whether an account password is set. The developer can add a note of up to 200 characters to a request or an account.
- What it does not show: the admin console does not show remote content, transcribed text, speech recognition words or account keys.
- Suspension: suspending an account signs it out on every device, and it cannot sign in until the suspension is lifted. Its account information and locked account key stay. The developer can also sign an account out on every device without suspending it.
- Deletion: the developer can delete only a suspended account, and deletes it as described under Deleting your account. To keep it from asking to join again, the developer can keep its sign-in service, identifier at that service, email address and name as a declined request for 30 days.
- Admin log: what the developer did (when, to which request or account, and what, with the email address shortened as in ab***@example.com) is kept for a year from when it was done, even if the account is deleted.
Deleting your account
Deleting your account in the app (Settings → Remote) deletes the information above at once, and note recordings and text left at Soniox within an hour. Your approval to join goes with it, so to use your account again you need to ask to join again. So that deleting and re-creating an account cannot reset the usage allowance, only the time used that month stays, with a hash of your sign-in's identifier, until the month ends.
A suspended account cannot be deleted in the app. Ask for its deletion under Contact, and the developer deletes it.
Processors and transfers abroad
While you use account features, the companies below process your information. The Amazon Web Services relay is in Seoul, Republic of Korea. The other companies' servers are outside the Republic of Korea. The information is sent over the network when you use the feature concerned. The app does not send it if you do not sign in or do not use the feature.
The relay decrypts the TLS connection and can see the same information as the Cloudflare server. This includes sign-in tokens, audio and transcribed text, and locked account keys. Remote content passes through with its end-to-end encryption intact.
| Recipient | Role | Location | What it receives | Kept for |
|---|---|---|---|---|
| Amazon Web Services, Inc. | Connection relay | Republic of Korea (Seoul) | The account information and voice data above (relayed only) | Not stored |
| Cloudflare, Inc. | Runs the server and its database | Cloudflare data centers, including in the US | The account information above, and remote's encrypted content (relayed only) | Until you delete your account (sign-up requests and the admin log: as above) |
| Soniox | Speech-to-text | United States | The sound of voice input and note recording, note recordings' files, and speech recognition words | Live audio for the duration of transcription. Files and their text for up to a day. |
| Google, GitHub | Sign-in | United States | You sign in at their service directly | As their policies say |
| Apple Inc. | Sign-in, push notification delivery | United States and elsewhere | Direct sign-in at Apple (the server asks Apple to revoke the token on account deletion) · Phone push token, fixed notification text and kind | Sign-in follows Apple's policy · Push notifications are held for delivery (delivery window set to at most 15 minutes) |
Update checks
The Microsoft Store updates the app installed from it; that app does not check for new versions itself. The macOS and Linux builds read new version information from GitHub Releases (github.com) when the app starts and every 4 hours while it runs; as with any web request, GitHub can see connection details such as your IP address. You can turn automatic checks off in Settings → About. Opening the release notes reads the recent releases from the same place.
Other services
The Microsoft Store, the Apple App Store, Amazon Web Services, Cloudflare, Soniox, GitHub, Google, and the hosts and websites you connect to follow their own privacy policies.
Contact
- Account and privacy questions: support@gradiendo.com
- Bugs and feature requests: https://github.com/moreih29/nexus-code/issues
Changes
If this policy changes, this document is updated along with its effective date.