Privacy Policy
How browsing, search queries, hosting requests and email contact work on this independent Over the Hill fan site.
Last updated:
1. Scope and contact
This Privacy Policy explains how Over the Hill Hub handles information when you visit overthehillhub.org, search its content, use interactive maps or contact the site. Over the Hill Hub is an independent fan website. It does not operate the game, a storefront or a multiplayer account service.
For privacy questions, contact [email protected]. This notice covers this website’s activities. Independent services such as Steam, Discord and email providers apply their own policies when you use them.
2. Technical information used to deliver the site
A browser requesting a page, image or other file sends technical information needed for the connection. This can include an IP address, browser and device information, requested address, request time, referring information where supplied, and security or error information. Hosting infrastructure may process these requests to deliver pages, detect abuse and investigate faults.
Reading the site does not require registration, a display name, a connected game account or a game save. The application does not ask for payment information. Information involved in ordinary browsing is separate from information you voluntarily include in an email.
3. Search queries and browser history
Site search matches a query against published content in your browser. Search submitted through the header puts the query in the search page address. That address can remain in browser history, copied links and routine hosting request records. List filters do not create a player profile.
Use search for game topics rather than private information. Do not enter passwords, account recovery codes or payment details. Clearing an input removes the visible query; it does not automatically erase earlier browser history or infrastructure records containing a requested address.
4. Map discoveries on your device
The map saves the IDs of discoveries you mark as found in browser local storage under oth-map-progress-v1. These are records for the website’s checklist, not a copy of your game save. The application does not upload them, connect them to an account or synchronize them between devices.
Use the map’s reset controls to clear supported progress records, or clear this site’s browser data to remove local records. Another browser profile, private browsing, blocked storage or cleared site data can show a different checklist. Anyone using the same browser profile may see the saved progress.
5. Personal notes, measurements and shared links
Map notes are stored separately under oth-map-notes-v1. They contain the note text, area and map position you choose and are not uploaded by the application. Individual notes can be deleted from the notebook. Clearing site data removes the stored notebook. Do not put passwords or other sensitive information in notes, especially on a shared device.
Measurements are temporary and disappear on reload. A shared map link identifies the selected area and, where applicable, a marker. It does not contain your private notes or discovery checklist. If you send the link through another service, its address is visible to recipients and may be retained by that service.
6. Cookies, analytics and advertising
The website uses Google Analytics 4 through the Google tag to measure page views and understand how visitors use the site. The tag sends measurement data to Google and can use first-party cookies to distinguish visitors and sessions. The application does not send your private map notes or saved discovery checklist as custom analytics events.
You can manage cookies through your browser settings or use tools that block analytics requests. Google applies its own privacy practices to the data it receives. Hosting infrastructure also processes technical requests for delivery, security and troubleshooting. The application has no account cookies or advertising network integration; its map storage serves the local functions described above.
7. Email correspondence
When you contact [email protected], the message may include your email address, name or signature, text, attachments and ordinary email metadata. Relevant information is used to understand the issue, respond where appropriate, review corrections or rights concerns, and keep a record of how the matter was handled.
A correction email does not subscribe you to a newsletter. Send only what is needed. Crop unrelated conversations and private account details out of screenshots. Do not send passwords, authentication codes, payment details or complete game saves. A page address, entry name, version and short explanation are usually a useful starting point.
8. Purposes and applicable processing grounds
Information is handled to deliver requested pages, protect service availability, maintain local map choices and address correspondence. Where applicable law requires a processing ground, routine delivery, security and correspondence may involve the legitimate interests of maintaining the website or steps needed to handle a request you make. Legal obligations may also require certain records.
A future optional activity that requires consent must explain the relevant choice separately. Merely visiting this website is not presented as blanket consent to unrelated processing. This policy describes the current functions rather than claiming that every possible legal basis applies to every visitor.
9. Providers, disclosures and processing locations
Hosting and email services necessarily process information involved in their services. Relevant information may also need to be reviewed by an adviser or disclosed in response to a valid legal requirement. Such handling should be limited to the purpose or obligation concerned.
Service providers may operate systems outside your country. The locations involved depend on the hosting and email services handling the request. Contact us with a specific privacy question if you need information about how a particular message or service is handled.
10. Retention, deletion and security
Local records remain until you delete them or the browser removes them. Correspondence is retained as reasonably needed to address the matter, maintain appropriate administrative records and meet applicable obligations. Retention varies with the request. Infrastructure log retention is managed by the provider and is separate from the local records held by this application.
No website, email channel or local storage system can be described as completely secure. Protect access to your device and email account, and avoid supplying unnecessary information. Deleting map progress does not delete a separate email you previously sent; deleting browser history does not remove a message from an email service.
11. Your choices and privacy requests
Depending on applicable law and the information involved, you may have rights to request access, correction, deletion, restriction, an objection to processing or a portable copy of information you supplied. Where processing actually relies on consent, you may have a right to withdraw it. These rights have conditions and exceptions; not all apply to every record.
Email [email protected] with the information and action concerned. Reasonable information may be needed to locate correspondence or verify that the request concerns you. Do not send identity documents unless a specific need and appropriate method have been explained. Local map data cannot be retrieved remotely by emailing us. Where applicable, you may raise concerns with the relevant data protection authority.
12. Children and policy changes
This is a general-audience fan guide and its features do not require children to provide personal information. Contact us if you believe a child has sent information that should be removed, providing enough detail to locate it without adding unnecessary information about the child.
Material changes to information practices will be reflected in this notice. The page’s last-updated date identifies its substantive revision. Review the current notice when using a new feature or when you have a question about how an existing feature handles information.