1. Current website and waitlist
The existing website privacy notice describes the live interest list, confirmation/removal flow, aggregate measurement and preferences. Those controls are separate from future licence terms. Browsing this legal centre does not grant a new permission to process data.
Contact [email protected] about information collected through the website. Product-account processing and optional screenshot contributions are separate purposes; we will provide the applicable privacy information before those services collect data.
2. Essential product/account data at launch
Account and licence operations may require contact details, authentication records, plan/payment references, device identifiers, activation state, validation times and security/audit events. We will disclose the actual data fields, purposes, lawful bases, processors, retention and transfer arrangements before collection begins.
We do not request game passwords or retain payment-card secrets in support records. We limit product-access checks and fraud investigations to necessary information. Essential licence validation does not require consent to unrelated marketing, screenshot training or advertising.
3. Operator-held customer information
The current Managed Farms workspace keeps customer groups, notes, agreements and work records locally on the installation. That is not a hosted customer portal or an automatic upload of the operator’s customer list. Exports and support attachments can still contain personal information; review them before sharing.
Operators must explain their own processing, access controls and retention to their customers and have the required lawful basis. Controller/processor roles depend on actual processing, not a blanket label. Where a service creates a processor relationship, we will provide the required data-processing agreement. Supplying a local tool alone does not establish that relationship.
4. Optional screenshots and VRA’s model
Optional customer examples are intended to help train and evaluate VRA’s own model—not a separate model that every customer must train. This is separate from buying a licence, obtaining support and subscribing to launch emails.
Before enabling contributions, we will explain what images and metadata may contain, local filtering, recipients, storage, retention, review choices and withdrawal. Redaction is not guaranteed anonymisation, and deleting a stored example cannot be promised to remove its influence from a trained model. Current public material describes a launch plan, not an enabled upload service.
5. Privacy requests and security
Depending on applicable law and processing, people may have rights to information, access, correction, erasure, restriction, objection and portability, and to withdraw consent or complain to a regulator. We use proportionate identity checks and do not require a passport or game credentials for every request.
Use [email protected] for privacy or security questions. Keep private confirmation links, account credentials and other people’s data out of public reports. Account cancellation, marketing withdrawal and a privacy-deletion request are different actions; we explain their effects and any lawful retention separately.
Questions, complaints or corrections: hello@vrabot.com.