Short version: OPAL has no telemetry and no analytics. It doesn’t collect, transmit, sell, or monetize your data. It talks to the network only to do the jobs you ask of it — fetching engine releases, indexing the gem repositories you add, and downloading what you tell it to.
What OPAL does not collect
- Your name, email, IP address, or machine identifiers
- Which projects you have, what they contain, or where they live
- Which engines you install or what you build
- Any content from
project.json,gem.json, or your source code
There is no telemetry system, no usage analytics, and no crash-reporting service built into OPAL.
What OPAL connects to — and why
OPAL reaches the network only to perform the actions you initiate:
| Connection | Purpose | Under your control |
|---|---|---|
| O3DE release metadata | List installable engine versions | Only used when you open Engine Downloads |
| Custom engine sources | List engine builds from hosts you add | Only the hosts you configure |
| Configured gem repositories | Index gems for the Asset Library | Only the repositories you add; remove one to stop |
| Gem / engine downloads | Fetch the files you choose to install | Only what you queue |
| Git hosts (GitHub / GitLab / Bitbucket) | Fetch release notes and clone gem source | Only for gems you inspect or download |
Everything above happens because you asked for it — opening the Engine Downloads page, adding a repository, or starting a download. Remove a source and OPAL stops talking to it.
Local data
OPAL stores its configuration and caches locally on your machine (settings, the O3DE manifest it reads, and its cache of indexed gem repositories so you can browse offline). This data stays on your device.
Your rights
Because OPAL collects no personal data, there is nothing for us to delete, export, or correct on your behalf. If you believe a bug caused OPAL to transmit something it shouldn’t, contact us and we’ll address it.
Changes to this policy
Material changes will be noted in the Changelog once OPAL is publicly released.