Skip to content
AAUTO BOTBrowser automation
HomeContact
HomePrivacy
Back to Auto Bot

Privacy and data use

Auto Bot Privacy Policy

This policy explains what information Auto Bot processes, why it is needed, where it is stored, and the choices available to you when using our Chrome or Firefox extension and website.

Effective: October 8, 2026Last updated: October 8, 2026

Privacy summary

Auto Bot uses Google Sign-In only to authenticate you and confirm that you are a valid user. We request basic identity information only: your Google account identifier, email address, display name, and profile information made available through the basic openid, email, and profile scopes. We do not request access to Gmail, Google Drive, contacts, calendars, or your Google password.

Your Activities, Jobs, Variables, settings, and execution history are designed to remain in browser-extension storage on your device. We do not sell personal information.

1. Scope and contact

This policy applies to the Auto Bot website, browser extension, Google authentication flow, and account-entitlement service. In this policy, “Auto Bot,” “we,” “us,” and “our” refer to the Auto Bot service. Questions and privacy requests can be sent to [email protected].

2. Information we process

Google account information

When you choose “Continue with Google,” Google authenticates your account. Auto Bot receives a Firebase user identifier and basic account details such as your email address, display name, and profile information. We use this information to create or recognize your Auto Bot account, maintain your signed-in session, and determine your feature access.

Locally stored automation data

The extension can store Activities, Jobs, Variables, selectors, schedules, settings, execution history, logs, and user-created templates locally in extension storage. Variables and extracted content can contain information you choose to collect from websites. Screenshots, PDFs, JSON, and CSV files are created or downloaded only at your direction.

Browser permissions and website access

Auto Bot may request browser permissions such as tabs, scripting, storage, downloads, notifications, and access to websites selected by you. These permissions let your workflows open or focus tabs, interact with page elements, extract content, capture screenshots, download output, and run schedules. Optional website access can be reviewed or revoked through Auto Bot settings or browser controls.

Service and diagnostic information

Our server may receive standard request information needed to operate and secure the service, such as request time, IP address, browser or user-agent information, response status, and security logs. The account-entitlement service verifies your Firebase identity token and returns your access level; it does not receive your locally saved workflows as part of that verification.

3. How we use information

  • Authenticate your account and maintain a secure session.
  • Confirm account status, subscription plan, limits, and available features.
  • Run browser automations that you explicitly create, configure, or start.
  • Save your preferences and workflow data locally on your device.
  • Protect Auto Bot against abuse, fraud, unauthorized access, and technical failures.
  • Respond to support, security, privacy, and account-deletion requests.
  • Improve reliability and diagnose failures using limited technical information.

We do not use Google account information for advertising, and we do not sell or rent personal information.

4. Browser automation and website data

Auto Bot acts only on workflows and websites selected by you. Page content used by a local workflow is processed in the browser to perform the requested action. Auto Bot does not independently decide which websites to access or what information to extract.

A workflow can intentionally submit information to a third-party website—for example, entering text into a form or messaging service. In that case, the destination receives the information because you configured the workflow to send it. The destination’s privacy policy applies to its handling of that information. You are responsible for ensuring your automations comply with applicable law, website terms, and the rights of other people.

5. When information is shared

We share information only as needed to operate Auto Bot, follow your instructions, protect the service, or comply with law. Relevant recipients may include:

  • Google and Firebase: to provide Google authentication, account identity, and identity-token verification.
  • Hosting and infrastructure providers: to serve the Auto Bot website and entitlement API and maintain security and operational logs.
  • Websites selected by you: when your workflow navigates to, reads from, or submits information to those services.
  • Legal and security recipients: when disclosure is reasonably necessary to comply with law, prevent harm, investigate abuse, or defend legal rights.

We do not sell personal information or share it with data brokers.

6. Storage and retention

Local automation data remains in extension storage until you delete it, clear the extension’s storage, reset the extension, or uninstall it. Exported files remain wherever you save them and must be deleted by you.

Google/Firebase authentication data and your Auto Bot account identifier are retained while your account is active and for a limited period afterward when reasonably necessary for security, legal compliance, dispute resolution, or service integrity. Operational server logs may be retained for a limited period for security and reliability. We retain information only as long as reasonably necessary for the purposes described here.

7. Your choices and controls

  • You may sign out of Auto Bot at any time.
  • You may edit or delete locally saved Jobs, Activities, Variables, schedules, history, and recordings.
  • You may revoke optional website permissions through Auto Bot settings or your browser’s extension settings.
  • You may revoke Auto Bot’s Google account access from your Google Account security settings.
  • You may uninstall Auto Bot to remove its extension storage from that browser profile.
  • You may request access to or deletion of account information by emailing [email protected] from your account email.

8. Security

We use reasonable technical and organizational safeguards, including Google/Firebase authentication, verified identity tokens, HTTPS in production, restricted API access, and browser permission controls. No storage or transmission method is completely secure, so we cannot guarantee absolute security. Do not store secrets in a workflow unless you understand how the extension and destination website will handle them.

9. Children’s privacy

Auto Bot is not directed to children under 13, and we do not knowingly collect personal information from children under 13. Contact us if you believe a child has provided information to Auto Bot.

10. International processing

Google, Firebase, and infrastructure providers may process information in countries other than your own. Those locations may have different data-protection laws. We use providers and safeguards appropriate to the service and information involved.

11. Changes to this policy

We may update this policy when Auto Bot’s functionality, providers, or legal obligations change. We will publish the revised policy here and update the “Last updated” date. Material changes may also be communicated through the extension or website when appropriate.

12. Contact

For privacy questions, account access, or deletion requests, contact Auto Bot at [email protected].

AAUTO BOTBrowser automation

Home · Contact

© 2026 Auto Bot. Beta software.