What data ReplayCore collects

ReplayCore operates as a data processor under the UK GDPR and the Data Protection Act 2018. You, the server operator, are the controller. You decide what is recorded through Configuration Studio and the dashboard's access controls; ReplayCore processes that data on your documented instructions.

To reconstruct a match, the recorder captures gameplay state: player positions and actions, block changes, entity events, and game events surfaced by your mini-game integrations. Players are identified by their Minecraft UUID and username.

Chat and command content is redacted by default: the recorder notes that a chat message or command happened, but does not store the message text or command arguments. These managed privacy defaults should only be relaxed with a lawful basis. Vanished staff are excluded from recordings by default.

The cloud stores replay archives and their metadata (server, integration, duration, size, retention window, visibility), plus account information for your panel users (name, email, password hash) and billing details handled by the payment processor.

Operational data such as usage metrics and error telemetry is collected to run the service reliably. Telemetry sent to monitoring sub-processors is scrubbed of player personal data.

ReplayCore only shares data with responsible third-party providers acting on its behalf, and uses a small set of sub-processors to deliver the service: Cloudflare (CDN, DDoS mitigation, Workers compute, and object storage; stores data in the region closest to the user automatically), OVH Cloud (dedicated infrastructure and database hosting; data-centre locations currently in London, United Kingdom and Beauharnois, Canada), Stripe (payment processing), and Resend (transactional email). We advise you to review each provider's own privacy policy. The authoritative list, and notice of changes, is maintained in the Data Processing Agreement at replaycore.com/legal/dpa.