CoreArmorX
Privacy & cookies
This notice explains the technical data, browser storage and external services involved when you use the CoreArmorX website. There are no site accounts, advertising pixels or audience-analytics scripts in the current website code.
- Data controller
- Mirica Andrei Valentin
- Privacy contact
- miricaandrei2004@gmail.com
Scope and contact
The controller identified above operates the CoreArmorX documentation and download website at https://wiki-corearmorx.icewolf23x.dev/. Use the email address above for privacy questions or requests.
This notice covers the website. Data handled by installed Minecraft plugins, individual server operators and external websites are outside its scope and may be subject to separate notices. Downloading a plugin does not send that server's player or configuration data to this website.
Hosting and technical connection data
GitHub Pages hosts the site and Cloudflare provides content delivery and security. These services process technical connection information, which can include IP addresses, requested resources, request times and browser or protocol information, to deliver and protect the service. GitHub states that visitor IP addresses are logged for security.
The site has no registration or contact form and does not maintain its own visitor-account database. This does not mean that browsing involves no personal data: infrastructure services still handle the technical information needed for a connection.
Release catalog, downloads and external links
Opening the Releases view requests public release metadata from the GitHub API. The catalog request does not include GitHub sign-in credentials. Downloading a file connects your browser to GitHub and its download infrastructure; ordinary connection data is involved in those requests.
Links to GitHub, Modrinth or other external sites open services governed by their own privacy notices. The website does not load those sites' account or marketing pages merely because their links are displayed.
Cookies and browser storage
The current site code does not set advertising or profiling cookies. It uses the functional browser storage listed below to remember your chosen appearance and reuse public release information. These records are not site-generated visitor identifiers or cross-site advertising profiles.
Cloudflare can use technical security cookies when a security check or challenge requires them. Whether a particular cookie is set depends on the security feature invoked. Its purpose and lifetime follow the provider's configuration and cookie documentation; this notice does not claim that every Cloudflare cookie is present on every visit.
| Storage | Purpose | Persistence |
|---|---|---|
corex.themeLocal storage | Your selected light or dark appearance. | Until changed or cleared in this browser. |
corex.github-releases.v2:icewolf23x/corearmorx-websiteLocal storage | Public GitHub release metadata and request retry status. | Reused for up to 15 minutes before refresh. The saved record remains until replaced or cleared; it is not automatically deleted at that interval. |
Purposes and legal bases
Where the GDPR applies, the purposes of technical delivery, service security and responding to ordinary correspondence are the controller's legitimate interests in operating useful, secure public documentation, under Article 6(1)(f). Handling privacy requests and other applicable legal requirements may rely on Article 6(1)(c).
Ordinary network information is needed to retrieve a page. Sending an email is voluntary, but sufficient contact information is needed to answer it. The website code does not profile visitors or make automated decisions with legal or similarly significant effects.
Email correspondence and retention
If you email the privacy contact, the controller receives your address and the content you send, including a name or attachments if you provide them. This information is used to handle the request and any related legal obligations, not to add you to a newsletter or marketing list. The contact mailbox uses Gmail; Google's privacy notice applies to that service.
Correspondence is kept for the time needed to resolve the request, necessary follow-up and applicable legal retention requirements. Include only information relevant to your request. Infrastructure-log retention follows the providers' policies. Browser-storage persistence is described in the table above; a cache refresh interval is not an automatic deletion deadline.
Service providers and international processing
The services involved are GitHub for hosting, the release API and downloads; Cloudflare for delivery and security; and Gmail if you contact the controller. Modrinth and other linked services are involved when you choose to visit them.
These providers operate internationally, so relevant technical data or correspondence may be processed outside your country or the European Economic Area. Their linked privacy notices describe the applicable transfer arrangements and safeguards. Contact the controller for questions about processing related to this website.
Your choices and rights
Browser controls let you inspect, block or remove cookies and local site data. Removing this site's local storage resets its saved theme and cached release information. Blocking storage does not create an account or subscribe you to anything; the site can use its default appearance and included release snapshot. Blocking infrastructure security cookies may prevent a provider's security check from completing.
Where applicable, you may request access, correction, erasure, restriction, portability or object to processing. Where processing is based on consent, you may withdraw it without affecting earlier lawful processing. Use the contact above rather than posting private information in a public issue tracker.
You may complain to a competent supervisory authority, particularly in the place of your usual residence, workplace or the alleged infringement. The European Data Protection Board directory lists national authorities.
Changes to this notice
The update date is shown above. This notice should be revised when website functions, providers or data practices change. Optional tracking would require a separate assessment and any legally required consent before activation.