Upgrade to Pro — share decks privately, control downloads, hide ads and more …

The Cookie Law

Sponsored · Ship Features Fearlessly Turn features on and off without deploys. Used by thousands of Ruby developers.

The Cookie Law

Privacy law

Avatar for firstfriday

firstfriday

March 01, 2012
Tweet

More Decks by firstfriday

Other Decks in Technology

Transcript

  1. Why  am  I  here?   •  Online  privacy  regulaEons  changed

     in  May   2011     •  Enforcement  from  May  2012    
  2. Why  am  I  here?   •  Only  provide  informaEon  –

     In  the  past   •  Consent  from  user  to  use  cookies  –  Now   •  Concerns  –  online  tracking  &  use  of  spyware   •  Behavioural  adverEsing  
  3. What’s  in  the  RegulaEons?   •  EU  DirecEve   • 

    Users  need  to  consent  –  can’t  be  assumed   •  There  are  exempEons  if  ‘strictly  necessary’  for   user  
  4. What’s  in  the  RegulaEons?   •  Both  have  responsibility  for

     third  party  cookies   •  Where  the  organisaEon  is  based   •  Aware  of  changing  circumstances  –  browser   soluEons,  public  awareness,  etc.   Before  we  go  any  further………………  
  5. What  is  a  cookie?   Gives  your  website  a  

      beVer  memory  than  a  goldfish  
  6. DuraEon   •  Session  cookies   – UnEl  you  complete  your

     visit  (e.g.  don’t  view  a   page  for  more  than  20-­‐30  mins)   – UnEl  you  exit  your  browser    
  7. DuraEon   •  Persistent  cookies   – A  future  date  

    – Usually  extended  on  next  visit  
  8. Domains   •  Only  sent  back  to  specified  domains  

    •  Site  ownership?   – not  sent  to  redefine.co.uk  if  set  for  firs^riday.info   •  Matches  right  to  le_   – sent  to  mail.google.com  if  set  for  google.com     – not  sent  to  google.co.uk  if  set  for  google.com  
  9. First  party  vs  third  party   •  Any  request  for

     content  can  set  a  cookie   •  First  party  –  sent  from  the  address  you’re   viewing   •  Third  party  –  sent  from  a  different  address   – e.g  image,  video,  social  media  badge  
  10. Privacy  concerns   •  Cookie  content  can  link  you  to

     a  database  with   vast  amounts  of  data   •  Persistent  cookies  so  tracking  can  conEnue   •  Set  by  third  party  content  so  can  follow  you   around  the  web  
  11. Privacy  concerns   •  Sent  &  received  without  the  knowledge

     of  the   user   •  No  problem  if  user  consents  
  12. First  steps     •  Audit  your  cookie  usage  

      •  Assess  how  intrusive  they  are     •  Update  privacy  policy   •  Signpost  cookie  informaEon  clearly  on  your   site  
  13. Does  your  site  have  user  accounts?   •  Account  login

     classed  as  excepEon   •  Could  have  consent  as  checkbox  when   registering  (like  T&Cs  agreement)  
  14. Do  you  have  an  ecommerce  site?   •  ExcepEon  -­‐

     Shopping  basket   •  View  products  -­‐  Don’t  need  cookies   •  Usually  have  account  login  as  well  
  15. Does  your  site  use  analyEcs?   •  Needs  consent  

    •  Might  be  necessary  for  site  owner,  but  not  for   users   •  Google  AnalyEcs  are  set  as  first  party   •  ‘highly  unlikely  to  prioriEse  first  party  cookies   used  only  for  analyEcal  purposes’   •  SoluEon  needs  to  be  provided  
  16. Does  your  site  use     third  party  services?  

    •  What  do  they  do  with  cookies?   •  Providing  informaEon  a_erwards  is  not   enough  –  e.g.  Google  Ad  Preferences   •  Consider  changing  suppliers   •  Providers  will  have  to  adapt  –  review  regularly