PRIVACY
Privacy
This policy explains how SynOct LLC handles information through the public Titan.Atlas websites and the optional Gmail connection in Titan.Atlas Desktop Free and Lite for Mac.
Effective October 22, 2026 · TITAN.ATLAS is operated by SynOct LLC.
What this page covers
This policy covers titanatlas.world, titanatlas.live and the Mac app's direct Gmail connection. Other Atlas deployments and separately configured House or chat services can have additional terms; those terms do not replace the Gmail disclosures on this page.
What the websites collect
- Requests you send us. If you email us or request beta access, we keep the address, name and message content you provide so we can respond and onboard you.
- Security telemetry. A small first-party security check runs on each page. It reports signs of attack — injected scripts, framing, trap-link touches. It never reads what you type or what is on the page and sets no cookies.
- Server logs. Request source addresses are recorded only in scrambled form (hashed with a key that rotates daily) to spot one source probing several of our sites. Plainly hostile requests (for example, attempts to open nonexistent admin pages) are reported the same way, without cookies, request bodies, or query strings.
Website privacy practices
- No advertising trackers, no analytics beacons, no third-party pixels.
- No selling or renting of personal information.
- No cross-site tracking cookies.
Beta access requests
Submitting the beta form records your email, optional name and interest in our intake system and notifies a person. We use it only to respond about Atlas access. Central case tracking is not live yet — requests sit in the launch intake, not a tracked support desk.
Gmail in Titan.Atlas Desktop for Mac
Connecting Gmail is optional. Google asks you to authorize access in your browser. Atlas receives OAuth tokens; you do not enter your Google password in the Atlas mail form. Atlas requests gmail.readonly to read and search mail and gmail.send to send messages you prepare and confirm. These features do not change Gmail labels, move mail to Trash or delete Gmail messages.
Atlas accesses your connected Gmail address, message and thread identifiers, senders and recipients, subjects, dates, previews, message content, folder information and attachment metadata or content. It uses this information to show and find mail, open attachments, and prepare replies or forwards. Search terms go to Google to search your mailbox. Mail is fetched when the mail view loads and when you browse, refresh, search or open messages. This connection does not maintain a complete synchronized copy of your mailbox.
When you compose, reply or forward, Atlas uses the chosen account, recipients, subject, message and attachments. Sending requires a separate message review and confirmation. Atlas submits the confirmed message to Gmail for delivery to the selected recipients.
How we use Google user data
We use Google user data only to provide or improve the mail features visible to you. We do not use it for advertising, sell it, or use it to train general-purpose AI models. We permit human access only with your specific consent or when necessary for security or legal reasons. Transfers are limited to providing or improving those visible features with your consent, or necessary security or legal purposes.
Atlas's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including its Limited Use requirements.
Where Gmail information is stored
Connection details, including the account address and any name or category you provide, are saved in the local app profile. Refresh tokens are stored through the native macOS Keychain. Current mail views also use application memory.
Kept drafts and prepared outgoing messages are saved locally. An outgoing record can contain your message, recipients, attachments, the original message used for a reply or forward, and delivery status. These content-bearing files are protected by local filesystem permissions; they are not encrypted by the app's mail-content store. Token protection in Keychain does not extend to these files.
Draft exports and downloaded attachments are separate files. A Free-to-Lite upgrade can also preserve authored mail in a local recovered-mail area.
Gmail retention, disconnect and deletion
The current version has no automatic age-based deletion for kept drafts or prepared outgoing records, including sent messages, uncertain delivery outcomes and abandoned preparations. Expiry of a send confirmation does not erase the saved message.
A successful Disconnect removes that connection and its saved refresh token from the local app profile. It does not delete Gmail messages, revoke Google's authorization grant, or erase saved drafts, outgoing records, recovered copies, exports or downloaded attachments. To remove Google's authorization, use your Google Account's third-party connections settings.
Discarding a retained reply draft removes its entry from that draft store. Abandoning an outgoing preparation keeps its record. The current app has no single control that permanently purges all saved mail content. Copies you exported, downloaded or backed up must be managed separately. Contact us for help identifying local files you want to remove; we cannot remotely erase files on your Mac.
Separate House and chat connections
The direct Gmail features communicate with Google; they do not automatically submit your mailbox content to Atlas chat. If you separately configure a House connection and submit text in chat, that text can be sent to the configured House under the chat routing and consent settings. This includes email information you copy into the chat.
That separate service can route requests to an AI provider according to its configuration. Check the operator's and provider's terms before submitting sensitive content. A Gmail connection does not establish those separate services' retention, training or human-access practices. Choosing Local / private for a chat turn keeps that turn from being sent through the House route; it does not stop the direct Gmail features from contacting Google.
Children and Titan.Quark
Titan.Quark is in design for family use and is not available today. Where Quark — or Atlas family features such as a child’s schedule — touches information about a child under 13, the Children’s Online Privacy Protection Act (COPPA) applies, and we build to it:
- Verifiable guardian consent first. A child cannot create an account, post, message or share anything until a parent or legal guardian completes a verifiable consent step — not a checkbox, a real verification.
- Guardian authority is absolute. A guardian can review everything the child’s account holds, change any permission, and delete the child’s profile and its data entirely, at any time, without asking us twice.
- Minimum collection. We collect only what the feature actually needs. No location tracking, no behavioral profiling, no cross-service identifiers for children.
- No advertising to children. Ever. Quark carries no ads, no affiliate links, no sponsored content aimed at child accounts — regardless of what our adult surfaces may one day offer. Children’s conversations, friendships and activity are never used as advertising inputs or fed into models for commercial purposes.
- No third-party sharing. Children’s personal information is not sold, rented or disclosed to advertisers, data brokers or social platforms. Any service provider that touches it does so under contract, for the feature only.
- Deletion is real. A guardian’s delete request removes the data, not just the view of it. Retention is limited to what law requires.
- School and family sources. Where Atlas reads a school notice or club email to maintain a family schedule, that input stays inside the family’s Atlas — it is never processed for advertising or shared with third parties.
These commitments are digital engineering gates, not marketing: Quark does not ship a child-facing feature until the consent, review and deletion paths behind it are verified. COPPA questions: atlas@titanatlas.live.
Billing data
If you buy an Atlas subscription, Stripe processes your payment details — we never store card numbers on our own servers. SynOct LLC receives and retains the billing records needed for tax, accounting, subscription state and legally required dispute handling. Subscription state (trial, active, past-due, suspended, ended) is tracked to operate your entitlement. Billing events never touch your local Atlas data.
Contact, support and deletion requests
Send privacy questions or deletion requests to atlas@titanatlas.live. Authorized SynOct personnel handle messages sent to this address. Central case tracking is not live yet; we do not promise a staffed support desk or a response-time guarantee.
Contacting us shares the address, message and attachments you choose to send. We use them to respond, resolve the issue and handle related security or legal obligations. Please do not include your Google password, OAuth tokens or unnecessary mailbox content. Disconnecting Gmail does not delete a separate support message or its attachments.
We retain active support correspondence only while needed for these purposes. We review it when an issue closes or you request deletion, and remove information that is no longer needed. We may retain the minimum information required for legal, accounting or security reasons. Deletion requests are handled manually after reasonable verification; tell us the address and correspondence concerned without sending extra sensitive information.
Deleting active correspondence does not automatically erase backup copies. Backups are restricted to recovery, security and legal purposes. We review retained backup copies separately when handling deletion requests and explain any necessary retention. We do not promise an automatic backup expiry or immediate deletion from every backup.