Legal
Cookies
The public site sets no cookies at all, and nothing it stores outlives the tab you close. Every piece of it is named below, one by one.
- 01
Reading stores nothing
Somebody who arrives and reads leaves nothing in their browser: not a cookie, not a value. Measured in production, walking the site: zero.
- 02
For this visit only
Two values appear in session storage the first time something is measured — when you send the form or press a subscribe button — and both are random numbers: a reader identifier and an identifier for the visit. They carry no name, email, company or country, and they disappear when the tab closes. The identifier is new on every visit, so nobody is followed from one visit to the next.
- 03
Your email does not stay in the browser
When you ask for the edition, the address travels to the server and is used to send you the document. It is not kept in the browser. It used to be, for a second form step that no longer exists and that never read it.
- 04
Cookies
Only the sign-in cookies of the private control tower, at /control and /auth, and only for whoever signs in there. No page a reader can reach sets a cookie, and no advertising cookie exists anywhere in the product.
- 05
The one thing that is kept
On that same private sign-in page, the time of the last secure-link request, held in local storage for an hour. It has to outlive the tab, because that is exactly what stops the mail provider being asked again from a second window. It is a timestamp; there is nothing else inside it.
- 06
What is measured, and by whom
Events — page opened, button clicked, edition requested — go to a server of CORREDOR's own. Nothing leaves it today: the site can send the same events to PostHog in the European Union and has no key configured, so none are sent; if one is ever configured, this page will say so first. They carry this visit's two identifiers, the campaign or referring site you arrived from, the page you landed on and whether the screen is a phone, a tablet or a desktop. PostHog's script is never loaded and nothing of theirs is stored. On CORREDOR's side both identifiers are salted and hashed before they are written down, so what is kept cannot be turned back into them.
- 07
How to erase it
Closing the tab is enough for everything the public site keeps. Clearing site data in your browser also removes the control tower's values. The site keeps working either way.
Subscription
Your comparable is already written. The question is who reads it first.
The complete edition arrives now, at no charge and with no automatic subscription. If the Southern Cone is not your market, you will see that there; and if it is, you will have the date, the file number and the figure before your counterparty does. And if you subscribe afterwards and it is not for you, you have 30 days: one click and the whole payment comes back, with nobody asking you anything.