Age-assurance record
The operator keeps an operational record of the intended method, provider, placement, data handling, effectiveness evidence and periodic review. The private archive remains closed until that system is configured.
Content and migration records
Source inventories, repair manifests, release notes and automated test results are retained so that pages are not silently lost, duplicated or replaced by the wrong content during deployment.
Applications and consent
Each serving application records the rules version, affirmative confirmations, submission time and a private reference. Sensitive answers remain in the database and are not copied into email alerts.
Bookings and payment status
A booking can record the selected service, calculated amount, enquiry status and provider reference. Card details stay with the external payment provider. Payment records are not created by games, archive language or a serving application.
Complaints and moderation
Administrative actions can be audited with a hashed actor identifier. Staff receive less information than the owner, and sensitive questionnaire fields are excluded from the moderation list.