Operator and scope
The business card identifies the operator when setup is complete. This notice covers the EnderBase website, accounts and license service. Your Minecraft server runs on your computer; this website does not host its worlds, console logs or player list.
Data and purposes
| Information | Purpose and source |
|---|---|
| Verified email, account ID, password authentication records and session tokens | Supabase signs you in, confirms your email and handles account recovery. Passwords are handled by Supabase Auth, not stored in the EnderBase license database. |
| Google or Discord account ID and provider profile metadata | Only when you choose that provider. Supabase may receive a name, avatar and email from the provider. The license service uses the verified account ID and email; it does not create a separate name or avatar profile. |
| License hash, key hint, encrypted recoverable key, tier, status, account assignment and timestamps | Issue and verify access, enforce device limits and deliver your own key downloads. Full keys are kept out of public lists. |
| Device identifier, optional device label and activation timestamps | Bind signed activation to a device and let you manage slots. Identifiers are pseudonymous; they are not treated as anonymous. |
| Discord ID linked to your account and current license tier | Only after a separate community-role choice. A configured bot can look up the highest active public tier; it does not receive the license key. |
| Request email, category, message, optional refund order reference and receipt of this notice | Answer support, refund, accessibility and privacy requests. Please omit passwords, full license keys, payment cards and unrelated sensitive details. |
| Terms version, verified account ID and acceptance time | Record the agreement requested for a customer account without collecting a birth date or an extra email copy. |
| Request IP/network metadata and short-lived hashed rate-limit buckets; owner audit events | Hosting, security, abuse prevention and an accountable record of owner actions. The application rate limit stores a hash derived from IP and minute, not a raw IP column. |
Payments and marketing
The store uses Stripe to process payments and subscriptions. Stripe receives payment information directly; EnderBase does not store full card numbers or security codes. We keep the verified account ID and email, Stripe customer and order references, subscription IDs, payment references, paid access dates and license delivery records needed to fulfill purchases, provide support, resolve disputes and meet applicable recordkeeping obligations. Sandbox checkout does not take real payments. Stripe handles payment data under its own privacy notice at stripe.com/privacy. This application has no mailing-list signup, advertising pixel, behavioral analytics or sale of personal data. Submitting a form does not subscribe you to marketing.
Service providers and transfers
OpenAI Sites and its hosting infrastructure, including Cloudflare database and file storage, serve the website and license records. Supabase provides authentication. Google or Discord handles a provider sign-in only when chosen and enabled. The community bot processes a linked Discord ID and tier when it is configured and you opt in. Providers may operate outside your country and maintain their own security logs. The operator must confirm provider contracts, regions and any required international transfer safeguards before offering the service internationally.
The desktop launcher can request server releases and content directly from Minecraft/server projects, Modrinth and, when you supply an approved API key, CurseForge. Those services receive the requests you choose to make and apply their own notices. Their project images are not embedded in this website.
Storage and retention
Sign-in uses necessary browser storage described in the cookie and storage policy. You can sign out on the current browser. Rate-limit rows expire after two minutes and are removed when later rate-limited requests run. Discord role links are removed from the license database when you disconnect them.
Open requests are kept while being handled. Resolved request records are eligible for automatic deletion 90 days after resolution, on a later owner inbox visit. Account, license, acceptance and audit records currently require owner review for deletion; no blanket automated retention schedule is claimed. The operator must establish ongoing deletion, backup and financial retention procedures before launch. A necessary legal or security record may need to be retained after a deletion request.
Your choices and rights
Use the privacy request form or the published support email to request access, a portable copy, correction or deletion, or to appeal a decision. No new account is required. We may need proportionate verification before disclosing or changing account data. Do not send identity documents or payment-card data unless a justified secure verification method has been arranged.
Rights depend on applicable law. Where the Texas Data Privacy and Security Act applies, requests generally require a response within 45 days; a permitted extension must be explained. Appeals must be handled within the applicable legal period, and a denial must explain how to contact the Texas Attorney General. We do not charge or disadvantage you merely for exercising a protected right. No targeted advertising, data sale or consequential automated profiling is configured.
Children
Customer accounts and purchases are intended for adults aged 18 or older. A parent or guardian can manage an account and supervise launcher use. Do not submit personal information about a child under 13. If you believe it was collected, contact the operator to arrange removal. An age statement alone is not a substitute for evaluating child-directed design or obtaining parental consent where required; the prelaunch child-audience review remains outstanding.
Security and changes
Customer key downloads are checked against a verified account, keys stored for recovery are encrypted, and owner endpoints require owner authorization. No system can promise perfect security. Material changes will receive a new policy date and, where appropriate, an account notice before a new use of data. Contact the operator with concerns.