Privacy Policy

This Privacy Policy explains what information the Yrendr website processes, why it is processed and how the website uses cookies and external services. The public website is designed to work without a user account and to keep data collection limited.

Who is responsible

The operator of the official Yrendr website is responsible for the processing described in this policy. Privacy questions or requests should be sent through an official Yrendr contact method published by the website or project operator.

Information processed when you visit

When you request a page or file, the web server and hosting infrastructure may process technical information such as your IP address, browser and device information, requested URL, referring page, date and time, and technical error or security information. This information is used to deliver the website, protect it, diagnose faults and maintain reliable operation.

Yrendr releases and plugins can be downloaded without creating a public account. Optional download measurement is disabled until a visitor explicitly accepts optional cookies in the cookie banner.

The first-party cookie yrendr_cookie_consent stores whether the visitor accepted or rejected optional cookies for up to one year. This preference cookie is used only to remember the visitor's choice.

Every published release or plugin download can increase a simple aggregate total counter. This aggregate counter does not use a tracking cookie or browser identifier and does not attempt to determine whether repeated downloads came from the same visitor.

After optional cookies are accepted, downloading a published release or plugin can also set yrendr_download_id. This cookie contains a random browser identifier and can remain on the browser for up to two years. The raw identifier is not stored in the database. Instead, Yrendr stores a one-way keyed hash together with the downloadable item that was requested. This is used only for a separate unique-download estimate.

If optional cookies are rejected, yrendr_download_id is not created. Rejecting through the cookie settings also removes an existing download identifier from the browser. The anonymous aggregate download counter can still increase. Visitors can reopen Cookie settings from the website footer to change their choice.

The full list of cookies, purposes and retention periods is described in the separate Cookie Policy.

Bug reports

Visitors can submit a bug report through the public website. A report stores the information entered in the form, such as the bug title, Yrendr version, category, description, reproduction steps and an optional contact email address. The bug form does not add a tracking cookie or store a browser identifier for the report. Contact information should only be provided when the visitor wants Yrendr to be able to follow up about the submission.

Analytics and advertising

The website does not use a third-party behavioural analytics or advertising platform by default. The built-in aggregate download counter does not use a tracking cookie. The separate unique-download estimate is first-party measurement limited to downloadable Yrendr content and is enabled only after optional-cookie consent.

If a new analytics, advertising or tracking service is introduced, the website, cookie banner and legal policies should be updated before that service is enabled. Optional tracking must remain disabled until any required consent has been obtained.

Fonts and third-party requests

The website may load web fonts from Google Fonts. When the browser requests those font resources, Google can receive technical connection information such as the visitor's IP address and user agent. Google processes that request under its own terms and privacy practices.

Downloads or other links can also point to external hosting, repositories, CDNs or other websites. Once you are redirected to an external service, that service controls its own processing.

Purposes and legal bases

Technical request and security data are processed to operate, secure and troubleshoot the website. Administration session data is processed to keep protected management functions secure. The first-party download identifier and its hashed database value are processed to maintain basic download statistics and understand whether a downloadable item has been requested by the same browser before.

Depending on the applicable law and the exact deployment, these activities may rely on legitimate interests, technical necessity or another available legal basis. Where consent is legally required for a future cookie or tracking technology, that technology should not be enabled before valid consent is obtained.

Service providers and international processing

Hosting, storage or CDN providers can process technical data on behalf of Yrendr where they are used to operate the website. External services such as Google Fonts or an external download host can receive request information directly from the browser. Depending on the selected provider and hosting location, processing can take place outside the European Economic Area. The relevant provider's safeguards and privacy terms then apply.

Data retention

Server and security logs should be kept only for as long as reasonably needed for operation, security and troubleshooting. The download cookie expires after at most two years. Download-counter records are retained as described in the download section above. Administration data is retained for as long as it is needed to operate and secure the administration area.

Security

Yrendr uses reasonable technical and administrative measures intended to protect the website and its administration area. No internet service can guarantee absolute security.

Your privacy rights

Where the GDPR or similar law applies, you may have rights to request access, correction or deletion of personal data, restriction of processing, data portability where applicable, and to object to certain processing. Where processing is based on consent, you can withdraw that consent without affecting earlier lawful processing.

You may also have the right to lodge a complaint with the competent data protection authority. In the Netherlands, this is the Autoriteit Persoonsgegevens.

Changes to this policy

This policy may be revised when the website, hosting setup, download measurement or other data practices change. The version and effective date shown on this page identify the policy currently in use.