Privacy policy

What stays in your browser

Your recent search history is stored in your browser's local storage. It is not uploaded as a history list. You can remove it with the Clear action in search or by clearing site data in your browser.

The site also keeps an anonymous voice id in local storage. It accompanies activity requests and reads of your own reaction or comment state, so the same browser remains recognisable after its session cookie expires. A visit report sent after visible reading time includes it so a first discovery can use the same anonymous profile. Reading-depth reports do not include it. The server stores a one-way hash rather than the original id and never publishes either. Clearing site data replaces the id and means earlier reactions can no longer be taken back from that browser.

Public actions, including the first visit to a token or launch new to xrp.ONL, can appear under a separately derived anon-… profile with an activity history. Previously known tokens and launches do not become new discoveries, even if they have no older discovery post. Opening the site's own pages and repeat visits do not become profile posts. If a signed-in profile has enabled publication, its name appears instead of the anonymous profile. The discovery records the profile available at that time; later visits do not replace its author. An older post with no saved author says Mystery discoverer or Mystery author. These labels do not identify anonymous profiles, and the current visitor is never assigned to an older discovery.

Opening Your anonymous profile sends the local voice id to a private lookup endpoint to find your public profile. This lookup does not create a public action or register a public profile. The public page and its birthday start with the first recorded public action. Author links on comments and in recent activity make existing anonymous profiles visible without requiring an account. Clearing site data starts a different browser identity; earlier public activity remains under its original profile.

Anonymous service data

To limit abuse and estimate unique attention, xrp.ONL may use a signed first-party session cookie, opaque actor identifiers, short-lived counters, and a coarse one-way network hash. Reactions are stored against an opaque actor key so duplicate actions can be reconciled. The application does not intentionally store raw IP addresses in its product database. No country or origin is taken from the request for any mark: a Live line says what happened, and never where it came from. The session cookie is issued once and expires within 30 days. A new session cookie does not replace the browser's local voice id or public anonymous profile. These identifiers are not derived from device GPS.

Following and bookmarks

Without a profile session, follows and bookmarks are stored in this browser. Their public target or post identifiers are sent to the service when you open the corresponding feed so it can load current content; the browser list is not saved to a profile. While signed in, these private preferences are stored against your profile identifier and are available to its signed-in browsers. They are never published as a follower list or a public feed action.

You can unfollow or remove a bookmark at any time. Clearing site data removes browser-only lists. Withdrawing a profile removes its stored follows and bookmarks. Browser-only lists and profile lists remain separate, including when you sign in or change profiles. A bookmark keeps a post reference, not a permanent copy of a comment; current moderation still applies.

Infrastructure processing

Hosting, database, cache, and upstream data providers process the technical request data needed to deliver the service. Their operational logs may include standard details such as time, requested path, browser information, and network address, subject to their own retention and security practices.

Profiles and proof sessions

A matching settled ONL burn can open a profile for the public XRPL address that sent it. xrp.ONL stores the profile identifier, linked address, public profile fields, the validated burn proof, and one-way hashes of opaque browser-session tokens. Several browsers may hold sessions for the same profile. xrp.ONL does not store a wallet key or signature and cannot transact from the linked address.

Withdrawing a profile releases its public name, unlinks its address, and revokes its browser sessions. The validated burn records and the underlying XRP Ledger transactions remain as permanent ledger history. Future recovery or transfer controls will state what proof they require and what profile data they change before the user acts.

No ad profiling

xrp.ONL does not use advertising pixels, sell personal data, or build cross-site advertising profiles. Public XRPL addresses and transaction data are already visible on the public ledger; searching them here does not make them private.

Your controls

You can clear local search history, delete site cookies, or stop using the service at any time. A profile owner can also withdraw the profile through the stated ONL burn flow, which releases the name and ends its sessions. Anonymous attention records are deliberately opaque, so it may not be possible to connect them back to a particular person.