Effective date: 2026-06-16. This is policy version 1, generated on 2026-06-16.
This policy explains how Capitol Hill Community Foundation (we refer to ourselves as "Ruth Ann Overbeck Capitol Hill History Project", "we", "us", or "our") uses cookies and similar technologies on https://www.capitolhillhistory.org. It tells you what these technologies are, why we rely on them, exactly which ones we set, and how you stay in charge of them. Read it alongside our Privacy Policy, which covers how we handle personal information more broadly.
A cookie is a small text file that a website asks your browser to store on your device. The next time you visit, the site can read that file to recognize your browser, remember what you did before, and keep certain features working. Other technologies, such as pixels, local storage, and software development kits, do similar jobs, and when we say "cookies" in this policy we mean all of them together.
Cookies come in two flavors depending on who sets them. First-party cookies are placed by us, the site you are actually visiting, and we use them to run the site and remember your choices. Third-party cookies are placed by another company whose tools or content appear on our pages, such as an analytics provider or an embedded video. That company sets and reads its own cookies under its own policies, and we tell you which third parties are involved in the table further down.
Cookies also differ in how long they stick around. A session cookie lasts only while your browser is open and disappears when you close it. A persistent cookie stays on your device for a set period, or until you clear it, so the site can remember you across visits. The table in section 3 lists how long each cookie we use is meant to last.
We sort every cookie and tracker we use into one of a few purposes, so you can decide about each group on its own. We only set cookies beyond the strictly necessary group after you allow that group in our banner.
Strictly necessary. These cookies are required for the site to function and for the choices you make to be honored. They do things like keep the site secure and remember the cookie preferences you set, so they run whenever you visit and cannot be switched off through the banner. Without them, parts of the site simply would not work.
Analytics. These cookies help us understand how visitors find and use the site, such as which pages draw the most interest and where people run into trouble. We look at this information in aggregate to spot trends and make the site better, not to single anyone out. We turn analytics on only after you allow this group.
The table below lists every cookie and tracking technology our site may set, grouped by the purpose it serves. For each one we name it, identify the provider, explain what it does, note its type, and show how long it lasts. We keep this table in step with what actually runs on the site, and we update it whenever our trackers change.
| Name | Provider | Purpose | Type | Duration |
|---|---|---|---|---|
| Strictly Necessary | ||||
| ck_consent | Consent Kit (first party) | Stores your cookie consent choices. | HTTP cookie | 1 year |
| Analytics | ||||
| Fathom Analytics | Fathom Analytics (usefathom.com) | Privacy-friendly, cookieless website analytics. Counts page views and visits in aggregate without setting any cookie or collecting personal information. | Cookieless analytics (no cookie set) | None (no cookie set) |
You are in control of every cookie that is not strictly necessary, and you never have to dig through settings to change your mind.
Apart from our own controls, your browser gives you another layer of choice. Most browsers let you see the cookies you have stored, delete them, block cookies from certain sites, or refuse them altogether, usually from a privacy or security menu. Browser makers publish their own guides, so check the help pages for the browser you use to find the exact steps. Keep in mind that blocking all cookies, including the strictly necessary ones, may stop parts of our site from working as you expect.
Cookies are not the only way information is gathered as you browse. We and some of our providers may also use pixels (sometimes called web beacons or tracking pixels), which are tiny, invisible images or snippets of code placed on a page or in an email. When your browser loads one, it can record that a page was opened or a message was read, often working together with cookies. We treat these technologies the same way we treat cookies: the strictly necessary ones run by default, and the rest load only after you allow the matching group, with the same controls described above.
We may revise this policy as our site changes, as we add or remove trackers, or as the law develops. When we do, we will post the new version here and update the effective date and version number at the top. If a change materially affects the cookies we use, we will ask you to make your choices again through the banner, so your consent always reflects what is actually running. Looking over this page now and then is the best way to keep up.
If you have questions about this policy or about how we use cookies, we are happy to help:
