Playtest Privacy Notice
Effective date: 28.08.2026
Version: 1.1
This Playtest Privacy Notice explains how BRICKWORKS GAMES LTD (“Brickworks”, “we”, “us”) collects and uses information during the closed Steam Playtest of Sublustrum.
This notice supplements our general Privacy Policy. If this notice and the general Privacy Policy differ in relation to this closed playtest, this Playtest Privacy Notice applies to the playtest-specific processing described below.
1. Who is responsible for your data
The data controller is:
BRICKWORKS GAMES LTD
28 Oktovriou, 367, Mediterranean Court, 1st floor, Flat/Office A5, 3107, Limassol, Cyprus
Privacy contact: privacy@brickworksgames.com
2. Publisher
Sublustrum is published by Hypetrain Digital.
Unless we tell you otherwise, raw bug reports, screenshots, crash reports, and diagnostic data submitted during this playtest are processed by Brickworks Games Ltd and authorized personnel or service providers acting on our behalf.
We may share aggregated or anonymized playtest findings with publishing partners for production, release planning, and quality assessment.
3. Steam Playtest
Access to the playtest is provided through Steam Playtest.
Valve / Steam processes Steam account and platform data under Valve’s own policies and terms. Brickworks Games Ltd is responsible for the bug reports, crash diagnostics, and playtest data that we collect through the game client, Unity Cloud Diagnostics / Unity Cloud User Reporting, and Unity Dashboard.
4. Unity Cloud Diagnostics / Unity Cloud User Reporting
Bug reports and crash reports submitted during the closed playtest are processed through Unity Cloud Diagnostics / Unity Cloud User Reporting.
Reports are submitted from the game client to Unity and are stored on Unity’s infrastructure. Authorized Brickworks Games Ltd personnel access these reports through Unity Dashboard for the purposes described in this notice.
Unity processes this data on behalf of Brickworks Games Ltd as a processor / service provider. Brickworks Games Ltd remains responsible for deciding why the data is collected, how it is used for the playtest, and how players are informed about this processing.
5. What we collect
Bug reports
When you manually submit a bug report, we collect:
- your bug description;
- the screenshot previewed in the bug report form;
- technical and diagnostic data attached to the report;
- report metadata.
Please do not include personal or sensitive information in your bug description.
Automatic crash reports
If Sublustrum crashes during the closed playtest, a crash report may be submitted automatically through Unity Cloud Diagnostics.
Crash reports are used to investigate crashes, improve stability, identify build-specific or hardware-specific issues, and operate the closed playtest.
Crash reports may include technical diagnostics and limited gameplay context needed to investigate the crash.
Diagnostic data
Bug reports and crash reports may include:
- build, package, Unity, and platform information;
- operating system and system language;
- display and graphics settings;
- device, memory, and graphics information;
- active scene name;
- camera position and camera direction;
- object or location the camera was looking at;
- approximate country;
- technical report metadata.
This may include fields such as:
- Platform
- BuildVersion
- UserReportingPlatformVersion
- TargetFrameRate
- SystemLanguage
- ResolutionHeight
- QualityLevel
- Orientation
- OperatingSystem
- IsEditor
- InstallerName
- GraphicsDeviceVersion
- GraphicsDeviceType
- DPI
- DeviceModel
- ActiveSceneName
- MainCameraPosition
- LookingAt
- LookingAtGameObjectPosition
- Expires
- UnityVersion
- PackageVersion
- Source
- SystemMemorySize
- ResolutionRefreshRate
- ResolutionWidth
- OperatingSystemFamily
- IsFullScreen
- InstallMode
- GraphicsMemorySize
- GraphicsDeviceVendor
- GraphicsDeviceName
- DeviceType
- BuildGUID
- MainCameraName
- MainCameraForward
- LookingAtGameObject
- ContentLength
- GeoCountry
6. Why we collect this data
We use this data to:
- investigate bugs;
- reproduce reported issues;
- investigate crashes;
- improve stability and performance;
- identify build-specific or hardware-specific problems;
- operate the closed playtest;
- protect the security and integrity of the playtest reporting flow;
- handle legal, security, or support matters if needed.
We do not use bug reports or crash diagnostics for advertising.
7. Legal bases
For players in the European Economic Area and the United Kingdom, we rely on:
- legitimate interests to operate the closed playtest, investigate bugs and crashes, improve stability, maintain security, and identify technical issues in a pre-release build;
- consent / affirmative submission when you manually send a bug report with screenshot and diagnostic data;
- legal obligations where processing is required by applicable law;
- legal claims where processing is necessary to establish, exercise, or defend legal claims.
For automatic crash reports, we rely on our legitimate interests to operate the closed playtest, investigate crashes, improve stability, maintain security, and identify technical issues in a pre-release build.
For players in other regions, we process playtest data as described in this notice and in accordance with applicable privacy laws.
8. Who can access the data
Access is limited to authorized people who need it for their role, such as:
- QA;
- developers;
- producers / project managers;
- authorized contractors supporting development, QA, infrastructure, or security;
- Unity as our reporting service provider / processor.
We do not sell bug report or crash diagnostic data.
9. International transfers
Brickworks Games Ltd is established in Cyprus.
Bug reports and crash reports are processed through Unity Cloud Diagnostics / Unity Cloud User Reporting and may be stored or processed by Unity and its subprocessors in countries where Unity or its subprocessors operate.
Where required by applicable law, Unity and Brickworks Games Ltd rely on appropriate contractual and legal safeguards for international data transfers, including applicable data processing terms and transfer mechanisms.
10. How long we keep the data
Bug reports and crash reports submitted through Unity Cloud Diagnostics / Unity Cloud User Reporting are normally retained for up to 90 days, depending on Unity plan, settings, and service configuration.
Aggregated or anonymized playtest findings may be kept longer because they no longer identify individual players.
When data is no longer needed, it is deleted or anonymized where technically available through Unity Cloud tools.
11. Your choices
You can choose not to submit a manual bug report.
If you do not agree to send a bug report with the screenshot and diagnostic data listed in the form, do not check the checkbox and do not submit the report.
Automatic crash reporting is part of this closed playtest. If you do not want automatic crash reports to be processed as described in this notice, please do not participate in the closed playtest.
12. Your privacy rights
Depending on where you are located, you may have rights to:
- request access to your personal data;
- request correction of inaccurate data;
- request deletion of your data;
- object to certain processing;
- withdraw consent where processing is based on consent;
- request restriction of processing;
- request data portability where applicable;
- lodge a complaint with a data protection authority.
To exercise your rights, contact:
Because bug reports and crash reports are processed through Unity Cloud Diagnostics / Unity Cloud User Reporting, we may need information that helps us locate your report, such as:
- report ID, if available;
- installation ID, if available;
- approximate date and time of submission;
- build version;
- country;
- description of the reported issue.
If we can locate the relevant data, we will request deletion or delete it through the available Unity Cloud tools, unless we need to retain it for legal, security, or claims-handling reasons.
13. Data we ask you not to provide
Please do not include the following in bug reports:
- real name;
- address;
- phone number;
- email address, unless specifically requested by support;
- payment information;
- passwords;
- Steam credentials;
- health or medical information;
- political, religious, or other sensitive information;
- information about other people.
14. Changes to this notice
We may update this Playtest Privacy Notice if the playtest changes, if we add new data collection features, if countries change, or if legal requirements change.
If we make material changes, we may ask you to review the updated notice before continuing the playtest.
15. Contact
BRICKWORKS GAMES LTD
28 Oktovriou, 367, Mediterranean Court, 1st floor, Flat/Office A5, 3107, Limassol, Cyprus
Email: privacy@brickworksgames.com