Cookie Policy
Last updated: October 14th, 2026
This Cookie Policy explains which cookies and similar techniques polakotravel.com uses, what they do and how you control them. It should be read together with our Privacy Policy.
1. What cookies are
A cookie is a small text file that a website stores on your device. Similar techniques, such as local storage and tracking pixels, work in much the same way. We use the word cookies for all of them in this policy.
2. Your choice
When you first visit our site you see a banner with three options: accept all cookies, reject all cookies that are not strictly necessary, or open preferences and choose per category. Analytics and marketing cookies are only placed after you have actively given consent. Rejecting is as easy as accepting, and refusing does not limit your use of the site in any way.
You can change or withdraw your choice at any time by opening the cookie preferences from the link in the footer, or by clearing the cookies in your browser, after which the banner appears again.
3. The categories we use
3.1 Strictly necessary
These make the website work and cannot be switched off. They remember what is in your shopping basket, keep you logged in, protect forms against abuse and store the cookie choice you made. They rely on our legitimate interest and require no consent.
Examples: WordPress session and login cookies, WooCommerce basket and session cookies, and our own cookie consent cookie.
3.2 Functional
These remember choices you make, such as your language or a filter you set on the trips page, so that the site behaves the way you left it.
3.3 Analytics
These tell us how many people visit the site, which pages they read and where they leave. We use Google Analytics for this. The data is used in aggregate form to improve the site. These cookies are placed only after you consent.
Examples: _ga and _ga_ cookies set by Google, with a lifetime of up to two years.
3.4 Marketing
These let us measure whether our advertisements work and show relevant advertisements to people who have visited our site. We use the Meta Pixel for this, which works with Facebook and Instagram. These cookies are placed only after you consent.
Examples: _fbp and fr cookies set by Meta, with a lifetime of up to three months.
4. The cookies we actually use
The list below is generated automatically from a scan of this website, so it always matches what is really placed. It shows the name of each cookie, who sets it, what it is for and how long it stays on your device.
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 |
|---|
| _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 |
| __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 |
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 |
WooCommerce Sourcebuster
SourceBuster is used by WooCommerce for order attribution based on user source.
| Name | Description | Duration |
|---|
| sbjs_current | Traffic origin information for the visitor’s current visit to your store | session |
| sbjs_first_add | Timestamp, referring URL, and entry page for your visitor’s first visit to your store (only applicable if the visitor returns before the session expires) | session |
| sbjs_current_add | Timestamp, referring URL, and entry page for your visitor’s current visit to your store | session |
| sbjs_migrations | Technical data to help with migrations between different versions of the tracking feature | session |
| sbjs_session | The number of page views in this session and the current page path | 30 minutes |
| sbjs_udata | Information about the visitor’s user agent, such as IP, the browser, and the device type | session |
| sbjs_first | Traffic origin information for the visitor’s first visit to your store (only applicable if the visitor returns before the session expires) | session |
5. Third parties
Some cookies are placed by companies other than us. We have no control over what they do with the data afterwards, so we point you to their own policies:
6. Managing cookies in your browser
Besides our banner, your browser lets you block or delete cookies. You will find this under settings, usually as privacy or site data. Blocking strictly necessary cookies means parts of the site, such as the shopping basket, will stop working.
7. Changes
When we add or remove a tool we update this policy and, where the law requires it, we ask for your consent again. The date at the top shows when it was last changed.
8. Questions
Write to info@polakotravel.com.
