1. Introduction
Our website, https://www.bmwblog.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.
We also use the website to collect and sell your personal information. In the document below we explain which data we have sold in the last 12 months, and we give you the possibility to opt-out.
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 personalize the advertisements for you, and we (and third parties) gain insights into the campaign results. This happens based on a profile we create based on your click and surfing on and outside https://www.bmwblog.com. With these cookies you, as website visitor are linked to a unique ID, so you do not see the same ad more than once for example.
You can object to the tracking by these cookies by clicking the “Revoke cookie consent” button.
6.3 Social media buttons
On our website we have included buttons for Facebook, Twitter, Instagram, Disqus and Pinterest to promote webpages (e.g. “like”, “pin”) or share (e.g. “tweet”) on social networks like Facebook, Twitter, Instagram, Disqus and Pinterest. These buttons work using pieces of code coming from Facebook, Twitter, Instagram, Disqus 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, Instagram, Disqus and Pinterest are located in the United States.
7. Placed cookies
Complianz
We use Complianz for cookie consent management.
| Name | Retention | Function |
|---|---|---|
| Functional | ||
| cmplz_choice | 365 days | Store if a message has been dismissed |
| cmplz_id | 365 days | Store anonymized statistics |
| cmplz_user_data | 365 days | Determines which cookie banner to show |
| complianz_policy_id | 365 days | Store accepted cookie policy ID |
| complianz_consent_status | 365 days | Store cookie consent preferences |
| cmplz_stats | 365 days | Store cookie consent preferences |
| cmplz_marketing | 365 days | Store cookie consent preferences |
Sharing
For more information, please read the Complianz Privacy Statement.
Google Ads Optimization
We use Google Ads Optimization for showing advertisements.
| Name | Retention | Function |
|---|---|---|
| Marketing/Tracking | ||
| google_experiment_mod* | 3 months | Track visits across websites |
Sharing
For more information, please read the Google Ads Optimization Privacy Statement.
Google Analytics
We use Google Analytics for website statistics.
| Name | Retention | Function |
|---|---|---|
| Statistics (anonymous) | ||
| _ga | 2 years | |
| _gid | 1 day | Count and track pageviews |
| Statistics | ||
| _gat_gtag_UA_* | 1 minute | Store a unique user ID |
| Purpose pending investigation | ||
| _ga_* | 2 years |
Sharing
For more information, please read the Google Analytics Privacy Statement.
Google reCAPTCHA
We use Google reCAPTCHA for spam prevention.
| 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.
YouTube
We use YouTube for video display.
| 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 | Store and track visits across websites |
Sharing
For more information, please read the YouTube Privacy Statement.
We use Twitter for display of recent social posts and/or social share buttons.
| Name | Retention | Function |
|---|---|---|
| Functional | ||
| local_storage_support_test | persistent | Load balancing functionality |
| Marketing/Tracking | ||
| metrics_token | persistent | Store if the user has seen embedded content |
Sharing
For more information, please read the Twitter Privacy Statement.
We use Facebook for display of recent social posts and/or social share buttons.
| Name | Retention | Function |
|---|---|---|
| Marketing/Tracking | ||
| actppresence | 1 year | Manage ad display frequency |
| _fbc | 2 years | Store last visit |
| fbm* | 1 year | Store account details |
| xs | 3 months | Store a unique session ID |
| fr | 3 months | Enable ad delivery or retargeting |
| _fbp | 3 months | Store and track visits across websites |
| datr | 2 years | Provide fraud prevention |
| sb | 2 years | Store browser details |
| *_fbm_ | 1 year | Store account details |
| Functional | ||
| wd | 1 week | Determine screen resolution |
| act | 90 days | Keep users logged in |
| c_user | 90 days | Store a unique user ID |
| csm | 90 days | Provide fraud prevention |
| presence | session | Store and track if the browser tab is active |
Sharing
For more information, please read the Facebook Privacy Statement.
Google Fonts
We use Google Fonts for display of webfonts.
| 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 Ads
We use Google Ads for advertising.
| Name | Retention | Function |
|---|---|---|
| Marketing/Tracking | ||
| google_pem_mod | persistent | Enable ad delivery or retargeting |
| ads/ga-audiences | none | Store information for remarketing purposes |
Sharing
For more information, please read the Google Ads Privacy Statement.
JetPack
We use JetPack for advertising.
| Name | Retention | Function |
|---|---|---|
| Statistics | ||
| tk_tc | session | Store the user’s usage history |
| tk_qs | 30 minutes | |
| Functional | ||
| jetpackState | session | Provide functions across pages |
Sharing
For more information, please read the JetPack Privacy Statement.
Advanced Ads
We use Advanced Ads for showing advertisements.
| Name | Retention | Function |
|---|---|---|
| Purpose pending investigation | ||
| advanced_ads_pro_visitor_referrer | ||
| advanced_ads_page_impressions |
Sharing
This data is not shared with third parties.
Automattic
We use Automattic for website development.
| Name | Retention | Function |
|---|---|---|
| Statistics | ||
| tk_ai | session | Store a unique user ID |
Sharing
For more information, please read the Automattic Privacy Statement.
CookieBot
We use CookieBot for cookie consent management.
| Name | Retention | Function |
|---|---|---|
| Purpose pending investigation | ||
| CookieConsent | 1 year |
Sharing
This data is not shared with third parties.
Criteo
We use Criteo for remarketing.
| Name | Retention | Function |
|---|---|---|
| Purpose pending investigation | ||
| criteo_fast_bid_expires | ||
| criteo_fast_bid | ||
| criteo_pt_cdb_mngr_metrics | ||
| criteo_pt_cdb_metrics | ||
| criteo_fast_bid_standalone_expires | ||
| criteo_fast_bid_standalone |
Sharing
For more information, please read the Criteo Privacy Statement.
Google Tag Manager
We use Google Tag Manager for website statistics.
| Name | Retention | Function |
|---|---|---|
| Purpose pending investigation | ||
| cto_bundle | ||
| Statistics | ||
| uslk_inital_url | persistent | |
| uslk_referrer | persistent | |
| uslk_operator_binding | persistent | |
| uslk_drag | persistent | |
| uslk_in_service_time | persistent | |
| uslk_page_impressions | persistent | |
| uslk_s | session | |
| uslk_e | 1 year |
Sharing
This data is not shared with third parties.
Loggly
We use Loggly for website performance optimization.
| Name | Retention | Function |
|---|---|---|
| Statistics | ||
| logglytrackingsession | session |
Sharing
This data is not shared with third parties.
Miscellaneous
| Name | Retention | Function |
|---|---|---|
| Purpose pending investigation | ||
| totalCalls | ||
| totalCallsTimeout | ||
| __VASTUtil__ | ||
| jd_vinewsrnot | ||
| google_adsense_settings | ||
| __gads | ||
| __qca | ||
| GED_PLAYLIST_ACTIVITY | ||
| goog_pem_mod | ||
| em_cdn_uid | ||
| em_p_uid | ||
| geo | ||
| userEmail2 | ||
| _at.cww | ||
| at-rand | ||
| at-lojson-cache-ra-* | ||
| __atuvc | ||
| __atuvs | ||
| advanced_ads_pro_server_info | ||
| __atssc | ||
| google_pubconsole | ||
| google_pubconsole_dfp | ||
| _pubcid | ||
| cio_71s4s | ||
| d3did2xnY20 | ||
| _pubcid_exp | ||
| fc | ||
| pv | ||
| criteo_pt_cdb_metrics_expires | ||
| pmtimesig | ||
| d3did2xnY21z | ||
| bulkSecret | ||
| criteo_pt_cdb_bidcachemap | ||
| apstagDebug | ||
| dt | ||
| invid | ||
| amzn_lsTest | ||
| _kxmattressfirm_data | ||
| kxmattressfirm_data | ||
| lkqdFrequencyCapTimestamp | ||
| __lsv__ | ||
| vast-client-last-successful-ad | ||
| OX_user_latency | ||
| OX_net_latency | ||
| OX_plg | ||
| prebid.cookieTest | ||
| IXWRAPPERLiveRampIp | ||
| IXWRAPPERAdserverOrgIp | ||
| cto_bidid | ||
| session_id | ||
| _kxcramer_data | ||
| kxcramer_data | ||
| pbjs-unifiedid | ||
| CMPList |
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
10.1 Categories of data
The following categories of data are sold to third parties
- Internet activity information, including, but not limited to, browsing history, search history, and information regarding a consumer’s interaction with an Internet Web site, application, or advertisement
10.2 Object to selling of personal data to third parties
You can object to our selling of your personal data by entering your email address and name here. We will then remove your data from the databases we sell 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:
iMedia Network Inc
2532 W Irving Park Rd
United States
Website: https://www.bmwblog.com
Email: privacy@bmwblog.com
Phone number: 3128132722
This Cookie Policy was synchronized with cookiedatabase.org on September 28, 2020
