Legal
This policy explains what information atrium collects through the website, the desktop app, the iOS and iPadOS app, and the push relay, how that information is used, and what choices you have.
Last updated: November 3, 2026
This policy applies to the atrium website at getatrium.dev, the atrium desktop app, the atrium iOS and iPadOS app, the atrium push relay at push.getatrium.dev, and the public feedback tracker linked from the site.
atrium is operated by Skybot, LLC. This policy is written to describe the product as it exists today. If data practices change, this policy will be updated.
We currently collect or process the following categories of information:
atrium is designed to keep core workspace and session state on machines you control. Local state stays on your Mac or Windows computer. When you add a Linux location, the app connects directly over SSH and that box stores its repositories, terminal sessions, scrollback, tasks, notes, and related configuration. atrium does not proxy that traffic or copy those repositories through an atrium-operated server.
Agents and AI providers have their own network connections. When you use one, prompts and the context the agent needs can be sent to the service you choose, under that service’s data practices. Custom provider definitions are saved in app state; their API keys are stored separately in your operating system’s credential store. atrium supplies the credential to the agent runtime or uses it to authenticate requests to the configured provider.
The iOS app connects directly to the machines you pair it with, over your own network or your own tailnet. Conversations, terminals and approvals travel between your phone and your machine; they don’t pass through an atrium server. Current versions of the iOS app encrypt that connection with TLS 1.3 and accept only the paired machine’s own key, so another device on your network can’t read the traffic or pose as your machine. Your phone learns that key from the pairing code or, if it was paired before this encryption existed, the first time it connects after you update. Pairing keys are stored in your phone’s Keychain and on the paired machine.
Messages, photos and dictated text you send from the atrium iPhone or iPad app go only to the computer you paired it with. If you run an AI agent there, such as Claude Code or Codex, that agent may send them to its AI provider, such as Anthropic or OpenAI, under your own account and that provider’s terms. atrium has no AI service of its own, and neither the app nor atrium’s servers receive or store your conversations. The app tells you this and asks for your agreement before the first message leaves your device.
The first time the iOS app needs its natural voices (Settings → Walk Mode → Voice), it downloads their voice model and pronunciation files once, from third-party model hosts such as Hugging Face and GitHub. As with any download, those hosts see your device’s network address and a standard request, such as the app’s user agent. No conversation content, pairing information or account data is sent. You can delete the downloaded files in Settings → Walk Mode → Voice → Delete voice data.
atrium sends a small amount of telemetry in two tiers. The core tier is on unless you choose Send nothing, and is limited to update and app-lifecycle events — including a periodic active-use heartbeat (version, OS, architecture, locale) that fires only while the atrium window is focused — and daily counts (how long the background service ran, how many directors and routines exist, and how many crashes occurred), never names or content. The optional analytics tier covers feature usage, performance counters, and crash stack traces, and is off until you opt in. Both tiers exclude file contents, command history, pane contents, browser URLs, and agent transcripts; the master switch disables both. Usage events go to PostHog and crash reports go to Sentry. Full details and the opt-out controls live in the telemetry documentation.
Optional performance recordings and support bundles stay on the machine until you share them. The recorder is off by default, has a time limit you can choose, and stops at 500 MB per trace. atrium retains the newest five recorder traces within a combined 2 GB budget. Manual bundles and profiles are outside that limit. Local logs and diagnostic fields can contain identifying details; review them before sharing them or posting a public issue.
Push notifications are optional, and the iOS app offers them only once it is paired with at least one machine. When an agent needs you and you aren’t using atrium on your phone or on your Mac, the Mac the agent runs on can send your phone a notification. Apple delivers notifications to iPhone and iPad apps only through its Apple Push Notification service (APNs), and only for a sender holding atrium’s APNs key, so your Mac hands each notification to a small relay we run, which passes it to Apple. In this section, “phone” also means an iPad running atrium.
Notifications are end-to-end encrypted. When you turn them on, your phone and each paired Mac agree on a key over the encrypted connection they already share; the key itself is never sent over any network. Your Mac encrypts each notification (such as the agent, project and command) before it leaves, and only your phone and that Mac hold the key.
Live Activities use the same relay to show agent progress and pending approvals on the Lock Screen and Dynamic Island. Their contents are encrypted before leaving your Mac, under a separate key derived from the notification key. Your phone stores that derived key where its widget extension can read it. The derived key cannot open ordinary notifications. Approval actions travel directly from your phone to the paired Mac, not through the relay.
To decide whether you’re using atrium on your Mac, atrium notes when you last clicked, typed, scrolled or moved the mouse in one of its windows there. Input in other apps doesn’t count. That time stays on the Mac and is never sent anywhere.
What the relay receives:
For Live Activities, the relay also receives Apple’s activity start or update token, whether a request starts, updates or ends the activity, its timestamp, whether it should alert, and any dismissal time. Activity contents are padded to a fixed size. Silent updates use a lower delivery priority than starts and alerts. The relay and Apple can see this delivery metadata and timing, which can suggest activity changes even though they cannot read the encrypted agent details.
About every few days your phone asks the relay for a new delivery pass. The relay sends the pass back to your phone through Apple, never in its reply, so only your phone can obtain one. Your phone gives passes only to Macs you still have paired, and each pass expires after 14 days.
The relay forwards each notification to Apple and reports whether Apple accepted it. It doesn’t store push tokens, delivery passes or notification contents. Its rate limits count requests per network address, and per phone using a one-way hash of the push token, for at most ten minutes. It has no user accounts and is not used for analytics or advertising. Apple receives your push token, delivery passes and the encrypted notifications in order to deliver them, under Apple’s own privacy policy.
You can turn notifications off in the atrium app (Settings → Notifications), in iOS Settings → Notifications → atrium, or for one device on your Mac (Settings → Remote access → Phones & tablets). Revoking your phone on a Mac stops that Mac’s notifications immediately. Removing a Mac from your phone deletes the key on your phone right away, and on the Mac too if it’s reachable. A Mac that can’t be reached may keep sending for up to 14 days, until its last delivery pass expires; your phone can’t open those notifications, so they may appear as a generic “New activity from your agents” alert. When no paired Mac is left, the app turns push notifications off and deletes its push token, delivery pass and keys.
We may share information with a small set of third parties that help operate atrium:
We may also disclose information if required by law or if needed to protect users, the service, or our rights.
~/.atrium/ directory.Website analytics is retained only as long as reasonably needed for product and site operations. Content you submit to GitHub is subject to GitHub’s own retention and visibility model. Local app data remains on its owning machine until you delete it or the app removes it.
The push relay keeps no copy of push tokens, delivery passes or notifications. Our hosting provider, Vercel, keeps request logs (the time, the requesting IP address, the user agent, the path and the result) for about a day for operations and security, under its own policies. The relay keeps push tokens and notifications out of its own log lines, but a push token may still appear in those hosting logs; if it does, it is deleted with them. A paired Mac keeps your phone’s push token, delivery pass and notification key until you turn notifications off, remove the Mac from your phone, or revoke the phone.
atrium is not directed to children under 13, and we do not knowingly collect personal information from children under 13.
We may update this policy as atrium evolves. Material changes will be reflected by updating the date at the top of this page.
For private questions or privacy-related requests, email sup@getatrium.dev.
For public bug reports and product feedback, use the public feedback tracker.
You may also want to review our Terms of Service.