Trust and transparency

Specific controls. Clear limits.

Autoqueue publishes the boundaries of the product, the exact access its extension requests, and what its evidence can and cannot prove. No trust badge replaces those details.

What Autoqueue does

  • Uses trusted public sources for supported drop signals.
  • Sends an email alert and, on Auto-Queue, sends an approved store URL to the member's authenticated browser connection.
  • Opens only allowlisted official retailer or official event URLs.
  • Leaves the queue, captcha, cart, payment, and checkout to the member.

What Autoqueue never does

  • Does not ask for or store retailer login or payment credentials.
  • Does not solve captchas, cart products, check out, bypass queues, automate refreshing, scrape retailers, or imitate human behavior.
  • Does not use affiliate links or paid click detours.
  • Does not automate a personal social-media account.

Browser extension

Minimal extension permissions

The source manifests for Chrome, Firefox, and Safari describe the same narrow access. The table explains each permission and its boundary.

Permission or originWhy it existsWhat it does not grant
storageSaves the access key, install id, connection status, dedupe keys, and small reconnect settings locally.Does not expose general browser history or arbitrary files.
alarmsRuns the connection watchdog and silence check.Does not read pages or automate retailer actions.
https://queue.autoqueue.app/*Allows the extension to connect to Autoqueue's bridge.Does not grant access to retailer sites.

The current extension does not request the tabs permission, inspect tab metadata, read browsing history, or read page contents. It uses the browser's standard tab and window creation APIs to open a validated URL.

These are extension permissions, not a claim about the entire account service. The website processes the account, security, billing, preference, and delivery records described in the Privacy Policy.

Official distribution

Available on official browser stores

Install Autoqueue only from the official listings below. Availability on a store is not an endorsement, certification, or guarantee by the platform.

ChromeInstall from Chrome Web StoreFirefoxInstall from Firefox Add-onsSafariInstall from Mac App Store

Account controls

Privacy and security controls

  • TLS protects transport to the website and Autoqueue bridge.
  • Bridge access keys are hashed for validation. Encrypted token material is retained only where the dashboard must display the member's key.
  • One active browser binding limits a key to one browser install at a time; members can switch browsers from the dashboard.
  • Operational logs use user or token ids instead of raw secrets where practical.
  • Autoqueue does not sell personal information or share a member's access key with retailers.
Privacy PolicyTermsSetup guideEmail support

Public records

Evidence and transparency

Autoqueue publishes three different kinds of evidence. Each answers a narrow question, and none substitutes for the others.

Alert evidence

Public daily drop logs include only non-invalidated events with evidence that the server sent at least one browser alert or the email provider accepted at least one alert.

They do not prove stock, queue entry, browser tab execution, inbox placement, or purchase.

Read the public drop logs

Scheduled endpoint checks

Autoqueue's first-party status service checks the website/account path and the alert engine every 60 seconds and publishes unknown when recent evidence is unavailable.

These checks do not prove complete source coverage, retailer availability, inbox delivery, or browser execution.

View Autoqueue status and incident history