Bypass terminology

These terms match how Bypass talks about setup and drops.

• Account — A registered login on a retailer. Managed in the Accounts tab.
• Account proxy — A proxy tied to a specific account for login / session work.
• Captcha — A challenge solved by you or a third-party solving API before checkout continues.
• Cook group — A Discord community sharing release info and setups. Ask them about strategy — Bypass does not coach illicit jigging.
• IMAP — Mail access used to pull OTPs / 2FA codes automatically.
• Jig — Altering profile details between orders so retailers are less likely to treat them as duplicates. Guidance belongs in your cook group, not these docs.
• Monitor — Work that watches a site for restocks or new products so checkout tasks can react quickly.
• PID / SKU — Product identifiers used to target a specific item.
• Profile — Shipping and billing data used to complete checkout.
• Proxy — An IP endpoint used to avoid bans and scale multiple tasks.
• Proxy list — A named group of proxies you assign to monitors or tasks.
• Session — Saved login state so an account does not need a full login every run.
• Site / module — The retailer integration you select when creating a task group.
• Task — A worker actively trying to cart and checkout a product.
• Task group — A collection of tasks for one site with shared settings.
• Task proxy — Proxies reserved for checkout workers (keep them separate from monitor lists when possible).
• Webhook — A Discord (or similar) URL that receives success, fail, or misc notifications.
• 2FA / OTP — One-time codes for login or account recovery; often fetched via IMAP.