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.

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. As soon as you click on “Save preferences”, you consent to us using the categories of cookies and plug-ins you selected in the pop-up, as described in this Cookie Policy. You can disable the use of cookies via your browser, but please note that our website may no longer work properly.

5.1 Manage your consent settings

 

 

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 Analytical cookies

We use analytical cookies to optimize the website experience for our users. With these analytical cookies we get insights in the usage of our website. We ask your permission to place analytical cookies.

6.3 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.

Because these cookies are marked as tracking cookies, we ask your permission to place these.

6.4 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.

NameRetentionFunction
Functional
cmplz_choice365 daysStore if a message has been dismissed
cmplz_id365 daysStore anonymized statistics
cmplz_user_data365 daysDetermines which cookie banner to show
complianz_policy_id365 daysStore accepted cookie policy ID
complianz_consent_status365 daysStore cookie consent preferences
cmplz_stats365 daysStore cookie consent preferences
cmplz_marketing365 daysStore cookie consent preferences

Sharing

For more information, please read the Complianz Privacy Statement.

Google Ads Optimization

We use Google Ads Optimization for showing advertisements.

NameRetentionFunction
Marketing/Tracking
google_experiment_mod*3 monthsTrack visits across websites

Sharing

For more information, please read the Google Ads Optimization Privacy Statement.

Google Analytics

We use Google Analytics for website statistics.

NameRetentionFunction
Statistics (anonymous)
_ga2 years
_gid1 dayCount and track pageviews
Statistics
_gat_gtag_UA_*1 minuteStore 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.

NameRetentionFunction
Marketing/Tracking
rc::csessionFilter requests from bots
rc::bsessionFilter requests from bots
rc::apersistentFilter requests from bots

Sharing

For more information, please read the Google reCAPTCHA Privacy Statement.

YouTube

We use YouTube for video display.

NameRetentionFunction
Marketing/Tracking
GPSsessionStore location data
Functional
VISITOR_INFO1_LIVE6 monthsEstimate bandwidth
Statistics
YSCsessionStore a unique user ID
PREF1 yearStore and track visits across websites

Sharing

For more information, please read the YouTube Privacy Statement.

Twitter

We use Twitter for display of recent social posts and/or social share buttons.

NameRetentionFunction
Functional
local_storage_support_testpersistentLoad balancing functionality
Marketing/Tracking
metrics_tokenpersistentStore if the user has seen embedded content

Sharing

For more information, please read the Twitter Privacy Statement.

Facebook

We use Facebook for display of recent social posts and/or social share buttons.

NameRetentionFunction
Marketing/Tracking
actppresence1 yearManage ad display frequency
_fbc2 yearsStore last visit
fbm*1 yearStore account details
xs3 monthsStore a unique session ID
fr3 monthsEnable ad delivery or retargeting
_fbp3 monthsStore and track visits across websites
datr2 yearsProvide fraud prevention
sb2 yearsStore browser details
*_fbm_1 yearStore account details
Functional
wd1 weekDetermine screen resolution
act90 daysKeep users logged in
c_user90 daysStore a unique user ID
csm90 daysProvide fraud prevention
presencesessionStore 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.

NameRetentionFunction
Marketing/Tracking
Google Fonts APInoneRequest user IP address

Sharing

For more information, please read the Google Fonts Privacy Statement.

Google Ads

We use Google Ads for advertising.

NameRetentionFunction
Marketing/Tracking
google_pem_modpersistentEnable ad delivery or retargeting
ads/ga-audiencesnoneStore information for remarketing purposes

Sharing

For more information, please read the Google Ads Privacy Statement.

JetPack

We use JetPack for advertising.

NameRetentionFunction
Statistics
tk_tcsessionStore the user’s usage history
tk_qs30 minutes
Functional
jetpackStatesessionProvide functions across pages

Sharing

For more information, please read the JetPack Privacy Statement.

Advanced Ads

We use Advanced Ads for showing advertisements.

NameRetentionFunction
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.

NameRetentionFunction
Statistics
tk_aisessionStore a unique user ID

Sharing

For more information, please read the Automattic Privacy Statement.

CookieBot

We use CookieBot for cookie consent management.

NameRetentionFunction
Purpose pending investigation
CookieConsent1 year

Sharing

This data is not shared with third parties.

Criteo

We use Criteo for remarketing.

NameRetentionFunction
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.

NameRetentionFunction
Purpose pending investigation
cto_bundle
Statistics
uslk_inital_urlpersistent
uslk_referrerpersistent
uslk_operator_bindingpersistent
uslk_dragpersistent
uslk_in_service_timepersistent
uslk_page_impressionspersistent
uslk_ssession
uslk_e1 year

Sharing

This data is not shared with third parties.

Loggly

We use Loggly for website performance optimization.

NameRetentionFunction
Statistics
logglytrackingsessionsession

Sharing

This data is not shared with third parties.

Miscellaneous

NameRetentionFunction
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 have the right to know why your personal data is needed, what will happen to it, and how long it will be retained for.
  • Right of access: You have the right to access your personal data that is known to us.
  • Right to rectification: you have the right to supplement, correct, have deleted or blocked your personal data whenever you wish.
  • If you give us your consent to process your data, you have the right to revoke that consent and to have your personal data deleted.
  • Right to transfer your data: you have the right to request all your personal data from the controller and transfer it in its entirety to another controller.
  • Right to object: you may object to the processing of your data. We comply with this, unless there are justified grounds for processing.

 

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, but you also have the right to submit a complaint to the supervisory authority (the Data Protection Authority).

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.

Please note that our website may not work properly if all cookies are disabled. If you do delete the cookies in your browser, they will be placed again after your consent when you visit our websites again.

10. 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