Privacy Policy

Automate.ax collects the account information, usage data, and automation content needed to provide the service. We use this information to operate, secure, support, and improve Automate.ax.

We may share information with service providers that help us run Automate.ax, with integrations you direct us to use, or when required by law. We do not sell your personal information.

Connected Google accounts

When you connect Google, we store your account identity and encrypted authorization tokens. Depending on the permissions you grant and the automations you deploy, we access Gmail messages, attachments and labels; calendars and events; Drive files and metadata; documents, presentations and spreadsheets; forms and responses; Meet conference records; or Google Ads and Data Manager data. We use that access to run the actions and triggers you configure, including reading, creating, updating or deleting data when your automation requests it. We request additional permissions when your automation needs them.

Automation inputs, results and run history may contain Google data. Authorized members of your organization can access shared run data. Your automations can send data to other connected services, HTTP destinations or AI providers you choose. Review those destinations before deploying: they receive the data your automation sends and apply their own retention policies. Our infrastructure providers process data to host, secure and operate Automate.ax.

Our use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including its Limited Use requirements. We do not sell Google Workspace user data, use it for advertising, or use it to train general-purpose AI models. User-directed AI processing must serve your automation and must not use Google Workspace data for general model training.

We do not allow people to read Google user data except with your explicit agreement to access specific data, when necessary for security or legal obligations, or when the data is aggregated and anonymized for internal operations as permitted by Google's policy. These restrictions also apply to people and service providers working on our behalf.

Security and retention

We encrypt data in transit and in production storage, encrypt integration credentials, and restrict application access by account, organization and project permissions. Operational logs redact sensitive fields and are retained for up to 30 days.

Your organization's retention setting controls completed run history. The period starts when the connected run finishes. Running or waiting automations retain the data needed to continue until they finish or are deleted. Disconnecting or revoking a Google account stops the applicable access; it does not itself erase existing run history. Deleted production database records can remain in access-restricted recovery backups. Automated backups normally expire within seven days; manual recovery snapshots do not expire automatically. When fulfilling a deletion request, we review these copies and tell you their deletion schedule or the reason for continued restricted retention. We retain billing or other records when required by law.

Request access, correction or deletion

Email info@automate.ax to request access to, correction of, or deletion of your personal information or connected Google data. Include your Automate.ax account email and the organization or project concerned. Do not send passwords, tokens or message contents. We verify your identity and authority, confirm the scope and any effect on shared automations, and tell you when deletion is complete or which records must be retained and why.

You can revoke Google access in Connected Accounts or in your Google Account connections. A deletion request concerns copies held by Automate.ax; it does not delete originals in Google or copies already sent to destinations you control. Remove local exports and contact those destinations separately when needed.

Analytics and advertising measurement

We use Google Analytics to understand visits and product usage. We use the Meta Pixel, Meta Conversions API, ChatGPT Ads Measurement Pixel, and ChatGPT Ads Conversions API to measure whether ads lead to registrations, checkout starts, subscription activations, and workshop applications.

These services may receive page and campaign information, browser identifiers, IP address, user agent, and hashed account identifiers. Conversion reporting runs from our servers after the related account, billing, or workshop action succeeds. We do not send raw email addresses in these conversion events, and we opt ChatGPT Ads events out of future user-level personalization by OpenAI.