About Meta AI Automator

Privacy

Meta AI Automator Privacy Policy

Effective date: July 27, 2026

This Privacy Policy explains what information the Meta AI Automator browser extension (the “extension”, “we”) handles, why it is used, where it is stored, and the choices available to you. Meta AI Automator is an independent product and is not affiliated with, endorsed by, or sponsored by Meta Platforms, Inc. Meta AI and related marks belong to their respective owners.

Summary. Prompts, queues, reference images, Meta AI page state, and generated media are processed in your browser and exchanged directly with Meta AI only when you use the extension. We do not receive your creative content on our servers. Our services handle only the minimum account, membership, installation, and usage-count information required for sign-in, plans, quotas, support, security, and abuse prevention. We do not sell personal data or show advertising.

1. Information we collect and process

1.1 Account information

  • When you sign in with Google or email and password, Firebase Authentication may provide your email address, display name, profile photo URL, and Firebase user ID.
  • We do not see or store your Google password. Email/password credentials are transmitted over HTTPS directly to Firebase Authentication and are not stored by us.
  • Firebase session and refresh tokens may be stored in Chrome extension storage to keep you signed in. They are removed when you sign out or uninstall the extension.

1.2 Membership, installation, and usage data

  • A randomly generated installation identifier may be stored to associate an installation with an account and prevent repeated trial or free-plan abuse. It is not derived from hardware identifiers.
  • Membership tier, trial state, access flags, and relevant start or expiry timestamps.
  • Daily prompt-run counts, reset time, and request identifiers used to enforce Starter quotas and prevent duplicate counting. We count runs; the prompt text is not stored on our servers.

1.3 Creative and operational data stored locally

  • Prompt text, queue items, output names, generation settings, character selections, reference-image selections, download counters, and recent project state are stored in Chrome extension storage on your device.
  • Reference files may be stored locally in the browser so they can be attached to Meta AI when you run a queue.
  • Operational logs are kept locally for troubleshooting for up to approximately one hour and are limited to the most recent entries.
  • Completed queue items may be compacted and stale queues may be reset after approximately 24 hours. Other local data remains until you clear it or uninstall the extension.

1.4 Meta AI page content

  • The extension reads the state of supported meta.ai pages to locate the prompt box, attach selected media, submit prompts, detect sign-in or creation-limit messages, monitor generation, find completed results, and start downloads.
  • This page state is processed locally in your browser. It is not sent to our servers.
  • Prompts and selected reference files are sent directly from your browser to Meta AI only when you run them, under your own Meta AI account and Meta’s terms and privacy practices.
  • Generated media may be retrieved from Meta AI or Meta’s content-delivery domains and saved through Chrome’s download system at your request.

1.5 Information we do not collect

  • No general browsing history, keystroke monitoring, or content from unrelated websites.
  • No prompt text, reference images, generated images, or videos on our servers.
  • No payment-card or bank information.
  • No advertising identifiers, and no creative or account data is sold to advertisers or data brokers.

2. How we use information

  • Account data for authentication, profile display, account support, and security.
  • Installation and membership data for plan access, trial enforcement, licensing, and abuse prevention.
  • Usage counts for Starter daily quota enforcement and displaying usage/reset status.
  • Local creative data solely to provide queue automation, reference attachment, generation monitoring, filenames, and downloads requested by you.

We use information only to provide, maintain, secure, and improve the extension; respond to support requests; prevent misuse; and comply with applicable law. We do not use it for advertising, creditworthiness, or lending decisions.

3. Storage, service providers, and sharing

  • Google Firebase provides Authentication, Cloud Firestore, and Cloud Functions for account, membership, and usage management.
  • Meta AI receives prompts and selected media directly from your browser when you initiate automation. Meta’s handling of that content is governed by your relationship with Meta and its own terms and privacy practices.
  • Chrome stores local extension data and performs downloads requested through the extension.
  • We do not sell personal information or share it with advertisers or data brokers. Information may be disclosed if required by law or necessary to protect users, the extension, or our legal rights.

4. Data security

  • Connections to Firebase and Meta services use HTTPS/TLS.
  • Server-side account data is protected by Firebase Authentication and Firestore security controls.
  • Local data is isolated within Chrome’s extension storage environment, subject to the security of your browser profile and device.
  • Administrative access to server-side account records is limited to support, security, abuse prevention, and account management needs.

5. Data retention

  • Account, membership, and usage records are retained while needed to operate your account and as reasonably necessary for security, fraud prevention, legal obligations, and dispute resolution.
  • Local operational logs are retained for approximately one hour.
  • Local queues, settings, references, and related state remain until automatically cleaned up, cleared by you, or removed when the extension is uninstalled.

6. Your choices and rights

  • Sign out from the extension panel at any time.
  • Remove queue items and locally stored references using the extension controls.
  • Clear extension data through Chrome or uninstall the extension to remove locally stored extension data.
  • Request access to or deletion of server-side account information by contacting us. We may retain information that is legally required or reasonably necessary for security and fraud prevention.
  • You may also exercise privacy rights available under the laws that apply to you.

7. Browser permissions

  • storage / unlimitedStorage — stores queues, settings, references, authentication state, and logs.
  • activeTab / tabs / scripting / sidePanel — opens the side panel and operates only on supported Meta AI tabs.
  • downloads — saves generated media and applies requested filenames.
  • identity — supports Google sign-in.
  • alarms — schedules and keeps track of queue work and delays.
  • clipboardWrite — copies user-requested text or data to the clipboard.
  • Host access — limited to Meta AI pages, Meta media delivery domains, and Firebase endpoints required for authentication, membership, and quotas.

8. International processing

Firebase and Meta may process information in countries other than your own. Their infrastructure and privacy terms govern processing performed by those services.

9. Children

The extension is not directed to children under 13, and we do not knowingly collect personal information from children under 13.

10. Changes to this policy

We may update this policy as the extension or applicable requirements change. The effective date above will be updated when revisions are published. Material changes may also be communicated in the extension or release notes where appropriate.

11. Contact

YouTube: @quiki.studio
Support: Buy Me a Coffee