Privacy at OpenViST.
This notice explains what personal data OpenViST processes, why it is used and the choices available to people who use the service.
Last updated: 18 October 2026
Who is responsible
OpenViST is a personal project operated by Ionut Popovici in Luxembourg. For privacy requests, use Contact OpenViST. The contact page provides the public email address; a private residential address is not published on the website.
Data OpenViST may process
- Account and contact data, such as a name, email address and sign-in information.
- Claim, correction and report information, including the listing concerned, the requester’s relationship to it and supporting evidence.
- Messages sent to OpenViST and the information needed to answer them.
- Routine technical and security data, such as IP address, browser information, timestamps, server logs and anti-abuse signals.
- Public information about technical projects, official repositories, documentation and relevant App Store records used to build directory profiles.
Representation evidence
Representation requests can include your stated role, account details, supporting public sources and verification results. Website and GitHub checks use a unique verification token. A successful GitHub check records the exact repository, verification-file path, blob identifier and check time. The verification file is public in the repository you choose to use. A technical check does not establish legal ownership or authority, and the request remains subject to review.
Purposes and legal bases
Data is used to operate accounts and respond to requested services; maintain an accurate directory; review claims and corrections; prevent abuse; secure and improve the website; and meet legal obligations. Depending on the context, the legal basis is performance of a requested service or contract, OpenViST’s legitimate interests in operating a trustworthy directory, compliance with a legal obligation, or consent where consent is specifically requested.
Assisted research and AI
Public website URLs and public page content may be processed by automated tools to support inspection, classification and editorial drafting. Private claim evidence, identity documents and the contents of private contact messages are not intentionally submitted to generative-AI services for classification. Claims and reports do not change the public record automatically; they are reviewed before publication.
Service providers and transfers
OpenViST uses technical providers for hosting, email delivery, security, backups and service operation, including SiteGround for website and email infrastructure. Automated website screenshot capture is disabled. Images retained from earlier tests are not displayed publicly and are not fetched again. Providers process data only for the relevant service. Where processing takes place outside the European Economic Area, OpenViST relies on an applicable legal transfer mechanism where required.
Public repositories and test infrastructure
OpenViST contacts GitHub to check public repository verification files and uses isolated VPS containers for recipe execution tests and GitHub for public source distribution and selected software checks. Published library material and linked execution reports are public; private representation evidence is not part of the public data feed or recipe library.
Optional audience measurement
When enabled, Google Analytics is loaded only after explicit consent. It is used to understand page usage and improve OpenViST, not to sell personal data or personalise advertising. OpenViST disables advertising storage, ad personalisation and Google Signals in its integration. Consent can be rejected or withdrawn from the Cookies page.
Browser Tools and your input
The current browser Tools process pasted text and selected file contents locally in the browser. Tool code does not upload these contents or results to OpenViST, send them to AI services, or persist them in cookies or browser storage. Reloading the page clears the tool interface; downloaded results remain wherever you save them. Loading a tool page still involves ordinary website requests, security logs and any separately consented analytics. Do not put confidential input in page URLs or support messages.
Retention
Data is kept only as long as reasonably needed for the purpose for which it was collected, including account operation, request resolution, directory audit history, security, backups and legal obligations. Retention therefore depends on the record and applicable requirements. OpenViST does not sell personal data.
Your rights
Depending on the circumstances, you may request access, correction, deletion, restriction, portability or objection, and may withdraw consent without affecting earlier lawful processing. Use the contact page. You may also lodge a complaint with Luxembourg’s National Commission for Data Protection (CNPD).
Cookies and external sites
See the Cookies page for current browser-storage information. OpenViST links to independent third-party websites; their privacy practices are their own.
Changes
This notice may be updated as OpenViST’s features or legal obligations change. The date above identifies the current version.
Learn and code copying
Reading Learn does not require an account. The current lessons do not save learning progress. Copy-code controls write the selected example to your clipboard when you choose Copy; they do not read your existing clipboard. Downloading an example does not execute it on OpenViST. Ordinary website requests, security logs and separately consented analytics remain subject to this notice.
Hosted Link Auditor
The hosted Link Auditor is separate from local browser utilities. It processes your account-linked website origin, ownership-verification request, audit jobs and private reports through WordPress and the OpenViST VPS. Website records expire after seven days, unverified challenges after one day, and jobs and reports after 24 hours; cleanup occurs when the service is used or polled. Reports can contain URL query parameters. Downloaded copies remain on your device after server-side expiry.
Recipe library and editorial drafting
Downloading published recipes or adjusting their code previews does not send a generation request to an AI provider. The editorial assistant is restricted to OpenViST administrators. A submitted editorial task and the relevant public documentation are sent to the configured AI provider to prepare a draft; administrators must not submit personal data, secrets or private correspondence. Drafts and their request history are stored for review. Signed-in reader improvement proposals, suggested code and their associated account and recipe are stored in a private review queue. Send only material you may contribute under the stated recipe licence, without personal data or secrets. Suggestions do not automatically change published recipes.
