1. Be the seller you describe
You must control the advertised server and have permission to sell every listed entitlement, use every image and publish the supplied contact information. Give accurate seller identity, business address and support details wherever required. Do not impersonate another server, claim unverified approval or describe a test environment as a live trading service.
You contract directly with the buyer for player packages. You are responsible for the product description, price and tax disclosure, supply, complaints, refunds and applicable consumer obligations. RealmCart is software infrastructure, not a merchant-of-record or tax-remittance service for your sales.
2. Payment accounts and costs
Complete the payment provider’s onboarding, verification and contractual requirements using truthful information. Enable sales only where the provider and platform confirm the necessary capabilities. Never process a payment for an undisclosed third party or use a personal payout email as proof of an approved merchant connection.
Managed sales use the platform fee applicable at checkout: 4% on Launch, or 3% on Grow and Network, before separate processing costs and taxes. Keep your own accounting records and meet registration, invoicing and tax obligations. Provider balances, reserves, chargebacks and payout schedules remain subject to the relevant provider relationship; a sales total is not a withdrawal balance.
3. Packages and Minecraft delivery
Describe exactly what the buyer receives, its duration, any expiry or reset conditions, required edition/version, server address and compatibility limitations. Supply a reasonable delivery expectation and explain whether the player must be online. Do not promise a rank, feature or server availability you cannot maintain.
Test commands and permissions on a compatible server before publication. Keep server backups and protect plugin credentials. You authorise the configured server to execute your package commands after verified payment; you remain responsible for their safety and effect. Investigate failed, duplicated or disputed delivery and provide any remedy due.
4. Game rules and customer data
Follow the current Minecraft EULA and Usage Guidelines, including server monetisation rules. Do not sell gameplay advantages or other entitlements that those rules prohibit; a cosmetic label does not make an advantage compliant. Do not sell prohibited cape imitations or cash-out virtual currencies. RealmCart does not certify a package’s compliance.
Provide the customer information, purchase history and privacy protections required for your activities. Use player identifiers and order details only for a lawful purpose, restrict staff access and disclose any server-side processing. Address data requests and incidents affecting your customers. Minecraft is not affiliated with or endorsing RealmCart.
5. Processing player information for your store
For personal data processed on your documented store instructions, you are the controller and Snoxium Games LTD is your processor. The processing lasts while the store service is provided, and afterward only as necessary to return or delete the data, resolve outstanding instructions or comply with law. It covers receiving and storing order records, payment-status reconciliation, delivery instructions and support investigation. Data subjects are your players, buyers and authorised staff; data includes supplied Minecraft usernames, package and order details, payment references and delivery results. Full card details are handled by the payment provider.
We process that information only to provide the agreed service and on your documented instructions, including settings and authorised support requests, unless law requires otherwise. We will tell you if an instruction appears to infringe applicable data-protection law. You must have a lawful basis for the data you submit and provide required notices; these terms do not authorise unrelated marketing.
We restrict access to authorised people under confidentiality obligations and apply appropriate technical and organisational safeguards, including access controls, encrypted provider credentials, protected connections and account-security controls. We will notify you without undue delay after becoming aware of a personal-data breach affecting data processed for your store, with available information to help you meet your duties.
You authorise Cloudflare as a hosting and database subprocessor for the hosted service. We require appropriate written data-protection obligations of subprocessors and remain responsible for their processing under this agreement. Before adding or replacing a subprocessor for your store data, we will notify you and give a reasonable opportunity to object on data-protection grounds. We will work with you on a reasonable solution or termination of the affected service if an objection cannot be resolved.
We will reasonably assist with data-subject requests, incident response, security obligations and any necessary impact assessment or regulator consultation, taking account of the processing and information available to us. On request we will provide information needed to demonstrate compliance and allow proportionate audits, subject to confidentiality and safeguards for other customers.
When the affected service ends, we will return or delete personal data on your written choice, and delete existing copies unless law requires retention; protected backups may be isolated until their normal replacement cycle. Transfers outside the UK or other relevant jurisdiction must use safeguards required by applicable law. These obligations apply to processor activities; the privacy notice separately describes the operator’s own account, security and billing records.