Official legal center

Privacy, support and safe play center

Here we explain Taverna Royale's account, online match, chat safety, purchase verification, account deletion, security disclosure and support processes in one place. The primary legal domain is tavernaroyale.com; tavernaroyale.app is reserved for app promotion and tavernaroyale.io for technical/future routing.

Read the privacy policy Service status Terms of service Account deletion path About Impressum

13+ target audienceNot positioned as a children's product; age rating is set separately in the store forms.

Account and guest flowGuest/local use is kept clearly separate from the Firebase Auth-based live account flow.

UGC safetyReporting, blocking, filtering and a moderation record plan are maintained for chat and player messages.

Official emailssupport, privacy, legal, dpo, deletion, billing, security, press and noreply channels are kept separate.

What is this center for?

Showing players clearly which data is used for which feature.
Unifying the support, account deletion, report/block and purchase/refund review paths.
Keeping the public page structure required for App Store / Google Play review ready.

Official contact

Support: support@tavernaroyale.com
Privacy: privacy@tavernaroyale.com
DPO: dpo@tavernaroyale.com
Legal: legal@tavernaroyale.com
Account deletion: deletion@tavernaroyale.com
Purchases: billing@tavernaroyale.com
Security: security@tavernaroyale.com
Press: press@tavernaroyale.com

Live online features	Firebase Auth, Cloud Functions, Firestore/RTDB presence, async/live matches, ELO, friends, leaderboards, tournaments, chat moderation, and push notification flows are each managed with separate security and store disclosures.
Purchases and economy	Gold, gems, battle pass and cosmetic content are not considered store-ready until store receipt validation, pending/deferred no-grant handling, restore, and IAP production credential evidence are complete.
Community safety	Before text chat goes live, accepted terms, content filtering, reporting/blocking, rate limiting, a moderation queue, and support review records must all work together.