What we collect.

Last updated 2 September 2026.

This page describes what happens to information you give this website. It is deliberately specific rather than generic, because a privacy notice that could describe any website describes nothing.

The application

If you complete the application, we store the website address you gave us, the company name and description shown back to you, the goals and budget range you selected, and the contact details you entered — your name, email, and optionally a phone number and role.

We use this to assess whether Atlas can help and to contact you about it. We do not sell it, rent it, or share it with third parties for their own marketing.

Website analysis

When you submit a website address, our server requests that page the way any browser would, and reads only what the site publishes publicly: its title, description, and visible introductory text. We do not attempt to access anything behind a login, and we do not crawl beyond the single page you gave us.

The extracted text is shown to you for confirmation and stored with your application. Nothing else from that page is retained.

Connected Google accounts

A client can connect a Google Workspace or Gmail account to Atlas. When they do, Google asks them to allow specific permissions, and Atlas uses each one for exactly one thing:

• Send email (gmail.send) — to send the outreach a client has approved from their own address, so it arrives from them rather than from Atlas. Atlas cannot read the mailbox: no read permission is requested, and none is held.
• Read contacts (contacts.readonly) — for a one-time import of the client’s address book into their own Atlas account, so they do not have to retype it. The names, email addresses, job titles, phone numbers and company names are saved as contacts in that client’s CRM. The access token used for the import is discarded immediately afterwards; nothing long-lived is kept for this permission.
• Basic account identity (openid, email) — to show the client which address they connected.

For the sending permission, Atlas stores the token Google issues so it can send on the client’s behalf later. That token is encrypted at rest, is used only to send, is never shown to anyone, and never leaves our servers.

Information received from Google is used only to provide the feature the client connected it for. It is not sold, not used for advertising, and not used to develop or train artificial-intelligence models. It is shared only with the infrastructure providers that run Atlas — our database and hosting — and only to operate that feature.

A client can disconnect at any time from within Atlas, or revoke Atlas’s access directly from their Google Account permissions. Revoking access stops Atlas sending from that address immediately.

Atlas’s use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

Analytics

With your permission, this site records first-party product analytics to improve page flow and forms. It records the route you viewed, a random session identifier, the fact that a control or form was used, and small technical properties such as timing. It does not record what you type, passwords, message contents, advertising identifiers, or precise location. You can continue without analytics, and you can email us to request deletion of product analytics records.

Technical logs

Our hosting provider records ordinary server logs, including IP addresses, for security and abuse prevention. We also hold request counts in memory briefly to rate limit the analysis and application endpoints.

Retention

Applications are kept while the request is active and for a reasonable period afterwards. If you would like yours deleted, email support@atlassolution.net and we will remove it.

Contact

Questions about any of this go to support@atlassolution.net. Atlas is based in New York, NY, United States.