Trust infrastructure
Privacy
A platform that asks you to trust its sourcing should not quietly track you. This page states what ZIX collects, and the answer is very close to nothing.
What is collected
Cookies
None for readersReading ZIX sets no cookies, so there is no consent banner. The one exception is the staff article editor: signing in there sets a single session cookie, sent only to the editor's own service, which ends when the editor signs out or closes the browser.
Analytics
NoneNo analytics, tag manager, pixel, session recorder or A/B testing tool runs on this site.
Third-party requests
NoneYour browser contacts only this domain. Fonts and images are served from here, not from Google or a CDN. The World Bank and IMF series are fetched when the site is built rather than when you read it. The commodity price ticker refreshes about once a minute, but it asks this server, which asks the price feed on its behalf — so the feed sees this server and never your IP address or browser.
Browser storage
One item, only if you use itChoosing light or dark mode stores a single value named zix-theme in your browser. It never leaves your device and is not sent to any server. Setting the theme back to “Match system” removes it.
Accounts
NoneThere is no sign-in for readers.
Newsletter
Not openThe newsletter is not open yet, and no email addresses are being collected.
What the server sees
Like any website, ZIX is served by a host that keeps standard request logs. Those logs contain your IP address, the page you asked for, the time, and your browser’s user-agent string. They exist so the site can be operated and abuse investigated. They are not used to build a profile of you and are not sold or shared.
One consequence worth stating plainly: the search box submits your query as part of the web address, so what you search for appears in those server logs. Nothing else on the site sends anything you type anywhere.
Verify this yourself
You do not have to take this page’s word for it. Open your browser’s developer tools, look at the Network tab, and reload any page on this site. Every request should go to this domain and no other — including the price refresh you will see about once a minute on pages carrying the ticker, which goes to /api/prices.php here rather than to the feed itself. Check the Application tab for cookies; there should be none.
A privacy claim you can check in thirty seconds is worth more than one you have to believe, which is the same principle the rest of the platform applies to its figures.
If this changes
Some planned features cannot work without collecting something. Paid briefings will need billing details handled by a payment processor. When any of that ships, this page will say so before it launches, naming the processor and what it receives.
Questions about this page go to contact.