The app store wrote the terms of sale for you. The moment you sell on the web, the sale is between you and the player, and two pages have to exist before the first purchase: terms (of sale) and privacy. Appside's Studio won't publish a store without links to both. This is what they need to contain, with the structure we used for our own demo game's pages. It isn't legal advice; the markets you sell in each have their own rules, and a lawyer should read the final text.
Terms of sale: the sections
| Section | What it must say | Why |
|---|---|---|
| Who is selling | Your legal entity, address, contact | Required almost everywhere; players need to know who took the money |
| What is sold | Virtual currency and items for use in the game; a licence to use them, not ownership | Sets up the refund and termination rules |
| No cash value | Virtual currency has no monetary value, can't be exchanged for money, isn't transferable | The sentence that keeps a wallet from being a financial product |
| Price and tax | Prices shown in the store, currency, whether tax is included (pricing) | Must match what the checkout shows |
| Delivery | Credited to the player's game account after payment, normally within minutes; what to do if it isn't | The webhook grants; say what the player should expect and the order ID to quote |
| Refunds | Your policy, in the sentences support will quote (refunds); the immediate-delivery consent for the EU and UK (below) | Avoids every argument |
| Account and termination | Purchases are tied to the game account; what happens on closure or ban | The hard case; say it before it happens |
| Changes to the game | Items may change with updates; no guarantee of permanence | Live games change |
| Governing law and disputes | Your jurisdiction; any consumer protections that override it | Standard, and required |
| Last updated | A date | Players and regulators read it |
Privacy: what the store actually sees
Keep it specific to the store; a generic privacy policy that doesn't mention web purchases is the common gap.
- What the store receives: the player identifier your backend signs into the token (how), optional targeting attributes (level, spender tier, country, new player), the order, and the checkout data handled on the payment side.
- Who processes payments: name the payment processor; the card details go to it, not to you or the store.
- What you keep: the order table (order ID, player ID, pack, price, dates) for delivery, support, refunds, tax and accounting; how long.
- Cookies and analytics on the store page: whatever you add; the store itself needs a session.
- Rights and contact: access, deletion, the address to write to; the EU/UK and California wording where you sell there.
Regional points to raise with your lawyer
- EU and UK: withdrawal rights for digital content. The 14-day right can be waived for digital content supplied immediately when the consumer expressly consents to immediate delivery and acknowledges losing the right (Consumer Rights Directive, Art. 16(m); the UK has its equivalent). The consent needs to be in the flow and the terms.
- Displayed prices: tax-inclusive in the EU and UK, exclusive in most of the US; match the convention (pricing).
- California and other US states: specific privacy disclosures where you have users there.
- Minors: your game's age rating and what that means for purchases.
- Tax identity: who the seller of record is; on Appside it's you (tax guide).
A working example
Our demo game, Starward, has a demo store on Appside with its own terms and privacy pages. They show the structure above for a demo game; the point of linking them is the shape, not the jurisdiction. Write yours for your entity and your markets.
Before you publish
- Both pages exist on a URL you control, dated.
- The refund rule in the terms matches the one support quotes and the Studio's refund practice.
- The price convention in the terms matches the checkout.
- The privacy page names the payment processor and what you keep.
- A lawyer in your main market has read both.
Then the Studio's publish checks pass, and the store goes live with the same two links in its footer.
Create your store free. No card needed; the legal links are required to publish, and now you know why.