TACZ Mod Privacy
Privacy information for this TACZ Mod resource, including static-site behavior, hosting data, external destinations, security practices, and future changes.
Privacy overview
This website is a static informational resource. Reading public pages does not require an account, login, profile, newsletter signup, or form submission. The packaged site is designed to work without collecting information that visitors intentionally submit through the website itself.
A deployed copy can differ if its operator later adds analytics, advertising, embedded media, forms, consent tools, or other services. The privacy information published on the deployed website should describe the configuration actually in use and should be updated when those services change.
Technical server information
A hosting provider may process technical request information needed to deliver and protect the site. Depending on the host, records can include an IP address, browser or user-agent details, requested pages, response status, referring page, and timestamps associated with ordinary web requests.
Retention periods, access controls, and security practices for hosting logs are determined by the hosting environment. The static website files do not create a log database, set a server-log retention period, or provide an administrative interface for reviewing those records.
Cookies and browser storage
The packaged site does not require cookies or browser local storage for its core navigation, guide pages, responsive menu, or FAQ behavior. Those interactions run in the browser without a visitor account and without needing stored profile information.
If a site operator adds analytics, advertising, embedded content, or another third-party feature, that service may use cookies or similar technologies. The operator should provide any notices, choices, or consent mechanisms required for the services and audience of that deployment.
External destinations
The website can direct visitors to resources outside this domain, including the direct software archive requested on the homepage. External services operate under their own privacy, security, availability, and account practices, which are not controlled by this website.
Following an external destination normally sends information required for a web request to that service. Visitors who need details about external logging, account data, cookies, or retention should review the policies provided by the destination they choose to use.
Information shared elsewhere
If you contact a project maintainer, participate in a discussion, or use another external platform, information you submit is handled by that platform and the people operating it. Avoid sharing passwords, authentication tokens, private keys, or unnecessary personal information in public technical reports.
For troubleshooting, software versions, reproduction steps, and logs with sensitive values removed are generally more useful than personal details. Screenshots and configuration files should also be checked for account names, tokens, server addresses, or other information you do not intend to publish.
Security and minimization
The static package is intended to function with minimal data handling. If new features are added, operators should collect only the information needed for a stated purpose, limit access to administrative systems, and remove information when it is no longer needed for that purpose.
Visitors should use the same minimization approach when sharing diagnostic material. Redacting credentials and unrelated identifiers reduces unnecessary exposure while still allowing technical information such as versions, error messages, and reproduction steps to be reviewed.
Changes to this notice
This privacy information should be reviewed whenever the deployed website changes in a way that affects data collection, storage, sharing, or third-party processing. Examples include adding a contact form, user accounts, analytics, advertising, embedded services, or a mailing list.
The site operator is responsible for making the published notice match the actual deployment and any rules that apply to it. Continued use of the public pages after an update is subject to the privacy information displayed on the website at that time.