Privacy

This page describes what therelevanceindex.com actually does with information. It is a static site generated in this repository and published on Netlify.

Accounts and cookies

There is no account system and no advertising network. The repository never writes a cookie: nothing in the code assigns document.cookie. Pages load PostHog. It counts visits, and whether someone arrived from an AI tool such as ChatGPT. It is set not to store cookies. What it holds is kept in memory for that visit only, so the site does not need a cookie banner. It may collect the page address, the referring site, campaign parameters such as utm_source, a rough location from the IP address, and basic browser details. That data is processed in PostHog's US cloud. On the homepage it also records two events, Data Story Play and Brand Submitted. Brand Submitted includes the brand name that was typed. It does not include the optional email address from the form. Questions about this go to hello@mikelitman.me.

What stays in the browser

The homepage reads a localStorage key, ml-theme, and uses it when choosing a light or dark appearance. If the key is absent, the page follows the system preference. The Submit a Brand form writes another localStorage key, ri-brand-submissions. Each entry holds the brand name, an optional category, an optional email address and a timestamp. That record stays on the device. The page does not upload it to a server run for The Relevance Index.

Email you type in

The digest form on the homepage posts your email address to Buttondown, at buttondown.com/api/emails/embed-subscribe/therelevanceindex, and opens the result in a new tab. Buttondown stores the address and sends the digest twice a month, on the 1st and 15th. This site does not keep its own copy of newsletter sign-ups. The publishing workflow sends the digest through Buttondown's API on that schedule. The contact address hello@mikelitman.me is ordinary email. Mail sent there is read by Mike Litman. This page does not describe a retention period, because the repository does not set one.

Other requests the browser makes

Pages load typefaces from Google Fonts. Pages that draw charts load Chart.js from jsDelivr. Those hosts receive the ordinary technical data of a request, including an IP address. The embeddable badge, embed.js, fetches the public scores file and keeps it in memory on the page that embedded it. It does not set a cookie.

Scores are not a visitor log

The published scores are built from Wikipedia pageviews, Reddit activity, an AI reading of culture, and, for 260 listed brands, market data. They are not a record of who visited this site. Netlify serves the files. Like any host, it can see request logs, including IP addresses. The repository does not configure a custom log-retention period.

To ask about this page, or about an email you sent, write to hello@mikelitman.me.