This page was last changed on August 30, 2021, last checked on August 30, 2021 and applies to citizens of the United States.
Change your cookie opt-in status: Manage cookie settings
1. Introduction
Our website, https://pilotdigital.com (hereinafter: “the website”) uses cookies and other related technologies (for convenience all technologies are referred to as “cookies”). Cookies are also placed by third parties we have engaged. In the document below we inform you about the use of cookies on our website.
2. What are cookies?
A cookie is a small simple file that is sent along with pages of this website and stored by your browser on the hard drive of your computer or another device. The information stored therein may be returned to our servers or to the servers of the relevant third parties during a subsequent visit.
3. What are scripts?
A script is a piece of program code that is used to make our website function properly and interactively. This code is executed on our server or on your device.
4. What is a web beacon?
A web beacon (or a pixel tag) is a small, invisible piece of text or image on a website that is used to monitor traffic on a website. In order to do this, various data about you is stored using web beacons.
5. Consent
When you visit our website for the first time, we will show you a pop-up with an explanation about cookies. You do have the right to opt-out and to object against the further use of non-functional cookies.
5.1 Manage your consent settings
You can also disable the use of cookies via your browser, but please note that our website may no longer work properly.
6. Cookies
6.1 Technical or functional cookies
Some cookies ensure that certain parts of the website work properly and that your user preferences remain known. By placing functional cookies, we make it easier for you to visit our website. This way, you do not need to repeatedly enter the same information when visiting our website and, for example, the items remain in your shopping cart until you have paid. We may place these cookies without your consent.
6.2 Advertising cookies
On this website we use advertising cookies, enabling us to gain insights into the campaign results. This happens based on a profile we create based on your behavior on https://pilotdigital.com. With these cookies you, as website visitor are linked to a unique ID, but will not profile your behavior and interests to serve personalized ads.
You can object to the tracking by these cookies by clicking the “Revoke cookie consent” button.
7. Placed cookies
Google Adsense
We use Google Adsense for showing advertisements. Read more
Name | Retention | Function |
---|---|---|
Marketing/Tracking | ||
_gcl_au | persistent | Store and track conversions |
Purpose pending investigation | ||
google_adsense_settings |
Sharing
For more information, please read the Google Adsense Privacy Statement.
WordPress
We use WordPress for website development. Read more
Name | Retention | Function |
---|---|---|
Marketing/Tracking | ||
__utmzzses | session | Stores source, campaign, and medium user data. |
Statistics | ||
__utmzz | 8 months | Stores source, campaign, and medium user data. |
Functional | ||
pilot_popup_notice | persistent | Presents a popup when users were redirected from our old domain, chicagostyleseo.com |
Sharing
This data is not shared with third parties.
Google Analytics
We use Google Analytics for website statistics. Read more
Name | Retention | Function |
---|---|---|
Statistics (anonymous) | ||
_ga | 2 years | Count and track pageviews |
_gid | 1 day | Count and track pageviews |
Statistics | ||
_dc_gtm_UA-* | 1 minute | Store number of service requests |
Sharing
For more information, please read the Google Analytics Privacy Statement.
CallRail
We use CallRail for call tracking. Read more
Name | Retention | Function |
---|---|---|
Marketing/Tracking | ||
calltrk_referrer | 1 year | Detect traffic source – referrer |
calltrk_session_id | 1 year | |
calltrk_fcid | 1 year | |
calltrk-* | persistent | |
calltrk-calltrk_referrer | 1 year | |
calltrk-calltrk_session_id | 1 year | |
calltrk-_ga | persistent | |
calltrk-calltrk_landing | persistent | |
calltrk_session_id_* |
Sharing
For more information, please read the CallRail Privacy Statement.
Hotjar
We use Hotjar for heat maps and screen recordings. Read more
Name | Retention | Function |
---|---|---|
Statistics | ||
_hjid | 1 year | Store a unique user ID |
0 | ||
_hjIncludedInSample | ||
_hjSessionResumed |
Sharing
For more information, please read the Hotjar Privacy Statement.
OptinMonster
We use OptinMonster for mailing list subscriptions. Read more
Name | Retention | Function |
---|---|---|
Statistics | ||
_omappvp | 11 years | Store last visit |
omVisitsFirst | persistent | Store a unique user ID |
omVisits | persistent | Store number of visits |
omSessionPageviews | session | Store and count pageviews |
omSessionStart | session | Store time of visit |
Sharing
This data is not shared with third parties.
Complianz
We use Complianz for cookie consent management. Read more
Name | Retention | Function |
---|---|---|
Functional | ||
complianz_policy_id | 365 days | Store accepted cookie policy ID |
complianz_consent_status | 365 days | Store cookie consent preferences |
Sharing
For more information, please read the Complianz Privacy Statement.
Google reCAPTCHA
We use Google reCAPTCHA for spam prevention. Read more
Name | Retention | Function |
---|---|---|
Functional | ||
rc::c | session | Filter requests from bots |
rc::b | session | Filter requests from bots |
rc::a | persistent | Filter requests from bots |
Sharing
For more information, please read the Google reCAPTCHA Privacy Statement.
Google Fonts
We use Google Fonts for display of webfonts. Read more
Name | Retention | Function |
---|---|---|
Marketing/Tracking | ||
Google Fonts API | expires immediately | Read user IP address |
Sharing
For more information, please read the Google Fonts Privacy Statement.
Wordfence
We use Wordfence for website security. Read more
Name | Retention | Function |
---|---|---|
Functional | ||
wfwaf-authcookie-* | 12 hours | Security tool to determine if a user is logged in. |
Sharing
For more information, please read the Wordfence Privacy Statement.
Google Maps
We use Google Maps for maps display. Read more
Name | Retention | Function |
---|---|---|
Purpose pending investigation | ||
Google Maps API |
Sharing
For more information, please read the Google Maps Privacy Statement.