Skip to main content
Cynavi

Privacy Policy

Last updated: July 15, 2026

Overview

Cynavi is a service operated by Cyber Laboratory. You can browse, search, and filter vulnerability information without logging in. However, logging in (free sign-up or log-in) is required to save bookmarks, registered products, read status, and response status.

Ads / tracking
Not used
Analytics tools
Anonymous stats only
Location / camera / microphone
Not used
Passwords
Not stored
Saving bookmarks, etc.
Login required
Personal data at login
Stored in Supabase

Features available without logging in

Even without logging in, you can browse, search, filter by category/data source/response status, sort, and view the About / Privacy Policy / Support pages. None of these actions send any information to the server.

Device-level display settings that don't need to be saved to an account — theme (light / dark / system), sort order, enabled/disabled data sources — are saved in your browser's localStorage regardless of whether you're logged in.

Features that require logging in

The following features are available only to users who have logged in (free sign-up or log-in). These actions cannot be performed, and no new data is created, while logged out.

  • Adding/removing bookmarks
  • Saving read status
  • Saving/changing response status (not started / in review / resolved / not applicable)
  • Adding, editing, or deleting registered products
  • Syncing across devices / deleting account data

Once logged in, this data is stored on Supabase, our authentication/database platform, and synced across devices. We do not collect or store your vulnerability-browsing history itself (which items you viewed). Only the results of your explicit actions — bookmarks, read flags, response status, registered products — are stored.

Login method and how we handle your email address

  • Login method: A one-time magic link sent to your email address (passwordless). We never ask for or store a password.
  • Purpose of your email address: Used only for login authentication and to identify the account to sync to. Never used for marketing.
  • Retention period: Kept for as long as your login account exists. Deleted when you delete your account, or via the "Delete server-saved data" action (see below).
  • If sending the email fails: If we can't send the email due to a system-side issue (network trouble, sending limits, misconfigured mail delivery, etc.), we show a generalized message. In that case, the screen never indicates whether the email address you entered is already registered.

Migrating and archiving data previously saved in your browser

If you used this app before login was required, your bookmarks, registered products, read status, and response status may already be saved in your browser. The first time you complete login or sign-up, you'll see a screen asking whether to migrate this existing data into your account.

  • If you choose "Migrate"

    It's saved to your account and can be synced across devices.

  • If you choose "Don't migrate"

    Rather than deleting the data, it's moved to an isolated storage area in your browser that isn't used by the normal screens, search, filters, or sync. This archived data can always be migrated to your account or deleted from the device at any time, from "Data from the previous version" in Settings. It's never automatically deleted without your explicit action.

None of migrating, archiving, or deleting this data causes anything to be sent to the server on its own.

External service providers we use and what information is sent to them

  • Supabase (authentication & database)

    Stores your login email address and the sync data described above (never the vulnerability information itself). Runs on Supabase's infrastructure, and Supabase's own privacy policy applies.

  • Resend (login email delivery)

    The email address you log in with, and the email body (sender address, link URL, expiration time), are delivered via Resend. Resend's own privacy policy applies.

  • Vercel (hosting / analytics)

    This site runs on Vercel. As with any typical web hosting, access logs (including IP addresses) may be temporarily processed on Vercel's infrastructure, but Cynavi does not use this for individual user behavior analysis. We also use Vercel Web Analytics (the standard tier) to improve the service and understand overall usage, collecting anonymous statistics such as page views, visitor counts, referrers, country, device, browser, and OS. We may also record a small number of anonymous events marking that a specific action occurred (for example, a product-registration action being started). None of this, including these events, is used to directly identify individuals, and Cynavi never sends your email address or Supabase user ID to Vercel Web Analytics.

* Of the above external integrations, Supabase and Resend are connected and in production use. You can check whether login is currently enabled on the login screen.

How vulnerability information is fetched server-side

Cynavi fetches vulnerability information from the following public APIs via this site's own server (a Vercel Route Handler), not directly from your browser. None of your personal information is included in these requests.

  • CISA KEV (Known Exploited Vulnerabilities catalog) — known_exploited_vulnerabilities.json
  • JVN iPedia MyJVN API — fetching the vulnerability list, individual vulnerability details, and a CVE-ID search (used when showing bookmarked items)
  • JPCERT/CC advisory and Weekly Report RSS feed
  • IPA important security information RSS feed
  • UK NCSC news RSS feed
  • CVE Program official CVE record (CVE Services API; each time a vulnerability's detail page is opened, only that one CVE ID is fetched. As the API instructs (no-store), the response is not stored)
  • MITRE CWE weakness names (CWE REST API; only the names of the CWE-IDs written in the official CVE record are fetched, and held in the server's memory for up to 24 hours)
  • ENISA European Vulnerability Database (EUVD; each time a vulnerability's detail page is opened, only that one CVE ID is sent to ENISA's official API to find the matching EUVD ID. As the API instructs (no-store), the response is not stored)

Information we don't collect or use

None of the following information or features are used on this site at all.

Location ・Contacts ・Camera ・Microphone ・Photo library ・Advertising identifiers ・Crash reporting tools ・Ad networks ・Third-party ad tracking cookies ・Push notifications ・Password authentication

Advertising features are not implemented at this time. If we implement them in the future, we'll update this policy beforehand and let you know.

Deleting data

  • Data remaining in your browser

    You can delete it anytime, whether or not you're logged in, from "Delete bookmarks, registered products, read status, and response status" in Settings.

  • Archived data from the previous version

    Legacy device data archived by choosing "Don't migrate" can always be permanently deleted via "Delete from this device" under "Data from the previous version" in Settings (no login required).

  • Deleting server-saved data

    From the account screen (/account), "Delete server-saved data" deletes only your synced data on Supabase while keeping your account.

  • Deleting your account

    From the account screen, "Delete account" permanently deletes both your server-saved data and your login account itself. This can't be undone.

Cookies & local storage

Your display language is saved in your browser's cookie/localStorage. While logged in, your chosen display language is also saved and synced to your account settings on Supabase. Only "ja" or "en" is ever stored — never an email address or other personal information.

While logged in, an authentication session cookie is stored in your browser to keep you logged in. It's used only to maintain your login state — never for advertising or tracking.

Disclosure to third parties

Cynavi does not sell, provide, or share user data with third parties, other than the external service providers listed above (Supabase, Resend, Vercel — each only to the extent needed to provide the service).

Children's privacy

Cynavi is not a site targeted at any specific age group. We do not knowingly collect personal information from children under 13.

Changes to this policy

If we change this policy, we'll update this page. We'll announce any significant changes on this site.

Contact

A dedicated contact channel for privacy-related questions isn't set up yet. We'll add it here once it's ready.

https://cynavi.cyberlaboratory.jp