Privacy

tldlog sets no cookies, uses no analytics or tracking scripts, and loads nothing from other websites: every file a page needs comes from tldlog itself. There are no reader accounts and no forms that send information to tldlog, so the site does not ask for any personal details.

What is stored in your browser

A few preferences are saved in your browser’s local storage, a small space that each website can use in the browser. They stay there: tldlog’s pages never send them to tldlog or to anyone else. Each one is saved only after you do something on the site: choose a theme, choose a language, open a piece or mark it as read, open a list of pieces (the home page, a section, the list of all the news or an archive), switch to headlines only, save a piece for later or follow a tag or an extension. Nothing is saved when JavaScript is turned off.

• tldlog:theme: the theme you chose with the theme button, light or dark. Until you choose, the site follows your device.
• tldlog:lang: the language you chose with the language switcher or the language notice. Once it is saved, the notice that offers a page in another language is not shown again.
• tldlog:read: the pieces you have opened or marked as read with the keyboard, as a list of internal identifiers, at most 200. It is used to mark those pieces with the “read” label.
• tldlog:compact: your choice with the “headlines only” button above the lists of pieces. While it is on, the lists show the headlines without their summaries, sources or authors.
• tldlog:visits: for each list of pieces you open, such as the home page or a section, when you last opened it and when your previous visit to it was, for at most 50 lists. It is used to draw the “your last visit” line between the pieces published since your previous visit and the older ones. Opening a list again within 30 minutes counts as the same visit.
• tldlog:saved: your reading list, the pieces you saved with the “save for later” button, at most 100. For each one it keeps the title, the address of its page on tldlog, its publication date and when you saved it. The reading list page shows them, and tldlog never receives them.
• tldlog:follow: the tags and extensions you follow with the “follow” button on their pages, at most 200. It is used to mark their pieces with the “followed” label in the lists of pieces, and to show only those pieces when you press “followed only” above a list.

Browsers can delete what a website keeps in local storage, for example when you clear your browsing data or, in Safari, after seven days of use without a visit to tldlog. The reading list is then empty, and the other preferences go back to their defaults.

Your browser may also show visited pieces in a different color, using its own history. That is a feature of the browser, not data kept by tldlog, and the button on this page does not clear it.

Clearing stored preferences

The “Clear stored preferences” button on this page deletes them all at once. The site then goes back to its defaults: the theme follows your device again, the language notice may come back, no piece is marked as read, the lists show their summaries again, the “your last visit” line starts over, the reading list is empty, and no tag or extension is followed. You can also delete this site’s data, including these preferences, in your browser’s settings.

What the hosting provider receives

tldlog is a set of prebuilt pages delivered by Cloudflare, the company that hosts the site. To send a page to your browser, Cloudflare’s servers receive what every browser sends with a request: the network address of your device (its Internet Protocol address, or IP address), the address of the page, and technical details such as the name and version of the browser.

Cloudflare can keep a log of the requests that the site’s code handles. tldlog has that log turned off, and it does not use Cloudflare’s service that delivers the full log of every request. It has also turned off Network Error Logging for tldlog.com, a Cloudflare feature that asks browsers to report failed connections to Cloudflare.

Cloudflare still keeps some information of its own:

• Traffic statistics. From its own records of the requests it handles, Cloudflare builds statistics for the site, such as the number of visits and the countries they come from. No script or tracker on the page is needed for this. Cloudflare counts visits by IP address and works out the country from it. tldlog sees totals, not a list of visits, for at least the last 30 days.
• Security events. When one of Cloudflare’s security features flags or blocks a request, for example because one address sent too many requests in a short time, Cloudflare records an event with details such as the IP address, the name and version of the browser, the page and the country. These events are kept for up to 31 days.

Cloudflare sets cookies of its own only for features that tldlog does not use, such as checks that ask a visitor to prove they are a person. If tldlog limits how many requests one address can make, the limit counts by IP address only, so it needs no cookie. How Cloudflare handles this information is covered by Cloudflare’s privacy policy, opens another website in a new tab.

Apart from these statistics, tldlog uses no analytics service and does not track individual readers.

Links to other websites

Links to sources and sponsors lead to other websites. Once you follow one, that website’s own privacy rules apply.

Contact

Marc Gelabert is responsible for this site. For questions about privacy, or about the data described on this page, write to info@tldlog.com.