RoyaleTools legal
Privacy Policy
How RoyaleTools handles Player Tags, local storage, cookies, analytics, search tools, and third-party services.
Last updated: July 1, 2026
Who operates RoyaleTools
RoyaleTools is operated by RekonMedia. RoyaleTools is a fan-made companion for Clash Royale players and is not endorsed by Supercell.
This policy explains what we collect, why we use it, and the choices visitors have before using Google Analytics.
Information visitors provide
Visitors can enter Clash Royale Player Tags to look up public game data, compare decks, calculate progression, and build Clan Wars decks. Player Tags are sent to RoyaleTools server routes so the browser does not call the official Clash Royale API directly.
Visitors may contact us through email, Twitter / X, Discord, or Tally forms. Those services may receive the information you choose to send, such as a message, social handle, email address, or profile listing request.
Game data and public profile data
RoyaleTools uses public Clash Royale account and deck information returned through our server-side relay and the official Clash Royale API. We use that data to render the requested tool result and product-friendly error states.
Public creator and pro profile pages may show social links, display names, badges, public Player Tags, and profile images. Published guides, community resources, public profiles, Meta Decks, vote totals, usage snapshots, and hashed voter keys can be stored in Supabase and shown or used by the site.
Some public guide or resource images may be hosted with image hosting providers such as ImgBB before they appear on RoyaleTools.
Storage and cookies
Essential storage keeps the site working. This includes the cookie consent choice, Saved Tag localStorage, security or rate-limit data, and storage needed for core tools.
Cookie settings also include optional analytics, preferences, and marketing/ad measurement categories. Preferences can cover optional language or display choices when those controls are used.
The Saved Tag feature stores one normalized Player Tag in your browser localStorage. It is optional, stays on your device, and can be removed from the Save Tag control.
Meta Deck voting uses an anonymous royale_meta_voter cookie to avoid duplicate votes and keep vote state consistent. Google Translate can set googtrans cookies after you open and use the language picker.
Analytics and consent
Google Analytics is optional. RoyaleTools loads the Google tag with analytics storage denied by default, then grants analytics only after you accept analytics cookies in the cookie banner or settings panel.
When enabled, analytics is limited to sanitized page views. We do not send Player Tags, deck lists, saved tag values, vote identifiers, email addresses, or raw query strings to Google Analytics.
If analytics is rejected or later turned off, RoyaleTools disables Google Analytics tracking and tries to remove first-party Google Analytics cookies from the browser.
You can accept all optional categories, reject them, or save a custom choice from Cookie settings in the footer.
Search and indexing tools
RoyaleTools uses Google Search Console, Bing Webmaster Tools, and IndexNow to verify site ownership, understand search visibility, submit sitemaps, and notify search engines about public URLs.
These tools help search engines crawl public pages. They are not used to store private tool results or to send Player Tags entered into forms.
Service providers
RoyaleTools runs on a Next.js and Vercel stack. It uses Supabase for public content and product data, Redis-compatible rate limiting for abuse protection, a private VPS relay for Clash Royale API requests, Google Analytics after consent, Google Translate after visitor action, Tally for forms, Discord for community links, Twitter / X for contact links, ImgBB or similar image hosting for public guide assets, and email for support.
These providers may process technical data such as IP address, browser details, request paths, timestamps, device information, and messages you submit to them. Their own policies also apply when you use their services.
Security and retention
We use server-side API boundaries, private secrets, rate limiting, and product-friendly error handling to protect the service and reduce abuse.
We keep operational data only as long as needed for security, reliability, analytics, support, publishing, or legal reasons. Browser localStorage remains on your device until you clear it or use the available controls.
Your choices
You can use RoyaleTools without accepting optional cookies. You can clear localStorage and cookies in your browser, remove your Saved Tag from the site controls, or avoid submitting contact forms.
You can contact us to ask privacy questions or request review, correction, or removal of information you submitted through RoyaleTools contact, guide, resource, or profile listing channels.
Changes
We may update this Privacy Policy when RoyaleTools changes, when providers change, or when legal requirements change. The date at the top shows the latest update.
Contact
Questions about these terms or privacy practices can be sent to [email protected].