Privacy Policy
Atum Platform is operated by Anka Ventures Vietnam LLC. This page explains how information is handled when you visit our website or use Atum Desktop, including its optional email, Drive and calendar connections.
For privacy questions or requests, contact minh@anka.vc.
Information you provide
We receive information you give us when you join the waitlist, contact us, create an Atum account, or use our services. This can include your name, email address, optional phone number, messages, prompts, files you choose to share, and information needed to operate your account. Only provide another person’s contact details when you have permission to do so.
Our website uses Vercel for hosting and website performance analytics, Google Fonts for fonts, Google Apps Script and Google Sheets for waitlist submissions, and Web3Forms for contact messages. These services receive the information needed to provide their functions, including technical request information such as an IP address, browser information and pages requested.
Optional Google connections
Connecting Google is separate from signing in to Atum. You choose which Google accounts to connect and which sources Atum may use in Settings. Gmail and Google Calendar share one connection; Drive is connected separately. Google connection availability depends on your app version and Google’s verification process.
- Gmail: Atum uses your account’s email address to identify the connection. When you ask for email help, it can search and read messages, including identifiers, headers, snippets and plain-text content. It can draft text in chat and send a plain-text email only after you confirm a native preview showing the sending account, recipients, subject and body. It does not delete, label or modify existing messages.
- Google Calendar: Atum lists available calendars and reads events from selected calendars, including titles, dates, times, locations and descriptions. It can create or edit personal timed events only after you confirm the calendar and event details. Invitation management, calendar deletion and recurring-series editing are not offered.
- Drive: Atum can search existing files and read supported files you request, including exporting supported Google documents to text. It does not create, edit, delete or share Drive files. This read-only permission covers existing Drive files; it is broader than access to individual files selected in a file picker.
Before Google authorization, Atum explains the requested service access, cloud AI processing and retained content. Connection credentials are kept in your account’s local encrypted storage, protected by the operating system. Provider tokens are not included in content returned to the AI model.
For an optional one-time connection reward, Atum Desktop may send a freshly refreshed, short-lived Google access token to Atum’s verification service. It uses the token only to request Gmail account metadata or primary-calendar metadata needed to prevent duplicate rewards; it does not request message or event content. Atum does not retain that access token or return it to the renderer or AI model.
How we protect sensitive data
These protections apply to information obtained from Gmail, Google Calendar and Drive, as well as the credentials used to access those services:
- Encryption in transit: Atum sends requests to Google APIs, Atum’s hosted service and its managed AI providers over HTTPS. Google API requests reject redirects so authorization headers are not forwarded to a redirected destination. The desktop sign-in callback uses a temporary loopback address on your own computer; OAuth state validation and PKCE protect that authorization flow.
- Credential encryption and device access: Google refresh tokens and action receipts are encrypted using the operating system’s secure-storage service. On macOS this uses Electron safeStorage with a key protected by Keychain. Atum refuses to save a new connection if secure storage is unavailable. On macOS, local credential files have owner-only permissions. Credentials are kept separately for each Atum account.
- Restricted access inside the app: Google credentials stay in the desktop main process and are not exposed to the chat interface or AI model. The optional connection-reward check described above is the limited server-side exception. Connection operations check the active Atum account and connection state; account changes or disconnection invalidate pending access. Sending email or changing an event requires a native confirmation showing the proposed action.
- Limited disclosure to AI services: Requested Google content is processed through the protected Gemini route described below. Requests stop if the required provider and data-retention controls cannot be met. Google connection errors use limited error codes rather than returning provider response bodies, which may contain personal information or credentials.
Local conversation history, summaries and files are distinct from the encrypted credential store and are not all encrypted by Atum. Their protection also depends on your operating-system account permissions and device security, including disk encryption where you enable it. Cloud AI processing requires the provider to process the requested content; Atum does not claim end-to-end encryption that hides that content from the processing provider.
Calendar on your Mac
If you connect Calendar on this Mac, macOS asks for full calendar access. Atum can read selected calendars and, after your confirmation, create or edit personal timed events. It does not manage invitations, edit recurring events or delete calendars. A calendar connected through both Google and macOS may return the same event twice. Atum does not collect an Apple Account password for this connection.
How your information is used and shared
We use information to provide the features you request, manage accounts, respond to support requests, operate and secure our services, and understand website reliability. Email, calendar and Drive information read for a conversation becomes part of that conversation’s context.
Cloud AI processing: Google-connected assistant work is sent through Atum’s managed server and OpenRouter to Google’s Gemini service on Vertex AI. Atum requires the specified Vertex endpoint, no fallback to other providers, denial of provider data collection and an endpoint eligible for OpenRouter’s zero-data-retention routing. If the protected route cannot be verified or is unavailable, the request stops. This processing is not entirely local to your device.
Connecting Google places assistant work in that Atum account’s workspace on that device on the protected Gemini route, including later conversations, summaries and shared memory. Model choice is fixed to Gemini for this workspace. Shared or group tasks configured for another model stop on this device. This restriction remains after disconnecting Google because retained material may contain Google data. It does not automatically label copies you deliberately export or send to other apps or people. Consider the destination’s privacy practices before sharing.
For workspaces without retained Google content, other managed model options may use OpenRouter and providers such as DeepSeek or Moonshot. A provider you configure yourself receives requests according to that configuration; it is unavailable for the Atum Desktop assistant in a protected Google workspace on that device. This protection does not control a separate Hermes installation or remote gateway that you run yourself.
AI processing and hosting may take place outside your country of residence. Provider routing and content-retention controls are separate from Atum’s own saved conversation history and from service records such as account identifiers, usage totals, billing and security logs. Zero-data-retention routing does not mean Atum deletes your conversations.
Atum’s use and transfer of information received from Google APIs follows the Google Workspace API User Data and Developer Policy, including its Limited Use requirements. We do not use connected Google content to train general-purpose AI models, sell it, or use it for advertising. Transfers are limited to providing the features you request, complying with applicable law, and protecting security as permitted by that policy. We do not permit routine human reading of your Google content; access must be permitted by the policy, such as your specific consent for support or a necessary security investigation.
Storage and retention
Atum can synchronize curated assistant memory, skills, assistant instructions, personal pets and selected app preferences through your account for use on other computers. On a computer where you connect Google, automatic synchronization and restoration of that assistant content pause to preserve Google data protection; new local content changes are not uploaded through account sync. Selected app preferences can still synchronize. This continues after Google is disconnected. It does not erase earlier account copies or change synchronization on your other computers. The connection disclosure and Agent sync settings explain this device-specific limitation.
Connection credentials remain in your Atum account’s local encrypted store until you disconnect that connection or remove the corresponding local data. Read results, summaries and drafts may remain in local conversation history, shared assistant memory and files. Encrypted action receipts retain identifiers and digests to prevent duplicate sends after a crash; they do not store the full message body. Disconnecting an account stops future access through that connection; it does not automatically erase information already included in conversations or stored by another service.
We retain account, waitlist and support information for the purposes for which it was collected, including providing the service and handling requests. The applicable service’s retention rules govern data processed by cloud providers. We do not promise that disconnecting an account immediately deletes every copy, backup or service record.
Your controls and requests
- Use Atum Settings to change which sources are searched by default, add another Google account, or disconnect an account. Review and delete retained conversations and local assistant data separately when you no longer need them. Disconnecting one Google account removes its Gmail, Google Calendar and Drive access. Other Google accounts remain separate.
- You can also revoke Atum’s Google access in your Google Account connections. Because Google sign-in and the desktop connection use the same Atum project, you may need to approve Google sign-in again.
- Manage macOS Calendar permission in System Settings → Privacy & Security → Calendars.
- To request access, correction or deletion of information we hold, or to leave the waitlist, email minh@anka.vc. We may ask for information needed to verify that the request concerns your data.
Changes and contact
We will update this page when our practices change and show the date above. For questions about this policy or how Atum handles your information, contact Anka Ventures Vietnam LLC at minh@anka.vc.