DATA & PRIVACY

Your account information.

Launch preview: merchant contact, retention periods, and the final privacy notice must be completed before paid launch.

What the portal uses

Sign-in supplies a site-specific user identifier and email. The portal stores your member ID, subscription references and status, device names and activation records, and release/status records needed to provide account access.

Payments

When enabled, checkout and billing management use Stripe-hosted pages. This portal does not collect or store full card numbers. It stores references and verified payment events needed to decide membership access.

Device activation

The customer app uses a generated installation identifier and a protected device token. Tokens are protected with Windows DPAPI on the PC and stored as hashes by the portal. A short-lived online membership check controls customer worker access. The service stores a hash of the public network address reported by its trusted hosting edge and uses it to restrict each activation to that network. A network change requires reapproval. Unlink your PC from your account to revoke access for both products.

Gameplay

The membership APIs do not upload gameplay frames. The portal is separate from local capture processing and does not need footage to verify a subscription.

Before launch

A public support contact and final data retention/deletion process must be provided by the merchant. Paid checkout remains disabled while launch configuration is incomplete.