Privacy

This site has no analytics, no advertising and no trackers. Nothing asks for your name or email. The only record of a visit is the web server's own request log, and the only thing stored about a person is what signing in keeps - and signing in is optional.

Who runs this

XRPLWin operates this website and is the controller of the little it processes. Questions and requests about your data: [email protected].

The ledger is public

Everything the site shows about an account, a transaction or a token is on the public Xahau ledger, where anyone can read it and nothing can be removed. The site reads it and explains it; it did not put it there and cannot take it away. If an address is yours, the ledger - not this site - is where it is public.

What is never collected

• Secret keys, seeds or recovery phrases: the site has no page that takes one and never asks.
• Your name, email or address, unless you write to us - and then only what you wrote.
• Which ledger accounts are yours. The site cannot tell; an address you look up is a public address like any other.
• Anything from analytics, advertising or tracking services: there are none.

What a visit leaves

• A request log. The web server records each request with its time, the address asked for, the response, your browser's name and your IP address, for keeping the site running and finding faults. A page's address is in it, so an account you looked up is in it too - against your IP address, not your name. Logs are kept for a limited time, then rotated away, and are not used to profile anyone.
• Rate limits. A few things are limited per IP address - the SQL console, signing in - and a counter for that lives briefly in the server's memory. That is all it is used for.
• A cache. Pages are the same for everybody and are cached in front of the server. The cache holds pages, not people.

What your browser keeps

No cookies are set unless you sign in. The site does keep a few preferences in your browser's own storage - the theme, the currency prices are shown in, which columns of a table you hid, a cache of account names it has looked up, and whether you have dismissed the notice about this. They never leave your browser and the cookies page lists them.

The node your browser talks to

Some pages read the ledger live, from your browser, over a WebSocket to a public Xahau node. That node's operator sees your IP address and the requests, as any server you connect to does. The site sends it nothing about you beyond the request itself.

Signing in

Signing in with Google or Xaman is optional. It uses OpenID Connect: the provider tells the site who you are, and the site keeps your provider, your identifier with that provider and the display name it gave - nothing else, no email, no password. A session is kept on the server for 30 days, and three cookies hold it in your browser: whs (the session), whli (a hint that you are signed in) and, for ten minutes during sign-in, whpre. Signing out ends the session and clears them. To have the record deleted, sign out and write to the address above.

Google and Xaman each see that you signed in to XRPLWin with them, under their own privacy policies, which are theirs to explain: Google's, Xaman's.

Services the server reads

To name tokens and NFTs, show their pictures and fill in prices, the server itself reads a few public services - token and NFT metadata directories, a price oracle feed, IPFS gateways. Those requests come from the server, not from your browser, and carry nothing about you.

In front of the server

The site may sit behind a content delivery network for availability and protection. A service in that position may set a short-lived, strictly necessary cookie of its own and sees requests pass through, under its own terms, not ours.

How long

The request log is rotated after a limited time. A sign-in session lasts 30 days unless you sign out; the sign-in record stays until you ask for it to go. A message you send us is kept as long as it takes to answer it. Nothing else about you is kept.

Why it is allowed

In the GDPR's words: the request log and the limits rest on our legitimate interest in keeping the site running and safe (article 6(1)(f)); the sign-in record is needed to give you what you signed in for (article 6(1)(b)). Nothing rests on consent, because nothing optional is collected.

Keeping it safe

The site is served over HTTPS only. The sign-in cookies are Secure, sent only to this site, and the session one cannot be read by scripts. The server keeps a hash of a session token, not the token. No method is perfect, which is one more reason to keep so little.

Children

The site is not aimed at children and knowingly keeps nothing about anyone under 16. If you believe it does, write to the address above and it will be removed.

Links elsewhere

Links that leave this site go to pages with their own privacy practices, which this page does not cover. The site tells you before you leave.

Your rights

Under the GDPR you may ask what the site holds about you, have it corrected or deleted, and object to its use. For a visitor who has not signed in there is nothing to hold beyond the request log; for one who has, the sign-in record above. Write to [email protected]. You may also complain to the supervisory authority of the country you live in.

Changes

If what the site keeps changes, this page changes with it; the date at the top is the date of the version you are reading.