Skip to content

Manage Cookies and Understand Site Tracking Choices Clearly

Information about how we use cookies to keep the site running and understand visitor preferences.

Last Revised: October 24, 2023

Digital archives require a baseline of technical memory to function properly. When you load a page, navigate between categories, or adjust a setting, the server needs a way to remember those actions across different requests. We achieve this continuity through small text files placed on your device. While these files are essential for basic site operations, they also open the door to tracking mechanisms that require careful management.

What Are Cookies?

Web browsers handle two distinct categories of these text files. Session cookies exist only while you keep your browser open. They act as temporary sticky notes, holding onto your preferences just long enough to get you through a single visit. Once you close the window, the browser wipes them away.

Persistent cookies take a different approach. They remain on your hard drive until they reach a predefined expiration date or you manually clear them. We rely on persistent files for tasks that span multiple visits, like remembering that you already dismissed a notification banner. Choosing between the two depends entirely on the task at hand. Temporary files handle immediate navigation needs, while persistent ones prevent you from having to repeat the same setup steps every time you return to the archive.

Types of Cookies We May Use

Site operations fall into three distinct tracking categories. The first category covers strictly necessary files. These handle core functions like recording your consent choices and keeping the site secure. You cannot disable these through our site systems because the platform simply breaks without them.

The second category involves performance and analytics. These files count page loads and track which archival sections draw the most traffic. Understanding these patterns helps dictate where we focus our preservation efforts. The final category encompasses advertising cookies. While we prioritize a clean reading experience, future site iterations may utilize these files to deliver relevant promotional content based on your browsing history.

Cookie categorization relies on standard browser protocols, which occasionally misclassify specific tracking scripts depending on your local security settings.

Third-Party Services and Future Tools

Building a reliable digital resource rarely happens in isolation. Content delivery networks currently help distribute our media files quickly across different geographic regions. These external servers often place their own operational cookies to manage load balancing and ensure you receive images from the closest available server.

As the site expands, the infrastructure will likely incorporate external analytics providers and advertising networks. When these third-party systems integrate into the platform, they bring their own tracking protocols. You maintain control over these external files through your browser's privacy controls, rather than our internal site settings.

How to Manage Cookies in Your Browser

You can tackle tracking management through two primary methods. The first involves using built-in browser settings to block all incoming cookies universally. You navigate to the privacy tab in Chrome, Firefox, or Safari, and flip the switch to reject everything. This guarantees maximum privacy.

The second method requires selectively blocking third-party trackers while allowing first-party files. This targeted approach usually yields a better reading experience. Blocking everything universally strips away basic functionality—menus might fail to load, and preference banners will reappear on every single page load. By targeting only third-party files, you block external advertising networks while keeping the core site navigation intact.

Digital privacy standards shift rapidly. When browser manufacturers update their default tracking protections or new privacy legislation takes effect, this document requires revision. We post all updates directly to this page and update the revision date at the top of the document.

A developer sits at a dual-monitor setup, watching a network tab populate with blocked script warnings after a major browser update. They adjust the site's consent manager, rewrite a few lines of the tracking policy to match the new technical reality, and push the commit live to the server.

Cookie settings