What this site does not collect
The site does not use Google Analytics, Plausible, Fathom, Matomo, or any other analytics service. It does not set first-party or third-party cookies. It does not use pixels, session replay, heatmaps, or fingerprinting scripts. It does not have a login system, a comment system, or a newsletter signup. It does not serve personalized ads or affiliate links.
The site loads two font families from Google Fonts: Inter and JetBrains Mono. When a browser requests those fonts, Google's servers receive the request, including the visitor's IP address and user agent, as part of the normal HTTP request. This site does not control that data and does not receive it. If a visitor wants to avoid that request entirely, they can block Google Fonts in their browser; the site's layout will fall back to system fonts.
What this site does collect
The site collects one kind of data: email messages sent to the contact address published in the site's metadata and on the legal pages. If a visitor sends an email, the site receives the visitor's email address, the message content, and any attachments. That data is used only to read and respond to the message.
Emails are not added to a mailing list, not sold, not shared with third parties, and not used for marketing. If a correction is sent by email and the correction is applied to a page, the source cited in the email may be referenced in the Changelog, but the sender's email address will not be published unless the sender explicitly asks for it to be.
The site does not have a contact form. It does not log IP addresses for email messages beyond what the email provider's normal operation requires. The email provider's own retention and security practices are outside this site's control.
Cookies and local storage
The site does not set cookies. It does not use localStorage, sessionStorage, or IndexedDB. The Copy Link and Share buttons use the browser's clipboard and share APIs, which do not store data on the site. The search field on the homepage filters the visible cards in the browser; it does not send the query to a server and does not persist it.
If a future version of the site adds a feature that requires cookies or local storage, this section will describe what is stored, why, and how to clear it. Until then, there is nothing to clear.
Third-party links
Profile pages cite third-party sources: ScriptBunker, ScriptBlox, Rscripts, Gridinsoft, Cloudflare Radar, Triage, Joe Sandbox, Bitdefender, BleepingComputer, Microsoft Q&A, GitHub, and others. Those links point to external sites. Once a visitor clicks one, the external site's own privacy policy applies. This site does not control those sites, does not receive data from them, and does not embed their content.
The site does not use affiliate links. It does not receive payment for a citation or a profile. If that changes, the change will be disclosed on the page where it applies and recorded in the Changelog.
Data retention
Emails sent to the contact address are retained for as long as needed to handle the message. A correction email may be retained longer if the source it cites is used in a page or a Changelog entry. There is no automated retention schedule, because there is no automated collection. The retention period is determined by whether the message still has a purpose.
If a visitor asks for their email to be deleted, and there is no ongoing correction or legal reason to keep it, it will be deleted. A request for deletion can be sent to the same contact address.
Rights and contact
If a visitor has sent an email to the site, they have the right to ask what data the site holds about them, to ask for a correction, and to ask for deletion. Those requests can be sent to the same contact address. Because the site does not have an account system or a database of visitor data, a request will be handled by searching the email inbox for the sender's address.
The site does not have a Data Protection Officer, because it does not process personal data at a scale that requires one. It does not transfer data internationally beyond the normal operation of email. It does not make automated decisions about visitors.
If a visitor believes the site has violated their data protection rights, they can complain to the data protection authority in their country of residence. The site does not have a representative in the EU or the UK, because it does not target those jurisdictions with personalized services or monitoring. This policy is written in English, which is the language of the site.
Changes to this policy
If the site's data practices change, this page will be updated and the change will be recorded in the Changelog. A change that affects what data is collected, why it is collected, or how long it is retained will be described in plain language. The "checked" date at the top of this page will move forward when the policy is reviewed, but the Changelog will only record a change if the policy's content actually changed.
This policy is not a legal contract. It is a description of what the site does. If it is inaccurate, the inaccuracy should be corrected, not defended.
Privacy questions
Does the site use Google Analytics?
No. The site does not use Google Analytics or any other analytics service. It does not set cookies, does not use pixels, and does not use fingerprinting. The only external request the site makes is for Google Fonts, which is described in the first section of this policy.
Does the site set cookies?
No. The site does not set first-party or third-party cookies. It does not use localStorage, sessionStorage, or IndexedDB. The search field and the Copy Link button operate in the browser and do not store data on the site.
What happens if I send an email to the contact address?
The site receives your email address, the message content, and any attachments. The data is used only to read and respond to the message. It is not added to a mailing list, not sold, and not shared. If you ask for deletion, it will be deleted unless there is an ongoing correction or legal reason to keep it.
Does the site have a cookie banner?
No. A cookie banner is required when a site sets non-essential cookies or trackers. This site does not set cookies or trackers, so there is nothing to consent to. If that changes, a banner will be added and this policy will describe what it asks for.
Is this policy GDPR-compliant?
The policy describes the site's actual practices. It does not claim a compliance status, because compliance depends on the site's operations and jurisdiction, not on a template. The policy explains what data is collected, why, how long it is kept, and how to exercise rights. If a reader believes a required element is missing, they can send a correction to the contact address.