Senserva Website Privacy Policy
How Senserva, LLC handles personal information collected through senserva.com. For product-side privacy (what Senserva does inside your Microsoft tenant), see Section 6 of the Senserva EULA; for the patch import on app.senserva.com, see 2.c5 below.
SIEMSERVA WEBSITE PRIVACY POLICY
Effective Date: November 13, 2026
This Privacy Policy explains what information Senserva, LLC ("Senserva", "we", "us") collects when you visit senserva.com and our related public pages (the "Website"), how we use it, who we share it with, and the choices you have.
This policy covers the Website and the patch import on app.senserva.com (2.c5). For information about how the installed Senserva product handles data inside your Microsoft tenant, see Section 6 (Data Privacy and Security) of the Senserva End User License Agreement at https://senserva.com/eula.html. The installed product runs on your own devices and does not send your security assessment findings or tenant configuration to Senserva. What our products do send, and only then, is described in 2.c2 to 2.c5.
1. Who we are.
The Website is operated by Senserva, LLC, 4661 White Bear Parkway, St. Paul, MN 55110, United States. Email: info@senserva.com.
2. Information we collect on the Website.
a. Information you give us. When you fill out a form on the Website, send us email (for example, to request an evaluation key, request pricing, or contact support), or reach out via a "mailto:" link, we receive whatever you choose to share: typically your name, work email, organization, role, approximate tenant size, and the substance of your inquiry.
b. Information collected automatically. When you load a Website page or call our data API, your browser or software sends standard request information: your IP address, the user agent string of your browser or tool, the referring page, the full address requested (including any query string), and the time. Calls to our data API at data.senserva.com and senserva.com/api, and CVE and KB pages that are generated on demand, pass through Microsoft Azure Front Door, which records that information together with the country your IP address is located in, the response status, size and timing, and a technical fingerprint of the encryption handshake your software uses (a JA4 fingerprint, which identifies the type of software). Requests for other pages are logged only by our hosting provider, Netlify, transiently, for operational, security, and abuse-prevention purposes.
c. Cookies. The Website sets no cookies for analytics, advertising, or tracking. Browse the site and nothing is stored on your device, which is why there is no cookie consent banner: there is nothing to consent to.
The one exception applies only if you choose to sign in. Sign-in is provided by Netlify Identity, our hosting provider's built-in service, with an email address and password, or with Google or GitHub if you prefer; when you use Google or GitHub we receive the name and email address on that account and nothing else. Signing in stores a sign-in token on your device so the site can tell it is still you on the next page, in the same way a door key works. It is created only when you sign in, it identifies you to us and to nobody else, it is never used to build a profile or to follow you to another website, and signing out removes it. Under GDPR and the ePrivacy rules this is storage strictly necessary to deliver a service you asked for, so it does not require consent, but you are told about it here because you should know what is on your device. If you never sign in, it never exists.
You can also sign in with a Microsoft account, which is how you report a problem with an update (below). Microsoft tells us the name and email address on that account and an identifier for it, and we keep them only inside the sign-in token on your device. We do not store them on our side. The token expires after seven days.
c2. Diagnostic reports you choose to send us (Patch25 and Senserva tools). Our diagnostic tools can send us a report about a computer that is having trouble taking Windows updates. Nothing is sent unless you ask for it. The tool prints exactly what it will send, field by field, before it sends anything, and it does nothing at all unless you supply the address to send it to.
We keep these reports. During the beta, and on the free tier, a report you send is stored so we can learn from it: one machine cannot tell us how Windows behaves generally, and the whole reason the tool exists is that a question about Windows servicing needed more than one machine to answer. We would rather say this plainly here than have you find it out later. We will review this on December 31, 2026.
What a report contains: version numbers of Windows system files, the Windows build and update revision, the language settings of the machine, and whether the tool was run with administrator rights. What it does not contain: the contents of any file, a list of software installed on the machine, documents, credentials, or anything about what you use the computer for.
Personal data is removed on your machine, before anything is sent, not by us after we receive it. That distinction is the point: a filter at our end would mean we had received the information and then discarded it. The tool replaces email addresses, IP addresses, network paths, account and domain names, and the machine's own name and user name, and it replaces the computer name with a one-way hash by default so we do not learn it. You can read the code that does this; it is published at github.com/Senserva/patch25-engine in tools/Get-VersionDivergence.ps1.
If you type a comment, it is stored exactly as you write it and it is read by people at Senserva. The automatic removal above catches addresses, paths and account names. It cannot catch a person's name written in an ordinary sentence. Please do not type anything into it that you would not put in an email to a stranger.
Because the reports are anonymous by default, we usually cannot tell which one is yours, so we cannot find it to delete it on request. That is a consequence of collecting as little as possible rather than a way of avoiding the obligation: if you send a report and want it removed, write to privacy@senserva.com with the date and approximate time you sent it and we will do what we can.
c3. Update problem reports, issues and fixes (beta). On the page for a Windows update (a KB page), a reader signed in with a Microsoft account can:
. say how the update went, by picking one item from a fixed list such as "Printing problems";
. describe a problem in a short title (10 to 120 characters), with the Windows version and the role of the machine picked from fixed lists;
. share a fix or workaround for a problem other readers reported (20 to 1,500 characters);
. press "Same here" on a problem, or "This worked for me" on a fix.
What we store. What you picked or wrote, the update it is about, the time, and a one-way hash of your Microsoft sign-in identifier. The hash lets one person count once, limits how much one person can post, and stops you confirming your own fix. We do not store your name, email address, organization or IP address with any of these.
Everything you write is read by a person before anyone else sees it. Titles and fixes are held until a Senserva moderator approves them. A moderator may correct spelling or remove something identifying before approving, and the record keeps what you wrote and what was published. An automatic filter refuses text with abusive language, links to anywhere but Microsoft's own documentation, email addresses, or anything that looks like an attack on a computer; refused text is not stored.
What is public. Approved titles and fixes, the counts for each item, and the number of readers who pressed Same here or This worked for me. Never who wrote or pressed anything.
Please do not type anything identifying. The filter catches email addresses and links. It cannot catch a person's name, a company name or a computer name written in an ordinary sentence, and a moderator may miss one too.
Changing or removing what you sent. A new report from you replaces your earlier one. To have a title or fix you wrote removed, write to privacy@senserva.com naming the update and what you wrote; because we keep only a hash of who sent it, we find it by its text.
Anything you post this way is also governed by the Senserva Community Terms at https://senserva.com/community-terms.html.
c4. The installed-apps list our patch products send (Senserva 360 Patch and Patch+). After it scans a computer, Senserva 360 Patch sends us the list of applications installed on that computer, at most once a day. In the free edition this is part of using the product and cannot be turned off. In paid editions it is on unless an administrator turns it off. The app says so on its own page, under "What is sent", and the command
p25 census show prints exactly what the next report would contain.
What the list contains: for each installed application, its name, its publisher, the first two parts of its version number (for example 8.6, not 8.6.9.1234), how the operating system records it, and whether we have patch data for it; and, once per report, a random number created when the app was installed on that computer, the product edition and version, and the operating system's name and build. What it does not contain: the computer's name, your name or any user name, file or folder locations, network addresses or hardware identifiers, or anything about who uses an application or when. The app removes any application whose name looks like it contains a file location, an email address, a Windows account identifier, or the computer's or user's name, and our server refuses such names too.
How it is tied to you, plainly. The report travels with the registration the app was set up with, because our server checks that a report comes from a genuine copy. The server uses the registration only for that check and to limit how many reports one registration can send; it keeps a one-way keyed code made from it, not the registration, your email address or the IP address the report came from. Even so, a list of installed applications can be distinctive, so we treat these lists as personal data: they are stored only in our own systems, read only by Senserva staff, never sold, and used only for the purpose below.
Why we collect it: to count how many people run each application, so we test and add patches for the most-used applications first, and to find applications we do not cover yet. Our lawful basis in the EEA, UK and Switzerland is our legitimate interest in deciding which applications to support, which also serves the people who use the product.
How long we keep it: the lists themselves for 90 days, then they are deleted; counts that no longer include the random number are kept. A record of each report (when it arrived, how many applications were accepted, and why any were refused, without the list) is kept for 365 days so we can detect misuse. Every time a member of our staff reads this data, that read is recorded too.
Your choices: in a paid edition, an administrator can turn reporting off. In the free edition, you can stop it by uninstalling the app. To have the lists from your computer deleted, run p25 census id and send the number it prints to info@senserva.com.
c5. The patch import on app.senserva.com (beta). While we test it, only people who sign in from Senserva's own organization can use it. When you sign in to app.senserva.com and press Import now, your browser asks Microsoft for read-only access, with your own work account, to Microsoft Defender for Endpoint and Microsoft Intune, and to Entra devices if you choose to include them. Microsoft shows you each permission before you approve it. The access tokens Microsoft issues are sent to our server for that one import, used only to read your organization's device and update data, and never stored or logged. A large organization's import finishes on our server after the page has its answer; the tokens then stay in that server's memory until the import ends, at most 15 minutes.
What we store. The result, which the page calls your view: the names of your devices as Defender, Intune and Entra report them; their operating system and version; when each was last seen or last signed in; Defender's exposure level; the device identifiers those services use; the updates each device is missing, with the CVEs they fix and our score for each; and, if you include Entra devices, the list of Entra devices and the bookmark Microsoft provides so the next import reads only what changed. While an import runs we also keep a short record of it: when it started, whether it is still running, and how it ended. We do not store your tokens, the user names Intune returns with each device, or anything else from your organization. Device names can include a person's name (a phone named "Jane's iPhone", for example), so treat your view as personal data of the people who use those devices.
Who can see it. You. Your view is stored under one-way hashes of your organization's identifier and your account's identifier, so a colleague in the same organization cannot read it, and no raw identifier is used to store it. The storage is reached only by the import service itself and by Senserva staff who operate and secure it.
How long we keep it. 30 days after your last import, then a daily job deletes it. Press Delete my imported data and it is deleted at once: the storage keeps no backup copy or earlier version. The record of an import in progress is deleted a day after the import ends.
Where. Microsoft Azure in the United States (the East US 2 region).
Not sent to an AI provider. Nothing from your import is sent to an AI provider. Scores are computed from public data (CISA's Known Exploited Vulnerabilities catalog, Microsoft, NVD or CIRCL, and FIRST EPSS) and from your own view.
Logs. Import requests pass through Azure Front Door, which records the request information listed in 2.b for 365 days, as Section 6 describes. That record does not include your tokens, which travel in the request's header and body, not its address. Our server's own log of an import holds counts and timings only (how many devices and updates, how many seconds), never a device name, and is kept 30 days.
d. Analytics. We use Plausible Analytics, an open-source, privacy-focused analytics tool, to see which pages people find useful. It is cookieless. It stores nothing on your device, assigns you no identifier, and cannot follow you to any other website. It records aggregate counts only: pages viewed, the site that referred you, your country, and your browser and device type. None of that identifies you, and we could not single you out from it if we wanted to.
Because it collects no personal data, it runs the same way for everyone in every country. We removed Google Analytics from this Website on August 2, 2026 and we do not plan to return to it.
We do not use advertising, retargeting, or cross-site tracking of any kind. We do not sell personal information and we do not share it for cross-context behavioral advertising.
e. The quick survey. The short survey asks two questions, a 1 to 5 star rating and a pick-any list of things to change or add, with no text box. It sits under the Senserva Watch sign-up on CVE and KB pages and at the foot of other pages. When you answer it we receive your answers, the address of the page you were on, and the time. Our hosting provider, Netlify, delivers it to us through its form service, which also records your IP address and browser user agent with each answer. We do not save your IP address or user agent: they stay in Netlify's form records, and nothing of ours copies them. It asks for no name or email address and stores nothing on your device.
f. Our free data API. Our patch and vulnerability data files (for example https://data.senserva.com/api/microsoft-patches.json, also available at https://senserva.com/api/microsoft-patches.json) are free and need no key, so we do not know who you are when you call them. We keep a full record of every call, with the information listed in 2.b, for 365 days. We use it to count how much each file is used and by what kind of software, to keep the service available and stop abuse, and to understand which organisations rely on the data. To do that we may look up which organisation a network address is registered to, using public internet registry records and reverse DNS. We do this at the level of organisations only: we do not use these records to identify or contact individuals, and we do not use any service that links IP addresses to people or contact details. Daily totals made from these records contain no IP address and may be kept longer.
3. How we use the information.
We use the information described above to respond to your inquiries and provide evaluation keys, licenses, and support; understand which pages of the Website are useful so we can improve them; measure use of our data API and decide what to publish next; publish the update reports, problems and fixes readers send, after a moderator approves them; detect and prevent abuse, fraud, and security issues; and comply with legal obligations and enforce our agreements.
We do not sell personal information. We do not share personal information for cross-context behavioral advertising. We do not use personal information to make automated decisions that produce legal effects.
4. Who we share it with.
a. Service providers. We share limited information with vendors that process data on our behalf and only on our instructions. These are:
. Plausible Analytics. Aggregate, cookieless site usage. Plausible's privacy policy: https://plausible.io/privacy.
. Our email provider, when you send us email through a mailto: link or a contact form.
. Our hosting providers: Netlify, for delivering the Website to you and storing transient request logs, and Microsoft Azure (Azure Front Door and Azure Monitor Log Analytics), for delivering the data API and on-demand pages and storing their request logs.
. Microsoft Azure, which stores update reports, problems and fixes.
. Microsoft Entra ID, which signs you in when you choose to sign in with a Microsoft account, and which grants app.senserva.com the read access you approve for a patch import.
. Microsoft Azure (Azure Functions and Azure Table storage), which runs the patch import on app.senserva.com and stores imported views (2.c5).
b. Compliance and legal. We may disclose information if required by law, subpoena, or other legal process, or to protect the rights, property, or safety of Senserva, our users, or others.
c. Business transfers. If Senserva is involved in a merger, acquisition, financing, or sale of assets, your information may be transferred as part of that transaction. We will notify you (for example, via the Website or by email) of any change in ownership or control of your personal information.
5. International transfers.
Senserva is based in the United States. If you visit the Website from outside the United States, your information will be transferred to and processed in the United States. Where required by law (for example, transfers from the European Economic Area, the United Kingdom, or Switzerland), we rely on appropriate safeguards such as the EU-US Data Privacy Framework, the UK Extension to that framework, or the European Commission's Standard Contractual Clauses.
6. Data retention.
Email inquiries: we keep email correspondence for as long as needed to respond to your inquiry and for legitimate business records, typically up to 36 months, then delete or archive it.
Analytics: Plausible retains aggregate counts only. There is no user-level or event-level record of you to retain, and no cookie to clear.
Hosting request logs: Netlify's logs are transient, typically retained no longer than 30 days. Requests that pass through Azure Front Door (the data API and on-demand CVE and KB pages) are retained for 365 days, so we can investigate abuse and security incidents after the fact, then deleted automatically. Daily totals made from them contain no IP address and are kept for as long as they are useful.
Patch imports on app.senserva.com: 30 days after your last import, or at once when you press Delete my imported data (2.c5).
Update reports, problems and fixes: published items stay published while the update is supported. Items a moderator rejects, and the moderation record, are kept until deleted on request.
7. Your choices.
a. Our analytics has nothing to opt out of. It sets no cookie, stores nothing on your device, gives you no identifier, and records only aggregate counts. It works the same way in every country because it collects no personal data anywhere. Request logs are kept for the security and measurement purposes described in 2.b and 2.f. If you want the records for your IP address deleted before the 365 days are up, email info@senserva.com with the address and the approximate dates, and we will delete them where we can reasonably establish the address was yours and the records are not needed to investigate abuse.
b. Browser controls. There are no cookies from this Website to block or delete. Some browsers offer a "Do Not Track" or Global Privacy Control (GPC) signal; our analytics collects no personal data, so there is nothing for that signal to stop.
c. Email. If you have emailed us, you can ask us at any time to delete that correspondence. Send a request to info@senserva.com.
8. Your rights.
Depending on where you live, you may have specific rights regarding your personal information:
a. EEA, UK, Switzerland (GDPR / UK GDPR). You have the right to access, rectify, erase, restrict, or object to processing of your personal information, the right to data portability, and the right to withdraw consent for any processing based on consent. Our lawful bases are: (i) legitimate interests, for responding to inquiries you initiate, securing the Website, securing the Website's on-demand pages, operating, securing and measuring the free data API, improving our product, and publishing the reports and fixes readers choose to send and keeping the record needed to moderate them, balanced against your interests; and (ii) compliance with legal obligations. You also have the right to lodge a complaint with your local data protection authority.
b. California (CCPA / CPRA). You have the right to know what personal information we collect about you, the right to delete that information, the right to correct inaccurate information, the right to opt out of sale or sharing for cross-context behavioral advertising (we do not engage in either), and the right not to be discriminated against for exercising any of these rights.
c. Other US states. We honor analogous rights provided to residents of states with comprehensive privacy laws (such as Colorado, Connecticut, Virginia, Utah, and Texas).
To exercise any of these rights, email info@senserva.com with the subject line "Privacy Request" and tell us which right you would like to exercise. We will respond within the time required by applicable law (typically 30 to 45 days). We may need to verify your identity before responding to certain requests.
9. Children's privacy.
The Website is intended for IT and security professionals and is not directed to children under 16. We do not knowingly collect personal information from children. If you believe a child has provided us personal information, contact info@senserva.com and we will delete it.
10. Security.
We protect Website inquiries and operational logs with reasonable administrative, technical, and physical safeguards appropriate for the type of information involved. No system is perfectly secure. We will notify you of a personal data breach affecting your information when required by applicable law.
11. Third-party links.
The Website contains links to third-party sites (for example, the Microsoft Security Store, GitHub, and Anthropic / Claude). We are not responsible for the privacy practices of those sites. Review their policies before using them.
12. Changes to this policy.
We may update this Privacy Policy from time to time. The "Effective Date" at the top reflects the latest version. Material changes will be highlighted on the Website. Continued use of the Website after a change indicates acceptance of the updated policy.
13. Contact us.
Privacy questions or requests:
Senserva, LLC
4661 White Bear Parkway
St. Paul, MN 55110
United States
Email: info@senserva.com
(c) 2026 Senserva, LLC. All rights reserved. Senserva is a trademark of Senserva, LLC.