Legal
Privacy Policy
Effective November 2, 2026 — v1.4: you can now mark each finding as resolved, dismissed, a real bug or not, and report a false positive to us. This page says what we keep of who marked each finding, who in a shared project sees it, and what we keep and email when you report a false positive. It also names the AI models that now analyze your scans: Gemini 3.5 Flash-Lite, with Claude Sonnet 5 reviewing its findings.
This page explains what data Canaryflux collects, why we collect it, and who we share it with.
We try to keep it short and in plain language. If anything's unclear, email
support@canaryflux.com and we'll explain.
Who we are
Canaryflux is a website QA scanning service operated as a sole-proprietor business by
Farid Islas, registered with Mexico's Servicio de Administración Tributaria
(SAT) under the Persona Física con Actividad Empresarial (PFAE) regime in Mérida,
Yucatán, Mexico. When this policy says "we," "us," or "Canaryflux," it means that business.
The data controller for the purposes of Mexico's LFPDPPP
(and the GDPR, where applicable) is Farid Islas, and the contact address for any privacy
request is support@canaryflux.com.
What we collect
We collect only what we need to run the product:
- Account data — your email, your name (if provided), and a bcrypt hash of
your password. We never store your password in plaintext.
- Scan data — the URLs you ask us to scan, the screenshots our scanner takes
of those URLs, the masked DOM excerpts and console logs the scanner captures, and the
findings our AI extracts. For Pro+ projects with authenticated scanning enabled, we also
store the session cookie or Authorization header you pasted (encrypted at rest — see the
Security section below). See the Cookies & local storage and
What we collect (detailed) sections further down for the full enumeration.
- Authenticated-scan content (Pro+ only). When you enable authenticated
scanning on a project, the screenshots and DOM excerpts we capture include whatever data
is visible to the session you provided. If you point Canaryflux at
/admin/customers
with an admin session, the customer list ends up in the screenshot we send to our vision
sub-processors (Google Gemini looks for bugs in it and Anthropic Claude reviews what Gemini
found — see Sub-processors below for full details) and store on our server until your
tier’s retention window expires.
The encryption we apply protects the cookie at rest; it does not redact the content the
cookie unlocks. Screenshots themselves are not redacted — our PII masker
pattern-matches DOM text and URLs (emails, phone numbers, tokens, card numbers) before the LLM
call, but anything visible on the rendered image (names, postal addresses, account balances,
free-text fields) reaches both Google Gemini and Anthropic Claude as image bytes. Besides you
and the people you open the project to, only Canaryflux’s founder can open its stored
screenshots, and only when needed for a support request you made or an abuse-of-service
investigation. 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. We recommend using a low-privilege test-account
session whenever possible — see
Authenticated scanning — what we see in
the security page for the full picture.
- Shared projects (Pro and Studio) — when you open a project to someone, we
keep their email, their role in each of your projects (Admin, Member or "View only"), since
when they can see it and since when they work in it, and who added them. While an invitation
waits, we keep the invited email, its role, its projects, who sent it, when, and when it
expires; its link is kept only as a fingerprint, never readable. In a shared project we also
keep who launched each scan, who created each share link, and who marked each finding
(resolved, dismissed, a real bug or not) and when. See Who else sees your
data for who sees what.
- Usage data — how many scans you run per month, which device profiles you
use, and when your account was created. This drives the quota system and is used to bill you.
- Onboarding survey (optional) — your role, your workspace name, what kinds
of bugs you want Canaryflux to catch, and how you heard about us. These answers are
forwarded to the founder's inbox so we know what customers are signing up for and can
prioritize what to build next. You can skip the questions; blanks are persisted as blanks.
We do not share these answers with anyone outside Canaryflux.
- Payment data — handled entirely by Stripe. We receive only a customer
identifier and the subscription tier you're on. We never see your card number.
- Feedback — what you send from the dashboard's feedback form, with the
page you were on (never its query string) and your browser type. It's also emailed to the
founder, who can reply to you directly. When you report a finding as a false positive, we
keep your optional message with the scan's and the finding's numbers, and email the founder
your message with the finding: its kind, severity and devices, and the title of an AI
finding with emails, phone numbers and keys masked — never its screenshot, its page's
address or the text a code check quotes from the page. That email stays in the founder's
inbox, also after an account is deleted. The people in your project see your 👎, never your
message.
- Server logs — each request's IP address and the page it asked for. Our
logs never keep a URL's query string (where tokens and codes ride) or a share link's token,
and they show emails shortened (
an***@example.com). IP addresses also sit
briefly in memory for rate-limiting and abuse prevention.
What we do with it
- Run scans you've asked us to run, and show you the results.
- Email you: to verify your address, to reset your password when you ask, a welcome once
you're verified, a summary of your first scan, an alert when a scan finds blockers (you can
turn these off in Settings), notices about your plan and payments, a confirmation when you
delete your account, and a few tips during your first week — sometimes a short personal
note from the founder. Every tip email has a one-click unsubscribe link, which carries your
address encrypted, never in plain sight.
- Bill you for paid plans (via Stripe) and enforce your monthly quota.
- Prevent abuse — rate-limiting, brute-force lockouts, anti-spam on the contact endpoints.
- Improve the scanner — we may look at anonymized failure patterns to make the detector better,
such as how many findings people marked as a real bug or not, counted by kind of finding.
We do not train models on your scan data.
Who else sees your data
The people you share a project with. If you open a project to someone (Pro and
Studio), they see its scans, findings and screenshots — also those of pages behind a
login — and can compare and export them. With "View only" that's all; a Member can also
scan it, mark its findings and create share links, and an Admin can also change its saved
login (never read it) and its site and invite or remove people. You and the project's Admins
see the email of each person in it; Members and "View only" see names, never an email.
Everyone in a project sees who launched each of its scans, and who marked each finding, by
name. If someone opens a project to you, they see your
email and your name. When you remove someone, or they leave, they lose access to the project
at once; screenshots they had already opened can stay viewable on their side for up to 7 days,
until those links expire, and what they exported stays with them.
We use a small set of third-party processors to run Canaryflux. Each of them only sees the
slice of data they need:
- Google (Gemini API) — finds candidate bugs. Receives the screenshots and
masked DOM excerpts your scans produce (Free and paid tiers alike) so Gemini 3.5 Flash-Lite
can extract findings. Canaryflux operates exclusively on the paid Gemini API tier, whose
commercial terms prohibit Google from using customer prompts or outputs to train Google's
models (the free Gemini API tier does not carry that commitment, and we do not use it).
Processing in the United States, under Standard Contractual Clauses where EU/UK personal data
is involved. Subject to
Google's privacy policy
and the Gemini API Additional Terms.
- Anthropic — reviews findings. Claude receives the same
screenshots and masked DOM excerpts on every scan: Claude Sonnet 5 confirms or rejects each
candidate Gemini found, and Claude Sonnet 4.6 looks for bugs itself when Gemini finds none
or is unavailable.
Anthropic's commercial API terms prohibit training on customer inputs or outputs. Processing
in the United States. Subject to
Anthropic's privacy policy.
- Stripe — handles all payment data. Subject to
Stripe's privacy policy.
- Resend — sends the emails listed above.
Subject to Resend's privacy policy.
- Railway — hosts the scanner backend. Subject to
Railway's privacy policy.
- Vercel — hosts the dashboard front-end. Subject to
Vercel's privacy policy.
- Cloudflare — DNS + TLS termination for canaryflux.com. Subject to
Cloudflare's privacy policy.
- Sentry — receives error reports from our server and from the dashboard
(stack traces, the page's path, browser type) so we can fix bugs. Before sending we strip
emails, tokens, cookies, Authorization headers and every URL's query string. Subject to
Sentry's privacy policy.
- Vercel Analytics — anonymous page-view counts on our website and the
dashboard: the page's path only, never its query string, with a share link's token hidden
(no personal identifiers, no cookies, no cross-site tracking). Subject to
Vercel's privacy policy.
- Google Fonts — our pages load their fonts from Google's servers, so your
browser's IP address reaches Google when it fetches them. Subject to
Google's privacy policy.
We do not sell your data, share it with advertisers, or hand it to any other third party
beyond what's listed above.
Data Processing Agreement. If you process EU/UK personal data through Canaryflux
(including by pasting an authenticated-scan session that exposes your own end-customers' data),
you need a written DPA with us before scanning begins. Email
dpa@canaryflux.com — we ship a standard DPA with
Standard Contractual Clauses (SCCs) on request, normally within one business day.
Cookies & local storage
Canaryflux uses your browser's local storage (not third-party cookies) to keep you signed in
and to remember your active project. Specifically:
- Session JWT — stored in
localStorage on the dashboard so you
stay signed in across tabs. Cleared when you sign out, or delete your account, in that browser;
on your other devices, the next visit finds the session dead. (Necessary — without this
you'd have to log in on every page load.)
- Your account and a copy of your work — your email and name, and a copy of
your projects and scan results, so the dashboard opens fast. Cleared when you sign out, or
delete your account, in that browser. (Necessary for the product to work.)
- UI state — your active project id, sidebar collapse state, and onboarding
progress are stored locally so the dashboard reopens where you left it. (Necessary for the
product to work.)
- A pending invitation — when you open an invitation's link, its key stays in
that browser while you sign in, sign up or verify your email, and goes once you accept it,
once it can't be used, or after 7 days. (Necessary for the invitation to work.)
- Vercel Analytics — our pages send anonymous page-view pings to Vercel,
without the page's query string. No personal identifiers are stored client-side;
daily-rotated hashed visitor IDs are used and reset every 24 hours. (Analytics — used to
understand which pages people use.)
- Sentry session replay — disabled by default. If we ever enable session
replay on the dashboard, we will update this policy and gate it behind a consent prompt
for visitors in the EU/UK.
We do not use third-party advertising cookies, conversion pixels, or cross-site trackers.
You can clear local storage at any time from your browser settings; this signs you out and
resets dashboard state but does not affect data we hold on the server.
What we collect (detailed)
For completeness — and because privacy regulations require us to be specific about every
category of data we touch:
- Scan inputs — the URLs you ask us to scan, the device profiles you pick,
and (for Pro+ projects with authenticated scanning) the session cookie or Authorization
header you paste. The latter is encrypted at rest using Fernet (AES-128-CBC + HMAC-SHA256)
with a key derived from our server-side master secret.
- Scan outputs — full-page screenshots from each device, masked DOM excerpts
(we mask emails, phones, and obvious PII patterns — in text and in URLs — before any LLM
call), captured console errors and network failures, and the findings our vision
sub-processors extract (Google Gemini finds, Anthropic Claude reviews).
- Compliance audit trail — for projects with a scan-permission attestation,
we store the attested origin, the exact text you agreed to (snapshot at consent time), the
timestamp, and your IP + User-Agent at grant time. This evidentiary record exists so we can
respond to abuse reports about scans run on your project. It is deleted with the project,
or with your account.
How long we keep it
- Account data — until you delete your account.
- Scan results — until you delete the scan, its project or your account.
The dashboard shows the ones inside your plan's history (7 days on Free, 30 on Solo, 90 on
Pro, 365 on Studio).
- Screenshots — saved to disk on the scanner and deleted when your plan's
history ends (7 / 30 / 90 / 365 days), or sooner if you delete the scan, its project or
your account. Screenshots of a free scan run without an account, and those taken when you
open a finding, are deleted after 7 days. Links to screenshots are signed and expire 7 days
after they're issued; the dashboard renews them for you.
- Feedback — until you delete your account.
- Shared projects — a person's access lasts until you remove them, they
leave, or the project or either account is deleted. An invitation is deleted once it's
accepted or cancelled, or when it expires, 7 days after it was sent. When someone deletes
their account, their email leaves the projects of others at once: from the scans they
launched, the findings they marked and the share links they created (which show "A
Canaryflux user" from then on),
from the people they invited or added, and from the site permissions they gave, which keep
only their date, site and text version — never their email, IP address or browser.
- Server logs — IP addresses cycle out of rate-limit memory within minutes.
Application logs are retained for up to 30 days for troubleshooting.
- Stripe data — retained by Stripe per their own policy; we keep only a
customer reference. When you delete your account we also delete your customer record at
Stripe, which removes your card and billing address; Stripe keeps past invoices and payments
for tax records.
- Backups — our hosting provider (Railway) keeps backup copies of our
database for up to 27 days (a daily copy kept 6 days and a weekly one kept 27) and of the
screenshots for up to 6 days. They expire on their own. We use them only to recover the
service after a failure; if we ever restore one, we delete again whatever had been deleted
after it was taken. For that, we keep a note of each deletion (and of each password,
unsubscribe or permission change) for 35 days, naming your account by a keyed fingerprint,
never your email.
Your rights
Whether you're in Mexico (LFPDPPP), the EU (GDPR), the UK, California, or anywhere else,
you can:
- Access the personal data we hold about you — email support@canaryflux.com and we'll send it over.
- Correct anything inaccurate — most fields are editable in the dashboard.
- Delete your account and everything tied to it — use the "Delete account"
button in your dashboard settings (or email us). Deletion is immediate and not reversible:
your account, projects (with their saved logins and permission records), scans, findings,
screenshots, share links, feedback and usage leave our database and servers at once, and
every session you had stops working. Copies inside our backups expire on their own within
27 days (6 for screenshots) and are never used to bring an account back. You can also delete
a single scan or project.
- Export your scan history in a portable format — email us to request it.
- Object to specific processing or revoke consent at any time.
If you believe we're mishandling your data, you have the right to lodge a complaint with
Mexico's Secretaría Anticorrupción y Buen Gobierno, which took over the former INAI's
data-protection duties under the 2025 LFPDPPP, or with the data-protection authority of your
country.
If your site was scanned by a Canaryflux user
Canaryflux is a tool that our users point at URLs they tell us they own or have authorization
to test. If you believe a Canaryflux user has scanned a site you operate without your
permission, and you would like the resulting screenshots, DOM excerpts, and findings removed
from our systems, email support@canaryflux.com
with:
- The full origin URL that was scanned (e.g.
https://your-site.example.com).
- Approximate date / time of the scan, if known.
- A contact email at the affected domain (so we can confirm ownership before deleting).
- Optional: any specific screenshot URL or finding ID you'd like prioritized.
We will acknowledge receipt within 2 business days and, once domain ownership is verified
(typically via a DNS TXT record or an email to a role address at the domain), remove the
associated scan artifacts within 30 days. We may retain a minimal audit log of the takedown
request itself, but no scan content. If the scan involved authenticated content captured
on behalf of a Canaryflux Pro+ customer, we will also notify that customer of the takedown
so they can stop using the affected URL.
If you believe the scan violated applicable law (e.g. unauthorized active scanning of a
private system), you can also report the account to abuse@canaryflux.com
and we may suspend or terminate it per our Terms.
Security
Passwords are hashed with bcrypt (cost factor 12). Session tokens are signed JWTs with a
14-day expiry. All traffic is HTTPS. Screenshot URLs are HMAC-signed with a 7-day expiry to
prevent unauthorized access. Failed login attempts trigger an account lockout after 5 tries.
No system is perfectly secure. If you discover a security issue, please email
security@canaryflux.com with the details — we'll
respond and fix it promptly.
Security-incident notification. If we discover a personal-data breach
likely to affect you, we will notify affected users via email without undue delay and
at most within 72 hours of confirming the breach, including: the nature of the breach,
the categories and approximate number of users affected, the likely consequences, and
the measures we've taken or propose to take to address it. This meets the GDPR Art 33/34
timeline and applies regardless of your jurisdiction.
Children
Canaryflux is not directed at children under 13. We don't knowingly collect data from anyone
under 13. If you believe a child has signed up, email us and we'll delete the account.
Changes to this policy
If we materially change how we handle your data, we'll email all active users at least 14 days
before the change takes effect. The effective date at the top of this page always reflects the
current version.
Contact
Privacy requests, complaints, and anything else: support@canaryflux.com.