Back to Autoqueue

Privacy Policy

Last updated: June 12, 2026

This Privacy Policy explains how Dcipher LLC collects, uses, shares, and protects information when you use Autoqueue, including the website, dashboard, email alerts, and browser extension.

Information We Collect

  • Account information, such as your email address, approval status, selected plan or tier, email alert preferences, and administrative account notes.
  • Authentication and security information, such as password hashes, two-factor authentication setup data, session records, IP address, browser user agent, and security logs. We do not store your raw password.
  • Extension authentication information, including your Autoqueue access key and a generated extension install id. The extension stores the key and install id locally in your browser. The bridge receives them to authenticate the connection, validates the key, and uses the install id for first-device binding.
  • Service activity, such as whether a connection authenticated, whether an alert was sent, whether a queue signal matched, and whether a device binding was reset. Logs use user ids or token ids where practical rather than raw secrets.
  • Email delivery information from our email provider, such as delivery, bounce, and failure status for Autoqueue service emails.
  • Billing information if paid billing is enabled. Payment details are handled by our payment processor. We do not store full payment card numbers.

How We Use Information

  • To create and secure your Autoqueue account.
  • To approve, disable, revoke, or reset access to Autoqueue features.
  • To authenticate the browser extension and enforce one active device binding for queue access.
  • To send queue-live alerts, upcoming-drop notices, account emails, and service updates.
  • To operate, debug, protect, and improve Autoqueue.
  • To prevent abuse, key sharing, fraud, unauthorized access, and activity that would violate Autoqueue's compliance boundary.

Browser Extension Data

  • The Autoqueue extension is a local actuator. It stores your access key, generated install id, connection status, and minimal local settings needed to connect.
  • The extension connects to the Autoqueue bridge using WebSocket over TLS. The access key is sent in the first auth message, never in a URL query string.
  • When Autoqueue detects a queue-live signal, the bridge sends an approved store URL to the extension. The extension opens that URL in a browser tab.
  • The extension does not solve captchas, bypass queues, automate checkout, scrape retailer pages, or act on your behalf on a retailer site.

How We Share Information

  • We do not sell personal information.
  • We may share information with service providers that help us run Autoqueue, such as hosting, database, email delivery, analytics, authentication, and payment providers.
  • We may disclose information if required by law, to protect rights and safety, to investigate abuse, or as part of a merger, acquisition, financing, or sale of assets.
  • We do not share your access key with retailers.

Data Retention

  • We keep account and service records for as long as needed to operate Autoqueue, comply with legal obligations, resolve disputes, enforce agreements, and maintain security.
  • We may retain logs for a limited period for security, debugging, abuse prevention, and reliability.
  • If your account is disabled or revoked, we may retain records needed to prevent abuse or preserve an audit trail.

Your Choices

  • You may contact us to request access, correction, deletion, or export of personal information, subject to identity verification and legal limits.
  • You may ask us to disable email alerts or queue access.
  • You may request a device binding reset if you reinstall the extension or move to a new browser.
  • You can remove locally stored extension data by uninstalling the extension or clearing its browser storage.

Security

  • We use technical and organizational measures designed to protect Autoqueue, including TLS, hashed access keys, encrypted stored secrets where needed, least-privilege access, and admin-only controls.
  • No system is perfectly secure. You are responsible for keeping your account credentials, email inbox, two-factor authentication codes, and Autoqueue access key safe.

Children

  • Autoqueue is not intended for children under 13. We do not knowingly collect personal information from children under 13.

Changes

  • We may update this Privacy Policy from time to time. The updated version will be posted on this page with a new last updated date.

Contact

  • Autoqueue is operated by Dcipher LLC. Contact us at labs@dcipher.dev.