docs(web): make the legal pages Cracked Studios' own, not Celo Core C…

[Samuel1-ona]

…o.'s

Both of Terreno's legal pages belonged to somebody else. They were inherited from its life as a Celo/MiniPay mini app and never updated.

app/terms was cLabs, Inc. d/b/a Celo Core Co.'s Terms and Conditions: it named them as operator, described a different chain and platform, covered two games that are not ours (MiniQuiz, MiniStreak), and sent legal questions to legal@celo.org. app/privacy named Celo Core Co. as Data Controller and routed every access, erasure and complaint request to privacy@celo.org. It had also drifted internally — §3 said transactions are recorded on the Celo Network while §4 said Base.

Both rewritten as Cracked Studios' own documents, adapted from the Blokaz Terms of Use so the studio's papers agree on operator identity, governing law (Nigeria / NICArb) and contact.

What is new rather than adapted

• Terms §2 Our Games — names Blokaz, Nukko and Terreno, with Blokaz's own terms taking precedence for Blokaz.
• Terms §9 Promotions and Starter Grants — the first-land grant is live in production with nothing in the terms describing it. Says an offer is discretionary, can stop when a budget is exhausted, and that an offer described in NIM means the VALUE of land bought for you, not NIM transferred to you — the same distinction the FAQ and the campaign copy make.
• Terms §7 states plainly that anyone may buy your land at the contract's price, with no notice and no way to refuse, and that nothing guarantees earnings. §19 adds a securities disclaimer.
• Privacy §4 and §11 say land ownership, prices paid and received and any on-chain display name are public and cannot be erased by us or anyone. The inherited text mentioned wallet addresses and transactions only.

Written from the code, not assumed

• Terms §7/§8 numbers were read off the deployed world contract on 2026-09-08: feeRate() 500 bps, initialPrice() 30000, minPrice() 1, HALVING_TIME() 2592000s. The inherited text had drifted — it claimed Terreno accepts "USDT, USDC and USDm" when getAcceptedTokens() returns USDC only.
• Privacy §6's "no cookies or tracking storage" was re-verified against posthog-provider.tsx: persistence 'memory', autocapture false, disable_session_recording true. It now also admits per-device preference storage exists and is not tracking.
• Privacy §7 said sub-processors were "listed below" and listed none; it now describes the categories actually wired in the codebase.
• Contact is support@crackedstudios.xyz throughout. The domain was checked, not assumed: MX resolves to mx1/mx2.privateemail.com.
• Fixed a dead cross-reference — terms §9 pointed grant abuse at §15 (Disclaimer), which grants no enforcement power; it now points at §11 and §17.

What this does NOT do

No lawyer has read either page. Three questions are recorded in docs/DEPLOYMENT.md rather than settled quietly: the minimum age (18 in both pages, 13 in the Blokaz terms), the registered legal name ("Cracked Studios" here, matching the support domain, against "Cracked Studio" in the Blokaz terms and crackedstudio on GitHub), and the absence of an Art. 27 GDPR representative for a Nigeria-established controller serving the EEA/UK.

Verification: lint clean, tsc --noEmit clean, 1018 tests pass. Content only.

Claude-Session: https://claude.ai/code/session_01Pa7dcWrqWwkwZE2mZWSG1P

The hole, and the fix

What this does NOT do / residual risk

Judgement calls

Issues

Closes #
Refs #

Stacking / conflicts

Verification evidence

Remaining ops steps

• none

Checklist

• Title is the commit message I want on main
• Ships the test that fails on pre-fix code; fixtures are real captured data; fakes honour their arguments
• Covers the seam, not only pure functions; any stated guarantee tested on its failure path
• Error responses audited for what they leak; reads on write paths bounded at the query
• Judgement calls / bundled product changes flagged above (or "none")
• lint / typecheck / test pass locally on the current head
• Re-read acceptance criteria of every Closes issue — all met
• Development sidebar links match Closes/Refs above
• README / runbook / .env.example / examples / error strings updated for the world this creates
• Lockfile touched → rebased on current main, lockfile regenerated (never hand-resolved)
• Wallet/provider tree touched → loaded in a normal browser, not only Nimiq Pay
• Money/security path → money-path-checklist.md run; payout logic compared against the other side
• No secrets in the diff
• Questions for the maintainer marked clearly at the end (or "none")

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
terreno-web	Ready	Preview	Sep 8, 2026 4:45pm UTC