Privacy Policy

1. Developer and scope

Horse Reality Enhanced (HRE) is an independently developed browser extension for Horse Reality. HRE is not developed or operated by the Horse Reality team. Horse Reality and any other services you use have their own privacy practices.

For support and privacy requests, use the developer contact details below.

2. Data processed and why

HRE uses information from the Horse Reality pages and game responses you access, together with information you enter in the extension. Processing depends on the features you enable.

• Game information: horse names and IDs, breeds, sex, age and status, genetics, conformation scores, stable or block membership, taglines, notes and Horse Reality account identifiers. These support the display, filtering, prediction and management features.
• Your extension data: preferences, Hidden Genes entries and review or lock status, Keep/Yeet decisions, Cut-Off rules and assignments, score history, Autonaming databases, templates, filter presets, summary settings and screenshot configuration.
• Technical information: the existing signed-in game session, request and cache state, and temporary operation markers needed to perform the requested features. Optional diagnostic data and screenshots are described separately below.

Public and private horse notes may be read temporarily and sent back to Horse Reality to preserve them when updating a horse. Text you enter in templates or notes, or include in an export, may contain personal information.

3. Storage, game requests and security

Persistent extension data is stored in the current browser profile using Chrome’s local extension storage. Temporary data also uses memory and session storage. In version 1.1.25, stored extension data is shared across Horse Reality accounts used in that browser profile; it is not separated by game account or automatically synchronised between devices.

HRE sends HTTPS requests to Horse Reality to read game information and carry out supported features using your existing game session. Actions such as Care All, Autonaming and enabled Keep/Yeet automation can update game data. HRE does not ask you to provide your game password to the developer.

The extension has no developer-operated upload endpoint and does not automatically send its stored records, backups, screenshots or diagnostics to the developer. HRE does not add encryption to local storage or exported backup files; their protection also depends on your browser, device and file-access settings.

4. Quick Screenshot and clipboard

When you request a Quick Screenshot, HRE captures the visible supported Horse Reality page, crops the image locally and writes the result to the clipboard. The captured area can contain information visible on the page. HRE does not read existing clipboard contents or upload the screenshot. Any later saving or sharing of that image is your own action. The browser may request an additional capture permission for this feature.

5. Optional diagnostics and support

Troubleshooting Mode is off by default. When enabled, it records bounded local diagnostic sessions, including the extension version, timings, counters, normalised page or request paths, errors and events. Common credentials and token-like values are masked, but records can still contain game details or other information from error messages. Redaction should not be treated as a guarantee that an export contains no personal information.

Diagnostics are exported only when you choose Export. HRE does not send the resulting file to the developer automatically. If you separately send a report, backup, screenshot or message for support, the developer receives the information you choose to provide and uses it to investigate and answer that request. Review the material before sharing it. Support correspondence and attachments should be retained only while needed for the request, related follow-up or an applicable legal obligation.

6. Retention, export and deletion

• Local settings and records remain until you remove them through available controls, replace them through an import, clear the extension’s storage or uninstall the extension. Switching off a feature does not necessarily erase its saved data.
• Diagnostic sessions remain until you use the Diagnostics Clear control or automatic pruning removes older sessions. Pruning is based on a limit on the number of sessions, not a promised deletion date. Turning Troubleshooting Mode off stops recording but does not itself erase previous sessions.
• Backup export creates a local JSON file. A validated import replaces the current backup-managed data; a temporary recovery journal remains locally until restoration or recovery succeeds. Back up your data before changing the extension’s identity or installation.
• Downloaded backups, diagnostic exports, saved screenshots and copies you have shared are separate from the extension’s storage. Uninstalling HRE does not delete those files or reverse changes already made in Horse Reality. You must manage those copies and game records separately.

7. Sharing, third-party services and limited use

HRE does not sell user data and includes no advertising SDK, analytics service, behavioural advertising or profiling of users. It uses data only for its described features and user-requested support. This limited-use approach follows the Chrome Web Store User Data Policy; user data is not used for unrelated purposes or training general-purpose AI models.

Horse Reality receives requests necessary for the game features. If you open documentation, community, donation or other external links, the destination service handles that visit under its own policies. Other installed extensions may interact with the same pages; their processing is outside HRE’s control. Optional future Google Drive transfers are described below.

8. Your choices and privacy rights

You can enable or disable individual features, keep Troubleshooting Mode off, choose whether to export or share files, and remove local data as described above. Refusing a permission may prevent the corresponding feature from working. The developer cannot remotely retrieve or erase data held only in your browser.

Where applicable data-protection law provides these rights, you may request access, correction, erasure, restriction or portability of personal data, object to processing based on legitimate interests, and withdraw consent for consent-based processing without affecting earlier lawful processing. Contact the publisher using the contact details below. You may also complain to your competent data-protection supervisory authority.

Publisher review required — legal basis: confirm the basis for any personal-data processing before publication. The proposed basis for necessary feature operation and handling support enquiries is the legitimate interest in providing and maintaining the service you request, subject to users’ rights. The proposed basis for optional Google Drive sync is consent. These proposals do not replace the publisher’s assessment of the actual processing.

9. Changes to this policy

This policy must be kept consistent with the released extension. Changes to the purposes, recipients or categories of data must be explained before the changed processing begins, with renewed consent where required. The revision date identifies the latest update.

10. Planned Google Drive sync — not active in version 1.1.25

The following is a proposed disclosure for the planned sync feature. It must be checked against the implemented version before activation or production OAuth verification. Current HRE does not connect to a Google account or transfer extension data to Google Drive.

Connection and access

The planned feature will be optional and start only after you choose to connect a Google account and authorise access. Google will handle sign-in; HRE will not receive your Google password. The proposed Drive permission is drive.appdata, which allows access to HRE’s own application-data area. Account identification needed to show the connected account, and authorisation tokens needed to access that area, will be used only for the connection and sync.

Data and purpose

The proposed sync covers selected settings, templates, horse records, Hidden Genes and their review or lock state, decisions, assignments and score history. It will transfer data between your devices and your own Google Drive app-data area, without a central developer database. Game login credentials, Google authorisation tokens, diagnostics, screenshots, temporary caches and pending game actions are excluded from the proposed synced dataset.

Control, retention and deletion

Under the proposed design, you will be able to pause sync, disconnect the account and separately delete HRE’s cloud data. Revoking access stops further authorised access but should not be assumed to delete existing cloud files. Uninstalling the browser extension should not be assumed to remove the cloud copy. Local copies and exported files must be managed separately. Cloud data will remain until you delete it or Google removes it under its service rules.

Google services and limited use

Google will process sign-in and Drive requests under the Google Privacy Policy and applicable service terms, including its provisions on storage locations and international processing. HRE will not promise storage in a particular country. Google API data will be used only for the disclosed sync feature and in accordance with the Google API Services User Data Policy, including the Limited Use requirements. It will not be used for advertising, sold, or used to train general-purpose AI models.

11. This website and GitHub Pages

When this project website is served through GitHub Pages, GitHub hosts and delivers its files. GitHub states that it logs and stores visitors’ IP addresses for security purposes, including for visitors who are not signed in. See GitHub Pages data collection and the GitHub Privacy Statement for its processing practices, retention and available privacy rights.

The website itself contains no analytics scripts, advertising trackers, contact forms or embedded third-party content. Its code does not set cookies or use browser storage. Fonts are provided by your device and the images are hosted with the page. Following an external link opens the relevant service; using an email link opens your email application. Information you choose to send for support is handled as described in section 5.

Visiting this website does not give it access to HRE’s stored horse records, extension settings or a Google account.