Account safety
How Sellu automates aggressively without looking like a bot.
Automation is only worth it if your account survives it. Everything Sellu does runs inside your own browser session — no shared bots, no server-side logins — and every action goes through a safety layer designed to look like a fast human, not a script.
Human-like pacing
- Every write action (message, offer, repost, follow…) is queued with a per-action minimum delay plus random jitter — typically several seconds between actions.
- Quantity-scaled slowdowns: the bigger the batch, the longer the gaps (large jobs run up to 2.5× slower per action). A 200-item job spreads naturally over hours.
- Daily caps are enforced per action type — for example 80 messages, 60 offers, 100 follows, and 30 reposts per day.
Graceful failure handling
- Rate limits & captchas — on a 429 or an unsolved challenge, the entire queue pauses (about a minute) and you get a visible banner and toast, instead of the extension hammering the marketplace. DataDome and Cloudflare challenges are solved silently in the background when possible.
- Blocked requests — if the marketplace blocks a request from the extension, it's transparently re-issued through the real page context.
- Expired sessions — a 401 triggers an automatic session refresh and one retry; logging out is detected and handled cleanly.
Your data stays local
Listings, orders, conversations, notes, SKUs — everything lives in your browser's local storage and IndexedDB. AI calls go from your browser straight to the provider you configured, with your own key. Nothing is proxied through our servers.
No safety layer makes automation risk-free
These protections dramatically reduce risk, but any automation is used at your own discretion. Start with conservative intervals and small batches, especially on a seasoned account you care about.