Last updated: 2026-07-05
xrpldashboard is a public website with no accounts, no third-party trackers, no cookies for tracking, and no ad networks. We keep first-party, cookie-less visit logs (page, country, browser family, a fingerprint that rotates daily; no IP addresses stored in our own table) and publish aggregates at /analytics. The exact schema is at /methodology#analytics-bot-filter.
Plain-English summary: Cloudflare and Render see the IP that connects (needed for transport + abuse defense); we do NOT store that IP in our own table. What we do write per visit — page path, country, a browser-family label, a fingerprint that resets every UTC day — is published in aggregate at /analytics with a live bot filter. One cookie remembers your language choice. That is all. No Google Analytics, no Meta pixel, no third-party trackers, no ad networks.
When you visit any page on the site, our hosting provider (Render) and CDN (Cloudflare) automatically log standard request metadata for security, abuse prevention, and uptime monitoring:
We don't aggregate this into a user profile, sell it, or share it with marketers. These platform logs are retained only as long as our hosting provider keeps them, and we use them solely for security and operational debugging.
First-party visit log, kept by us, cookie-less.
In addition to the platform logs above, we also write ONE row per HTML page load into a first-party table called page_views. That row carries: the page path (or a normalized version — /wallet/<addr> is normalized to /wallet before being written); the country code from CF-IPCountry; a browser-family label (e.g. Chrome, Safari); a visitor fingerprint that hashes the connecting IP together with a salt that ROTATES EVERY UTC DAY (ip_day_hash), so the same visitor cannot be linked across days; a referrer host if present; a UTC timestamp; and a machine-classified is_bot flag. We do not store raw IP addresses in this table. We publish aggregate counts (page, country, browser family, bot vs human) at /analytics. The exact schema and the bot filter are documented at /methodology#analytics-bot-filter. This is what "first-party analytics" means for us: our own table, no third parties, no cookies, cannot be joined to any external database.
If you visit the language menu and pick a locale, we set a single cookie named
xrpl_lang
to remember your choice on subsequent visits. That cookie stores nothing else and isn't shared with anyone.
/wallet/<addr>
reads public ledger data and isn't tied to the IP that asked.The pasted content is not stored. When you paste a wallet address, token (SYMBOL.rIssuer), URL, or domain into the /check tool, it is processed in-request to look up on-chain signals and public TOML metadata, and the result is rendered back to you.
/check) and standard request metadata, never the query string.
Because /check is a permalink URL (?q=…), the pasted content is visible in your browser's address bar and history, and appears in standard HTTP access logs at our hosting provider (Render) and CDN (Cloudflare) alongside every other request URL. Those logs are retained by our providers for a short operational window and are used only for security and uptime, per each provider's privacy policy linked above.
Legal basis (EEA/UK visitors): legitimate interest in providing a free anti-fraud information tool (GDPR Art. 6(1)(f)). The processing is minimal (paste plus result), ephemeral (in-request), and pursues an interest — helping visitors evaluate identity claims about XRPL assets they were considering interacting with — that outweighs the minor privacy impact of temporary URL logging by the platforms above.
xrpldashboard is not directed at children under 13, and we don't knowingly collect personal information from anyone under 13. If you believe a child has provided information to us, please email us and we'll delete it.
The site is built on a few third-party providers. Each operates under its own privacy policy:
contact@xrpldashboard.com.
Sees the contents of emails we send.
Privacy.xrplcluster.com, s1.ripple.com, s2.ripple.com,
and a handful of public Ethereum RPC providers. From their side, requests appear to come from our server, not from you (except for the in-browser WebSocket subscription, which connects from your browser directly to
wss://xrplcluster.com).
See the methodology for the full list.Emails sent to contact@xrpldashboard.com are forwarded through Squarespace's email-forwarding service to a personal Gmail inbox, and replies are sent through Brevo's SMTP relay. We retain those emails so we can continue the conversation. We don't add senders to any marketing list.
Depending on where you live, you may have rights under laws like the EU GDPR or California CCPA — including the right to access, correct, or delete personal information we hold about you, and to ask us not to use it for certain purposes. Because we collect so little (no accounts, no profiles), there usually isn't much to act on, but we'll handle any request in good faith. Email us at contact@xrpldashboard.com.
If this policy changes, we'll update the "last updated" date at the top and flag material changes on the homepage for a short window. Continued use of the site after changes take effect means you accept the revised policy.
Privacy questions, deletion requests, or anything else: contact@xrpldashboard.com.