Canaryflux
Help center

How can we help?

Answers about your first scan, devices, findings, billing, and privacy. Search below or browse by category.

Tip: press / from anywhere on this page to focus the search.

Getting started

From signup to your first ranked finding in a few minutes.

How do I run my first scan?

1. Sign up with your work email — verification email arrives in under a minute.

2. Open the dashboard, paste the public URL of a site you own or have permission to test in the New Scan field, and pick at least one device profile (we suggest iPhone 15 Pro + Desktop Chrome for your first run).

3. Click Run. Your scan returns ranked findings in a few minutes — typically 1-5 minutes on Free's 3 devices, which run one after another, and longer on Studio's 17. You'll see live progress per device while it runs.

4. Open any finding to see the screenshot, console output, and reproduction steps. On Solo and up, hit Share to send it to anyone — they don't need an account.

Which device profiles should I pick?

If you don't know, start with iPhone 15 Pro, Pixel 8, and Desktop Chrome — the three on every plan.

Add iPad Pro if you sell to creatives or have a heavy tablet audience. Add Galaxy S25 Ultra if you target Android markets outside the US. Add MacBook Pro 16-inch (Studio, drawn by Safari's engine) if your customers skew Apple.

iPhone, iPad and Mac pages are drawn by WebKit, the engine inside Safari, so Safari-only layout bugs show up; Android and Windows ones by Chromium, the engine inside Chrome and Edge. It's the real engine, not a real phone: fonts and form controls can differ slightly from the device in your hand.

Every additional device profile opens the page again from scratch on that device. Each device makes the scan longer; it's still one scan. Pick what matters; you can always re-run later.

How long does a scan take?

Scan time scales with device count and pages: typically 1-5 minutes for a Free-tier 3-device single-page scan, and about a minute per device and page beyond that — a Studio scan of 17 devices × 4 pages can take an hour. Longer if the target site is heavy or slow to respond, or if other scans are ahead of yours in line. A scan that gets near its time limit (90 minutes) finishes with the pages it covered and says which ones it left out.

You don't have to wait — close the tab and we'll email you a summary if the scan turns up at least one blocker finding. Lower-severity findings stay quiet in the dashboard.

Can I scan a localhost or staging URL?

Localhost (127.0.0.1, localhost) and any RFC1918 private IP are rejected by our SSRF guard — the scanner runs in our cloud, not on your machine, so it has no path to your local network.

For staging, use a public staging URL (e.g. staging.yourapp.com or a Vercel/Netlify preview URL). If a preview or staging URL needs a login (Vercel protects previews by default), make it public or scan it on Pro or Studio with a saved session cookie or Authorization header — see Scanning auth-protected staging.

What if my scan fails or times out?

Failed scans don't count against your monthly budget. You'll see the failure reason directly in the dashboard (DNS, TLS, navigation timeout, etc).

Most common causes: aggressive bot-protection on the target site (Cloudflare challenge, Akamai bot manager), a redirect chain that loops, or a 503 from the origin under load. Try again in a few minutes — if it keeps failing, email support with the run ID.

Scans & crawl

What counts, what's captured, how multi-page crawl works.

What counts as one scan?

One scan is one run against one URL, across all the device profiles you selected for that run. Selecting 5 devices is still one scan against your monthly budget.

On Pro and above, a single scan can also crawl multiple pages — 2 on Pro, 4 on Studio — and each page is captured on every selected device. Still one scan.

How does multi-page crawl work?

Before the scan, Canaryflux opens the URL you pasted once — with your saved login, if the project has one — and reads its links. The next pages come from your main menu first (pricing, features, docs…), then from the rest of the page, the ones nearest your home page first. Your sitemap, or the one your robots.txt names, only fills in if the page runs short. Footer links, legal pages and other languages come last.

Every page is on the site of the URL you pasted: the same domain, with or without www — never a subdomain, another site, or the site your URL redirects to. A page that redirects to another site is skipped, and the next one takes its place. A link whose name or address speaks of logging out, deleting, cancelling, paying or sending something — in English, Spanish, Portuguese, French, German or Italian — is never opened. With your saved login, a page only comes from a link a visitor can see, with a name.

Your plan sets how many pages one scan covers: 1 on Free and Solo, 2 on Pro, 4 on Studio. If your site has fewer, the scan says so.

What does Canaryflux actually do on the page?

For each device + page combination, we:

  • Open a fresh sandboxed browser context (no shared cookies, no extensions).
  • Navigate to the URL and wait for the network to go idle.
  • Capture a full-page screenshot at the device's viewport, at 2× pixel density on phones and tablets and 1× on desktops and laptops (not each model's own density: an iPhone 15 Pro's screen is 3×).
  • Click up to 2 main links or buttons, never one that sends a form.
  • Capture a second screenshot post-interaction so we catch broken modals, signup flows, video players.
  • Record console errors, network failures, and a stable DOM excerpt.

We don't click destructive buttons (Delete, Cancel subscription, Sign out), and we never type into a form or send one.

How often should I scan?

If your site is changing often: before every deploy, plus a weekly scan of your key pages to catch regressions in pages you didn't touch.

If your site is fairly static: once a week is usually enough. Add a one-off scan whenever you ship a new section.

Canaryflux doesn't run scans on a schedule: re-run a scan from the dashboard whenever you ship.

Do you store the full page source?

No raw HTML. We store three things: the rendered screenshot as captured — the image is not redacted, anything the browser drew on screen is in it (this matters most for Pro/Studio authenticated scans, where the session may see customer or billing data); a small DOM excerpt with text-pattern PII (emails, phones, JWTs, Bearer / Authorization tokens, Stripe / AWS / GitHub / Slack key patterns, credit-card-like and SSN-like strings) masked before it's sent to the LLM; and the captured console + network signals, also masked.

Screenshots are not redacted. Free-text fields like names, postal addresses, and account balances aren't pattern-matched either, so any of those visible on the page reach our vision sub-processors (both Google Gemini and Anthropic Claude) as image bytes under each provider's commercial API terms. Stored screenshots are purged on our daily sweep once they age past your plan's history window.

See the Security page and the Privacy page for the full data inventory and sub-processor list.

Findings & severity

How we rank, what to trust, what to ignore.

What do the severity levels mean?

Critical — the page is broken for real visitors right now. Blank hero, modal blocking the whole page, signup form throwing errors, payment widget failing to load.

High — a primary user task is broken on at least one device. Mobile nav unclickable, CTA button cut off, key product image missing.

Medium — degraded UX but the page still works. Layout overflow on small viewports, console errors that don't block rendering.

Low — polish issues. Misaligned spacing, minor typography drift, low-priority console warnings.

The AI sets the severity of its findings by what the bug actually breaks; code checks set it from what they measure.

How does the AI grading work?

Each capture goes to a vision-capable LLM with a tightly-tuned QA prompt. The model returns candidate findings from what's visible in the screenshot plus the console / network signals we recorded.

A second verification pass re-grades each candidate for confidence — runs the screenshot back through with a different prompt and checks whether the evidence really supports the finding. Findings the reviewer judges false are dropped; ones it can't confirm stay, marked Uncertain.

I think a finding is wrong. What do I do?

Open the finding and answer "Is this a real bug?" with 👎 No. It stays in your list, marked, and your answer is remembered for 180 days: when a later scan of the same project finds the same thing again — the same page, the same element, the same kind of problem — it arrives already marked "not a bug", still listed and still counted, with who said so and when. When we can't be sure it's the same finding, it arrives unmarked, as new. Click 👎 No again to take the answer back.

Report false positive, in the same window, also sends it to us, with a note if you like: we treat false findings as bugs in our own product. A mark never changes what the scanner looks for by itself — we read the reports and tighten the detector ourselves.

How do I reproduce a finding locally?

Every finding includes the URL, device profile, viewport size, and user-agent string we used. To reproduce on your machine:

  • Open Chrome DevTools → device toolbar.
  • Pick the matching device (or set the exact viewport + DPR from the finding's metadata block).
  • Navigate to the URL. The bug should appear within the first paint.

If you can't reproduce, open the scan's run from the Runs page and use the row's kebab menu → Re-run scan — sometimes flaky third-party scripts only break on specific runs.

What's the regression diff?

Available on every plan. From a scan's menu on the Runs page, choose Compare with previous run: it compares that scan with the previous scan of the same URL in the same project and highlights what's new, what's resolved, and what's persisting.

Use it after you ship: scan the same page again, and the diff shows you what broke and what got fixed since the last scan.

Plans & billing

Upgrades, downgrades, refunds, invoices. Handled through Stripe.

How do I upgrade or downgrade my plan?

Settings → Billing, then pick the new plan. Stripe shows you what changes and asks you to confirm. Upgrades take effect instantly and are prorated — you get the new quota right away and we only charge the difference for the rest of the current cycle.

Downgrades take effect right away too, and the unused part of your current plan becomes credit on your next invoices, so you don't lose paid time. Changing plans never resets the scans you've used this month.

If a renewal payment fails, your plan is paused and your account is on the Free plan until the invoice is paid. Pay it from Settings → Billing — with the same card or a new one — and your plan comes back right away.

How do I cancel?

Settings → Billing → Manage subscription opens the Stripe customer portal. Cancel takes effect at the end of your current billing period — no auto-renew, no surprise charge.

What's the refund policy?

You can get a full refund of your first paid subscription when all three are true:

  • It's the first paid plan you've ever had on Canaryflux (free tier doesn't count).
  • It's been 14 days or fewer since your first paid charge.
  • You've run fewer than 20 scans on the paid plan.

Scans you ran while on the free tier don't count toward the 20-scan limit — only paid scans do.

Why first plan only: the free tier (3 scans/month across 3 device profiles) is the real "try it" path. The paid-plan refund is for buyers who committed to evaluating, gave it an honest shot, and decided it's not for them. Once you've been on any paid plan — refunded or not — that signal is locked in and future plans aren't eligible.

How to request it: email support@canaryflux.com from your account address and we'll process the refund within 5-10 business days. No forms, no "tell us why."

The fine print: Annual plans qualify for the same 14-day / 20-scan window from initial purchase (renewals aren't refundable — cancel before the renewal date instead). Tier upgrades mid-cycle (e.g., Solo → Pro on day 5) stay under the original first-plan window on the price difference — not a new refund window. Service outages, scanner errors, and billing mistakes are refunded separately and aren't subject to the 20-scan cap or the first-plan rule. Accounts suspended for Terms of Service violations aren't eligible. EU, UK, and Turkey customers retain their statutory cooling-off rights regardless of usage.

Do you offer annual billing?

Yes — annual billing is self-serve. On the pricing page, toggle Annual · Save 20% above the plan cards and pick your tier. You'll be charged once for the full year. Annual billing costs about 20% less; the exact yearly total is shown at checkout before you pay. If you'd prefer to be invoiced rather than charged on a card, email sales@canaryflux.com and we'll set up a manual annual invoice.

Annual plans qualify for the same 14-day / 20-scan refund window from initial purchase — but only if it's your first paid plan on Canaryflux. If you've already had a monthly subscription, switching to annual is treated as a new plan and isn't refundable. After day 14 (or 20 scans, whichever comes first), annual plans run until the end of the paid term; mid-cycle downgrades to monthly take effect at the next renewal, in line with our Terms.

Where do I find invoices?

Settings → Billing → Manage subscription opens Stripe's portal, which has every invoice with a download link. Invoices are also emailed to your account address on the day of charge.

Need a custom billing address, VAT number, or PO on the invoice? Update it in the Stripe portal under Billing info; the next invoice will use the new details.

What happens if I hit my scan cap mid-month?

The Run button is disabled and the dashboard shows a banner with your usage. Quotas reset on the 1st of each calendar month at midnight UTC.

If you need more scans right now, upgrade — the upgrade is prorated and your new quota is available immediately.

Account & access

Login, password resets, email changes, team seats.

I forgot my password.

Click Log in → Forgot password. Enter your account email and we send a single-use reset link with a 1-hour TTL.

If the reset email doesn't arrive, check spam — and confirm you're using the same email you signed up with. Requesting a second reset immediately invalidates the first.

How do I change my email address?

You can't change your email from the dashboard. Email support from your current account and tell us the new address — we'll move your account and confirm when it's done. Your runs, findings, and billing carry over.

How do I delete my account?

Settings → Account → Delete account. You'll see exactly what gets removed (your account, projects, scans, findings, screenshots, share links and saved logins) and what's cancelled (your Stripe subscription — Stripe keeps past invoices and payments for tax records), and you'll be asked for your password to confirm. If you sign in with Google or GitHub, you type DELETE instead.

Account deletion is permanent and cannot be undone. A paid plan ends at once — no further charges — and the days left on it aren't refunded: to use them, cancel your plan first and delete your account when it runs out. If you have an unused refund window, request the refund before deletion.

Can I share a project / scan auth-protected staging?

Sharing a project — on Pro and Studio, open People in the dashboard, write the person's email, choose their role and pick the projects. They get an email, accept it with an account of their own (free), and see those projects in “Shared with me”. Only the invited email can accept, so a forwarded invitation doesn't work.

The roles, one per person in each project:

  • View only — sees the scans, findings and screenshots, and can compare and export them. Right for a client.
  • Member — also scans the project (as a visitor, never with its saved login), takes new screenshots, creates share links and deletes the scans they launched.
  • Admin — also renames the project, changes its saved login and its site, scans with the login, deletes any of its scans, and invites or removes Members and “View only” from the project's Who has access.

Only you delete a project or change someone's role (in People). Your plan covers everything, and every scan your team launches counts against your scans for the month; they pay nothing. People who work in your projects (Admin or Member) take a seat: 3 on Pro and 10 on Studio, you included, counting pending invitations. Up to 50 people with “View only” come on top. If your plan gets smaller, those who started working first keep their seats and the rest wait until one frees up — nothing is deleted. Remove someone, or cancel a pending invitation, at any time — they lose access right away, and the share links they created there stop opening unless you choose to keep them. Each project's Share links (in its menu) lists its links, who made each one, and lets you revoke them.

Authenticated scanning — available on Pro and Studio. From the project's kebab menu, choose "Authenticated scan…" and paste a session cookie or single Authorization header per project; we Fernet-encrypt it at rest and replay it on the next scan, capturing whatever the logged-in session can see. With a cookie or an Authorization header, iPhone, iPad and Mac are still drawn by Safari’s engine; a header with any other name sends them through Chrome for that scan, because Safari would carry it along when your site redirects to another one. A login the scanner couldn’t send as pasted — a line break or a tab, a header with an accent, an emoji or an invisible space copied along, a header without a value, a cookie without a name=value pair — isn’t saved, and the window says what to fix. Free and Solo run as a logged-out visitor only. SSO redirects, MFA challenges, and per-request CSRF tokens still defeat cookie/header replay — for those, a long-lived test account or a staging URL behind basic-auth is your best bet. Only paste a test or staging session, never a real customer's. Do not paste sessions that reveal health, financial-account, biometric, or government-ID data (GDPR Art 9 / LFPDPPP “datos sensibles”) without express consent and a processor agreement covering that category. See the Authenticated scanning block on the Security page for the full handling model.

Privacy & security

What we send to the LLM, what we never send, who can see your scans.

Is my scan data private?

Inside the dashboard, scan data is gated to your workspace — other customers can't see it, we never sell it, and we don't use it to train any model. Behind the scenes our sub-processors (see the full list below) process it on our behalf: Google Gemini looks for bugs in the screenshots via the paid Gemini API (commercial terms prohibit training on inputs), Anthropic Claude reviews each finding on the same screenshots and takes over when Gemini is unavailable (commercial terms prohibit training on inputs), Railway stores them on our disk until your tier's retention window expires, Sentry receives error reports with emails, tokens and URL query strings stripped. Besides you and the people you open a project to, only Canaryflux's founder can open stored screenshots, and only when needed for a support request you made or an abuse investigation.

Share links you generate use 24-byte cryptographically random URL-safe tokens with a 90-day expiry; the server stores only the SHA-256 hash of each token. Anyone with the URL can view that one finding (no sign-in required), so be careful if the screenshot shows authenticated data — revoke any time from the finding's Share menu.

What do you send to the LLM?

For each finding pass, we send the rendered screenshot plus a masked DOM excerpt with text-pattern PII and credentials redacted before the call: emails, phone numbers, credit-card-like numbers, SSN-like strings, JWTs, Bearer / Authorization tokens, and Stripe / AWS / GitHub / Slack key patterns. We also send masked console / network signals.

We do not send raw page HTML, your pasted scan cookies, or your pasted Authorization headers. The screenshot itself, however, is sent as-is — free-text fields like names, postal addresses, and account balances aren't pattern-matched in the DOM excerpt and are not redacted from the image either. Anything visible on screen reaches our vision sub-processors as image bytes — both Google Gemini and Anthropic Claude.

By default the scanner runs as a logged-out visitor. On Pro and Studio you can opt in to authenticated scanning (project kebab menu → "Authenticated scan…") — in that mode, the screenshot and DOM excerpt reflect whatever your test session can see, including billing pages, customer data, and PII inside the authenticated area. Use a test / staging session, not a real customer's.

We use Google's commercial Gemini API (paid tier) to look for bugs and Anthropic's commercial Claude API to review them (and as the fallback). The standard commercial terms with both providers already prohibit training on customer API inputs or outputs. We do not currently hold a separate enterprise zero-data-retention agreement with either provider (which would also suppress provider-side abuse-monitoring buffers); customers with an explicit ZDR requirement should email dpa@canaryflux.com.

How long do you keep my scans?

Screenshots are kept for the window defined by your plan — 7 days on Free, 30 days on Solo, 90 days on Pro, and 365 days on Studio — and then deleted. Your scans' findings stay in your account until you delete the scan, its project or your account; the dashboard shows the ones inside your plan's window.

On account deletion, we immediately delete your account, projects, scans, findings, screenshots and share links from our database and servers. Copies inside our backups expire on their own within 27 days (6 for screenshots) and are never used to bring an account back. Stripe keeps past invoices and payments under its own policy to satisfy tax and anti-fraud requirements.

Who do you share data with?

Only our sub-processors, each scoped to a specific job: Google Gemini API (looks for bugs in screenshots + masked DOM), Anthropic Claude (reviews each finding on the same screenshots + masked DOM, and takes over when Gemini is unavailable), Railway (compute + Postgres hosting), Vercel (marketing + dashboard static hosting), Vercel Analytics (anonymous page-view telemetry across both marketing and dashboard pages, without query strings), Cloudflare (DNS + TLS termination), Stripe (billing), Resend (transactional email), Sentry (server- and client-side error monitoring — emails, tokens, cookies, Authorization headers and URL query strings stripped before send), Google Fonts (web fonts for our pages).

Full sub-processor table with what each one sees on the Security page. EU/UK customers can request a standard DPA with SCCs at dpa@canaryflux.com.

No articles match "". Try a different keyword, or email support.

Still stuck?

The founder reads every support email and replies personally.