Automater.AI — Privacy Policy
Effective date: 2026-10-08 · Last updated: 2026-10-28
We are revising this Privacy Policy. This version applies until we post a revised version on this page.
This Privacy Policy describes how WEBRULON LLC, a New York limited liability company, collects, uses, and shares information about you when you use Automater.AI — the Automater Lite and Automater Desktop applications, our websites, Automater PRO and related services (collectively, the “Service”). Automater.AI is a product of WEBRULON LLC (“we”, “us”, “our”).
The Automater Lite Cloud Capture browser extension is covered by a separate Extension Privacy Policy.
1. Information We Collect
Account information
Automater Lite can be used without an account. When you create one, we collect your email address, a hashed password (if you set one), your selected display name (if any), and your verification status. If you sign in with GitHub or Google, we receive your email address and basic profile details from that provider (your name, username and profile picture) instead of a password. We collect timestamps for account creation, last login, and email verification.
Billing information
When you buy Automater PRO, Stripe processes your payment instrument in its own payment form. From Stripe we receive the email address you enter there, a Stripe customer ID, a Stripe subscription ID and the subscription status. We use them to email you a license code and, if you are signed in or attach the code to an account later, to link PRO to that account. You do not need an account to buy. When a license code is activated, we record the IP address it was activated from, and a code has one active activation at a time. We do not store your full payment card number, expiration date, or security code.
Usage statistics in the Automater applications
Automater Lite (from version 0.1.19) and Automater Desktop send us usage statistics so we can see which versions are in use, which features are used, and where the applications fail. About 20 seconds after the application starts (about 30 seconds in Automater Desktop), then about every 15 minutes, and when the application closes, each installation uploads to our own servers (api.automater.ai):
- a random installation identifier generated on the computer the first time the application runs. It is not derived from your hardware, account or network, and it is replaced by a new random identifier whenever you turn usage statistics off and back on;
- the application name and version, the operating system and its major version, the processor architecture, the display language, and whether the installation is free, signed in, or PRO;
- daily counts of events from a fixed list — for example “app opened”, “dictation completed (local)”, “library search”, “upgrade button clicked”, “JavaScript error”, “unclean exit” — and, for a few timing events, a total duration so we can compute an average (start-up time, dictation latency);
- which supported AI tools and developer tools are installed on the computer (names only, for example “codex”, “claude” or “git”; no file paths; recorded once a day).
We may match the installation identifier to a website download using the same IP address and operating system, looking back up to 72 hours before the installation’s first usage upload. Through that download’s attribution reference, we may link the installation to a sign-up or purchase made in the same browser. We use these links internally to report which campaigns lead to installs and purchases; we never share these matched links, or the campaign attribution behind them, with advertising platforms. The match is an estimate: people sharing an IP address and operating system can be matched incorrectly. This matching also applies when you have not accepted advertising cookies; those matches are labelled “matched (no consent)” in our internal reporting and are never sent to an advertising platform or included in an offline conversion upload.
Usage uploads never include the content of your sessions, prompts, transcripts, files, file paths, window titles, your machine name, user name, account identifier or email address. With each upload we record the country it came from. When IP storage is enabled, we also keep the IP address it was sent from for up to 90 days. We use the request IP address for the download match above, even when IP storage is off; stored IP addresses also support counting, de-duplication and abuse prevention. Like any request to our servers, an upload can also appear in our request logs, which do record IP addresses (see “Logs” below). Event names that are not on that list are discarded.
Usage statistics and crash reports are on by default in both applications. In Automater Lite one switch covers both, and you can turn it off at any time under Settings → Privacy & access, as the Windows installer’s terms page and Settings tell you. (Lite 0.1.21 to 0.1.29 asked before sending them.) In Automater Desktop you can turn them off under Settings → System → Privacy & telemetry; the first-run onboarding also offers both switches. In both applications, setting the environment variable DO_NOT_TRACK=1 turns them off. We can also stop collection remotely for every installation. While we test new versions, an operator setting on our servers can temporarily collect first-party usage counts from installations where usage statistics are turned off (Automater Lite 0.1.26 and later; Automater Desktop versions after 10.2.8); it does not change your saved choice or apply to crash reports, and DO_NOT_TRACK=1 still turns it off. Automater Lite shows you your installation identifier (“support ID”), so you can ask us to delete the statistics tied to it (Section 8).
Each night our servers also mirror the previous day’s usage statistics of each installation, as daily aggregates, to Google Analytics 4 through its server-side Measurement Protocol so that application and website reporting can be viewed together. That mirror runs on our servers, not in the application; it carries the same counts and attributes described above (including the country) under a one-way hashed installation identifier, and never the IP address, machine name, account or content. It includes only data from installations that share usage statistics.
Tips and offers counts (Automater Lite). Automater Lite shows short tips and offers inside the app. About every 5 minutes, and when the window closes, it sends our servers per-day counts of how often each tip or offer was shown, clicked, dismissed or rated, together with the application version and whether the installation is free, signed in or PRO. These counts carry no installation identifier, account, message text or machine identifier. They are sent only while usage statistics are on and the Settings → App updates → “Send anonymous tips & offers stats” switch is on; both are on by default.
The legacy web application at app.automater.ai uses PostHog product analytics only after you opt in through its cookie banner; the Lite and Desktop applications do not load PostHog or any other third-party analytics SDK.
Signed-in devices (Automater Lite)
When you sign in to Automater Lite, it registers your computer with your account. It sends a device name (by default your computer’s name followed by “(Lite)”), a machine identifier made by hashing your computer’s hardware ID, the operating system, the app version, and your computer’s name and your operating-system user name. While you are signed in, it regularly sends a heartbeat with the device’s ID and app version.
Usage sync (Automater Lite, when signed in)
When you are signed in, Automater Lite uploads to your account daily totals of the AI tool usage it reads on your computer: for each tool and model, token counts, estimated cost, request counts and active minutes, with labels that name the tool and say how the numbers were collected. For Automater’s own auto-code tool it also sends the location of that tool’s local database file, which can include your user folder name. Usage sync never uploads your conversation text; chat history sync (below) is a separate setting. Publishing a profile on the public leaderboard (leaderboard.automater.ai) is optional and uses your GitHub identity.
Voice (Automater Lite)
Automater Lite can turn your speech into text and read text aloud. It does this on your computer once its local voice models are installed and working. When you are signed in, it sends the audio you dictate, or the text you ask it to read aloud, to Automater Cloud Voice if you choose the Automater Cloud voice route (included with Automater PRO). Under the default Auto route it may also do so while the local models are not ready or if they fail. Free accounts get a limited Cloud Voice allowance that is available only while local voice setup finishes. When you are signed out, or when you choose the Local voice route, dictation audio and the text you have read aloud stay on your computer, unless you turn on voice redirection (below).
Offline voice model. To turn speech into text on your computer, Lite downloads a speech model (about 670 MB) from Hugging Face (huggingface.co), which hosts the open model files, and a voice runtime (about 120 MB) from our update server. Hugging Face receives the download request, including your IP address, under its own terms. No audio, text or account information is sent with it. From Lite 0.1.22 the download starts the first time you use voice (in Lite 0.1.21 it started when the app first opened), and Lite postpones it on metered or cellular connections.
Automater Cloud Voice processes audio and text on Automater-hosted models or through approved providers, which can include OpenAI, Groq, Deepgram, ElevenLabs and Meta (Muse). A provider that handles a request receives the audio or text under its own terms. Automater uses the audio and text only to complete the request and does not store them in its voice systems. We keep a usage record of each request (your account and device, the kind and amount of audio or text, and which service handled it) to apply your allowance.
Voice redirection is a separate setting and is off by default. If you turn it on, Lite can send the text of a spoken summary through our servers to another of your signed-in devices so that device can read it aloud.
Camera FX (Automater Lite)
Camera FX processes your webcam video on your computer; no camera frames or images leave it. While Camera FX runs, Lite checks your Automater PRO status or license code with our servers, and those checks contain no camera data. From Lite 0.1.21, the Camera FX virtual camera component is not part of the Lite installer. The first time an Automater PRO user starts Camera FX, Lite downloads it from our update server, checks its signature, and installs it with Windows administrator approval.
Encrypted archive backup
If you are signed in with an account on one of our workspace plans (Pro, Team, Business or Enterprise), Automater Lite backs up your local session archive every 6 hours. It encrypts the archive on your computer with AES-256-GCM, using a key kept in your operating system’s credential store, and uploads only the encrypted copy to our storage; we cannot read it without that key. Automater PRO does not include this backup. You can turn it off with Lite’s “Enable scheduled backup” switch.
Chat history sync (Automater PRO, off by default)
Automater Lite and Automater Desktop can copy your chat history to your account so that your other signed-in computers can open it. This is off until you turn on “Sync chat history across my computers”, and it runs only while you are signed in with Automater PRO. While it is on, each computer uploads the chats that started on it: the chats from AI tools that Automater shows in its chat history, and your chats in Automater itself. For each chat it uploads:
- each message’s text, who sent it (you, the AI or a tool), its time, and the tool calls it made with their inputs and results (very long ones are shortened);
- images and other files attached to the messages;
- the chat’s title, the name of its project folder (not the full path), the AI tool and its session identifier, details such as the model, and when the chat was created and last changed;
- an identifier for the computer it came from, which we show with the device name that computer is registered under (see “Signed-in devices” above).
Before upload, the application replaces text that looks like a password, API key, access token or private key with a placeholder in message text, tool calls and chat titles. It recognizes common formats only, so a secret in another format can still be uploaded, and it does not change images or files. Chats you have moved to the vault are never uploaded.
Synced chats are not end-to-end encrypted. They travel to api.automater.ai over an encrypted (TLS) connection and are stored on our servers in a form we can read, as the switch says. Synced chats and their files count toward a 10 GB limit per account; at the limit, new uploads pause.
Synced chats stay in your account until they are deleted. Turning the switch off, signing out or the end of your PRO subscription stops syncing; it does not delete what was already synced. Moving a synced chat to the vault deletes its copy from our servers: we delete its messages, title and details and keep only a record of the chat’s identifiers and the time it was deleted, so your other computers know to remove it. Files from that chat stay in your synced storage. To have all of your synced chat history deleted, email us (Section 8).
Website analytics and advertising
Our public websites — automater.ai (including the /upgrade order page), classic.automater.ai, account.automater.ai and leaderboard.automater.ai — load Google Tag Manager, a tag container that in turn loads the analytics and advertising services below. Section 4 lists each of them with its cookies and says whether it loads before you make a cookie choice. These services run in the website only; the Automater desktop and Lite applications do not load them, and a website page displayed inside the Automater Lite browser card is not counted.
Google Analytics 4 (Google LLC / Google Ireland Ltd). We measure how the
website is used: the pages you visit and the page you came from, the
approximate location derived from your IP address (Google Analytics 4 does not log or store IP addresses), your device type, browser, operating
system, language and screen size, and interactions such as clicks, scroll
depth, outbound links, file downloads and video plays. We also send
conversion events — for example that a sign-up was completed, that checkout
was started, or that a purchase was completed and for which plan. These events never include your password or payment details. When you type an email address, phone number or postal address into a form on our websites, the Google tag may also send Google a hashed (one-way encoded) copy of it so that Google can match conversions. Google Analytics identifies your browser with a random client
identifier stored in a first-party cookie (_ga, _ga_*), which lets us
count returning visitors and attribute a sign-up to an earlier visit.
Google Signals (advertising features). We have enabled Google Analytics’ advertising features. When you are signed in to a Google account that has Ads Personalization turned on, Google associates your visit with that account to give us aggregated demographic and interest reports, cross-device reporting, and remarketing audiences we may use to show Automater advertising on Google’s network. Google does this under its own privacy policy; we never receive the identity of an individual visitor from it. You can turn this off for your Google account at any time (see Section 8), and where consent is required it is only active after you accept analytics and advertising cookies in our consent banner.
Microsoft Clarity (Microsoft Corporation). We use Microsoft Clarity to record how visitors interact with our websites, including the /upgrade order page and the account pages: mouse movement, clicks, scrolling, page structure and navigation, replayed as session recordings and aggregated into heatmaps. Clarity masks text you type into form fields before it leaves your browser. Payment card details are typed into Stripe’s own payment form, which Stripe serves inside our page and Clarity cannot record. Clarity uses first- and third-party cookies (_clck, _clsk, and Microsoft cookies CLID, MUID, MR, SM, ANONCHK, SRM_B) to link the pages of one visit together. Microsoft processes this data under the Microsoft Privacy Statement and may also use it for its own fraud-detection and advertising purposes as described there.
Google Ads, Meta Pixel, OpenAI Ads Measurement Pixel and X Pixel. These tags tell us which of our ads on Google, on Meta (Facebook, Instagram), on OpenAI and on X led to visits, sign-ups, leads and purchases, including the plan, amount and currency of a purchase; Google and Meta can also use them to build audiences for our ads. They set the cookies _gcl_au, _fbp, __oaiq_consent and __obref on our websites; the providers set cookies on their own domains, and X sets cookies on its own domains. When you type contact details into a form on our websites, the Google tag, the Meta Pixel and the OpenAI pixel may send Google, Meta and OpenAI a hashed (one-way encoded) copy of your email address and, for Google and OpenAI, of your phone number, name or location. We never send them your password or payment details. They are off when your browser sends a Global Privacy Control signal or when you choose “Essentials only”, and in the European Economic Area, the United Kingdom and Switzerland they run only after you choose “Accept all”.
Download counts. When you click a link to download Automater Lite, our update server counts the click with the installer you chose, the campaign code in the link, your country and your IP address. This counts a redirect to the installer, not a completed download. We use the IP address for counting, de-duplication and abuse prevention, and delete it from the download-count record after 90 days.
A separate download-attribution record keeps the browser’s attribution reference (attr_ref), campaign (UTM) values, landing page, referring site, operating system and cookie choice, when available. It keeps the download’s IP address and browser user agent for 7 days, for every cookie choice, including Global Privacy Control, “Essentials only”, and no choice in the EEA, UK or Switzerland. We use the IP address and operating system to match the download to an installation as described above. Matches from downloads without advertising consent are for our internal reporting only, never for advertising platforms or offline conversion uploads. Advertising cookie and click identifiers (for example _fbp, _fbc, _ga, gclid) are stored only when advertising is allowed by your choice and region and Global Privacy Control is off; they are removed after 7 days. The remaining download-attribution record is deleted after 90 days.
Campaign attribution on forms. When you create an account, sign up for our newsletter or waitlist, send a contact message, or ask us to email you a download link, we also store the visit’s attribution reference, campaign (UTM) values, landing page and referring site, when available. These fields help us report which campaigns lead to sign-ups, enquiries and purchases. We never store advertising click identifiers with these account or form records.
Server-side conversion events. Our servers also report some conversions directly to advertising platforms, without going through your browser:
| Recipient | Event and when | What is sent | Follows your cookie choice and Global Privacy Control? |
|---|---|---|---|
| Meta (Conversions API) | LiteDownload: you click a link to download Automater Lite |
IP address, user agent, Meta browser and click identifiers (_fbp, _fbc), the page address, the operating system, installer and campaign code |
Yes: not sent with Global Privacy Control or “Essentials only”, or in the European Economic Area, the United Kingdom and Switzerland before “Accept all” |
| Meta (Conversions API) | CompleteRegistration: you create an account · Lead: you sign up for our newsletter or waitlist · Subscribe: you buy Automater PRO with an account |
hashed email address; for accounts and purchases also a hashed account identifier; for accounts your IP address and user agent; for purchases the amount and currency | No: sent for every account sign-up, newsletter or waitlist sign-up and purchase |
| OpenAI (Ads conversions) | app_installed: you sign in to Automater Lite on a new computer |
hashed email address, hashed account identifier, IP address, user agent | No |
| Where enabled: Google Analytics 4, Google Ads, X, Meta and OpenAI | download clicks and purchases; IP-matched installations are not sent | IP address, user agent, ad click and browser identifiers, the Google Analytics client identifier and campaign (UTM) values; for purchases also a hashed email address and account identifier, the amount, currency, order and plan | Yes: sent only when the download or checkout passed the same consent check as LiteDownload |
Cloudflare (Cloudflare, Inc.). Cloudflare delivers our websites and API, and on automater.ai it also serves our Google Tag Manager container from our own domain. It reads your country from our /cdn-cgi/trace address so we know whether to show the cookie banner, and Cloudflare Web Analytics counts page views and load times without cookies.
Crash and error reports (legitimate interest)
We collect crash reports and error traces through Sentry from our servers and the legacy web application. The Automater Lite and Automater Desktop applications can also send crash reports; we switch this on release by release, so some versions send none. From the applications this means: application crashes (native crash dumps and, in Lite, Rust panics), unhandled JavaScript errors, the application version, operating system and architecture, and a short technical trace of what the program was doing. Crash reports are scrubbed before transmission: authentication tokens, password fields, session identifiers, URL paths containing a verification or reset token, your user name and machine name, and user-specific file paths are removed or replaced. In both applications, where a version sends crash reports, crash reporting is on by default under the legitimate-interest basis described in Section 3 below, and you can turn it off at any time: in Automater Lite under Settings → Privacy & access (the same switch as usage statistics), in Automater Desktop under Settings → System → Privacy & telemetry.
Logs
Our backend records server-side logs of API requests, including IP address, user-agent, timestamp, and the response status. It also stores a sample of routine requests, and every failed or slow request, as activity events with the same details and, if you are signed in, your account ID. Section 6 says how long we keep both.
Automater AI Network (optional beta)
The Automater AI Network connects your own devices to each other over a private network. It is an optional beta, open by invitation only, and it is off by default. Joining requires Automater PRO. From Lite 0.1.21, the network tunnel installer is not part of the Lite installer: Lite downloads it from our update server (updates.automater.ai) when you join, and nothing is installed or connected until then. When you join, Lite installs a network tunnel service based on WireGuard (the Windows service “AutomaterTunnel”), which asks for Windows administrator approval, and your devices then connect through a hub operated by WEBRULON LLC.
Joining links an authenticated account to a registered device and a private overlay address. We process device names, platform, public WireGuard keys, account and device identifiers, address assignments, enrollment and revocation events, latest handshake time, and aggregate bytes sent and received. This operational information is required to authorize and operate the network; it is separate from optional product analytics.
Traffic passes through the hub. WireGuard encryption ends at the hub and is applied again for the next device, so the hub can see addresses inside the private network and any traffic that your applications do not encrypt themselves. SSH, SFTP and correctly configured HTTPS provide their own encryption. The private network alone does not provide end-to-end encryption against the hub operator.
On Windows, Automater Core (the background process that comes with Automater Lite) manages the network connection, even when the Lite window is closed. Closing the window does not sign you out. Signing out stops the local tunnel and asks our servers to remove the device’s access to the network; ending your session elsewhere removes it too. If the hub cannot receive the change, removal stays pending until the hub reconnects, and a pending removal does not confirm that traffic has stopped. A hub outage interrupts connectivity, and if we cannot confirm your session, the tunnel can disconnect.
Device private keys are generated on your device and kept in the operating system’s credential store; the tunnel service receives them in memory. Adding a phone, where available, uses an import file or QR code that contains that phone’s private key: anyone who obtains it can use those credentials until they are revoked. Our servers store, in encrypted form, the preshared keys needed to configure the hub. We exclude enrollment and network-configuration requests from our request logs. Automater Lite on platforms other than Windows cannot join the network.
We keep network audit events for 30 days; the latest operational counters are kept on each device record. Records of retired network addresses and configuration revisions, which prevent an address from being reused and let a removal complete, are kept separately from audit events.
2. How We Use Information
We use the information we collect to:
- create and authenticate your account, including delivering email verification links;
- provide, maintain, and improve the Service;
- process payments and renewals;
- diagnose and fix bugs through crash and error reports;
- understand product usage in aggregate — which versions are in use, which features are used, how often the applications fail (usage statistics; you may turn them off);
- measure website traffic, understand which pages and campaigns lead to sign-ups and purchases, and improve the website (Google Analytics, Cloudflare Web Analytics, Microsoft Clarity session recordings and heatmaps);
- measure Automater advertising on Google, Meta, OpenAI and X, and build audiences for it on Google and Meta (Google Ads, Google Signals, Meta Pixel, OpenAI Ads Measurement Pixel, X Pixel, and the server-side conversion events in Section 1);
- comply with legal obligations and enforce our Terms of Service;
- send you transactional email related to your account or subscription (we do not use your email address for marketing without separate consent).
3. Legal Bases (GDPR)
For users in the European Economic Area, the United Kingdom, and Switzerland, we process personal data on the following legal bases:
- Contract necessity (Article 6(1)(b)) — to create your account, authenticate you, deliver the Service you use or subscribed to (including device registration, usage sync, Cloud Voice, encrypted backup, chat history sync and the AI Network when you use them), issue and activate your license code, and bill you.
- Legitimate interest (Article 6(1)(f); see Recital 47) — to collect crash and error reports through Sentry from our servers, the legacy web application, Automater Lite and Automater Desktop, and to collect the usage statistics (and, in Automater Lite, the tips-and-offers counts) described in Section 1 from Automater Lite and Automater Desktop. We have determined that keeping the Service stable and secure and understanding in aggregate how the applications are used is a legitimate interest that is not overridden by your fundamental rights, given the scrubbing measures, the random and user-resettable installation identifier, the fixed event list, the absence of session content in uploads, the internal-only use of installation links, and the one-click opt-out described in Section 1. We also rely on our legitimate interest in measuring our advertising to send the server-side conversion events that Section 1 lists as not following your cookie choice (account sign-ups, newsletter and waitlist sign-ups, purchases with an account, and Automater Lite sign-ins on a new computer).
- Consent (Article 6(1)(a); ePrivacy Article 5(3)) — to load product-analytics scripts through PostHog in the legacy web application, and to set analytics, session-recording and advertising cookies on our websites, and to send the server-side conversion events that follow your cookie choice (Section 1). The Lite and Desktop applications load no third-party analytics SDK at all. On the websites, visitors in the European Economic Area, the United Kingdom and Switzerland see a consent banner, and until they choose analytics runs without cookies and advertising features are off; campaign references and UTM values may still be stored as described in Section 5.
- Legal obligation (Article 6(1)(c)) — to retain records of payment, tax, and similar transactions where applicable law requires it.
4. Service Providers and Third-Party Services
We use the service providers and third-party services listed below. Service providers process personal data only on our instructions. The services marked † also use what they collect for their own purposes, under their own privacy policies.
“Our websites” means automater.ai (including /upgrade and /intel), account.automater.ai, leaderboard.automater.ai, and classic.automater.ai while it is still online. “Before a choice” means before you click a button in our cookie banner. We show the banner only to visitors in the European Economic Area, the United Kingdom and Switzerland. Everywhere else the services below load with the page, except that the advertising services (Google Ads, Google Signals, Meta Pixel, OpenAI Ads Measurement Pixel and X Pixel) do not load when your browser sends a Global Privacy Control signal.
Loaded in your browser on our websites
| Provider | What it does on our websites | Where | Before a choice: US and other regions without a banner | Before a choice: EEA, UK, Switzerland | Privacy policy |
|---|---|---|---|---|---|
| Cloudflare, Inc. | Delivers our websites and API (network, security, encryption). Reads your country from our /cdn-cgi/trace address so we know whether to show the cookie banner. Cloudflare Web Analytics counts page views and load times without cookies. A Cloudflare script decodes the email addresses we hide from spam bots. |
All our websites and api.automater.ai | Yes | Yes | cloudflare.com/privacypolicy |
| Google Tag Manager (Google LLC; Google Ireland Ltd) | Loads the Google, Microsoft, Meta, OpenAI and X tags below and applies your cookie choice to them. Sets no cookies of its own. | All our websites | Yes | Yes; the tags it holds wait for your choice | policies.google.com/privacy |
| Google Analytics 4 † (Google) | Measures how our websites are used: pages, traffic sources, download clicks and other events. Cookies _ga, _ga_4GJGSXQ3KN. |
All our websites | Yes | Yes, without cookies until you accept | policies.google.com/technologies/partner-sites |
| Google Signals † (Google) | Google Analytics advertising features: demographic and cross-device reports and remarketing audiences, for visitors signed in to Google with ad personalization on. | All our websites | Yes, unless Global Privacy Control is on | No, only after “Accept all” | policies.google.com/technologies/partner-sites |
| Google Ads † (Google) | Measures which Google ads lead to sign-ups, leads and purchases (purchase value and currency) and can build remarketing audiences. Cookie _gcl_au, and Google cookies on doubleclick.net and google.com. |
All our websites | Yes, unless Global Privacy Control is on | No, only after “Accept all” | policies.google.com/technologies/partner-sites |
| Microsoft Clarity † (Microsoft Corporation) | Records clicks, scrolling, mouse movement and page layout as session replays and heatmaps, and contacts Microsoft’s c.bing.com. Cookies _clck, _clsk, and Microsoft cookies CLID, MUID, MR, SM, ANONCHK, SRM_B. |
All our websites, including /upgrade and the account pages | Yes | No, only after “Accept all” | microsoft.com/privacy/privacystatement |
| Meta Pixel † (Meta Platforms, Inc.; Meta Platforms Ireland Ltd) | Measures which Meta (Facebook, Instagram) ads lead to visits, leads, registrations and subscriptions (subscription value and currency) and can build ad audiences. Cookie _fbp. |
All our websites | Yes, unless Global Privacy Control is on | No, only after “Accept all” | facebook.com/privacy/policy |
| OpenAI Ads Measurement Pixel † (OpenAI) | Measures which OpenAI ads lead to visits, registrations, leads and subscriptions (plan, amount and currency). Cookies __oaiq_consent, __obref, and Cloudflare cookies on openai.com. |
All our websites | Yes, unless Global Privacy Control is on | No, only after “Accept all” | openai.com/policies/privacy-policy |
| X Pixel † (X Corp.) | Measures which of our ads on X led to sign-ups, leads and purchases; sets cookies on X’s domains. | All our websites | Yes, unless Global Privacy Control is on | No, only after “Accept all” | x.com/privacy |
| Google Fonts (Google) | Serves the fonts on account.automater.ai. Google receives your IP address and browser details. | account.automater.ai | Yes | Yes | developers.google.com/fonts/faq/privacy |
| Stripe, Inc. | The payment form, payment processing and subscription billing. Stripe’s form also loads fraud checks from hCaptcha (Intuition Machines, Inc.) and HUMAN Security, Inc. Cookies __stripe_mid, __stripe_sid, and Stripe, hCaptcha and HUMAN cookies on their own domains. |
automater.ai/upgrade, account.automater.ai payment pages, Stripe’s billing portal | Yes, when a payment page opens | Yes, when a payment page opens | stripe.com/privacy · hcaptcha.com/privacy · humansecurity.com/privacy-policy |
| X (X Corp.) | Shows X posts quoted in Intel articles. | Intel articles that quote an X post | Yes, when you scroll near the post | No, only after “Accept all” or a click on the post | x.com/en/privacy |
| LinkedIn (LinkedIn Corporation) | Shows LinkedIn posts quoted in Intel articles. | Intel articles that quote a LinkedIn post | No, only when you click to load the post | No, only when you click to load the post | linkedin.com/legal/privacy-policy |
Not loaded in your browser
| Provider | What it does | Legal basis | Region | Privacy policy |
|---|---|---|---|---|
| Stripe, Inc. | Payment processing and subscription records | Contract necessity | United States | stripe.com/privacy |
| Our own mail server | Sends account and purchase email (verification, license codes, receipts). No outside email service receives it. | Contract necessity | Our servers in the United States (Secaucus, New Jersey) | — |
| Cloudflare, Inc. | Receives email sent to @automater.ai addresses and forwards it to our mailbox (Email Routing); stores our encrypted database backups for 30 days (R2) | Contract necessity; legitimate interest | Global network | cloudflare.com/privacypolicy |
| Sentry (Functional Software, Inc.) | Crash and error reporting from our servers and apps | Legitimate interest | United States | sentry.io/privacy |
| PostHog Inc. (Cloud EU) | Product analytics in the legacy web app (app.automater.ai) | Consent (opt-in) | European Union | posthog.com/privacy |
| Google LLC / Google Ireland Ltd | Nightly server-side mirror of each installation’s daily, pseudonymous app usage statistics to Google Analytics (Measurement Protocol; see Section 1) | Legitimate interest | United States | policies.google.com/privacy |
| Meta Platforms, Inc. / Meta Platforms Ireland Ltd † | Server-side conversion events (Conversions API) for download clicks, account, newsletter and waitlist sign-ups, and purchases (Section 1) | Consent for download clicks; legitimate interest for sign-ups and purchases | United States | facebook.com/privacy/policy |
| OpenAI † | Server-side conversion event when you sign in to Automater Lite on a new computer (Section 1) | Legitimate interest | United States | openai.com/policies/privacy-policy |
| Google, X Corp., Meta and OpenAI † | Where enabled, server-side conversion events for downloads, matched Automater Lite sign-ins and purchases that passed the consent check (Section 1) | Consent | United States | policies.google.com/privacy · x.com/privacy |
We do not sell your personal information to third parties under any definition of “sell” we are aware of. Under the California Consumer Privacy Act, allowing Google (Google Ads and Google Signals), Meta, OpenAI and X to use your browsing information for cross-context behavioral advertising may be considered “sharing”. You can opt out via the “Do Not Sell or Share” control in the website footer or by enabling the Global Privacy Control signal in your browser, which we honor. That opt-out turns off our advertising tags and the server-side conversion events that follow your cookie choice; those for account, newsletter and waitlist sign-ups, purchases with an account and Automater Lite sign-ins (Section 1) are sent regardless.
5. Cookies & Telemetry
On our websites (automater.ai, classic.automater.ai, account.automater.ai, leaderboard.automater.ai):
| Category | What | Examples | Duration | Your control |
|---|---|---|---|---|
| Essential | Signing in, remembering a referral code or the offer you arrived from, your cookie choice, your theme and display preferences | access_token, automater_ref, automater_consent, automater_hero_theme, automater-theme, automater_promo, automater_fomo |
session to 1 year | always on |
| Payment | Stripe’s payment form and its fraud checks (hCaptcha, HUMAN Security), on payment pages only | __stripe_mid, __stripe_sid, and Stripe, hCaptcha and HUMAN cookies on their own domains |
set by each provider | always on when a payment page opens |
| Analytics | Google Analytics visitor identifier | _ga, _ga_* |
up to 2 years | banner or Cookie settings (EEA/UK/CH) · Section 8 |
| Session recording | Microsoft Clarity visit identifiers | _clck, _clsk, and Microsoft cookies CLID, MUID, MR, SM, ANONCHK, SRM_B |
set by Microsoft | banner or Cookie settings (EEA/UK/CH) · Section 8 |
| Advertising | Google Ads and Google Signals, Meta Pixel, OpenAI Ads Measurement Pixel, X Pixel | _gcl_au, _fbp, __oaiq_consent, __obref, and cookies the providers set on their own domains (for example doubleclick.net, google.com, openai.com) and cookies X sets on its own domains |
set by each provider | banner or Cookie settings · Global Privacy Control · Google Ads Settings |
| Embedded posts | X and LinkedIn posts quoted in Intel articles | cookies X and LinkedIn set on their own domains | set by each provider | see Section 4 |
| Campaign attribution | A random reference and the first and latest visits with campaign or ad-click parameters: time, landing path, referring site and UTM values; click identifiers only when advertising is allowed | automater_attr cookie, automater_attr_v1 local storage |
cookie: 90 days; attribution used within 90 days of the first tagged visit | GPC, “Essentials only”, and no choice in the EEA/UK/CH remove click identifiers; reference and UTM values remain |
If you visit from the European Economic Area, the United Kingdom or
Switzerland, we display a consent banner on your first visit. Until you
make a choice, Google Analytics runs without cookies; session recording
and advertising features are off. The campaign attribution reference and
UTM values described above may still be stored without advertising click
identifiers. Your
choice is stored in the automater_consent cookie for 12 months and applies to all of the websites above; change it at any time
via “Cookie settings” in the footer. Elsewhere, these cookies are set when
you load the page and you may opt out as described in Section 8. We honor
the Global Privacy Control browser signal as a refusal of advertising
cookies. Choosing “Essentials only” in the banner or in “Cookie settings”
refuses advertising cookies everywhere and, in the European Economic
Area, the United Kingdom and Switzerland, analytics and session-recording
cookies too.
In the Automater applications, we distinguish four categories of client-side storage:
- Essential. Required for the Service to function — for example, the cookie or local-storage entry that keeps you signed in. Always on; cannot be disabled.
- Usage statistics. The daily counts and installation identifier described in Section 1, kept in the application’s local storage under a random installation identifier and uploaded to our servers. On by default; may be turned off at any time, which also deletes the locally buffered counts and, when turned back on, issues a new installation identifier.
- Crash reports. Sentry’s crash-reporting integration, in versions that include it. On by default on the legitimate-interest basis described in Section 3. May be turned off at any time.
- Tips and offers counts. The per-day counts described in Section 1, kept in Automater Lite’s local storage until they are uploaded. On by default; may be turned off at any time under Settings → App updates.
You can change these choices at any time — in Automater Lite under
Settings → Privacy & access (one switch covers usage statistics and crash
reports), in Automater Desktop under Settings → System → Privacy & telemetry (the
first-run onboarding also offers separate switches for crash reports and
usage statistics). Setting DO_NOT_TRACK=1 in the environment turns both off. Tips-and-offers counts in Automater Lite have their own switch under Settings → App updates and are not affected by DO_NOT_TRACK. The applications never record session replays.
6. Data Retention
| Data class | Retention |
|---|---|
| Encrypted database backups | 30 days, then deleted |
| Account record | Until you delete the account, plus 30 days for backup expiry |
| Activity events (audit trail and a sample of API requests, which can include IP address, user-agent and account ID) | 90 days; error and critical events are kept until deleted (used for support, security, fraud prevention and product analysis) |
| Email verification tokens | 24 hours; the token field is set to NULL when you verify or when the link expires |
| Password reset tokens | 1 hour; same null-after-use behavior |
| Stripe billing records | Per Stripe’s retention policy and our tax obligations (typically 7 years) |
| Server logs | 30 days |
| Sentry crash reports | 90 days (Sentry default), unless required for active investigation |
| Application usage statistics — daily event counts | 400 days, then deleted nightly |
| Application usage statistics — installation record (random identifier, version, OS, plan, country, first/last seen, matched download and campaign attribution) | Kept while the identifier is in use; orphaned when you reset it (turn statistics off and on) or uninstall; deleted on request with your support ID |
| IP addresses recorded with application usage uploads and website download-count records | Up to 90 days, then deleted nightly |
| Download attribution: IP address and user agent for every cookie choice; advertising cookie and click identifiers only when allowed (Section 1) | 7 days, then removed nightly |
| Download attribution: reference, campaign values, landing page, referring site, OS and matched installation identifier | 90 days, then the record is deleted nightly |
| Campaign attribution on account and form records | Kept with the account, newsletter or waitlist sign-up, contact message or email-link request; no separate automatic attribution expiry |
Browser attribution (automater_attr cookie and automater_attr_v1 local storage) |
Cookie lifetime: 90 days; attribution is used only within 90 days of the first tagged visit |
| PostHog analytics events (legacy web app, if you opt in) | Up to 7 years per PostHog default; configurable on request |
| Google Analytics event-level data | Up to 14 months (our Google Analytics event-data retention setting); aggregated reports are retained by Google without a time limit |
| Google Signals data | Held by Google under its own policy; membership of a remarketing audience expires after the period we set for that audience |
| Microsoft Clarity session recordings | 30 days; favorite recordings and a random sample are kept for up to 9 months (Microsoft’s Clarity retention) |
| AI Network audit events | 30 days |
| Chat history sync (Section 1) | Until the chat is deleted or you ask us to delete your synced history; a deleted chat leaves a record of its identifiers and deletion time; copies in encrypted database backups expire 30 days later |
You may request earlier deletion of your account and its associated records by emailing privacy@automater.ai; see Section 8.
7. International Transfers
We are based in the United States and process your information there, on our own servers in the United States (Secaucus, New Jersey) and through the providers listed in Section 4, some of which also process it in other countries. Specifically:
- PostHog Cloud EU — analytics data from the legacy web application is stored in the European Union (Frankfurt). No outside-EU transfer occurs for this data class.
- Sentry (US) — crash and error reports are stored on Sentry’s US infrastructure.
- Stripe (US) — payment data is processed in the United States under PCI-DSS controls.
- Cloudflare (global network) — our websites, API and inbound email pass through Cloudflare’s global network, and our encrypted database backups are stored in Cloudflare R2.
- Google, Microsoft, Meta, OpenAI and X — the website analytics, session recordings and advertising measurement described in Section 4, and the server-side conversion events and Google Analytics mirror described in Section 1, are processed by these companies, including in the United States; the services marked † in Section 4 also use this data for their own purposes under their own privacy policies.
- Voice providers — when Automater Cloud Voice uses an outside provider (Section 1), that provider processes the audio or text, including in the United States.
Where the law requires a transfer mechanism, we rely on the recipient’s certification under the EU-U.S. Data Privacy Framework and its UK and Swiss extensions where it has one, and otherwise on the European Commission’s Standard Contractual Clauses in its data processing terms.
8. Your Rights
Depending on your jurisdiction, you may have the right to:
- access the personal data we hold about you;
- correct inaccurate personal data;
- request deletion of your personal data (“right to be forgotten”);
- restrict or object to processing;
- request a machine-readable copy of your data (data portability);
- withdraw consent at any time, where processing is based on consent (you may also do this for analytics directly through the cookie banner);
- lodge a complaint with your local data-protection authority.
Opting out of website analytics
- Use the consent banner (EEA/UK/CH) or “Cookie settings” in the website footer at any time: “Essentials only” refuses or withdraws advertising cookies everywhere, and analytics and session-recording cookies in the EEA, the UK and Switzerland. Elsewhere, Google’s add-on below turns off Google Analytics.
- Install Google’s opt-out browser add-on: https://tools.google.com/dlpage/gaoptout.
- Turn off Ads Personalization for your Google account: https://adssettings.google.com. How Google uses data from sites that use its services: https://policies.google.com/technologies/partner-sites.
- Microsoft Clarity: Microsoft Privacy Statement https://privacy.microsoft.com/privacystatement, Clarity terms https://clarity.microsoft.com/terms, Microsoft ad settings https://account.microsoft.com/privacy/ad-settings.
- Meta Pixel and OpenAI Ads Measurement Pixel: Meta’s privacy policy https://www.facebook.com/privacy/policy/ and OpenAI’s privacy policy https://openai.com/policies/privacy-policy/. “Essentials only” and Global Privacy Control turn both off.
- X Pixel: X’s privacy policy https://x.com/privacy. “Essentials only” and Global Privacy Control turn it off.
- Enable Global Privacy Control in your browser; we treat it as a refusal of advertising cookies and of any “sharing” under the CCPA, except the server-side conversion events that Section 1 lists as not following it.
Opting out of application usage statistics and crash reports
- Automater Lite: Settings → Privacy & access → “Share usage statistics to help improve Automater Lite” (it covers crash reports too). Turning it off stops uploads immediately and deletes the locally buffered counts, except while the testing setting described in Section 1 is on.
- Automater Desktop: Settings → System → Privacy & telemetry, or the individual crash-report and usage-statistics switches shown during first-run onboarding.
- Automater Lite tips and offers counts: Settings → App updates → “Send anonymous tips & offers stats”.
- Any platform: set the environment variable
DO_NOT_TRACK=1before starting the application. - To have the statistics already stored under your Automater Lite installation deleted, copy your support ID (Settings → Privacy & access → Diagnostics & recovery → Copy support ID) and email it to privacy@automater.ai. This request also covers the matched download and campaign attribution linked to that support ID, including associated account or form attribution we can identify through the download reference. Include the support ID so we can find the installation record, whether or not it matched a download or account. Automater Desktop does not show its identifier.
If you are a California resident, you also have rights under the California Consumer Privacy Act (CCPA), including the right to know what personal information we collect about you, the right to delete it, and the right to opt out of any “sale” or “share” of personal information (see Section 4 regarding Google Ads, Google Signals, Meta, OpenAI and X).
To exercise any of these rights, email privacy@automater.ai from the email address associated with your account. We aim to respond within 30 days. A self-serve data-rights portal is on our roadmap; until it ships, all requests are handled manually.
9. Children
The Service is not directed to children under 13 (or 16 in the European Economic Area), and we do not knowingly collect personal information from children. If you believe a child has provided us with personal information, please email privacy@automater.ai and we will delete it.
10. Security
We use industry-standard measures to protect personal data, including TLS in transit, encrypted database backups, scoped database credentials, and least-privilege access controls. No system is perfectly secure; we encourage you to use a strong, unique password and to enable any multi-factor-authentication options we offer.
11. Changes to This Policy
We may update this Privacy Policy from time to time. When we do, we will revise the “Effective date” at the top of this document and, if the changes are material, we will provide reasonable advance notice (for example, by email or by an in-app notice). Your continued use of the Service after the effective date of the revised Privacy Policy constitutes acceptance of that Policy.
12. Contact
Questions about this Privacy Policy or how we handle your personal data? Email privacy@automater.ai. For all other questions, email support@automater.ai.