What this notice covers
This notice describes Atom’s macOS beta, its production account service, and this website. Atom processes speech on your Mac, but it is not an entirely offline service: beta sign-in uses an online account, and external assistant providers process the content you send them.
The public website previews the product. Invited beta users sign in through the Atom app; this site does not offer public downloads or account registration.
Your account and Google sign-in
The production beta requires an Atom account. Sign-in runs through WorkOS AuthKit. If you choose Google, Google and WorkOS handle basic identity, email, and profile information to authenticate you. Atom uses the resulting identity to create and secure your account, recognize your signed-in devices, and provide trial and license access. Hosted sign-in pages may use cookies or similar storage to complete and secure sign-in.
The Google connection requests basic profile and email access, not access to your Gmail messages, Drive files, or Calendar. WorkOS is configured not to return Google OAuth tokens to Atom. This sign-in connection does not give the assistant access to those services; tools or agents you connect separately have their own permissions.
Our account database stores your email address and verification status; Atom, WorkOS, and sign-in-provider identifiers; account creation and update times; and linked device records. Device records include a generated identifier, device type, a label that can be your Mac’s computer name, sign-in and last-seen times, session identifiers, revocation status, and refresh-token hashes. We also store trial dates and license entitlements.
Cloudflare Workers runs the account service at api.heyatom.ai, with records in Cloudflare D1. Short-lived sign-in and recovery records support authentication. Hashed source IP addresses, request times, and attempt counts help limit abuse. Hosting and authentication providers also receive normal connection information, such as IP addresses and browser or app information.
On your Mac, Atom stores account credentials and session information in macOS Keychain. Signing out of the app and deleting an account are different actions; signing out does not delete the server-side account.
Speech and files on your Mac
Speech recognition runs on-device. Dictation, selected-text editing, and on-device correction do not send microphone audio to the Atom account service. Local text-to-speech generates spoken replies on your Mac.
Atom can save dictation and assistant history, settings, Dictionary entries, and other working files locally. Meeting folders can contain transcripts, notes, speaker labels, names you enter, saved note versions, and screenshots you capture. These are ordinary files in your selected vault. A folder you place in iCloud Drive or another synced location is subject to that service’s behavior.
Vocabulary and context features can read nearby text or information about the active app through macOS permissions. Assistant tools can access additional content, including files or screen images, when used for a task. See the next section for external-provider processing.
If you enroll your voice for Ambient listening, Atom stores voice embeddings and associated microphone information locally to help distinguish you from other speakers. These are derived voice characteristics, not just a text label. The owner profile can learn from subsequent hotkey dictations. This profile is separate from development-only cross-meeting speaker-memory features.
Removing an Atom account does not erase files, histories, voice profiles, backups, or provider sessions on your Mac. Manage local content separately in the app or its storage locations. Obtain any permission required before capturing or processing another person’s speech or meeting content.
When content leaves your Mac
When you use an external assistant, writing, correction, or meeting-processing provider, the relevant text and instructions go to that provider. Depending on the feature and tools used, requests can include conversation history, selected or nearby text, vocabulary hints, meeting content, files, or screen images. Providers such as Claude, Codex, Cursor, and OpenCode use their own accounts, tools, and service policies. A configured local API can also point to another computer.
Ambient listening uses TypeSafe’s Jev decision service to help decide whether speech is addressed to the assistant. Requests include text and recent conversational context, the assistant’s state, and active app or window information. Guest settings affect which other speakers’ words are included. This decision path sends text, not microphone audio.
With your own TypeSafe key, requests go directly to TypeSafe. Where the licensed relay is available, they pass through Atom’s Cloudflare relay at jev.voicemode.io. The relay validates a license key and activation identifier with Polar to issue a short-lived token. It forwards decision requests and records operational metadata such as a pseudonymous credential identifier, route, outcome, timing, and model. Its application code does not store decision request or response bodies. An Atom account by itself does not currently provide this relay access.
Signing in with Google is not consent to send all local content to an AI provider. The features and providers you use determine those transfers. Review their settings and privacy policies before sharing sensitive material.
Licenses and payments
If you link an existing license, the account service sends the license key to Polar for validation and records a key hash, Polar identifiers, the linked account, plan, status, and relevant dates. Claim attempts and conflicts are recorded for abuse prevention and support. Direct license activation can also send Polar a device label and activation identifier.
Payments and license records are handled by Polar. Atom’s account database does not collect card numbers. The current production account beta has automatic purchase synchronization disabled; this website does not offer checkout. This notice does not announce payment availability.
Website, updates, and support
Cloudflare hosts the website and delivery infrastructure. Visiting this site or requesting an update, app download, or model file exposes normal network metadata to the hosting service. This website also loads General Sans fonts from Fontshare, whose servers receive the font requests.
The delivery Worker derives limited request analytics from download, update-feed, and model-catalog requests. Depending on the request, records include time, file path, app version or user agent, coarse country, source or referrer information, network provider, and a salted IP hash rather than the raw IP address in those analytics tables. These are delivery records, not a copy of your dictation history. The app can contact legacy voicemode.io delivery services as well as heyatom.ai services.
If you contact support or privacy, your message, address, attachments, and our replies are handled in Google Workspace. The support address is a Google Group delivered to its members. Please avoid sending passwords, tokens, license keys, or private recordings unless a specific support process requires them.
Retention and deletion
The account service cleans up expired sign-in and recovery records. We retain account and linked-device information for as long as needed to provide the account, manage access, and respond to your requests. Where no fixed period is stated, retention depends on those purposes, the type of record, and applicable obligations. An expired token does not mean every associated database record has been erased.
The account-deletion workflow removes the account profile and related account-linked records and requests removal of the WorkOS user. It can require reauthentication and may remain pending if the authentication provider is unavailable. Revocation records and detached license or conflict records can remain; account deletion does not automatically delete Polar’s transaction records, support correspondence, local files, or records held by other providers.
The delivery Worker’s configured cleanup keeps detailed update/model activity for up to 30 days, download records for up to 90 days, and aggregate counts for up to 120 days. The separate Polar webhook audit store has a 90-day expiry. These fixed periods apply to those stores, not to every account record, hosting log, Jev metric, provider system, or backup. Security and fraud-prevention records, license and transaction records, and records needed to resolve disputes or meet legal obligations may need to be retained after an account closes. We retain them for those purposes rather than setting a single deadline for all records. Backup copies may persist through backup rotation and recovery processes; deletion from an active service does not necessarily remove every backup immediately. Providers apply their own retention and deletion processes to records they hold.
For access, correction, export, or deletion requests, contact privacy@heyatom.ai. We may need to verify that a request concerns your account. You can also review or revoke the Google connection in your Google Account; this does not itself erase local Atom files or every record held by Atom.
Service providers and security
The services described above include Cloudflare for hosting, storage, and delivery; WorkOS and Google for authentication; Google Workspace for correspondence; Polar for licensing and payments; Fontshare for website fonts; and the AI providers you use. Data can be processed outside your country under the providers’ arrangements.
Account requests use HTTPS, Mac account credentials use Keychain, and account access is tied to authenticated device sessions. These measures reduce risk; they do not make any system immune to misuse or compromise. Service providers handle data under their applicable policies and service arrangements. We do not promise that their retention periods or processing locations are identical to ours. We do not sell your personal data.
Children’s privacy
Atom is not directed at children under 13. If you believe a child has provided personal information through Atom, contact privacy@heyatom.ai so we can investigate and address it.
Contact and changes
Atom is the product and service described in this policy. For privacy questions, write to privacy@heyatom.ai. For beta support, use support@heyatom.ai. We may update this policy as Atom develops. We will post the updated policy here with a revised date. Before material changes to how we collect or use personal information take effect, we will provide advance notice through the app or this website. Where consent is required, we will ask for it before the new processing begins; publishing an update or your continued use alone does not provide that consent.