Safety & support
Privacy, logs and screenshots
Understand what diagnostic evidence can contain, what to redact and what should never be sent to support.
Optional model improvement#
The launch plan includes script-based automation and optional dataset contribution during normal VRA runs. Young Studio will train its own VRA model; customers will not need to train a model or manually assemble screenshots.
Additional customer examples are separate from core operational diagnostics, licensing and marketing consent. Preferences start off and have independent failed/low-confidence, successful-example and human-review choices.
Consent, privacy filtering, review, withdrawal, deletion and documented storage terms must be ready before launch. The experimental vision/language model is planned for a later iteration, only after internal testing demonstrates an improvement over script-based automation. VRA is pre-release; this is the release roadmap, not a claim that collection is available today.
No automatic unlearning is promised for already-trained models. Read the dedicated product notice for the current boundary and the separate treatment of previously uploaded optional records.
Local execution and customer evidence#
VRA is designed to operate the customer’s Windows and LDPlayer environment. The Command Centre presents local farm configuration, run results and diagnostic evidence needed to understand failures.
The public website interest list is separate. It stores the confirmed email, optional farm-count range, consent evidence and mail state described in the privacy notice; it does not ask for game passwords or emulator configuration.
What captures may show#
- Character or tribe names visible in the game.
- Resource amounts, city level, queue state and current screen.
- Emulator profile labels or Windows window titles.
- Error text and the timing of a failed step.
Never send#
- Game passwords, email passwords, recovery codes or payment details.
- Licence secrets, private activation material or SMTP/API credentials.
- An entire emulator image when a screenshot and result record are sufficient.
- Unredacted information belonging to another person.
Open every screenshot and text file yourself. Redact unrelated names, chat and identifiers while preserving the failed control and visible state.
Still stuck?
Complete the evidence checklist before contacting support. Never send passwords, recovery codes, payment details or private licence material.