Cookie Policy

A cookie is a small piece of data a website asks your browser to store and send back on later visits, usually so the site can recognize you or remember a preference. This website’s pages set none. Nothing here writes a cookie, and there’s nothing for you to accept, block, or manage as a result.

No cookies, no localStorage, no sessionStorage. The site keeps nothing in your browser between visits, and nothing about you carries from one page to the next.

The clearest example is the dark/light theme switch in the header. Toggling it changes the page immediately, but the choice isn’t saved anywhere. That’s deliberate, not an oversight. Doing it properly means reading the saved preference back before the page paints, so the wrong theme never flashes on screen — and that part isn’t built yet. Until it is, the toggle resets to the default every time you load a page, the same as everything else about your visit.

This site uses Vercel Analytics (opens in a new tab) to count page views in aggregate: how many people visited a page, not who any of them were. It sets no cookie and writes nothing to your browser’s storage.

To count unique visitors without a persistent identifier, Vercel computes a hash from each request and keeps it valid for one calendar day before discarding it and starting over, so visits can’t be linked across days or across different sites. We don’t receive raw IP addresses or any other personal identifier from it — only aggregate counts and general figures like page, referrer, and rough location and device type.

This site is hosted on Vercel, and like any web host, Vercel necessarily sees the ordinary metadata of every request that reaches it: your IP address, the page you asked for, and your browser’s user agent. That’s true of any website you visit and isn’t specific to anything this site adds.

One page makes a request to a third party beyond that: the embed builder in the docs. If you type a complete custom Discord emoji reference into one of its button fields, your browser fetches that emoji’s image directly from Discord’s own CDN (cdn.discordapp.com) so the preview can show it. That request tells Discord your IP address and browser user agent, the same as any image request to any site would. It only happens if you type a full emoji code yourself — it never fires just from loading the page or from a partial entry.

This is a finding, not an excuse: no United States law requires a cookie-consent banner, this site sets no cookies for a banner to disclose, and its one analytics script is cookieless by design. Put together, there’s nothing here for a consent banner to actually do.

To be plain about what that reasoning does and doesn’t cover: it’s scoped to United States law, because that’s this operator’s home jurisdiction. It isn’t a claim that this approach satisfies EU or UK cookie-consent rules for a visitor there — that question wasn’t the basis for this decision, and we’re not asserting an answer to it here.

If this site ever added a cookie, or an analytics or tracking script that isn’t cookieless the way Vercel Analytics is, this page gets rewritten to say so before that change ships, and a consent mechanism would need to be added at the same time, not after. Nothing on this site works that way today.

This page covers the website you’re reading. For what the bot stores about you and how to have it deleted, see Privacy. For the terms that apply to using Righteous, see Terms. Questions about any of it go to the support server — or, for anything formal, righteouscord@gmail.com.