About this site

Privacy

Updated .

Text on this page was drafted with AI tools; every figure is computed by code from the cited official source.

500metrics is built to collect as little about its readers as possible. You can read every page without an account. An account is optional: it keeps the pages you save and the email alerts you set, and it needs nothing but an email address ("Saved figures, alerts and accounts" below says what it keeps). The site runs no advertising and runs three small scripts of its own to show and count its pages (one counts page views, one fills the day's figures in the page header, and one, on pages with a chart, shows the date and values of the point you choose, or the name and figure of the bar or part you choose on any other chart, lets you choose a time range or zoom, and lets you save, copy or share a picture of the chart); none of the three sets a cookie. Two more scripts of its own serve saved figures, alerts and accounts: one on every page and one on the three account pages, described below. Our fonts, styles and images are served from 500metrics.com itself. The only thing a reading page loads from another company's servers is the tag of Google Analytics, which the site uses to count visits: it loads from Google's servers, sets cookies in your browser and sends information about your visit to Google. "How we count visits" below says more. The sign-in page loads one more thing from another company: Cloudflare's bot check, described below. Apart from that tag, the bot check, the counts described on this page and what you choose to keep with an account, the site collects nothing about you.

We decide how the personal data described here is used. Write to us about anything on this page; the address is on the contact page.

What happens when you visit a page

The site runs on Cloudflare, which delivers our pages. To send a page to your browser, Cloudflare necessarily receives your IP address and the request your browser makes (the address of the page, your browser's user agent and similar technical details). Cloudflare also uses this information to protect the site from attacks and abuse. Cloudflare processes it on our behalf under its own data processing terms; its privacy policy is at https://www.cloudflare.com/privacypolicy/.

Pages that show the day's figures in their header also run a second small script, apart from the one that counts page views. It asks this site for one file, /figures.json, which is the same for every visitor, and writes the figures in it into the header. It sends nothing about you beyond the request your browser makes for any file of this site, sets no cookies and stores nothing on your device. It reads no cookie, file or storage on your device; it uses the page's own address only to tell which figure is the page you are on.

Pages with a chart run a third script, a file of this site's own, served like our stylesheet. It shows the date and the values of the point on a chart that you point at with a mouse, touch with a finger or reach with the arrow keys, and, on a chart that is not a dated line or column chart (ranked bars, a segment bar, a dial, a calendar, a small drawing), the name and the figures of the bar or part you point at. It also lets you choose a time range or zoom into a chart, and it writes the view you chose into the page's address after the # sign, so that a link you copy or share opens the same view; that part of the address stays on your device and is never sent to us. It reads the chart's numbers from the page itself, makes no request of its own other than for the second file described below, sets no cookies and stores nothing on your device. It reads no cookie, file or storage on your device, and it sends nothing about where you point. The buttons over a chart save a picture of it, copy the picture or the page's address, and open a menu of places to share the page. The picture is made on your device from the chart's own numbers, or, for a chart that is not a dated line or column chart, from the shapes and words the page draws, and nothing is uploaded by this page. The code that makes it, the two menus and the cards that show the name and figures of a bar, a part or a dial are a second file of this site's own, which your browser loads the first time you point at, touch or focus a chart that is not a dated line or column chart (ranked bars, a segment bar, a dial, a calendar, a small drawing), point at or use the camera or share button, or open a menu; it is a request for a file of this site, the same for every visitor, and nothing about you is sent beyond that request. If you choose Share, your device's own share sheet gets the picture, or the page's title and address, and the app you choose receives them. Copy puts the picture, the page's address or the credit line on your clipboard. The share links to X, Telegram, WhatsApp and Reddit carry only the page's title and address, and open only when you click one; this site makes no request to any of them before. The script sets no cookie, uses no storage and sends no beacon, and the only things it puts on your device are a picture you choose to save and what you choose to copy.

Saved figures, alerts and accounts

Every data page has a Save figure button and an Alerts button. The pages you save are listed on My figures (/my-figures), alerts are set on Alerts (/alerts), and you sign in on Account (/account). We call these three the account pages. They are not listed in search engines, and they do not carry the Google tag; our own page view count runs on them as on every page.

Without an account. Saving a figure keeps the list in your browser's storage on your device, and nothing about it is sent to us when you save. When you open My figures, the page asks the site for the latest reading of each saved page: that request carries the addresses of those pages and nothing else about you. The site keeps the latest reading of every public page it is asked about, with nothing about who asked. Alerts drafted before signing in stay in your browser. When you sign in, the pages saved in that browser are added to the account and the drafts become alerts of the account.

What your browser keeps. A reader who never saves a figure, drafts an alert, opens My figures or signs in gets none of this. These are written only when you do one of those things:

WhereNameWhat it keeps
Browser storage (kept)m5.savedthe list of pages you saved, with the time you saved each one
Browser storage (kept)m5.seenthe reading of each saved page that My figures last showed, so it can mark what changed
Browser storage (kept)m5.draftsalerts drafted before signing in (up to five)
Browser storage (until the tab is closed)m5.backthe page to return to after signing in
Cookie, set by the sitem5_sessionkeeps you signed in; it ends a hundred and eighty days after the sign-in or its last renewal, and it is renewed when you use the site with fewer than ninety days left; it contains a random token, of which the site keeps only a hash, is sent only to the account service (/api/account) and cannot be read by scripts
Cookie, set by the sitem5_intells the page's script that you are signed in; it contains no secret and lasts as long as the sign-in
Cookie, set by the sitem5_pendties a sign-in code you asked for to this browser, for up to one hour; it cannot be read by scripts

The three cookies are set only when you ask for a sign-in code or sign in, and they are needed for that. Signing out clears the sign-in cookies, and the saved list, the readings and the drafts kept in that browser.

The two scripts. One small script of the site's own runs on every page: it shows the number of saved figures and the Sign in or Account link in the page header, and the Save figure and Alerts buttons on data pages. A second runs only on the three account pages and draws them. They make no request unless you are signed in or use one of these features, every request they make goes to this site (apart from the bot check of the sign-in page, below), and a page reads the same without them.

Signing in. An account needs only an email address. You sign in with a six-digit code that the site emails to that address (the same email has a link that does the same); the first sign-in makes the account. There is no password. The code works for ten minutes; the site keeps it only as a hash and deletes it once it is used, or within a day of running out. The address entered, and the version date of the terms you ticked the box for, are kept with its code, so that the code can be checked and sent and the agreement can be recorded, and are deleted with it, also when no account is made. To limit abuse, the site counts requests for codes for each email address and each network address, requests for readings for each network address, and the changes and test emails each account asks for in an hour; it keeps these counts as salted hashes, not as the addresses or the account themselves, and deletes them within two days. It also counts the emails it sends in a day, with nothing about whom they went to. An account is for adults, 18 and over.

The bot check. The sign-in page, and only that page, loads Cloudflare Turnstile from challenges.cloudflare.com, while you are signed out. It runs Cloudflare's code in your browser to tell a person from a program, and Cloudflare receives what that check needs from your browser. Cloudflare, which already delivers the site, runs it under the privacy policy named above and the privacy addendum it publishes for Turnstile.

What an account keeps. With an account, the site keeps:

  • your email address and when the account was made;
  • the list of pages you saved, in your order, with when each was saved;
  • your alerts: the page, the kind (each new figure, above a level or below a level), the level, whether the alert is on or paused, whether its emails are off or paused for a day, the figure it last compared with, how many times and when it last went off, and when it was made and last changed;
  • the messages of your account (alerts that went off, weekly summaries, test emails and notices about your emails), for ninety days, and whether each email went out, for thirty days;
  • your sign-ins: for each, a hash of a random token, when it was made, when it was last used and when it ends; a sign-in unused for a hundred and eighty days is removed;
  • your email settings: the weekly summary on or off and whether the Account page has asked about it, all alert emails paused, or paused for a day and until when, whether your address refused mail and how many times, and when these settings last changed;
  • the counts of changes and test emails described under "Signing in", for up to two days.
  • the version date of the terms of use you agreed to, and when you agreed, which are deleted with the account.

Nothing else is kept with an account: no password, no name and no payment details. The Account page lets you download everything kept with your account as one file, and delete the account at once: deleting it removes the account and everything tied to it.

The emails. The site sends a sign-in code only to the address entered on the sign-in page, and every other email only to the address of an account. It sends only these: sign-in codes; the alerts you set, each of which is a page's own public sentence and a link, the same words for every reader who set the same alert on the same page; a weekly summary of new figures on your saved pages, only if you turn it on; and a test email when you ask for one. There is no newsletter and no promotion, and the emails carry no tracking pixel and no tracked link. Every alert and summary email has a link to stop it and a one-click unsubscribe, and an account can pause all alert emails and turn the weekly summary off. The emails are sent through Cloudflare's email sending service, which processes your address and the email on our behalf, so accounts and alerts bring in no company that did not already serve the site.

How we count visits

We count visits in two ways: with Google Analytics, and with counts of our own.

Google Analytics. Every page of the site, the pages that say a page is missing or gone included, runs a small piece of Google's code in its head. It loads Google's tag from Google's servers (www.googletagmanager.com), and the tag sets cookies in your browser and sends information about your page visit to Google, to servers that the page's security policy names: google-analytics.com, analytics.google.com and googletagmanager.com. The site does not ask for your consent before the tag runs and has no switch to turn it off. We use it to count visits. Google's privacy policy is at https://policies.google.com/privacy. The three account pages (My figures, Alerts and Account) are the one exception: they do not run Google's code or load its tag, so Google receives nothing from them.

Our own counts. We also keep our own counts of visits and page views, made from what your browser sends with every request. A small script counts each page view, sets no cookies and stores nothing on your device. It runs once the page has loaded and is shown, and it reads no cookie, file or storage on your device. It reads the page's path, the address of the page you came from without anything after "?", the three campaign tags, and one browser setting that says whether the browser is run by automation. A browser run by automation is not counted as a page view. Our code writes one line for every page a browser opens, for every request from a known search or AI crawler, and for about one in ten of the other requests. A line gives the kind of page requested, the response code and how long the response took; for a page a browser opens, and for search crawlers checked against their published addresses, it also gives the page's path. It can also contain the address of the page you came from, if your browser sends it, without anything after "?" (only the site's name for webmail and similar private services); the campaign tags of the link you clicked (utm_source, utm_medium and utm_campaign); your country; the kind of device (phone, tablet or computer); for crawlers, the crawler's category or name; and a visitor code.

The visitor code is a number of 16 bits made from your IP address, your browser's user agent, the site and the date. It changes every day and is made differently for each website, so it cannot link your visits from one day to the next or from one website to another. It lets us estimate how many different readers came in a day. If your browser sends Do Not Track or Global Privacy Control, we make no visitor code, and your page view still counts in the totals. That is true of our own counts only: the page does not check these signals before it starts the Google tag.

We never keep your IP address, the text of your browser's user agent, any cookie or anything read from your device in our own counts. Your IP address and user agent are used only while your request is answered: to make the visitor code, to tell browsers from crawlers and to see the kind of device. Cloudflare deletes these lines after about three months, and we keep nothing from them after that.

Our counts are estimates, not counts of people: some programs pass for browsers, and the number of different readers in a day is worked out from the visitor codes, not counted.

Our own counts use no cookies, local storage or pixels. Because the visitor code is made from your IP address and user agent, the same browser on the same network gets the same code for one day; the code changes every day, so nothing we keep in our own counts can recognise you from one day to the next. We do not build profiles of readers from our own counts, and we do not pass them to anyone for advertising or in exchange for money or anything else of value. For what Google does with the information its tag receives, see Google's privacy policy, linked above.

When you email us

If you write to our address, Cloudflare's email routing forwards your message to the mailbox where we read it. We use your address and message only to answer you and to deal with what you raised, for example to correct a number. We keep messages only as long as we need them for that purpose, and longer only where a message concerns a correction, a complaint or a legal matter that we must be able to show we handled. Writing to us never adds your address to any list: the site emails only an address that asked for a sign-in code or has an account, and only what was asked for (see "Saved figures, alerts and accounts").

People named in our data

The site names people only as they appear in public SEC filings: the officers, directors and ten percent owners whose purchases and sales of their company's shares are reported on Form 4, shown as filed with the role they report, and the investment managers that file Form 13F reports, under the name on their filing. The pay pages show the pay of a company's principal executive officer and name no one, and the site names no one else. We show only what the filing itself shows. If a line names you and you think it is wrong, write to us at the address on the contact page.

Where the UK or EU General Data Protection Regulation applies, we rely on our legitimate interests: to deliver and protect the site (Cloudflare's processing), to count visits so that we know which pages are read and how people find them, to answer people who write to us, and to protect the sign-in from abuse (the bot check and the counts of code requests). We have weighed these interests against your rights and kept the data to the minimum the site needs to work. For our own visit counts that means the counting stores nothing on your device, keeps no IP address, uses a visitor code that changes every day, and its lines are deleted after about three months. The Google tag is different: it sets cookies in your browser and sends information about your visit to Google (see "How we count visits").

What an account keeps, and the emails it asks for, we keep and send to provide the service you asked for when you signed in, and only for as long as the account exists or for the shorter times named above. You can stop any email from the email itself, and delete the account and everything kept with it at any time from the Account page.

Your rights

Depending on where you live, you may have the right to ask what personal data we keep about you, to have it corrected or deleted, to object to our use of it, or to limit it. Write to us at the address on the contact page and we will answer within one month. If you have an account, the Account page lets you download everything kept with it and delete it yourself, at once. Without an account, we keep so little that in most cases the answer will be that, beyond your email to us and an address entered on the sign-in page (deleted with its code, within a day), we keep nothing we can tie to you: our own visit counts keep no IP address, name or account. For what Google's tag collects, see Google's privacy policy, linked above. If you are in the UK or the EU, you may also complain to your data protection authority (in the UK, the Information Commissioner's Office, https://ico.org.uk ).

If you live in California or another US state with a privacy law, write to us at the address on the contact page about your rights. Browser signals such as Global Privacy Control and Do Not Track change only our own counts (see "How we count visits"): when your browser sends one, we make no visitor code for your visit.

Children

The site is not directed at children and we do not knowingly collect personal data from anyone under 13 (or under a higher age, up to 16, where the law of your country sets one). An account is for adults, 18 and over. If you believe a child has written to us or made an account, tell us and we will delete the message or the account.

Changes to this page

When we change how we handle personal data, we update this page and the date at the top before the change takes effect. Accounts, saved figures and email alerts were added this way: this page has described them from the day they started, and they are something you choose to use yourself. If we ever add anything else that collects more than this page describes, this page will describe it first, and you will have to choose it yourself.