This privacy policy is a draft for review and isn't in effect yet. Nuko Nova Dynamics LLC will publish the final version here before it applies. Highlighted items in brackets are still to be filled in.
Privacy policy
Draft of November 3, 2026
Who we are
Uplink Room is made by Nuko Nova Dynamics LLC (“Nuko Nova”, “we”). This policy covers the Uplink Room desktop app, the bridge it runs on linked machines, the Room API that the app and agents use, and this website, uplinkroom.com.
Questions about this policy: [privacy contact email], [mailing address of Nuko Nova Dynamics LLC].
The short version
- You sign in with an email address, or with Google, which shares your name, email address and profile picture with us.
- What your team creates in Uplink Room (messages, tasks, files, shared terminals and the rest) is stored so your team can use it. Your team decides who sees it.
- Error reports are scrubbed of terminal text, documents, messages, tokens and email addresses before they leave the app.
- Usage data says which parts of the app get used, never what's in them. You can turn it off in Settings, Privacy, “Share usage data”.
- We don't sell personal information and don't use it for advertising.
What we collect and why
Your account
Sign-in runs on Clerk. With email, Clerk keeps your email address and either a password or the one-time codes it sends you. With Google, Google shares your name, email address and profile picture. We use these to create your account, sign you in, and show your team who you are. Your session is kept on your computer, encrypted with the operating system's keychain; on Linux without a supported keyring, it's kept in memory only and you sign in each time the app starts.
We use information from Google only to sign you in and to show your name and picture to your team. We don't use it for advertising and don't share it with anyone except the service providers listed below that run Uplink Room for us.
What your team creates
The room's data is stored on Convex, in the United States: your team, its members and agents, channels and messages, projects, tasks and runs, files and their comments, saved settings for machines, and the activity log of who did what. Only members of your team can read your team's data, as their role and the team's settings allow.
- Shared terminals. When a terminal on a linked machine is shared, its output and what people type into it pass through the room and are stored with the team's data, so teammates can watch it and see who typed what. [retention period for terminal output and input; the room keeps it until the team or terminal is deleted today]
- Spaces. A Space's screen goes from the bridge on its machine straight to the teammates watching it, on the same network or over Tailscale. It isn't stored by the room.
- Calls. Calls run on LiveKit. No call audio or video is recorded or kept. If someone asks the Notetaker agent to join, it transcribes the call on one of the team's own machines and stores the transcript in the room, where it's kept for 30 days after the call ends. Call notes and the tasks it proposes stay in the channel like any message.
- Shared browsers. A shared browser is a cloud browser run by Hyperbeam. Whoever starts one chooses whether it keeps its logins. Saved logins (cookies, passwords, history and bookmarks) are stored encrypted by Hyperbeam. When they're forgotten, the room stops using them; Hyperbeam deletes a profile nobody has loaded for three months.
- Cloud machines. A cloud machine is a Linux computer on Vercel Sandbox that the room starts and stops for your team. Its disk, with whatever your team keeps on it, is kept while the machine exists.
- Agents over A2A. When you send work to an agent such as Hermes or OpenClaw, the room sends your message to that agent's own gateway, which is run by whoever connected it, not by us. What happens there is up to that gateway and its operator.
- Coding agents. Uplink Room doesn't run agents itself. Claude Code, Codex and the other tools run on your machines under your own accounts with their providers, and those providers' terms and privacy policies apply to what you send them.
Error reports
Installed builds of the app and the bridge send error reports to Sentry so we can fix crashes and bugs. A report holds the error's type and where in the code it happened, the operating system, the app's version, and the member ID of whoever is signed in. It never holds terminal output, file contents, transcripts, message bodies, tokens, your name or your email address, and we ask Sentry not to keep IP addresses or locations.
To turn error reports off, start the app with UPLINK_NO_TELEMETRY=1 (or DO_NOT_TRACK=1) in its environment.
Usage data
Installed builds send usage events to PostHog, such as that the app opened (with its version and the operating system), that you signed in, started a run, joined a call, answered an approval, or opened the Inbox, a file, a Space or a shared browser, and the kind of thing involved, such as which coding agent a run used. Events carry your member ID and your team's ID, never your name or email address, and never what's in messages, terminals, transcripts, documents or web addresses. Screen recordings of a session hide all text and typing and leave out terminals, files, Spaces and shared browsers entirely.
Usage data is on by default. Turn it off in Settings, Privacy, “Share usage data”; that stops it on that computer at once.
Updates
The app checks uplinkroom.com for a new version when it starts and every four hours. Those requests carry what any web request does, such as your IP address, and an anonymous ID the update library keeps on your computer.
This website
uplinkroom.com sets no cookies and runs no analytics. Vercel, which hosts it, processes the request data any website receives, such as IP addresses and browser details, to serve and protect the site.
Who processes data for us
These companies run parts of Uplink Room for us and handle data only to do that:
- Clerk: sign-in and accounts.
- Google: signing in with Google, when you choose it.
- Convex: the room's database and file storage.
- LiveKit: calls.
- Hyperbeam: shared browsers and their saved logins.
- Vercel: this website, app downloads and updates, and cloud machines.
- Sentry: error reports.
- PostHog: usage data.
We may also disclose information when the law requires it, or to protect the people who use Uplink Room. [counsel to confirm wording on legal requests and business transfers]
How long we keep it
- Your account: until it's deleted.
- Your team's data: until the team, or the item, is deleted.
- Call transcripts: 30 days after the call ends.
- Files uploaded but never added: one hour.
- Error reports and usage data: [retention set in Sentry and PostHog]
Your choices
- Turn usage data off in Settings, Privacy.
- Turn error reports off with the environment setting above.
- To see, correct or delete your information, or to delete your account, write to [privacy contact email]. [counsel to confirm which state or national privacy rights apply and how requests are verified and answered]
Security
Sessions and tokens are encrypted on your computer. Agents act through keys with limited scopes and can do at most what the person who added them can. The bridge on each machine enforces that machine's own limits, set by whoever it belongs to. No system is perfectly secure, and we'll tell you if a breach affects your information as the law requires.
Children
Uplink Room is for work teams and isn't meant for children. [counsel to confirm the minimum age]
Changes
When this policy changes, the new version appears here with its date. If a change matters to how your information is used, we'll tell you in the app or by email first.
See also the terms of use.