GUIDE / LEGAL PAGES

Terms and privacy for your web store: the checklist

A game web store needs terms of sale and a privacy page before it can take money. What each must cover for digital goods (what the player buys, delivery, refunds, virtual currency has no cash value, account termination, governing law), what the privacy page must say about the data the store sees, regional points (EU and UK withdrawal rights for digital content, California), and a working example from Appside's demo game. Not legal advice.

Updated

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.

Regional points to raise with your lawyer

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

  1. Both pages exist on a URL you control, dated.
  2. The refund rule in the terms matches the one support quotes and the Studio's refund practice.
  3. The price convention in the terms matches the checkout.
  4. The privacy page names the payment processor and what you keep.
  5. 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.

Frequently asked questions

Do I need separate terms for the web store?

You need terms that cover the web purchase: what's sold, how it's delivered, the refund rule, and that virtual currency has no cash value. If your existing game terms already cover purchases outside the app store, link them; most don't, because the app store's terms covered the sale until now.

Why does Appside require legal links to publish?

Because a store taking money without terms and a privacy page is a problem for the player, the publisher and the payment side. The Studio's publish checks look for both links; the pages are yours to write.

What about the EU 14-day withdrawal right?

For digital content delivered immediately, EU and UK rules allow the right of withdrawal to be waived when the consumer expressly consents to immediate delivery and acknowledges losing the right. Your checkout flow and terms need that consent; a lawyer in your market should confirm the wording.

Does the store collect personal data?

The store sees the player ID your backend puts in the token, the order, and the payment details handled on the payment side. Your privacy page should say what the store receives, what your backend keeps (the order table), and who the payment processor is.

Can I copy Appside''s demo game pages?

They're published as a working example of the structure for our demo game, not as a template for your jurisdiction. Use the structure; have the content reviewed.

Sources

Related

SEE IT YOURSELF

Build your store
before the first call.

Try the live demo ↗Create your store
LET’S TALK

Book a demo

Connect with Oded to arrange a walkthrough of Appside.

Contact Oded on LinkedIn ↗