Privacy

Public game observations

RoyaleRecord primarily processes public Clash Royale game data. Observed player names and tags, clan membership, trophies, decks, battle records, ranking positions and related public values may be stored historically. A player account on RoyaleRecord is not required for these public observations to exist.

Historical continuity

Historical observations may remain after a name, clan membership or other value changes upstream. Retention depends on the purpose and operation of the historical record; RoyaleRecord does not promise a fixed retention period that the application does not enforce.

Technical protection data

For security and availability, the application processes request metadata and rate limits protected routes. The active rate limiter uses a SHA-256 hash of the client IP address instead of writing the raw address into the counter filename. Application logs redact recognized secrets and authentication values.

Cookies, tracking and sale

The current website does not set advertising, analytics or account cookies and does not include third-party tracking code. RoyaleRecord does not sell user data. If these practices materially change, this policy and any required consent controls must be updated before that change is released.

Contact before production

A monitored privacy contact will be published when the owner configures the production contact address. No unmonitored or invented address is presented here.