Docs

Getting started.

Everything you need to know to install Sweep Collector, hook up an account, and let the scheduler take it from there. If anything's missing, email us. These pages will grow with the catalog.

Install the desktop app

Sweep Collector is a desktop app. It runs on macOS and Windows today (Linux is on the roadmap; see our repo for status).

  1. Hit Download on the home page and grab the build for your OS.
  2. On macOS, open the .dmg and drag Sweep Collector.app into Applications. On Windows, run the .exe installer.
  3. Launch the app. The first time it runs it'll set up a local SQLite database under your user data directory and ask you to sign in.

Auto-updates ship through the same channel. Once the app is installed, new versions land in the background and prompt you to relaunch.

Create your account

Accounts are managed through this website. The desktop app signs in against the same credentials.

  1. Go to /signup and create an account with your email and a password.
  2. Check your inbox for a verification email and click the link. Verified accounts can sign in to the desktop app.
  3. Open /account and start a subscription. Checkout runs through Stripe; you pick the number of personas (usually one) and the rest of the flow is standard card capture.

You can change the number of personas, update your payment method, or cancel any time from the Manage subscription button. It opens the Stripe Customer Portal.

Add your first site

Once the app is signed in and you have an active subscription, the dashboard will show your catalog of supported sites. To get one running:

  1. Pick a site from the catalog and click Add account.
  2. Sweep Collector opens a real Chrome window (using your installed Chrome, not a bundled Chromium) for you to log in. Cookies persist in a per-site profile directory after that, so you only log in once.
  3. Enter the credentials you want stored locally for re-login. They're encrypted with your OS keychain and never leave your machine.
  4. The site's card on the dashboard now shows a schedule. Toggle Auto-run on and you're done.

Don't see a site you need? Email us. We add sites on request and the catalog ships through normal app updates.

How the scheduler works

Each site has a cadence baked into the catalog (typically every 25 hours for a daily-bonus claim that's gated on a 24-hour timer). The scheduler ticks every 30 seconds and fires jobs that are due.

  • Jobs run in the background. The app keeps a small browser context per site, drives Chrome through it, and records the run's logs and balance snapshot to the local database.
  • If your laptop is asleep when a job is due, the scheduler picks it up the next time it ticks. There's no make-up window; a missed run is just one missed cycle.
  • You can run a job ad-hoc from the site card's Run now button at any time.

Run history lives on the site detail panel: open the card, scroll the activity list, and you'll see every claim with timestamps, the resulting balance, and a log download for the curious.

The persona model

A persona is one real person's set of accounts across the catalog: one gains.com login, one chumba login, and so on. Most people only need one persona.

You'd add a second persona if a second real person is sharing the app: a spouse, a roommate. Each persona is one license, one Stripe quantity, and one isolated set of credentials, cookies, and balance history. The desktop app's persona picker switches between them.

We deliberately don't support multiple accounts at the same site for the same persona. Every site we automate treats account-stacking as a ban-worthy signal.

Where your data lives

Sweep Collector is local-first. The split between what's stored on the server and what stays on your machine:

On the server (this website's Worker and database)

  • Your account email, hashed password, and email verification status.
  • Billing state: Stripe customer and subscription IDs, quantity (persona count), period dates. No card numbers; that's all Stripe.
  • License rows that link each persona to your account (one row per active persona, plus a device-binding fingerprint so the desktop app knows it's activated).

On your machine (local SQLite and per-site Chrome profiles)

  • Site credentials, encrypted with your OS keychain via Electron's safeStorage (the same primitive 1Password and Slack use). Stored as opaque blobs.
  • Cookies, localStorage, and IndexedDB for each site, kept in a per-site Chrome profile directory under your user data folder.
  • Balance history, run logs, and schedule state, all in a single SQLite file next to the database.

No telemetry. No analytics on the marketing site. The Worker only sees what it needs to authenticate your sessions and bill you.

Want it gone? /account has a Danger Zone that deletes your account, cancels the Stripe subscription, and removes the server-side rows. The desktop app's data is yours to remove from your user data directory when you're done with it.

Getting help

Email nick@kyter.com with anything: bugs, site requests, billing questions, "is this broken or am I doing it wrong." We read every message.