This page was last changed on May 8, 2020, last checked on May 8, 2020 and applies to citizens of the United States.
1. Introduction
Our website, https://diggitally.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 Social media buttons
On our website we have included buttons for Facebook, Twitter, LinkedIn, WhatsApp, Instagram and Pinterest to promote webpages (e.g. “like”, “pin”) or share (e.g. “tweet”) on social networks like Facebook, Twitter, LinkedIn, WhatsApp, Instagram and Pinterest. These buttons work using pieces of code coming from Facebook, Twitter, LinkedIn, WhatsApp, Instagram and Pinterest themselves. This code places cookies. These social media buttons also can store and process certain information, so a personalized advertisement can be shown to you.
Please read the privacy statement of these social networks (which can change regularly) to read what they do with your (personal) data which they process using these cookies. The data that is retrieved is anonymized as much as possible. Facebook, Twitter, LinkedIn, WhatsApp, Instagram and Pinterest are located in the United States.
7. Placed cookies
Wistia
We use Wistia for video display. Read more| Name | Retention | Function |
|---|---|---|
| Purpose pending investigation | ||
| wistia-video-progress-* | persistent | |
| Marketing/Tracking | ||
| wistia | persistent | Store performed actions on the website |
Sharing
For more information, please read the Wistia Privacy Statement.
Elementor
We use Elementor for content creation. Read more| Name | Retention | Function |
|---|---|---|
| Statistics | ||
| elementor | persistent | Store performed actions on the website |
Sharing
This data is not shared with third parties.
SiteGround
We use SiteGround for website hosting. Read more| Name | Retention | Function |
|---|---|---|
| Functional | ||
| wpSGCacheBypass | persistent |
Sharing
For more information, please read the SiteGround Privacy Statement.
Google Fonts
We use Google Fonts for display of webfonts. Read more| Name | Retention | Function |
|---|---|---|
| Marketing/Tracking | ||
| Google Fonts API | none | Request user IP address |
Sharing
For more information, please read the Google Fonts Privacy Statement.
Google reCAPTCHA
We use Google reCAPTCHA for spam prevention. Read more| Name | Retention | Function |
|---|---|---|
| Marketing/Tracking | ||
| 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.
Vimeo
We use Vimeo for video display. Read more| Name | Retention | Function |
|---|---|---|
| Statistics | ||
| __utmt_player | 10 minutes | Track audience reach |
| vuid | 2 years | Store the user's usage history |
Sharing
For more information, please read the Vimeo Privacy Statement.
YouTube
We use YouTube for video display. Read more| Name | Retention | Function |
|---|---|---|
| Marketing/Tracking | ||
| GPS | session | Store location data |
| Functional | ||
| VISITOR_INFO1_LIVE | 6 months | Estimate bandwidth |
| Statistics | ||
| YSC | session | Store a unique user ID |
| PREF | 1 year | Track visits across websites |
Sharing
For more information, please read the YouTube Privacy Statement.
| Name | Retention | Function |
|---|---|---|
| Functional | ||
| local_storage_support_test | persistent | Load balancing functionality |
| Marketing/Tracking | ||
| metrics_token | persistent | Stores if the user has seen embedded content |
Sharing
For more information, please read the Twitter Privacy Statement.
| Name | Retention | Function |
|---|---|---|
| Marketing/Tracking | ||
| bcookie | 2 years | Store browser details |
| li-oatml | 1 month | Enable ad delivery or retargeting |
| li_sugr | 3 months | Store browser details |
| UserMatchHistory | 30 days | Enable ad delivery or retargeting |
| lidc | 1 day | Store performed actions on the website |
| bscookie | 2 years | Store performed actions on the website |
| X-LI-IDC | session | Provide functions across pages |
| Functional | ||
| BizographicsOptOut | 10 years | Store privacy preferences |
Sharing
For more information, please read the LinkedIn Privacy Statement.
| Name | Retention | Function |
|---|---|---|
| Marketing/Tracking | ||
| actppresence | 1 year | Manage ad display frequency |
Sharing
This data is not shared with third parties.
Miscellaneous
| Name | Retention | Function |
|---|---|---|
| Purpose pending investigation | ||
| undefined | ||
| loglevel | ||
| _ga | ||
| complianz_policy_id | 365 days | |
| _gid | ||
| complianz_consent_status | 365 days | |
| _gat | ||
| wp-api-schema-modelhttps://diggitally.com/wp-json/wp/v2/ | ||
| _ada_config |
Sharing
This data is not shared with third parties.
8. Your rights with respect to personal data
You have the following rights with respect to your personal data:
- you may submit a request for access to the data we process about you;
- you may object to the processing;
- you may request an overview, in a commonly used format, of the data we process about you;
- you may request correction or deletion of the data if it is incorrect or not or no longer relevant, or to ask to restrict the processing of the data.
To exercise these rights, please contact us. Please refer to the contact details at the bottom of this Cookie Policy. If you have a complaint about how we handle your data, we would like to hear from you.
9. Enabling/disabling and deleting cookies
You can use your internet browser to automatically or manually delete cookies. You can also specify that certain cookies may not be placed. Another option is to change the settings of your internet browser so that you receive a message each time a cookie is placed. For more information about these options, please refer to the instructions in the Help section of your browser.
10. Selling data to third parties
We do not sell data to third parties
11. Contact details
For questions and/or comments about our Cookie Policy and this statement, please contact us by using the following contact details:
Geir Hoem
Jon Sivertsens veg 1, 7022 Trondheim, Norway
Norway
Website: https://diggitally.com
Email: garyholms@gmail.com
Phone number: +5584987946580
This Cookie Policy was synchronized with cookiedatabase.org on May 8, 2020