Privacy
A description of what this site actually does with information when you read it.
Private reference history
Retired game-product records and source history may be retained privately to support corrections and recovery. They are not a public browsing history, visitor profile, or searchable archive of previous products. Selecting a game mode does not create an account or a personal profile.
An anonymous, read-only site
PatchRecord has no public accounts, sign-ups, comments, community features, payments or contact forms. You do not submit personal information to read it.
Dark appearance
PatchRecord uses its dark appearance consistently, regardless of your device settings. The site does not read or save an appearance preference in your browser.
Performance and interaction analytics
On public content pages, PatchRecord measures loading (LCP), interaction responsiveness (INP) and visual stability (CLS) to improve the site. It also counts search submissions by entry point, item-history openings by family, and source-link openings by source category. Replit's injected analytics tracker receives those named events and fixed categories when enabled in Publishing settings, and separately handles pageviews. PatchRecord stores only daily event counts, the deployed build, a broad page category, and fixed event categories for 30 UTC days. Exact URLs, search terms, source URLs, IP addresses, user agents, account IDs and individual measurement values are not stored by these application event records. The application's aggregate collector creates no tracking cookie or persistent visitor identifier. A randomized page-load ticket is used for replay protection; its hash, revision counter and coarse measurement bucket are stored for at most 24 hours to prevent duplicate counting when measurements change. Event replay counters also expire within 24 hours. Expired records are deleted when the next measurement or event arrives. Do Not Track and Global Privacy Control disable application collection. Known bots, automated browsers and private admin pages are excluded. Replit-hosted analytics can be disabled separately in Publishing settings. Encrypted recovery snapshots follow the separate backup retention policy. Hosting infrastructure may still retain its own request logs as described below.
Hosting and security processing
Like any website, requests pass through hosting and network infrastructure that processes technical information such as IP address, requested URL, time and browser details in order to deliver pages, keep the service running and protect it against abuse. That infrastructure may keep operational logs. PatchRecord does not use this information to build profiles and does not sell it, but it cannot promise that no logs exist.
Searches, filters and URL state
Search terms, filters, sort order and opened weapon or attachment details are kept in the page address (for example /?q=… or /?weapon=…) so links, refresh and Back work. They are not saved in cookies or browser storage. Because they are part of the requested URL, hosting request logs described below may contain them; the application's own event counts do not store search terms or exact URLs.
External links
Source links open external websites, and the footer X link opens x.com/patchrecord in a new tab. PatchRecord embeds no X feed, widget or social tracking. Those sites have their own privacy practices, which apply once you follow a link.
Changes to this page
If site behaviour changes in a way that affects this description, this page will be updated to match.