Cook­ie State­ment

On John Deere’s web­sites and online ser­vices (“Online Ser­vices”), var­i­ous cook­ies and oth­er tech­nolo­gies are used such as Brows­er or HTTP cook­ies, local shared objects (Flash cook­ies), local stor­age (such as HTML5), web beacons/pixel tags, embed­ded scripts, ETags and oth­er tech­nolo­gies (col­lec­tive­ly, “Cook­ies”). These tech­nolo­gies may store and/or access data on a device. This Cook­ie State­ment incor­po­rates, and forms part of, the John Deere Enter­prise Pri­va­cy State­ment.

This Cook­ie State­ment includes infor­ma­tion about Cook­ies, how they are used and how to man­age or dis­able these tech­nolo­gies. By using the Online Ser­vices you agree John Deere can use these tech­nolo­gies that are described in this Cook­ie State­ment. John Deere may change this Cook­ie State­ment from time-to-time, the lat­est ver­sion is not­ed by the “Last Updat­ed” date on the top of this page. If you have any ques­tions, please con­tact us by email at PrivacyManager@JohnDeere.com or by postal mail at Cen­ter for Glob­al Busi­ness Con­duct, c/o Pri­va­cy Man­ag­er, Deere & Com­pa­ny, One John Deere Place, Moline, Illi­nois 61265 USA.


Cook­ies: How they are used

When you vis­it or inter­act with John Deere’s Online Ser­vices, John Deere (and/or autho­rized third par­ties) store and/or access data using Cook­ies. The spe­cif­ic types of tech­nolo­gies used may change from time-to-time, but the fol­low­ing is a brief descrip­tion of how Cook­ies are used on the Online Ser­vices.

Essen­tial or Nec­es­sary Cook­ies

Essen­tial or Nec­es­sary Cook­ies. These are Cook­ies that are nec­es­sary for the func­tion­ing of the Online Ser­vices. For exam­ple, they are used to enable the oper­a­tion of the Online Ser­vices, enable access to secure areas of the Online Ser­vices, remem­ber pre­vi­ous actions (e.g., entered text when nav­i­gat­ing back to a page in the same ses­sion), remem­ber items placed in a shop­ping bas­ket or cart dur­ing a ses­sion, secure the Online Ser­vices and for the admin­is­tra­tion of the Online Ser­vices (e.g., load bal­anc­ing, fraud pre­ven­tion). With­out these Cook­ies, the Online Ser­vices would not func­tion prop­er­ly and/or John Deere may be unable to pro­vide cer­tain ser­vices.

Func­tion­al Cook­ies

These are Cook­ies that are not nec­es­sary to the oper­a­tion of the Online Ser­vices, but they enhance the use of the Online Ser­vices by remem­ber­ing cer­tain choic­es you may make and pro­vid­ing enhanced fea­tures. For exam­ple, they are used to remem­ber site pref­er­ences or choic­es, such as remem­ber­ing pref­er­ences for lan­guage, coun­try, region or oth­er online set­tings made (e.g., text size, fonts). These cook­ies and oth­er tech­nolo­gies can be used to enable request­ed func­tions such as watch­ing a video (e.g., YouTube video) or pro­vid­ing com­ments. They can also be used to pre­vent a service(s) from being offered to you if you already received it or pre­vi­ous­ly indi­cat­ed you do not wish to receive it (e.g. requests to par­tic­i­pate in cer­tain types of sur­veys). If you have an account with the Online Ser­vices the infor­ma­tion col­lect­ed may be asso­ci­at­ed with your account.

Func­tion­al Cook­ies also col­lect infor­ma­tion about how the Online Ser­vices are used, includ­ing which pages are vis­it­ed most often, the brows­er or oper­at­ing sys­tem used, where users have come to the Online Ser­vices from, whether an item or link is viewed or used, error mes­sages gen­er­at­ed and whether com­mu­ni­ca­tions John Deere sends are opened or read (also known as ana­lyt­ics or per­for­mance Cook­ies). This infor­ma­tion is used to help John Deere improve its Online Ser­vices, count the num­ber of vis­i­tors, iden­ti­ty usage pat­terns, fix issues in the Online Ser­vices, and make the Online Ser­vices eas­i­er to use. If you have an account with the Online Ser­vices the infor­ma­tion col­lect­ed may be asso­ci­at­ed with your account.

Some ana­lyt­ics and per­for­mance Cook­ies are used in con­nec­tion with ser­vices pro­vid­ed by third par­ties, includ­ing the fol­low­ing:

  • Google Ana­lyt­ics is a web ana­lyt­ics ser­vice pro­vid­ed by Google. Google Ana­lyt­ics may col­lect infor­ma­tion about your use of the Online Ser­vices (includ­ing your IP address). Infor­ma­tion gen­er­at­ed will be trans­mit­ted to and stored by Google on servers in the Unit­ed States of Amer­i­ca. For more infor­ma­tion, please vis­it Google’s site. Google also pro­vides a brows­er add-on that allows you to opt-out of Google Ana­lyt­ics across all web­sites.
  • Adobe Ana­lyt­ics is a web ana­lyt­ics ser­vice pro­vid­ed by Adobe. Adobe Ana­lyt­ics is used to col­lect infor­ma­tion about your use of the Online Ser­vices (includ­ing your IP address). Infor­ma­tion gen­er­at­ed will be trans­mit­ted to and stored by Adobe on servers in the Unit­ed States of Amer­i­ca. For more infor­ma­tion, please vis­it Adobe’s site.

Tar­get­ing or Adver­tis­ing Cook­ies

These Cook­ies col­lect infor­ma­tion about your brows­ing habits and online behav­ior, includ­ing across dif­fer­ent browsers and devices used by you, in order to serve adver­tise­ments that may be of inter­est to you on the Online Ser­vices and oth­ers’ sites and ser­vices you may vis­it. For exam­ple, your brows­ing activ­i­ty on the Online Ser­vices and your activ­i­ties on oth­ers’ sites and ser­vices can be used to infer infor­ma­tion about you, which can be used to make adver­tise­ments more rel­e­vant to you (com­mon­ly referred to as ‘inter­est-based adver­tis­ing’). They also are used to lim­it the num­ber of times you may see an adver­tise­ment and to help mea­sure the effec­tive­ness of adver­tis­ing cam­paigns. They remem­ber you vis­it­ed the Online Ser­vices (includ­ing pages vis­it­ed and links fol­lowed) and this infor­ma­tion may be shared with oth­er orga­ni­za­tions such as adver­tis­ers and adver­tis­ing net­works. These cook­ies usu­al­ly are placed by third-par­ties. Data col­lect­ed through Func­tion­al Cook­ies (such as ana­lyt­ics and per­for­mance Cook­ies) also may be used, in part, to facil­i­tate adver­tis­ing.


Third Par­ty Cook­ies

John Deere may use third par­ties who use their own Cook­ies to store and/or access data relat­ing to your use of, and inter­ac­tion with, the Online Ser­vices. For exam­ple, as ref­er­enced in Cook­ies – How They Are Used, John Deere uses ana­lyt­ics and adver­tis­ing ser­vices pro­vid­ed by third par­ty com­pa­nies and they may set their own Cook­ies.

The Online Ser­vices may con­tain con­tent from third par­ties such as Google Maps, YouTube, ZMags and ShareThis and plu­g­ins from social media sites like Face­book (“Like” but­ton), Twit­ter (“Share to Twit­ter”) and Linkedin. When you con­nect to these ser­vices, the third par­ties may store and/or access data using Cook­ies over which John Deere does not have con­trol, includ­ing their own Func­tion­al or Tar­get­ing or Adver­tis­ing Cook­ies. If you are logged in to a social media web­site while vis­it­ing the Online Ser­vices the social media plu­g­ins may allow the social media web­site to receive infor­ma­tion that you vis­it­ed the Online Ser­vices and link it to your social media account.

John Deere does not con­trol the Cook­ies used by these third par­ty ser­vices or their poli­cies or prac­tices. Please review those third par­ties’ cook­ie, pri­va­cy and data shar­ing state­ments.


Man­ag­ing Cook­ies

John Deere Cook­ie Con­sent Man­ag­er

You may click on the but­ton below to access John Deere’s Cook­ie Con­sent Man­ag­er. John Deere’s Cook­ie Con­sent Man­ag­er is a brows­er cook­ie-based tool that may allow you to mod­i­fy set­tings relat­ed to cer­tain Func­tion­al and Tar­get­ing or Adver­tis­ing Cook­ies. It is not pos­si­ble to mod­i­fy set­tings relat­ed to Nec­es­sary Cook­ies. The tool works by com­mu­ni­cat­ing the select­ed set­ting to third par­ty com­pa­nies to ini­ti­ate a third party’s opt-out mech­a­nism, if avail­able. The effect of such selec­tion may be described in the third party’s cook­ie, pri­va­cy and/or data shar­ing state­ments. If the tool is unable to inte­grate with a third par­ty this will be not­ed in the Advanced Set­tings page with infor­ma­tion about such third par­ty. The Advanced Set­tings page will also pro­vide infor­ma­tion about Cook­ies used on the Online Ser­vices.

The tool will only work on the Inter­net brows­er you use to make your choice and it will only func­tion prop­er­ly if your brows­er is set to accept third-par­ty brows­er cook­ies. If you delete cook­ies, change browsers, com­put­ers or oper­at­ing sys­tems, you will need to make a new selec­tion.

Tar­get­ing or Adver­tis­ing Cook­ies

A num­ber of the third par­ty com­pa­nies that use Tar­get­ing or Adver­tis­ing Cook­ies are mem­bers of the Net­work Adver­tis­ing Ini­tia­tive (NAI). Indi­vid­u­als may opt out of tar­get­ed adver­tis­ing deliv­ered by NAI mem­ber ad net­works by vis­it­ing http://optout.networkadvertising.org.

Also, there are indus­try self-reg­u­la­to­ry pro­grams to pro­vide indi­vid­u­als with choic­es relat­ed to see­ing inter­est­ed-based ads from par­tic­i­pat­ing com­pa­nies.

These tools may use cook­ies to record and imple­ment your pref­er­ences. As a result, if you dis­able or delete cook­ies, you may need to go through the opt-out process again. If you set your brows­er to reject third-par­ty cook­ies, your pref­er­ence may not be record­ed. The effect of opt­ing-out is explained on each site.

Brows­er Cook­ies

Your web brows­er may offer func­tion­al­i­ty that allows you to choose whether to accept or decline the use of brows­er cook­ies. Most web browsers are set to accept brows­er cook­ies by default. For more infor­ma­tion about the avail­able con­trols, please vis­it your brows­er or device’s set­tings. Bea­cons are gen­er­al­ly used in con­junc­tion with brows­er cook­ies. If you delete or decline the use of brows­er cook­ies via brows­er set­tings, bea­cons may not be able to func­tion prop­er­ly. Please note if you remove or dis­able all cook­ies the Online Ser­vices may not func­tion as intend­ed.

For Cook­ies used in emails and oth­er com­mu­ni­ca­tions, you may lim­it their use by set­ting your email client to dis­play HTML emails as text only. Please con­sult the “Help” sec­tion of your email client for more infor­ma­tion.

Flash Cook­ies

Flash cook­ies are dif­fer­ent from brows­er cook­ies. Remov­ing or reject­ing brows­er cook­ies via a brows­er set­ting does not nec­es­sar­i­ly affect Flash cook­ies. You may learn how to man­age Flash cook­ies by going to the Set­tings Man­ag­er for Adobe Flash Play­er or vis­it­ing Adobe’s web­site. If you dis­able Flash cook­ies you may not be able to take advan­tage of all of the fea­tures of the Online Ser­vices.

HTML5 Local Stor­age

It may be pos­si­ble to block or delete HTML5 local stor­age func­tion­al­i­ty from your browser’s set­tings. With­out HTML5 you may not be able to take advan­tage of all of the fea­tures of the Online Ser­vices.

Do Not Track

John Deere does not cur­rent­ly take actions to respond to “Do Not Track” sig­nals because a uni­form tech­no­log­i­cal stan­dard has not yet been devel­oped.


Def­i­n­i­tions

Brows­er or HTTP Cook­ies

Brows­er cook­ies are small pieces of infor­ma­tion that web­sites send to your device when you vis­it to unique­ly iden­ti­fy your brows­er or to store infor­ma­tion or set­tings in your brows­er. Cook­ies com­mu­ni­cate infor­ma­tion to John Deere or third par­ties to help us pro­vide the Online Ser­vices, pro­vide a cus­tomized expe­ri­ence, ana­lyze how the Online Ser­vices are used and enable John Deere to detect cer­tain kinds of fraud (amongst oth­ers). There are sev­er­al types of brows­er cook­ies:

  • First par­ty cook­ies are cook­ies set or placed by the web­site or domain that is being vis­it­ed (e.g., John Deere). These may be ses­sion or per­sis­tent cook­ies.
  • Third par­ty cook­ies are cook­ies that are set by a web­site or domain oth­er than that of the web­site or domain cur­rent­ly being vis­it­ed. These may be ses­sion or per­sis­tent cook­ies.
  • Ses­sion cook­ies are cook­ies that at expire once you close the brows­er (although there may be a small delay in some instances before expi­ra­tion, such as mobile brows­ing). These may be first or third par­ty cook­ies.
  • Per­sis­tent cook­ies are cook­ies that remain on a user’s device for the peri­od of time spec­i­fied in the cook­ie (or until delet­ed). These may be first or third par­ty cook­ies.

Web Bea­cons

Web bea­cons (also called clear GIFs or pix­els) are tiny graph­ic images or lines of code placed in the Online Ser­vices or in emails that include a unique iden­ti­fi­er to allow us (and/or third par­ties) to deter­mine unique user vis­its and whether you have per­formed a spe­cif­ic action. When you access these pages or open or click an email, these tech­nolo­gies gen­er­ate a notice of that action. These tools are often used in con­junc­tion with HTTP cook­ies and are gen­er­al­ly used to mea­sure respons­es to com­mu­ni­ca­tions and improve Online Ser­vices and pro­mo­tions.

LSO & Local Stor­age

Oth­er tech­nolo­gies, such as local shared objects (e.g., Flash cook­ies) and local stor­age (e.g., device or HTML5 local stor­age and caching), allow John Deere (and/or third-par­ties) to per­son­al­ize and enhance your online expe­ri­ence by stor­ing and retriev­ing data on a device. Flash cook­ies use tech­nol­o­gy to remem­ber set­tings, pref­er­ences and usage sim­i­lar to brows­er cook­ies, but these are man­aged through a dif­fer­ent inter­face than the one pro­vid­ed by your web brows­er. HTML5 uses the local stor­age of the device that access­es the Online Ser­vices. The Online Ser­vices may record infor­ma­tion in local stor­age and read it when it is need­ed.

Embed­ded Script

An embed­ded script is pro­gram­ming code that is designed to col­lect infor­ma­tion about your inter­ac­tions with the Online Ser­vices, such as links clicked. The code is tem­porar­i­ly down­loaded to your device from John Deere or a third-par­ty ser­vice provider and is active only when you are con­nect­ed to the Online Ser­vice.

ETag

An ETag is an opaque iden­ti­fi­er assigned by a web serv­er to a spe­cif­ic ver­sion of a resource found at a URL. If the resource at that URL changes a new and dif­fer­ent ETag is assigned. ETags are a form of iden­ti­fi­er.