Legal
Privacy policy
Effective date: 2026-06-06
1. Data we collect
Gamibase website flows may collect account identity, contact details, support context, and commercial onboarding metadata needed to provide access, respond to requests, and reconcile entitlements.
2. How we use it
We use this data to authenticate users, operate pricing and onboarding flows, respond to support requests, and maintain entitlement and audit records for commercial access.
3. Product data boundary
Gamibase is built around local-first operation. Website account data and commercial metadata are separate from local project source files and Unreal assets processed by the runtime on your machine.
4. Product telemetry
Gamibase product telemetry (the CLI, MCP runtime, and UE Bridge plugin) is default-on but spooled only to a local file on your machine. The data plane is currently dormant and in beta: the producer performs no automatic upload and nothing is transmitted off your machine unless you explicitly run 'gamibase telemetry upload'. We do not collect telemetry from this website beyond the website and account data described above.
5. What product telemetry would collect
If you choose to upload, telemetry is limited to k-anonymized build, crash, toolchain, and Unreal Engine compatibility aggregates. It carries no raw project source, no asset contents, and no personal data: identifiers are stripped and only aggregate dimension keys and counts are exported, per the telemetry scrub contract. The purpose is to diagnose build and compatibility failures and improve product reliability. We rely on legitimate interest as the lawful basis for product-reliability telemetry, pending the legal sign-off recorded in our consent source-of-truth; this section is that web-facing source-of-truth and is kept consistent with the in-product opt-out and the service-side scrub policy.
6. Opting out of product telemetry
Product telemetry is controlled in-product, not on this website. Run the 'gamibase telemetry' command to view status and opt out from the CLI and MCP runtime, and use the telemetry control in Unreal Engine Project Settings to opt out of the UE Bridge plugin. Because nothing leaves your machine without an explicit 'gamibase telemetry upload', opting out before uploading guarantees no product telemetry is ever transmitted.
7. Sharing and processors
We may use infrastructure and billing processors to run website login, account management, and commercial activation flows. We do not publish customer secrets in source control or expose deployment credentials in public artifacts.
8. Retention and requests
We retain only the information needed for account operation, entitlement support, and required business records. Contact us if you need help with account or data requests.
9. Contact
Questions about privacy or data handling can be sent through the Gamibase contact page.
Need Team onboarding help? Visit /team-request.