📁 Profiles, Emails, & Info Lists

SweepFlow runs off reusable data lists that power automated sweep entries. This page breaks down each list type and shows you how to obtain and organize them properly.

---

👤 Profiles (Preset Manager)

Profiles are simple presets that bundle all your lists into one easy-to-select config. Each profile links:

• 📧 Email List

• 🌐 Proxy List

• 🏠 Address List

• 🔐 Account List

• 💳 Card List

Profiles help you save time by allowing 1-click setup during task creation 📸

---

📧 Email Lists

Email lists are essential for entries. You can use:

• ✅ Gmail

• ✅ Outlook (can be generated directly inside SweepFlow)

• ✅ Yahoo

• ✅ iCloud

• ✅ Catchalls (e.g. [e-mail])

---

🛠 How to Get Emails

1. Generate Outlooks in SweepFlow

   • Use the built-in Outlook generator under the Tools tab.

2. Buy Gmail / Yahoo / iCloud

   • Trusted marketplaces: OGUsers, Swapsea, EpicNPC, or reputable Discord servers.

   • Look for aged and IMAP-enabled accounts.

3. Use AYCD (AutoSolve Suite)

   • AYCD helps you generate, warm, and manage bulk emails.

   • Key tools include:

     • Generator – Auto-creates emails using catchalls or real domains

     • Inbox Manager – IMAP login to monitor inboxes for verification links

     • AutoSolve – Solves captchas automatically during signups

     • Session Handling – Keeps logins alive using cookies and profiles

🔁 AYCD is especially useful when using Gmails or Outlooks in high volume across many modules.

---

💡 Catchalls Explained

Catchalls let you use unlimited email aliases under one domain.

Example:

• Registered domain: sweeploot.com

• Entry emails:

  • [e-mail]

  • [e-mail]

  • [e-mail]

  • All go to the same inbox

---

📦 How to Set Up a Catchall

1. Buy a domain

   • GoDaddy

   • Namecheap

   • Google Domains

2. Set up email forwarding using one of:

   • ImprovMX (Free)

   • Zoho Mail (Free/Pro)

   • Google Workspace (paid)

   • Cloudflare Email Routing (Free)

3. Forward all emails to your main inbox (e.g., [e-mail])

4. Use AYCD or SweepFlow to generate aliases for entries

✅ Perfect for scaling and creating unique identities with one inbox

---

🧪 SweepFlow Proxy Load

SweepFlow’s backend is extremely light. You don’t need hundreds of proxies or huge data plans:

• 1 proxy per entry to keep entries unique

This makes high-quality resi or ISP plans both affordable and effective — no wasted overhead.

---

Pro Tips

• Residential first — works best for nearly all sites

• ISP if needed for consistency or strict security modules

• DC only if you know the module has weak protection

• Don’t reuse the same proxy for 10+ tasks at once

• Use rotating resi or ISP for harvesters and AYCD to boost v3 scores

---

🏠 Address Lists

Some sweeps require real addresses, or flag duplicate entries. Jigging helps you get around this.

Each address list can contain 1 or many entries. Most sites will require:

• Street Address

• City

• State

• ZIP

---

🧪 How to Jig Addresses (Safely)

Use these common jigging patterns:

Base Address	Jigged Versions
123 Main St Apt 1	123 Main St #1
123 Main St Apt 1	123 Main Street Apt. One
123 Main St	123 Main St (Back)
123 Main St	123 Main St FL 1
123 Main St	123 Main St (Upstairs)
123 Main St	123 Main Street B
123 Main St	123 Mαin St (replace “a” with Greek “α”)
123 Main St	123 Main St Bldg A
123 Main St	123 Main St, Unit 1

Avoid excessive or unrealistic jigging — stick with postal-acceptable formats.

You can use Excel or Python to generate 100s of variations easily.

---

🔐 Account Lists

These are for sweeps that require sign-in or account creation.

Format:

[e-mail]:password123

Use AYCD to automate signups and manage login sessions.

You can also monitor inboxes for account verification links.

---

💳 Card Lists

Card lists are rarely needed but supported. Each entry contains:

• Card Number

• Expiry Date

• CVV

• Billing ZIP (optional)

This is used only in modules that involve purchase-required entries, free trials, or bonus game unlocks.

🔄 Majority of sweepstakes do not require a card list — it’s a niche use case.

---

🧠 Modular System

SweepFlow only prompts for what’s needed per module.

If a task doesn’t need cards or logins, those fields are hidden — so you’re never overwhelmed.

---