Privacy

What this site collects, what it does not, and who touches it. Short version: no accounts, no ads, no cross-site tracking, no cookies, one cookieless traffic counter, and nothing sold to anyone. Effective September 5, 2026, corrected September 8, 2026, updated October 9, 2026.

Who is responsible

The XRP Macro Intelligence Desk is built and run independently by an individual operator, GenXKrypto. There is no company behind it. For privacy questions, contact support@xrpmacro.com.

The short version

There are no user accounts, no logins, and no email signup. Nothing on this site asks for your name, email address, or any other identifying detail.

This site sets no cookies. That is why you do not see a cookie banner: there is nothing to consent to.

There are no ads, no advertising pixels, no affiliate links, no social media tracking widgets, and no cross-site tracking of any kind. There is one third-party script: Vercel Web Analytics, a cookieless traffic counter, described in full in the next section. It is the only third-party analytics on the site; the desk also keeps its own anonymous count of visits that arrive through its own tagged links, described in the same section.

No data from this site is sold, rented, or shared with anyone for marketing purposes. Ever.

Traffic measurement

The site uses Vercel Web Analytics to count visits. It is cookieless. Instead of storing an identifier on your device, it derives a temporary hash from the incoming request, and that hash is discarded after 24 hours. It does not follow you across other websites and does not build a profile of you.

What that produces for the desk is aggregate only: how many people visited, which pages they opened, the referring site, device type, browser, operating system, and a country-level location derived from network information. There is no way to look at that data and identify an individual reader, and no attempt is made to do so.

Since September 15, 2026, the same tool also counts a few anonymous interactions, so the desk can see which parts of the site are actually used: opening a dashboard tile (which gauge), opening a source link (the outlet's domain only, such as reuters.com), using the Copy link or Share on X buttons, turning brief alerts on or off, and installing or opening the site as an installed app (with a coarse device type: iOS, Android, or other). These counts carry no identifier and nothing you type, use the same cookieless method as page visits, and are only ever seen in aggregate.

Since October 9, 2026, the desk also counts visits that arrive through its own tagged links, the ones it posts with labels such as utm_source=x in the address, so it can tell which of its posts actually send readers here. Only those tagged arrivals are counted; an ordinary visit records nothing. Each one is counted as a Vercel interaction as above and stored as a single row in the desk's database holding the time, the link's labels, the page type you landed on, and the same coarse device type (iOS, Android, or other). No identifier, address, or anything you type is stored. To stop a page refresh from counting twice, your browser keeps a small note in session storage, which is not a cookie and is cleared when you close the tab. The public site can add these rows but cannot read them back.

Vercel also keeps standard server request logs, the same kind every web host keeps, as part of operating the infrastructure. Those belong to Vercel, are not used by the desk for analysis, and are not published anywhere.

Brief alerts

Brief alerts are entirely optional and off by default. If you install the site as an app and turn them on, your browser generates a push subscription and sends the desk three technical values: an endpoint URL supplied by your browser vendor's push service, and two cryptographic keys used to encrypt the notification. That is all that is stored. No email address, no device name, no identity, and nothing tying the subscription to a person.

Those values are used for one purpose: sending a notification when a new brief publishes. They are never used for anything else and are never shared.

The database is configured so that the public site can add a subscription but cannot read subscriptions back, including its own. Turning the toggle off unsubscribes your device immediately, and the stored record is removed automatically the next time a notification attempt finds the endpoint dead.

Reading the site requires nothing from you

Briefs, claims, watch items, history, and sources are public and readable without identifying yourself in any way. The XRPL amendments table shown on the Watch page is fetched by the desk's server, not by your browser, so loading that page does not expose your device to the data provider.

Who processes data on the desk's behalf

Vercel hosts the site and provides the traffic measurement described above. Supabase provides the database that stores published briefs, the anonymous tagged-link counts, and, if you opt in, push subscriptions. Both are United States based infrastructure providers operating under their own privacy terms. No other third party receives anything.

If you are in the EU, UK, or a similar jurisdiction

You have rights of access, correction, deletion, and objection regarding personal data about you. In practice the desk holds almost nothing that could be linked to you: analytics data is aggregated and cannot be traced back to an individual, tagged-link counts carry no identifier, and a push subscription record contains no identifying information.

If you enabled brief alerts and want the subscription removed rather than left to expire, turn the toggle off and email support@xrpmacro.com, and it will be deleted. For anything else, ask, and you will get an honest answer about what does or does not exist.

Children

This site publishes financial and macroeconomic analysis for an adult audience. It is not directed at children, and it does not knowingly collect information from them.

Changes

If the data practices described here change, this page changes with them and the effective date at the top is updated. If the desk ever adds something material, an analytics change, a monetization feature, anything that collects more than it does today, it will be stated plainly here rather than quietly folded in.

Correction, September 8, 2026. The summary above previously said this site runs no third-party analytics scripts, which contradicted the Traffic measurement section on this same page describing Vercel Web Analytics. The wording was wrong, not the practice: Vercel Web Analytics has been in use throughout and is described here unchanged. The summary now says so directly. No data practice changed on this date, and nothing new is being collected.

Update, September 15, 2026. Anonymous interaction counts were added to the existing Vercel Web Analytics, listed in full under Traffic measurement. No new third party, no cookies, and no identifiers were added.

Update, October 9, 2026. The desk now counts visits that arrive through its own tagged links, described under Traffic measurement. Each is stored as one anonymous row in the desk's existing database. No new third party, no cookies, and no identifiers were added.