Privacy policy
What this preview does now, and what must be disclosed when accounts and billing launch.
Draft for launch · Updated September 7, 2026. No payments or accounts are active in this preview.
Current preview
The hosted site supports Discord sign-in; the local preview does not. Checkout remains disabled. There are no payment forms, analytics, or marketing pixels. The plan selector operates in browser memory and does not submit your selections. No purchase or customer record is created. The site requests font files from Google Fonts; Google receives the request information needed to serve them, including your IP address. A local or future hosting server may also process ordinary connection logs.
Future account and payment data
When enabled, membership services are expected to use an email address, a payment-provider customer reference, membership status, purchase and expiry dates, and an authorized Discord user ID. Card details should be collected directly by the chosen payment provider. The actual providers, data categories, and purposes must be confirmed and this notice updated before collection starts.
Account security and app connection records
When you sign in on the hosted site, successful Discord sign-ins, verified purchases, membership expiry, license-key issuance and revocation, and administration actions are recorded for access management and support. The connected app service reports authenticated connection check-ins and last-seen time to authorized administrators. A connection does not establish that you are playing. These records do not include screenshots, keystrokes, private Discord messages, or a list of running programs. The final retention period will be published before activation.
Discord access
The planned connection will use Discord authorization to identify the account receiving membership access. The service will associate its Discord user ID with verified paid entitlement. This does not authorize collection of unrelated messages, contacts, or server activity. The requested permissions must be shown when linking.
Use, sharing, and security
Membership information will be used to deliver access, reconcile payments, assist with support, and protect accounts. Only the service providers needed for those functions should receive it. Secrets and payment credentials must remain server-side. Final disclosures must identify the operator, providers, legal bases where applicable, and any international transfers.
Retention and your choices
A retention schedule must be established before launch, covering active accounts, payment records required by law, support correspondence, and security logs. Depending on your location, you may have rights to access, correct, erase, restrict, or obtain a copy of your data and complain to a data protection authority. The privacy contact will be added before personal data is collected.
Cookies and local storage
This implementation does not set advertising cookies or store your plan choice in local storage. Future authentication or billing features may require essential cookies. Any optional tracking and applicable consent controls must be disclosed before activation.
Children and updates
This preview is not intended to collect information from children. Age eligibility and any parental consent requirements must be finalized for the offered product before registration opens. Material privacy changes will be reflected here with an updated date.