Privacy overview
This Platinum Mod website is a static reference. The packaged site does not include user accounts, profiles, advertising scripts, analytics code, a database, or a server-side contact processor. Reading the homepage, legal notices, guide category and guide articles does not require visitors to submit personal information to the website code itself.
Hosting and server records
A hosting provider may still create normal access, security or error logs. Depending on the deployment, those records can include the requested path, timestamp, browser details, referring page, approximate network information or an IP address. Those records are controlled by the hosting environment and its administrator rather than by the HTML, CSS and JavaScript included in this package.
Cookies and local storage
The packaged files do not intentionally set advertising, analytics or account cookies. The small JavaScript file is used for interface behavior such as responsive navigation and FAQ controls. If a future operator adds analytics, embedded services, a consent platform, a form provider or other third-party code, this notice should be reviewed so the published privacy information matches the deployed website.
Downloads and external services
The homepage contains one direct software archive button. Following that link sends a request to an external hosting service, which may process technical information under its own terms and privacy practices. The Guide category may also discuss project resources, but the site does not require an external account merely to read its local content. Visitors should review the destination service before signing in or submitting information.
Information shared for support
If you ask for technical help through a public issue tracker, discussion area or other community channel, information you post may become visible to other people. Avoid sharing passwords, access tokens, private server details, personal identifiers or unrelated log content. Review logs and attachments before posting them and include only the technical details needed to explain the problem.
Data minimization
The static design keeps the website’s own data needs intentionally small. Navigation, reading, local search through the page and opening internal routes do not need a profile. A deployed copy can still sit behind a content delivery network, firewall, hosting dashboard or other infrastructure that introduces additional processing, so the operator should document those services separately when they are used.
Changes to this notice
This privacy page describes the current packaged site. If the site is modified to add forms, analytics, advertising, embedded media, account features or other services that collect or transmit data, the privacy notice should be updated at the same time. Maintaining accurate information about the deployed configuration is more useful than relying on a generic statement that no longer matches the website.
Operational responsibility
Site operators should also check the privacy settings of any hosting, security, caching or delivery service placed in front of the static files. If logs are retained, access should be limited to people who need them, retention should be appropriate to the purpose, and published statements should accurately describe any tools added after this package was created. Visitors should use the legal notice for the deployed site rather than assuming every copy uses identical infrastructure.