Question 1

What happens when my site needs a login?

Accepted Answer

Before any AI persona starts, a real browser logs into your site once using the credentials you provide, then every persona begins already inside the product, so they never see your login screen. If we can't get past your login, the test stops immediately with a clear explanation instead of burning your credits.

Question 2

Where are my credentials stored and how are they protected?

Accepted Answer

Credentials are encrypted (Fernet) the moment they reach our API and stored only in encrypted form. Encryption keys live in Google Secret Manager, never in code, config files, or logs. They're decrypted only inside the isolated test worker, by the browser automation that performs the login.

Question 3

How long do you keep my credentials?

Accepted Answer

They're deleted the moment your test finishes, whether it succeeds or fails. Nothing to expire, rotate, or worry about. The trade-off: re-running a test asks you to enter them again. We think that's the right trade.

Question 4

Does the AI ever see my passwords?

Accepted Answer

No. Only a deterministic browser script (no AI) ever touches credential values. It types them into your login form the same way a password manager would. The AI personas start after login is complete and work purely from what's on screen.

Question 5

My site uses Google/SSO login, 2FA, or CAPTCHA. Can you test it?

Accepted Answer

Yes, with Browser Login: you log in manually once in a real browser session (completing any SSO, 2FA, or CAPTCHA yourself), we capture that session, and every persona reuses it. We never automate third-party SSO providers, because that's against their terms and unreliable. Captured sessions are deleted when the test ends, like everything else.

Question 6

Do you train AI models on my data?

Accepted Answer

No. Your URLs, screenshots, credentials, and reports are never used to train models.

Question 7

Do AI personas find real UX problems, or just make things up?

Accepted Answer

Findings are grounded in what actually happened in the browser, not invented after the fact. Each persona drives a real Chromium session, and every issue in the report is tied to the specific step where it occurred, with the persona's reasoning and a click-by-click replay (screenshots + narration) you can watch yourself. If you don't agree a flagged issue is real, the replay shows you exactly what the persona saw, so you can judge for yourself instead of taking the AI's word for it.

Question 8

Is CrowdRunner a replacement for talking to real users?

Accepted Answer

No, and it's not meant to be. Generative research, interviews, and watching real customers will always tell you things synthetic personas can't. CrowdRunner is the fast, cheap pass you run before you ship, when you don't have testers, a QA team, or weeks to recruit, so obvious broken flows get caught before they reach production instead of after. Think of it as a dress rehearsal, not a substitute for your audience.

Question 9

Is this bug-testing, or UX feedback?

Accepted Answer

Both. Every persona reports the hard failures (broken flows, dead ends, errors) and the softer friction a pass/fail test misses: where they hesitated, what confused them, and why they'd give up. You get the bugs and the 'why' behind them, with a click-by-click replay for each.

Question 10

What kinds of sites can CrowdRunner test?

Accepted Answer

Any website or web app reachable by a browser: marketing sites, SaaS products, e-commerce stores, docs. Public pages work out of the box; areas behind a login work via credentials or Browser Login. We handle cookie banners, popups, and dynamic content automatically.

Question 11

Can I test a staging or pre-production site?

Accepted Answer

Yes, as long as it's reachable over the internet: a public staging URL, a preview deployment, or a login-/password-protected staging environment (use credentials or Browser Login for the gate). Sites that only run on your own machine (localhost) aren't reachable from our servers yet; in-browser localhost testing is on our roadmap.

Question 12

How long does a test take?

Accepted Answer

Most runs with 3–10 personas finish in roughly 20–60 minutes. You can watch personas live in the spectator view while the test runs.

Question 13

What happens when I re-run a test?

Accepted Answer

A re-run launches a fresh test with the same setup and current pricing. If the original test logged into your site, you'll be asked to re-enter credentials, because we deleted them when the first run finished.

Question 14

What do I get in a report?

Accepted Answer

Each persona's full journey with screenshots and step-by-step narration, a synthesized findings report ranked by severity, Lighthouse performance and axe accessibility results, and a combined report you can hand straight to your coding assistant.

Question 15

How does pricing work?

Accepted Answer

Pay-as-you-go step-credits: 1 credit = 1 persona doing 1 step, and unused credits are refunded when a test ends early. See the pricing page for packs, or request a free test.

Common
questions.

Your next release
deserves a dress rehearsal.

Commonquestions.

Your next releasedeserves a dress rehearsal.

Common
questions.

Your next release
deserves a dress rehearsal.