Privacy policy
Last updated: 2026-11-04
Atom Personal Assistant is a privately operated personal AI assistant used only by its owner.
Google data accessed
- Gmail: read email messages and threads belonging to the owner, in order to identify action items, deadlines and commitments, and to prepare draft replies. Drafts are only created after the owner separately authorises it.
- Google Calendar: read the owner's calendar events in order to prepare reminders and context for upcoming meetings.
- Google Drive: read specific documents that the owner has selected or that the assistant itself created, so they can be used to answer the owner's requests.
Purpose and use
Google data is used only to carry out the tasks the owner asks for: summarising messages, finding action items, preparing reminders, and answering questions about the owner's own documents. No profiling, advertising, resale or unrelated secondary use takes place, and data is not used to train any model.
Storage
Google access and refresh tokens are stored in permission-restricted files readable only by the owner's account, on the owner's own server and computers. Processed text, summaries, memory notes and assistant configuration are stored in the same private locations. Public pages such as this one contain no personal data and are served separately from all private data.
External service providers and sharing
To generate responses, the text the assistant is working on is sent to third-party model providers, for example OpenRouter and the model vendors it routes to, which may include OpenAI. Those providers process the text in order to return a result and are bound by their own terms. Google account content is not sold, not published, and not shared with advertisers or any other third party.
Retention
Conversation history, memory notes and logs remain on the owner's private storage so the assistant stays useful over time, and are deleted when the owner removes them or revokes access. Google access tokens are retained only while the connection is active, so revoking access in the owner's Google Account immediately makes the stored tokens unusable. No fixed retention period is promised, because retention is controlled directly by the owner.
Security
Access is limited to the owner. Credentials are kept in permission-restricted files on private infrastructure, are not published, and are not placed in public repositories or reports. Traffic to this information site is served over HTTPS. No system is perfectly secure, so these are the measures actually in place rather than a guarantee.
Deletion and revoking access
The owner can delete all stored data at any time, and can revoke this application's Google access from the Google Account permissions page at myaccount.google.com/permissions, which stops all further access immediately. Questions or requests can be sent to the contact address on this page.
Questions
Contact: contact@namandoes.com