Privacy policy
Last updated 2026-11-18. Plain language first; the detail follows.
The short version
- No account is needed. Without one, CyberView sets no cookies, runs no analytics or advertising, and sends nothing about you to us. Your environment list, your Vulnerabilities software list and your settings stay in your own browser.
- Inventory files you drop in are read on your device and never uploaded, with or without an account.
- If you create an account, we keep your email address, your settings, and only what you choose to sync. A synced environment is encrypted in your browser with a passphrase we never see, so we cannot read it.
- Email alerts are opt-in. To send them we must keep the product and vendor names you choose to be alerted about, in readable form. You can stop them with one click in any alert.
- You can export or delete everything from your account page at any time. Deletion is immediate and permanent.
- We do not sell, rent or share personal information, and we do not use it for advertising or to train AI models.
Who is responsible
CyberView is a non-commercial project run by the CyberView maintainer (GitHub: xanderhutch), based in Ontario, Canada. The maintainer is accountable for personal information under Canada's Personal Information Protection and Electronic Documents Act (PIPEDA) and acts as its privacy officer. Where the EU or UK GDPR applies to you, the maintainer is the controller.
Privacy contact: cyberviewthreats@gmail.com
What we collect and why
| Information | When | Why | Legal basis (GDPR) |
|---|---|---|---|
| Standard web request data (IP address, browser, page requested), kept by our host GitHub | Every visit | Delivering the site and protecting it from abuse. We do not receive or analyse these logs. | Legitimate interests |
| Email address; sign-in method (email link or GitHub); sign-in times; account settings | If you create an account | To let you sign in and keep your settings | Contract (providing the account you asked for) |
| Your environment list, encrypted in your browser with your sync passphrase | Only if you turn on sync | To restore your list on your other devices. We hold only the encrypted data and cannot read it. | Consent |
| Alert terms (the vendor and product names you choose), alert frequency, the date and wording of your consent | Only if you turn on email alerts | To match new events and send you alerts, and to prove you asked for them | Consent |
| Which events were emailed to you, and when | While alerts are on | So the same event is not sent twice. Kept 90 days. | Consent |
| Error reports you choose to file | If you use "Report an error" | To correct the record. These are public GitHub issues under your GitHub account; do not include personal information. | Legitimate interests |
Community posts. If you choose to post to the community feed, you do it on GitHub with your GitHub account. We receive what GitHub makes public: your username, your post and when you made it. A published post shows your username and text on this site and stays in the public repository's history. A refused post is not published here, but the GitHub issue you created remains under your control on GitHub. To have a published post removed, use its Report link or the contact on the About page; you can delete or edit your GitHub issue yourself at any time. Do not put personal information about yourself or anyone else in a post.
We do not knowingly collect sensitive categories of personal information, and we ask you not to put names of individuals, credentials, internal hostnames or IP addresses in your environment list.
What stays on your device
The site stores your environment list, display settings and, if you sign in, your session in your browser's local storage. These are not cookies, are not sent to us with each request, and are not used for tracking. You can clear them at any time in your browser's site settings. Files you drop into "My environment" or the Vulnerabilities page's "My software" are read by your browser and are never transmitted; the Vulnerabilities page keeps the product names, versions and device counts you add in local storage on your device only, and "Clear my list" removes them.
Who processes data for us
- GitHub, Inc. (United States): hosts the site and the public repository, and records visit logs. GitHub's privacy statement.
- Supabase, Inc.: account sign-in and database, in the region named on the account page. Supabase privacy policy.
- Brevo (Sendinblue SAS, France): delivers alert emails. It receives your email address and the alert contents. Its privacy policy.
- GitHub sign-in, if you choose it: GitHub tells us your verified email address and account ID.
These providers may process information outside your country, including in the United States, where it may be accessible to authorities under local law. They act on our instructions under their data processing terms.
How long we keep it
- Account information: until you delete your account.
- Alert history: 90 days.
- When you delete your account, your account, settings, synced data and alert history are erased immediately. Our providers' backups roll off within their normal cycle (for Supabase, typically up to 7 days on the free plan).
Security
The site uses HTTPS everywhere and a strict Content Security Policy, loads no third-party scripts, and pins the code it serves. Database rows can only be read or changed by their owner (row-level security). Synced environments are encrypted with AES-GCM using a key derived from your passphrase (PBKDF2, 600,000 iterations) in your browser. No system is perfectly secure; if we learn of a breach affecting your information that poses a real risk of significant harm, we will notify you and the relevant regulator as the law requires.
Your rights
You can, at any time and free of charge:
- Access and export your information (Account page, "Export my data").
- Correct it (change your settings or list).
- Delete it (Account page, "Delete my account").
- Withdraw consent to sync or alerts (turn them off, or unsubscribe from any email).
- Object to or restrict processing, and ask questions, using the contact above.
We answer requests within 30 days. If you are not satisfied, you can complain to the Office of the Privacy Commissioner of Canada, or your local data protection authority (for example the UK ICO or an EU supervisory authority).
Children
CyberView is a professional security tool. Accounts are not intended for anyone under 16, and we do not knowingly collect information from them.
People named in events
Events describe organisations, public bodies and published research. Where a source names an individual (for example in a court case), we report only what the official or published source states. Leak-site claims list organisation names only; we never copy stolen data or personal details from them. If you are named and believe an entry is wrong or should be removed, see corrections and removal requests.
Changes
We will post changes here with a new date. If a change materially affects account holders, we will tell them by email before it takes effect. Earlier versions are in the public history of this page.