Privacy
Short version: OPAL ships with telemetry off. We don’t collect anything unless you explicitly opt in. We never sell, share, or monetize user data.
What OPAL does not collect by default
- Your name, email, IP address, machine identifiers
- Which projects you have, what they contain, where they live
- Which engines you install, what you build
- Any content from
project.json,gem.json, or your source code
What OPAL collects when you opt in
Under Settings → Advanced → Telemetry, you can opt in to two categories:
1. Crash reports
- Stack traces from crashes and unhandled errors
- OPAL version, OS name + version, CPU architecture
- A generated install ID (not tied to you)
Never included: file paths containing user data, project or engine contents, personal identifiers.
2. Anonymous feature-use stats
- Which pages you visit in OPAL (counts, not sessions)
- Which actions you invoke (e.g. “installed engine”, “started build”)
- Time-to-first-project on first install (a UX metric)
All stats are aggregated, bucketed, and stripped of anything identifying before they leave your machine. We don’t run analytics inside OPAL — it’s a single HTTPS POST to a collector endpoint you can block via your firewall or network policy.
What OPAL must connect to, regardless of telemetry settings
| Endpoint | Purpose | Opt out? |
|---|---|---|
| O3DE release metadata | List available engine versions | No (no engines without it) |
| Configured gem repositories | Index gems | Remove the repo |
| OPAL update check | Notify you of OPAL updates | Yes — Settings → Advanced → Auto-update |
| OPAL crash reporter | Only if opted in | Yes — default off |
Data retention
- Crash reports: 90 days, then purged.
- Feature-use stats: aggregated indefinitely in anonymous bucket counts only.
- No user-identifying data is retained at any stage.
Your rights
Because we don’t collect user-identifying data, there’s nothing to delete, export, or correct. If you believe that has changed — for example, a bug causes personal data to leak into a crash report — contact us and we’ll address it.
Changes to this policy
Material changes will be announced in the Changelog and via the in-app update notification. The policy is versioned and ships with every release as PRIVACY.md inside the install directory.
Last updated: 2026-04-20.