Privacy policy

How CVEMonitor uses your data when you browse, save bookmarks or subscribe to security alerts, and how to exercise your rights.

Who is responsible for your data?

MTRZK Solutions Prosta Spółka Akcyjna (MTRZK SOLUTIONS P.S.A.) operates CVEMonitor.io and is the data controller. For a privacy question, a correction to a public record or a request about your data, email us or write to ul. Pokoju 5/12, 44-300 Wodzisław Śląski, Poland.

Browsing and using the public API

You can read the site, check a software version and use the public API without giving us an email address. We receive your network address and the details needed to answer your request, such as a product name, version or search term. To keep the API available, we count requests using a keyed identifier derived from your IPv4 address or IPv6 network prefix. The counter expires at the end of its rate-limit window, normally one minute.

The web server's access log records the time, method, page path, response status and size. It omits query strings and masks private notification paths. We process requests and diagnose failures under Article 6(1)(f) GDPR. Our legitimate interests are providing reliable access to public security information and protecting the service against abuse.

Public CVE records and publisher advisories can include a researcher's name or handle. We obtain this material from public sources and keep it in the security catalog so readers can trace a report and its corrections. Our legitimate interest under Article 6(1)(f) is documenting security findings and attributing them to their sources. Send us the record URL if you want us to review a reference to you.

Signing in by email

When you request access to My notifications, we use your email address to send a single-use sign-in link. If you start from a filtered feed, we can keep your selected filters with the sign-in request and restore them in the form after you sign in. New sign-ins use the address with any +tag removed. If you choose recovery for an existing tagged address, the recovery link goes to that exact address.

The link expires after 15 minutes. Redeeming it sets the cvemonitor_notifications cookie so only the signed-in mailbox can manage its subscriptions. The cookie is limited to the subscription API and expires after 24 hours. Signing out ends the current session. Our legitimate interest under Article 6(1)(f) is verifying control of the mailbox and protecting private settings. Requesting a link does not subscribe you to alerts.

Choosing and stopping alerts

When you opt in to recurring security alerts, we use your address, selected filters, delivery frequency and any digest time and time zone to send matching updates. Our legal basis is your consent under Article 6(1)(a) GDPR. You choose this separately when creating a notification. If you subscribe through the public sign-up endpoint, you must also confirm the subscription by email within 48 hours.

For new or reactivated subscriptions, we record when you gave consent, the wording version, delivery channel and the settings you selected. This lets us demonstrate consent as required by Article 7(1) GDPR, under Article 6(1)(c). We also record which updates matched and whether delivery succeeded so we can investigate failures and avoid duplicate messages.

You can withdraw your consent at any time. Follow the unsubscribe link in an alert and confirm, or open My notifications, select the subscription, choose Stop notifications and confirm. You can also contact us. Stopping a subscription cancels queued alerts and disconnects its Slack channel. A message already being sent may still arrive. Withdrawal does not affect the lawfulness of earlier processing.

Who receives data?

Our hosting infrastructure processes requests and stores the service's records. When we send email, the mail delivery service and your mailbox provider receive the destination address and message, including any sign-in or subscription link in it.

If you connect Slack, we store the incoming webhook URL encrypted and send matching public updates or a test message you request to the selected channel. People with access to that channel can read those messages. To stop sending to Slack while keeping email alerts, remove the webhook in My notifications.

Your mailbox provider and Slack workspace may process data outside the European Economic Area, including in the United States. Slack describes its international transfers and available safeguards in its privacy policy. You can ask us for information about the providers and transfer safeguards that apply to our processing and how to obtain a copy.

How long we keep notification data

The service removes expired sign-in links and sessions during regular cleanup. It removes notification abuse-prevention counters whose time windows started more than 48 hours earlier. These counters use keyed identifiers derived from a network or email address.

While an alert is active we keep the address and settings needed to deliver it. Stopping an alert records the withdrawal date. We keep the stopped subscription to honour the withdrawal, any recorded consent to document what you agreed to, and the email delivery history to resolve delivery issues. The history includes encrypted message content. These records have no automatic deletion deadline. You can request erasure, including for a sign-up that you never confirmed.

Bookmarks and other browser storage

When you save a bookmark, your browser keeps its name, the record address or filter settings and any default view in local storage. They stay on that browser until you remove them or clear the site's data. Opening a bookmark sends the usual page or filter request to the site.

The current tab also remembers your last feed or version-check address in session storage so you can return to it. The public site does not set advertising or analytics cookies.

Your rights and how to use them

You can ask for access to your personal data, correction, erasure or restriction of processing. You can request a portable copy of data you supplied where the GDPR's conditions apply. You can object on grounds relating to your situation when we rely on a legitimate interest. We match alerts to filters you select. We do not make automated decisions about you that have legal or similarly significant effects.

Use the controller contact above and tell us which subscription or public record your request concerns. We use the details you send to handle your request and comply with our GDPR obligations under Article 6(1)(c). We may ask for information needed to confirm your identity. You can also lodge a complaint with the President of Poland's Personal Data Protection Office (UODO), or with the supervisory authority where you live or work or where the alleged infringement occurred.