Atlas Platform Privacy Policy

Effective date: October 7, 2026

1. Who we are

Atlas Platform ("Atlas Platform", "we", "us") is shop-management software operated by Atlas Auto Glass, 1712 W. Dallas St, Houston, TX 77019. This policy covers the Atlas Platform web portal at new.atlasautoglass.com and its mobile app. It does not cover the Atlas Auto Glass customer website, which has its own privacy policy.

2. Our role

Our customers are the businesses that use Atlas Platform ("shops"). A shop's users are its owners and employees. Information a shop enters about its own customers belongs to the shop: names, phone numbers, vehicles, jobs, call recordings and messages. We process it on the shop's behalf and follow the shop's instructions. If you are a customer of a shop, contact that shop about your information.

3. Information we collect

• Account information: name, email, phone, role and login activity of shop users.
• Shop data: customers, vehicles, jobs, quotes, invoices, payments, inventory, time clock entries, team chat and files a shop uploads.
• Calls and messages: recordings, voicemails, texts and call details for shop phone numbers, plus AI-generated call summaries and suggested replies.
• Website leads: form submissions and marketing attribution (for example the ad click ID and landing page) from a shop's website: one the shop builds and hosts in Atlas Platform, or its own site when the shop installs our tracking. A site built in Atlas Platform can also carry the shop's own Google Analytics tag, which sends its visitors' activity to the shop's Analytics property.
• Google user data: only if a shop administrator connects Google (section 5).
• Meta (Facebook and Instagram) data: only if a shop connects its Facebook Pages to receive its lead ads (section 6).
• Ad click protection: for each visit that arrives on a shop's website from one of its ads, when the site runs our tracking script and the shop has not turned click protection off: the visitor's IP address, browser user agent, a random device ID kept in a first-party cookie (_atlas_vid, with the shop's ID added to the name on sites Atlas Platform hosts), a one-way hash of stable browser traits and the IP address, the ad click ID and its campaign and keyword, the landing page, time on the page and number of taps, and whether the browser identified itself as automated. We use it only to spot repeat and automated clicks on the shop's ads (fraud prevention), show them to the shop's administrators and, where the shop has blocking in Google Ads, exclude from the shop's Google Ads campaigns the IP addresses an administrator blocks, or that auto-block flags once an administrator turns it on. We delete it after 90 days.
• Technical data: device, browser, IP address and logs needed to run and secure the service.

4. How we use information

We use it to provide and support Atlas Platform for the shop, to keep it secure and prevent abuse, to meet legal obligations, and to contact shop users about the service. We do not sell personal information, and we do not use shop data, Google user data or Meta data for advertising.

5. Google user data

A shop administrator can connect the shop's Google accounts in Settings → Integrations → Google Marketing. On Google's consent screen they choose which of the following to allow. Atlas Platform then receives only what they allowed.

What we receive, and what we use it for

• Your Google email address (userinfo.email): shown on the connection card, so the shop can see who authorized the connection.
• Google Ads (adwords): the Google Ads accounts the user can access (account ID, name, currency, manager status), the account's conversion actions, daily cost, clicks, impressions, calls and conversions by account, campaign, keyword, search term, city and hour, Google's record of each ad click (click ID, keyword, match type and city) and of each call from an ad (start time, duration and caller area code), and the IP exclusions Atlas Platform added. We use it to let the administrator choose the shop's account and conversion action, to show ad spend and return on ad spend next to job revenue on the shop's Marketing dashboard, and to match ad clicks and ad calls to the shop's leads.
• Google Search Console (webmasters.readonly, read-only): the Search Console properties the user can access, and the chosen property's search performance by day (search queries, pages, clicks, impressions, click-through rate and average position). We use it to show which searches and pages bring the shop customers.
• Google Analytics (analytics.readonly, read-only): the GA4 properties the user can access, and the chosen property's website traffic by day (sessions, engaged sessions, key events and new users by channel, source, medium and landing page). We use it to show where the shop's website visitors come from, including visits referred by AI assistants. If the shop builds a website in Atlas Platform, we also list the chosen property's web data streams (name, measurement ID and website address) so the shop can put its own Google tag on that site, and we show that site's visits next to its leads.
• Google Business Profile (business.manage): the Business Profile accounts and locations the user manages (location name, title and address); for the chosen locations, daily calls, website clicks, direction requests and Search and Maps views, plus monthly search keywords with their impressions; the locations' reviews (the reviewer's public name and photo, the star rating, the comment and the owner's reply); and the locations' posts. We use it to show each location's demand next to its revenue, and to let the administrator read and answer reviews and see which job a review is probably about, by matching the reviewer's name to the shop's own jobs. When someone in the shop presses Fill from Google in Automations, we read the chosen listings' phone number, address and review link (or the place ID it is built from) to suggest each location's link for review-request texts; nothing is saved until they save it. If the shop allows it, we also read the listing's name, hours, address, phone, service area and description to suggest the shop's business details; they stay drafts until the shop approves them. Approved details are what the shop's AI phone and text agents tell customers (see Sharing), and a website the shop builds in Atlas Platform can start from the approved name, phone and description. We never edit the listing itself, and never change or remove anyone else's reviews or posts.

What we send to Google

Through the Google Marketing connection, Atlas Platform sends Google only these changes, and its servers refuse any other request before it is sent:

• Paid jobs, as conversions. When a lead who clicked one of the shop's Google ads becomes a paid job, Atlas Platform uploads an offline conversion to the shop's own Google Ads account. It contains the ad click ID (gclid, gbraid or wbraid), the conversion action the administrator chose, the time of payment, and the job value and currency. We never send the customer's name, email, phone number or address.
• IP exclusions, only when an administrator blocks an IP address or turns on auto-block. Blocking in Google Ads is offered only to the shops we turn it on for. Atlas Platform adds the IP address an administrator blocks, or a repeat or automated ad clicker that auto-block flags once an administrator has turned it on, to the shop's enabled Search campaigns as an IP exclusion. It removes the exclusions it added when an administrator unblocks them or, for automatic blocks, when they expire. It never removes an exclusion someone added in Google Ads.
• Review replies and posts an administrator writes. When an administrator writes a reply to a Google review, or a Business Profile post, and sends it (now or at a time they choose), Atlas Platform publishes it on the chosen listing, and removes it if they take it down.

We never change ads, bids, budgets, keywords or listing details, and never change or remove anyone else's reviews or posts.

Who can see it

Only the shop that connected it. Each shop's data is kept separate, and no other shop can see it. The reports and the connection are for the shop's administrators. A few things filled from Google are seen by the shop users allowed to manage them: review links (Automations), a website's Google tag and visit counts (Websites), and approved business details (AI agents).

Sharing

We do not sell Google user data or use it for advertising, including retargeting or personalized or interest-based ads. We do not use it to develop, improve or train AI or machine-learning models, and we do not send it to AI providers, with one exception the shop controls: Business Profile listing details the shop approves as its business details (name, hours, address, phone, service area and description) may be given to the AI provider that answers the shop's calls or texts, OpenAI or ElevenLabs, so the agent can tell customers. Today they go to OpenAI: on phone lines the shop sets to use OpenAI's voice, in texts the shop's Text agent answers, and, as far as they are in a website draft, when someone in the shop asks for copy suggestions. Those providers process them only on our instructions (section 7). We transfer it only as needed to provide the features above (for example to our hosting provider, Amazon Web Services), to comply with the law, for security, or as part of a merger or acquisition with notice to the shop.

Human access

Our staff do not read a shop's Google user data unless the shop asks us to for support, or it is needed for security or to comply with the law.

Storage and security

The Google access token is encrypted at rest (AES-256) on servers in the United States and is never sent to the browser. All connections use HTTPS.

Retention and deletion

We keep the Google token until the shop disconnects. Disconnecting (Settings → Integrations → Google Marketing → Disconnect) deletes the stored token and stops all syncing, so Atlas Platform can no longer reach the Google account. Google keeps listing Atlas Platform among the account's connected apps until you remove it there, as described below. IP exclusions Atlas Platform added stay in the shop's campaigns while it is disconnected. An administrator can remove them in Google Ads; an unblock, or an automatic block's expiry, is sent to Google once the shop connects again. Reconnecting removes nothing by itself. Business Profile data is deleted within a day of the shop disconnecting Google, and a location's data is deleted as soon as the shop unticks that location. The exception is listing details imported for the AI phone agent: they are kept with the shop's business details after a disconnect, so the agent keeps answering the same way, until the shop rejects them on the Business context page and publishes again, or asks us to delete them. Review links and a website's Google tag that the shop saves from our suggestions are its own settings and stay until it changes them. Search Console and Analytics data is kept for up to 16 months, and a property's data is deleted when the shop switches to a different property. Other report data already synced (ad spend and conversion-upload records) stays in the shop's reporting history. We delete any of it within 30 days if the shop asks us to, and as described in section 8 if the shop closes its account. Anyone can remove Atlas Platform's access at any time at myaccount.google.com/connections. To request deletion, email [email protected].

Google Calendar

If a shop connects Google Calendar, Atlas Platform creates, updates and removes calendar events for the shop's appointments, and uses that access only to keep those appointments in sync.

Limited Use

Atlas Platform'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.

6. Meta (Facebook and Instagram) data

A shop can connect its Facebook Pages so that the leads from its Facebook and Instagram lead ads arrive in Atlas Platform. Someone the shop allows to manage integrations connects them by signing in with Facebook in Settings → Third Party Integrations → Meta Ads Integration, and can disconnect at any time. Atlas Platform asks for the permissions Meta requires to receive a Page's leads: pages_show_list, pages_read_engagement, pages_manage_metadata, pages_manage_ads, leads_retrieval and business_management. Meta requires pages_manage_ads to read a Page's leads; Atlas Platform does not use it to create or change ads.

What we receive, and what we use it for

• The Facebook account that connects: its Facebook user ID and name, and which permissions it granted, shown on the connection card so the shop can see who connected it.
• Pages: the Pages that person shares on Facebook's screen (ID and name), so the shop can choose which to connect, and an access token for each Page it connects.
• Lead forms: each connected Page's lead forms (name, status and questions), so the shop can choose which answer goes into which contact field.
• Leads: when someone submits a connected Page's lead form, Meta tells Atlas Platform, and we read that lead: its answers, its form and when it was sent. If the shop has mapped the form and the lead has a valid phone number, we save it as a contact in the shop's account with the answers the shop mapped (for example name, phone, email, address, company and notes) and the shop's tags, or fill in only what the existing contact with that phone number is missing. We log each lead's outcome (lead ID, Page, form, result and, for a lead we did not save, why), so the shop can see that every lead arrived.

What we send to Meta

Atlas Platform asks Meta to send it a Page's new leads when the shop connects that Page, and to stop when the shop disconnects it. Disconnecting Meta entirely also asks Facebook to remove Atlas Platform's permissions from the account that connected it. Nothing else: it never creates or changes ads, posts or messages, and it sends Meta no customer data, conversions or other events.

Who can see it

Only the shop that connected it. The connection, Pages, form mappings and lead log are shown to the shop users allowed to manage integrations, and contacts created from leads are seen like the shop's other contacts.

Sharing

We do not sell Meta data, give it to data brokers, or use it for advertising or to develop, improve or train AI models. Once a lead is saved as a contact, it is the shop's customer information (section 2) and is handled like the rest of it, including by the service providers in section 7 that the shop's features use, for example Twilio when the shop texts the customer.

Storage and security

The Facebook and Page access tokens are encrypted at rest (AES-256) on servers in the United States and are never sent to the browser. All connections use HTTPS.

Retention and deletion

Disconnecting a Page stops its leads; its token and form mappings are kept so it can be connected again. Disconnecting Meta (Settings → Third Party Integrations → Meta Ads Integration → Disconnect) stops all leads, deletes the stored Facebook login, Page tokens and form mappings, and asks Facebook to remove Atlas Platform's permissions. Contacts already created and the lead log stay with the shop's other data. Anyone can also remove Atlas Platform from their Facebook account in Facebook's settings, under Business integrations (or Apps and websites); Meta then stops sending leads and the stored tokens stop working, and we delete them when the shop disconnects or asks us to. To ask us to delete Meta data, email [email protected]; we delete it within 30 days, and as described in section 8 if the shop closes its account. If you filled in a shop's lead form and want your information deleted, ask that shop, or email us and we will help the shop respond.

7. Service providers

These providers help us run Atlas Platform and process data only on our instructions:

• Amazon Web Services: hosting, database and file storage (United States)
• Twilio: phone numbers, calls, texts and recordings
• OpenAI: call summaries, suggested text replies, AI voice and text answering on the lines a shop sets to use it, website copy suggestions, and other AI-assisted features. It receives only the call transcripts, messages, job details or draft text the feature needs. The only Google user data it receives is the Business Profile listing details the shop approves as its business details (section 5).
• ElevenLabs: AI voice answering, where a shop turns it on. It may receive the Business Profile listing details the shop approves as its business details (section 5).
• Square and Stripe: payment processing
• Pusher and Google Firebase Cloud Messaging: real-time updates and mobile notifications
• Our email delivery provider: account and notification emails
• Services a shop connects: when a shop connects another service, such as QuickBooks, a bank account through Plaid, or an import from GoHighLevel, data moves between it and Atlas Platform only as that connection needs, on the shop's instructions.

We also disclose information when the law requires it, or to protect rights and safety.

8. Retention

Shop data is kept while the shop's account is active. When a shop closes its account, we delete its data within 90 days, unless the law requires us to keep it. A shop can ask for an export first.

9. Security

Data is encrypted in transit (HTTPS), and sensitive credentials are encrypted at rest. Each shop has role-based permissions. Access to production systems is limited to authorized personnel.

10. Your choices

Shop users can update their details in the portal or ask their shop administrator. Shop administrators can ask us to export or delete data by emailing [email protected]. If a shop holds information about you, contact that shop; we will help the shop respond.

11. Children

Atlas Platform is for businesses and is not directed to children under 13.

12. Changes

We will post updates on this page with a new effective date, and tell shop administrators about material changes.

13. Contact

Atlas Auto Glass, 1712 W. Dallas St, Houston, TX 77019, [email protected]