Privacy Policy

1. Overview

STL Automate LLC ("STL Automate," "we," "us," or "our") provides automation services and operates internal automation tools. This policy explains what information we access or collect, why we use it, what we may store, and the choices available to users.

2. Information You Provide

We may collect information that you submit through our website or provide while working with us, including your name, work email, optional phone number, company, and descriptions of your automation needs. For project requests, this may include the problem, current and desired workflow, systems and tools involved, repair status, target timing, and budget range. We use that information to respond to inquiries, assess project fit, provide requested services, and communicate about those services.

3. Google User Data We Access

When a user connects a Google account and grants permission, our job-search automation may access:

• Gmail messages and message metadata needed to identify and read job-alert emails from LinkedIn, Indeed, ZipRecruiter, and Glassdoor
• Gmail messages and message metadata needed to identify and read job-application confirmation emails
• The ability to send Daily Digest emails and application-preparation notification emails from the connected account
• Google Sheets data needed to add or update relevant job and application information in the user's tracker

We access this data only after the user authorizes the Google permissions requested by the automation.

4. How We Use Google User Data

Google user data is used to provide the connected job-search features: finding relevant job alerts and application confirmations, extracting job and application details, maintaining the user's Google Sheets tracker, preparing Daily Digests, and sending application-preparation notifications. The information is processed through STL Automate's n8n workflows for these purposes.

5. Storage, Sharing, and Retention

Relevant parsed job and application information may be stored in the user's Google Sheets tracker and in limited n8n workflow or data-table state used to operate the automation. We retain information only while it is reasonably needed to provide and maintain the requested features, resolve operational issues, or meet applicable legal obligations.

We do not sell Google user data or other personal information. We do not use information accessed from a connected Google account for advertising. We do not transfer Google user data except as necessary to provide the user-authorized automation, maintain its security, comply with applicable law, or with the user's consent.

Project intake submissions are sent to our server-side lead endpoint and forwarded through our n8n integration so we can review and respond. We may record project inquiries in our customer relationship management system. Information is shared with service providers only as needed to operate this process.

To request deletion of stored information, contact us at contact@stlautomate.com. We will evaluate and handle the request based on the information held and any applicable obligations.

6. Google API Limited Use

STL Automate's use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

7. Security

We use reasonable technical and organizational safeguards intended to limit unauthorized access to the systems and accounts that process user information. Access is limited to what is needed to operate and maintain the automation. No system can be guaranteed to be completely secure.

8. Revoking Google Access

You can revoke STL Automate's access to your Google account at any time from your Google Account third-party connections settings. Revoking access stops future access through that authorization, but it does not automatically delete information already stored. Contact us if you also want to request deletion of stored information.

9. Website Analytics and Cookies

We use PostHog for website analytics. We record page views and the browser SDK automatically captures some page-element interactions, including clicks, input changes, and form submissions. Its autocapture does not include values entered in input, select, or textarea fields. Our explicit analytics events report page views, CTA clicks, and successful intake milestones with route, offer, and attribution details; they do not include intake field values such as your name, email, phone number, company, or free-text project details. PostHog session recording is disabled.

The PostHog browser SDK uses local storage with a cookie fallback to retain an analytics identifier across visits. The SDK's default cookie lifetime is 365 days; no expiration is configured for its local-storage entry, which may remain until cleared from the browser. The SDK may also send standard technical information, such as browser type and referring URL. You can manage cookies through your browser settings.

If you choose to allow Google Ads conversion measurement, we load Google's Ads tag to measure whether advertising visits result in a successfully submitted project inquiry. Google may use cookies or similar identifiers for this measurement. We store your choice in your browser for up to six months; after that, we ask you again. The six-month period is our browser-storage setting. You can change or withdraw your Google Ads measurement choice at any time using Google Ads measurement choices. The conversion event reports successful intake only and does not include form fields such as your name, email, phone number, company, or project details. This choice controls Google Ads measurement only. PostHog site analytics remains separate and is not controlled by this choice.

If you withdraw consent after the Google tag has loaded, the site sends a consent update marking all four Google consent signals as denied; that update may itself involve a request to Google. The site stops calling future Google Ads conversion events. The tag code may remain loaded in the current browser tab until you reload the page or close the tab. After your declined choice is saved, reloading starts a page where the Google Ads tag is not loaded. Withdrawing consent does not delete information Google may already have received.

For information about how Google handles data from sites that use its services, see Google's Business Data Responsibility information and Google's Privacy Policy.

10. SMS and Mobile Messaging

We do not share, sell, or rent mobile phone numbers or SMS opt-in information to third parties or affiliates for marketing or promotional purposes. Phone numbers collected for text messaging are used only to deliver requested or service-related messages. Message and data rates may apply. Reply STOP to opt out or HELP for help.

11. Changes to This Policy

We may update this policy as our services or data practices change. The revised policy will be posted on this page with a new last-updated date.

12. Contact

For privacy questions or requests, contact contact@stlautomate.com.