This Privacy Policy explains how information relates to browsing the Better Foliage Mod website, loading its page resources, following its links, and contacting its operator when a working email channel is available. Better Foliage Mod is a fan resource, not the developer of every project described on its pages. This policy concerns the website's activities and does not replace the policies of separate download platforms, email providers, or other services. The distinction between website-controlled information and information handled by separate providers is important when deciding where to direct a privacy question.
Scope of this policy
The website presents informational pages about a Minecraft visual mod, together with site information and navigation. Its current pages do not require visitors to register, create a profile, or submit a contact form. Reading a page does not create a website user account. The site is not designed to receive payments, store Minecraft login credentials, or manage game accounts. Visitors should not send passwords, authentication codes, or payment details through a contact channel. Information can still be involved in ordinary web requests, hosting operations, and voluntary email correspondence, even when a website has no registration system.
This policy describes the visible website implementation and the purposes for which information may be relevant to operating it. Hosting and email infrastructure can have their own operational practices, which cannot be fully inferred from a static page. A service reached through a download link also operates separately from this website. If you need to understand a particular provider's handling of information, consider the interaction with that provider directly. The website cannot guarantee that every separate service uses the same privacy choices or retention practices simply because a link to that service appears in the resource.
Information involved in browsing
Ordinary page requests
When a browser requests a web page, the systems delivering that page may receive technical information needed to handle the request. This can include an IP address, request path, browser information, and related connection details. The exact information recorded depends on the hosting environment and its configuration. The website's static files do not themselves establish how long a hosting provider keeps operational logs. Such logs may help a provider diagnose delivery problems, identify abusive traffic, or investigate errors. They are distinct from a visitor deliberately submitting a personal profile through a form.
A request path can reveal which page was requested, while browser information can help identify technical problems affecting particular devices. Referrer information, when supplied by the browser, may indicate the page from which a request originated. Browser settings and service configuration can affect what is transmitted or recorded. The website does not require visitors to provide a personal name in order to view its content. Nevertheless, technical information can sometimes relate to an identifiable person, especially when combined with information held by another provider. It should not be treated as automatically anonymous merely because it is technical.
Information entered into the page
The current Contact Us page contains no contact form and does not submit a message when you browse it. Its temporary email placeholder is not an active website mailbox. The page's text does not collect a name, email address, or message through an input field. Other visible controls, such as navigation and the homepage demonstration, are intended to support reading and interaction rather than create visitor profiles. If a future feature asks for information, the purpose and handling of that feature should be explained before it is relied on. The presence of this policy is not consent to undisclosed collection.
Cookies and browser storage
The current website code
The current site JavaScript does not include code to set tracking cookies or save visitor information in local storage or session storage. It handles interface behavior such as the menu, visual demonstration, and display of the copyright year. The absence of storage code in those files does not prove that every service in a hosting environment is incapable of using cookies. Infrastructure, embedded services added later, or separate destinations may behave differently. This policy distinguishes what the page code does from broader claims about systems that are configured outside those files.
Your browser choices
You can manage cookies and stored website data through your browser settings. Those controls may let you inspect, remove, or restrict data stored by particular services. Their exact names and effects vary between browsers. Blocking a separate provider's storage can affect that provider's functionality, but it does not require you to submit information to this site's nonexistent contact form. If you have a question about an observed cookie, identify the domain and the interaction involved rather than assuming that all cookies visible during a browsing session originated from this website.
Changes involving measurement tools
The current website files do not include an analytics or advertising tracker. If measurement or advertising tools are introduced, the operator should assess their information practices and revise the relevant privacy explanation before those tools are used. Where applicable rules require a choice or consent, that requirement should be addressed for the actual feature. This page does not promise that all future tools will operate in the same way as the current static implementation. It explains the current scope so visitors can distinguish ordinary page functionality from a separate tracking feature.
Fonts and other page resources
The pages request fonts from Google Fonts. Loading those fonts can involve requests to Google-operated domains, which may receive connection information such as the visitor's IP address and browser request details. This is separate from the website's own JavaScript setting a tracking cookie. Font requests are used to display the site's typography, and the provider controls its own service infrastructure. If the fonts cannot load, the page styles include fallback fonts. Visitors who restrict external requests through browser tools may therefore see a different typeface while still being able to read the text.
The website also serves images, style sheets, and scripts used for its own presentation. Requests for these resources can be handled by the hosting environment in much the same way as page requests. A decorative image does not need a visitor's name to display, but delivering it still involves a network request. The distinction helps explain why a site with no registration or contact form can still have technical processing associated with browsing. The site does not use its logo animation as a reason to ask for personal information, and animation is not necessary to understand the privacy text.
Email correspondence
Voluntary messages
If a functioning contact email address is configured and you choose to write to it, the message may include your sender address, display name, subject, message body, and any attachments you send. Your email provider and the receiving provider also handle delivery information according to their own arrangements. Send only information relevant to the inquiry. For an ordinary correction, the page name and the affected statement are usually more useful than extensive personal details. A voluntary email is different from passive browsing because you choose the content you disclose in the message.
The temporary [email protected] address currently displayed on Contact Us is a placeholder, not a working Better Foliage Mod mailbox. Do not send information to it or expect that the operator can retrieve messages addressed to it. The explanations in this policy concerning email describe the handling relevant to a real mailbox once one is established. They do not establish that the placeholder forwards messages or is monitored. The status of the contact address should be checked before using email as a route for questions, corrections, or requests relating to personal information.
How correspondence may be used
Relevant correspondence may be used to understand an inquiry, reply to the sender, investigate a website problem, or review an attribution or privacy concern. It should not be treated as permission to publish the sender's address or private message on the website. If a report helps identify a content correction, the correction can often be made without exposing the person who reported it. The website is not intended to build marketing profiles from ordinary support questions. Any use outside the stated purpose would need its own appropriate explanation and basis rather than being assumed from the act of sending a message.
Purposes and necessary information
Information relevant to website operation may support delivery, maintenance, troubleshooting, security, and communication about a specific inquiry. These purposes should be connected to the information actually needed. A broken-link report does not normally require an identity document, and an accessibility question does not require a medical history. Collecting less information can make a request easier to handle and reduce unnecessary exposure. The appropriate legal basis for a particular processing activity depends on the operator's role, the activity, and applicable requirements; this page does not claim that one basis automatically covers every possible future feature.
If an inquiry requires verification, the operator should limit the request to what is proportionate to the matter being addressed. For example, a question involving an earlier email may be easier to assess when the requester can identify the relevant correspondence. That does not mean all visitors must provide formal identification to ask a question. Where a legal obligation applies, the relevant obligation may affect how the request is handled or which records must be retained. The website's informational role does not remove applicable privacy responsibilities, and this policy should not be read as permission to ignore them.
Providers and sharing
Hosting and email providers may process technical information or correspondence as part of delivering their services. Depending on the service arrangement, they may act on instructions from the operator or handle certain information under their own responsibilities. This website's static files do not name a complete set of infrastructure providers or establish all of their storage locations. The operator should use suitable arrangements for any provider handling personal information on its behalf. Necessary service processing is different from selling visitor details, and the resource has no visitor-data sales feature in its current implementation.
Information may also need to be handled in response to a valid legal requirement or to address a specific security problem, subject to applicable law. Such circumstances should be assessed on their actual facts rather than used as a reason for indiscriminate disclosure. Access to correspondence should remain limited to people or services that need it for the relevant purpose. A privacy request concerning another provider's separate records should be directed to that provider. The website cannot promise to control data held by every organization involved in a visitor's internet connection, email delivery, or software download.
Retention and security
Keeping information for a relevant purpose
Information should be retained only for as long as necessary for its purpose, taking account of any applicable obligations and the operational context. Hosting logs may have a provider-defined retention period, while correspondence may need to remain available long enough to complete an inquiry or document its resolution. This page does not invent a fixed period for a hosting or email service that has not been identified. Records that are no longer needed should be reviewed for deletion or appropriate minimization. A request to remove information may need to be assessed alongside a legitimate obligation to retain particular records.
Protecting information
Reasonable protection depends on the systems actually used to host the site and manage correspondence. Access controls, service configuration, and secure handling of messages can contribute to that protection. No website can promise that every transmission or storage system will be completely free from risk. Visitors can help by excluding secrets, unnecessary attachments, and sensitive personal information from ordinary inquiries. If you report a security concern, describe the relevant behavior without attempting to access another person's information. Responsible reporting does not require demonstrating a problem by collecting or publishing private records.
Your requests and choices
Depending on applicable law and the circumstances, you may have rights to request access, correction, deletion, restriction, or other action concerning personal information. Those rights can have conditions and exceptions. A request should identify the information or interaction concerned so the responsible party can understand it. You may also be able to raise a concern with a relevant supervisory authority where applicable. This policy does not limit rights that apply by law. It also does not promise that the website can act on records controlled solely by a separate download platform or email provider.
When an active contact address is available, the operator can assess requests relating to information within its control. The present placeholder cannot serve that function. In an initial request, avoid sending more personal data than is needed to identify the issue. If additional clarification is necessary, it should be connected to that issue. Changing browser settings, avoiding unnecessary emails, and reviewing third-party practices are choices available to visitors, but these choices do not transfer all privacy responsibility away from the operator. The relevant responsibilities depend on the actual activity and the applicable requirements.
Children and shared devices
The site provides general information about a Minecraft mod and does not offer a child account system or intentionally request children's personal profiles. Younger visitors should avoid sending identifying information through email and seek help from a responsible adult where appropriate. If an operator learns that unnecessary personal information about a child has been received, it should assess the appropriate response under applicable requirements. On shared devices, other users may be able to see browser history or locally saved files. Those local circumstances are separate from data collected by the website and are best considered when using a shared browser.
Changes to privacy practices
This policy should remain consistent with the website's actual features and service arrangements. If the operator adds a form, account feature, analytics service, or other processing activity, the explanation should be reviewed accordingly. Visitors can read this page to understand the described practices and check Contact Us for the status of the email channel. Questions should focus on the relevant interaction so that the website's handling can be distinguished from the separate services involved.