Privacy Policy

Last updated: 10 November 2026 · Version 1.0

Short version: this website collects nothing about you. The Corex application running on your computer collects nothing about you either. Everything below is just the long version of that sentence.

1. Who this policy covers

This policy applies to two things: the Corex website you are reading now, and the Corex Windows application you can download from it. Both are operated by Corex Integrated Software Technologies. (referred to as "we", "us" or "Corex"). If you use any third-party service we link to — Discord, Ko-fi, GitHub, publisher websites — that service's own privacy policy applies, not this one.

2. What we collect on this website

No analytics, no tracking pixels, no fingerprinting, no advertising cookies, no session cookies, no user accounts. We do not know you visited. We do not run Google Analytics, Meta Pixel, PostHog, Plausible, Fathom or anything similar.

Our web host sees the same technical information every web host sees when a browser requests a page — your IP address, the time of the request, the URL you asked for, your User-Agent string. That information is used only to serve the page back to you and to protect the server from abuse. It is not aggregated, not analysed, and not shared.

3. Cookies and local storage

This website does not set any cookies. It does not write to localStorage, sessionStorage or IndexedDB. There is no consent banner because there is nothing to consent to.

4. Fonts and external resources

The website loads the Inter font from Google Fonts (fonts.googleapis.com and fonts.gstatic.com). When your browser fetches that font, Google's servers see your IP address and User-Agent as part of a normal HTTP request. Google states that the Fonts API does not use cookies for end users and does not log identifiable information for serving fonts, but that is Google's commitment, not ours. If this bothers you, the browser extensions NoScript, uBlock Origin or Decentraleyes will block or locally substitute the font without breaking the site.

We do not embed any other third-party scripts, iframes, trackers or widgets.

5. Links to other sites

We link to our Discord community server, our Ko-fi tip jar, and to publisher websites and download sources for the applications in the Corex catalog. When you follow one of those links, your browser connects directly to that service. We do not track clicks and we do not sit in the middle. Each of those services has its own privacy policy.

6. Downloading Corex

When you download Corex.exe from this website, the server records the same minimal HTTP request information described in section 2. We do not watermark, serialise or personalise the download — everyone gets the same file.

7. What the Corex application collects on your computer

Nothing. Corex is a local application. It runs on your device, writes to your device, and reads from your device. It does not have an account system. It does not phone home. It does not post installation telemetry. There is no "report anonymous usage" setting because there is nothing to report.

What Corex stores locally on your machine, in %LOCALAPPDATA%\Corex\:

Settings — your preferences, the EULA version you accepted, a hardware identifier used to pin the EULA acceptance to this specific machine.
History — a record of past installation sessions, so Corex can show you what you installed and when.
Logs — one file per month for the application, one file per installation session. Logs are passed through a redactor before being written, so URL credentials, tokens, API keys, passwords and authorization headers are replaced with a mask.
Catalog cache — a copy of the application catalog, if a newer version was fetched from an HTTPS source.
Downloads — the installer files Corex has downloaded, by default deleted after a successful install.

All of this stays on your device. None of it is uploaded, copied or synced to anyone — not to us, not to a cloud provider, not to anyone else.

8. What happens during an installation

When Corex installs an application, your device connects directly to the publisher of that application (Windows Package Manager repository, Microsoft Store, GitHub, the publisher's own HTTPS endpoint). Those destinations see the same technical information any download client reveals: your IP address, the file you asked for, your User-Agent. We are not part of that connection and we do not proxy it. Each publisher has its own privacy policy for its downloads.

9. Children

Corex is not directed at children. We do not knowingly collect any information from anyone, including children.

10. Your rights

Under the GDPR and comparable laws you have the right to access, correct, delete and port personal data we hold about you, to object to its processing, and to lodge a complaint with a supervisory authority. Since we do not hold personal data about you, there is nothing to access, correct, delete or port. If you want to delete what Corex has stored locally, remove the folder %LOCALAPPDATA%\Corex\.

11. Security

The website is served over HTTPS. Corex refuses to download over plain HTTP, even after a redirect. Downloaded files must pass signature and checksum verification before the installer is allowed to run.

12. Changes to this policy

If this policy changes, the new version will appear here with a new "Last updated" date. If a change affects how your data is handled, we will highlight it at the top of this page.

13. Contact

Questions about this policy or about Corex: join our Discord community and send a message in the appropriate channel.