IESET policy
Privacy Policy
IESET is built as a public evidence map. The privacy posture follows that design: collect as little visitor data as practical, keep provenance public and auditable, and avoid tracking people when the framework only needs to track claims, data, and methods.
Last updated: May 5, 2026
Information we collect
You can browse IESET without creating an account. The site is primarily a public research library, so ordinary reading should not require you to submit personal information.
For security, reliability, and analytics, our hosting and delivery providers may process standard web request data such as IP address, user agent, referrer, approximate location, requested URL, and request time. IESET also uses Cloudflare Web Analytics through a first-party, cookie-less beacon to understand aggregate site usage.
If you contact IESET, open an issue, send a pull request, submit review material, or otherwise contribute, we may receive the information you choose to provide, such as your name, email address, GitHub handle, affiliation, comments, and attached files.
The IESET corpus also contains public research provenance, including citations, publisher/API metadata, fetch timestamps, hashes, git commits, and source links. That provenance is about the evidence record and is not intended to profile site visitors.
How we use information
We use operational data to keep the site available, secure it against abuse, diagnose errors, understand which public pages are useful, and improve the research interface.
We use contribution and contact data to review submissions, discuss corrections, attribute public contributions when appropriate, maintain reproducible records, and respond to requests.
We use provenance data to make hypotheses, datasets, and published results auditable: every table should be traceable back to its source, fetch time, and content hash where available.
Sharing and publication
IESET does not sell personal information and does not run targeted advertising.
We share data with service providers that operate the site, including hosting, security, analytics, repository, and deployment providers. Those providers process data so the site and research workflow can function.
Contributions made through public channels, such as public repositories or issue trackers, may be published with their associated attribution and discussion history. Do not submit confidential material through public contribution channels.
We may disclose information if required by law, to protect the site and its users, or to investigate misuse of IESET services.
Cookies and tracking
IESET does not intentionally place advertising cookies or build cross-site advertising profiles.
The public site currently includes Cloudflare Web Analytics, which is configured as a privacy-preserving, cookie-less analytics beacon. Cloudflare and other infrastructure providers may still process technical data needed for security, caching, abuse prevention, and delivery.
Retention and correction
Operational logs are retained only as long as reasonably needed for security, debugging, analytics, and compliance.
Public research records, git history, citations, hashes, and contribution discussions may be retained indefinitely because reproducibility depends on stable provenance. If a public contribution includes personal information that should not have been included, contact us through the contribution channels and we will review reasonable redaction requests while preserving the integrity of the evidence record.
Your choices
You can browse the public site without logging in. You can also avoid submitting personal information by not using public contribution or contact channels.
If IESET later enables accounts, OAuth sign-in, private workspaces, or email subscriptions, this policy should be updated before those features are used for expanded personal-data processing.
Children
IESET is not directed to children under 13, and we do not knowingly collect personal information from children.
Contact
Questions, correction requests, and privacy concerns can be raised through the public contribution channels linked from the contribute page. Please do not include sensitive personal information in public issues or pull requests.