Effective: August 8, 2026
Last reviewed: September 9, 2026
Hook the Horizon carries advertising and sells Field Decks. That is how the writing gets paid for, and it means the site sets cookies. This page says which ones, whose they are, and how to turn off the ones you can turn off. The register at the bottom is generated from what the site itself records, so it is current rather than remembered.
Strictly necessary. These keep the site working — they remember the choice you made in the banner, hold a session together between pages, and keep a purchase attached to you long enough to hand you the download. They are set whatever you choose here, because without them nothing works.
Statistics. These count visits and tell us which pages actually get read, in aggregate. They’re how we’d know, say, whether the ice-fishing pages get read in December or in March. They stay off until you accept them, and declining them costs you nothing except our count.
Commerce. When you buy a Field Deck, the checkout and its payment provider set cookies to keep the order together and to catch fraud. They are set when you start a purchase, not while you are reading.
Advertising. Display advertising here comes through Google AdSense, and the publisher account is declared publicly at hookthehorizon.blog/ads.txt. Google sets cookies through that code to cap how often you see the same advertisement and to record whether one was seen or clicked. Where personalization has not been switched off, those cookies also decide which advertisement gets selected, using activity Google recorded elsewhere on the web.
Those cookies belong to Google, not to this site, which is why their names and durations are Google’s to publish and to change, and why they do not appear in the register below — that only lists what this site sets itself. Google keeps the current list on its own advertising technologies page.
Turning advertising cookies off. Three controls actually work. Google’s ad settings switch off personalized advertising for your account or for the browser you are in. Blocking third-party cookies in your browser stops them being set here at all. And the preferences panel in the banner lets you refuse categories directly. Switching personalization off does not remove the advertising. It stops the advertising being about you.
Readers in the UK, the EEA and Switzerland are covered by Google’s regional consent defaults, which withhold advertising storage until a consent signal has been recorded.
Spam protection. Akismet checks comments and form submissions for spam signals. Without it the contact form fills with garbage inside a week.
What none of this does. No cookie here is used to work out where you fish. Location privacy is a standing rule on this site and it is not undone by the analytics; see Conservation and Location Privacy.
Changing your mind. Use the cookie settings link in the footer at any time. Clearing your browser’s site data for hookthehorizon.blog clears every choice recorded here, which means the banner will ask again.
Questions. Write through the Hook Us page. The full privacy policy covers what happens to anything the site collects.
Essential
Essential cookies enable basic functions and are necessary for the proper function of the website.
| Name | Description | Duration |
|---|
| wpconsent_preferences | This cookie is used to store the user's cookie consent preferences. | 30 days |
Comments
These cookies are needed for adding comments on this website.
| Name | Description | Duration |
|---|
| comment_author | Used to track the user across multiple sessions. | Session |
| comment_author_email | Used to track the user across multiple sessions. | Session |
| comment_author_url | Used to track the user across multiple sessions. | Session |
Statistics
Statistics cookies collect information anonymously. This information helps us understand how visitors use our website.
Google Analytics
Google Analytics is a powerful tool that tracks and analyzes website traffic for informed marketing decisions.
Learn more| Name | Description | Duration |
|---|
| __utmb | Used to distinguish new sessions and visits. This cookie is set when the GA.js javascript library is loaded and there is no existing __utmb cookie. The cookie is updated every time data is sent to the Google Analytics server. | 30 minutes after last activity |
| __utmc | Used only with old Urchin versions of Google Analytics and not with GA.js. Was used to distinguish between new sessions and visits at the end of a session. | End of session (browser) |
| __utmz | Contains information about the traffic source or campaign that directed user to the website. The cookie is set when the GA.js javascript is loaded and updated when data is sent to the Google Anaytics server | 6 months after last activity |
| __utmv | Contains custom information set by the web developer via the _setCustomVar method in Google Analytics. This cookie is updated every time new data is sent to the Google Analytics server. | 2 years after last activity |
| __utmx | Used to determine whether a user is included in an A / B or Multivariate test. | 18 months |
| _ga | ID used to identify users | 2 years |
| _gali | Used by Google Analytics to determine which links on a page are being clicked | 30 seconds |
| _ga_ | ID used to identify users | 2 years |
| _gid | ID used to identify users for 24 hours after last activity | 24 hours |
| _gat | Used to monitor number of Google Analytics server requests when using Google Tag Manager | 1 minute |
| _gac_ | Contains information related to marketing campaigns of the user. These are shared with Google AdWords / Google Ads when the Google Ads and Google Analytics accounts are linked together. | 90 days |
| __utma | ID used to identify users and sessions | 2 years after last activity |
| __utmt | Used to monitor number of Google Analytics server requests | 10 minutes |
Jetpack Stats
Jetpack's built-in visitor analytics. It records page views, referring sites, search terms, and outbound link clicks, and also carries the shared visitor-tracking library used by Jetpack Instant Search and WooCommerce Analytics.
Learn more| Name | Description | Duration |
|---|
| tk_ai | Stores a randomly-generated anonymous visitor ID so Jetpack's Tracks analytics library can link tracking events to the same visitor. | Session in wp-admin; up to 5 years on the frontend |
| tk_qs | Queues analytics events for Jetpack's Tracks library so none are lost if the page closes before they can be sent. | 30 minutes |
| tk_tc | Used once per page load to work out which cookie domain the Tracks library should use, then removed as soon as it's read back. | Session (deleted immediately after use) |
| tk_aip | Stores a list of anonymous visitor IDs so they can be merged into one identity once a visitor is recognized. | Up to 5 years |