Privacy, explained for this website.

This draft covers kortyx.io and its documentation. Cloud data processing and self-hosted deployments have their own service-specific scope.

Kortyx is the product brand. The current controller’s identity, contact address, and private contact email must be confirmed before this becomes a published privacy notice.

Delivering a page involves your IP address and request metadata, such as browser information, requested URLs, and request times. Our hosting and delivery arrangements, any associated logging, and their retention periods must be confirmed in the final notice.

Browser storage is limited to your selected theme and c15t privacy-preference state. The cookies page lists each storage mechanism, its purpose, and its duration.

Where you choose to contact the project through GitHub, GitHub processes the information under its own privacy notice. Use redacted examples and sample data in public issues and discussions, and keep personal or confidential information private.

The website uses browser preferences to remember choices you make. Technical request data is necessary to deliver and protect the website. The final notice must specify the applicable legal bases, named service providers, retention periods, and any international-transfer safeguards for the actual deployment.

Website preferences are stored locally in your browser. Future Cloud terms acceptance will use a separate authenticated flow with version-specific records and retention disclosures.

Depending on applicable law and the processing involved, you may have rights to access, correct or delete personal data, restrict or object to processing, and receive portable data. Where processing relies on consent, you can withdraw it at any time; processing carried out lawfully before withdrawal retains its lawful status.

You may also complain to the competent data-protection authority. Privacy requests belong in a verified private contact channel. Confirm that route as part of this notice’s publication review.

The page carries a revision date. Changes to data practices require an updated notice and storage inventory. Introducing optional services also requires the applicable user choices and tested consent controls before those services load.