Privacy and Cookies
This page explains what data HeritageJackpot collects, how session storage is used for the age gate, and how to contact us about privacy matters.
What we collect
This site is static: it does not run a server-side application, does not require account registration, and does not collect payment information. Standard web-server logs (such as IP address and requested page) may be generated by the hosting infrastructure for security and reliability purposes, consistent with typical web hosting practice.
Session storage and the age confirmation
When you confirm your age on this site, we record that confirmation using your browser's localStorage under the key heritagejackpot_age_ok, so the age prompt only appears once, the first time you visit this site on a given device and browser. This value is stored only in your browser, is never transmitted to us or to any third party, and stays until you clear your browser's site data. We do not use cookies to track this confirmation.
The License Ledger filter tool
The interactive filter tool on The License Ledger stores your selected filters in the page's URL address bar (as URL parameters) rather than in a cookie or local storage, so that a filtered view can be bookmarked or shared. No filter selection is transmitted to any server beyond the normal request for the page itself.
Third-party services
This site loads typeface files from Google Fonts, which may involve a request to Google's servers when a page loads. Any outbound travel-affiliate link, as described on our editorial policy page, will take you to a third-party site governed by that site's own privacy practices, which we do not control.
Your choices
You can clear session storage at any time by closing your browser session or by using your browser's privacy or developer tools. Because this site does not maintain a user database, there is no account data to request, correct, or delete on our end.
Changes to this statement
We may update this statement as the site changes. The version published here reflects our current practice as a static, non-account-based archive site.