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.

The complete recording profile stores chat and ordinary command content. Known authentication arguments and named secret values are filtered. Owners can redact all chat text or command arguments. Vanished staff are included by default; an owner can explicitly exclude them.

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 shares data only with providers acting on its behalf, in these categories: hosting and infrastructure; content delivery, storage and security; and email delivery. Payments are handled by Tebex as merchant of record. The Data Processing Agreement at replaycore.com/legal/dpa sets out the terms, and a current sub-processor list is available to customers on request.