Giter Site home page Giter Site logo

jkwakman / open-cookie-database Goto Github PK

View Code? Open in Web Editor NEW
194.0 12.0 91.0 1.31 MB

The Open Cookie Database is an effort to describe and categorise all major cookies. All cookie descriptions are saved in a downloadable CSV file. All contributions to the CSV file are welcomed.

License: Apache License 2.0

open-cookie-database's Introduction

Open-Cookie-Database

The Open Cookie Database is an effort to describe and categorise all major cookies. All cookie descriptions are saved in a downloadable CSV file, Google Spreadsheet or browseable and searchable in an html file. All contributions to the CSV file are welcomed.

How to contribute

All contributions are gratefully received. To contribute to the Open Cookie Database, please follow the following contribution guide.

Category Descriptions

The definitions of the categories are as follows:

  • Functional (also known as technical, essential or strictly necessary)
  • Personalization (also known as preferences)
  • Analytics (also known as performance or statistics)
  • Marketing (also known as tracking or social media)
  • Security

Wildcard match

The last column in the database is called "Wildcard match". A 0 in this column means that the cookie name is not a wildcard, and a 1 means that the cookie name is a wildcard.

Where a cookie name is not a wildcard, it means that the cookie name is a fixed string. For example, the cookie name _ga will always be _ga when set by Google Analytics.

However, if a cookie name is a wildcard, it means the exact cookie name may change from one website to another. Thankfully, the cookie name will always match a certain pattern. For example, the cookie _gac_1234 is a wildcard cookie name, because the 1234 part of the cookie name can be any string.

open-cookie-database's People

Contributors

afrancht avatar baudev avatar ecebeci avatar fellyph avatar gagan0123 avatar haleon0 avatar hwgn avatar jkwakman avatar meetinthemiddle-be avatar milindmore22 avatar mitchgreen avatar mohdsayed avatar n3t avatar pareyesv avatar rtbot avatar thierrymaasdam avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

open-cookie-database's Issues

Duplicate Cookies

Hello again,

My tool reported some more duplicated cookies, so I'll pass this info on. Happy to remove/fix them myself through a PR.

  • i (72ac111c-477f-484f-b97d-62870b65ae85 and 3b89dcd0-1da7-4382-8d20-a4c9eb614e00) - once Yandex, once OpenX. This seems to be a genuine double usage.
  • clientSrc (c3a9fc08-a42e-449c-8584-58580baa1e4f & a7d2b130-e322-4f4d-86c4-b2c86e8e7517) - both Salesforce, one 1st Party, one 3rd
  • autocomplete (6cd0e40c-9cfc-4ce7-b9c4-7a312003d1bf & 42219382-45ea-4f39-acfb-6da2df996eda) - as above
  • disco (abcdaa07-7021-4979-a521-2afe3a7f1de3 & 00396982-e60c-4713-aa0c-c00ade38ff8d) - as above
  • inst (461a5ae4-12cb-413e-8c06-3d899fdeb3b3 & 4a3c8234-e9b6-4f5f-bb2e-1943dfe3e95a) - as above

If we normalize Domain-field to be empty to indicate Websites set this cookie to their own domain, I think it's fine to have duplicate names. Just right now, automated parsing of cookies that could be set to anywhere is near impossible to be 100% reliable.
If you agree, I could continue #21 and write a script to replace Advertiser's website domain and similar with empty fields.

Add `HTML Local Storage` and `Tracking Image` beside `Cookies`

There is a misconception that the German "DSGVO" or GDPR in general only need to consider cookie data. All external services and their tracking options are meant within the meaning of the law.

This would require listing not only cookies but also cookie-like techniques: "HTML5 Local Storage" or classic tracking images (Sometimes called: "pixels").

Providers such as Cookiebot etc. already do this.

Would it make sense to include this data here as well?

Non-Cookie entries in the Database

There are currently three non-cookie entries in the DB, starting with Line 163. I suggest removing them as they carry no actual usable information (except that these services use JS Tags?) and may cause unexpected behavior in software utilizing the database.

Edit: Also just found a duplicate on Line 455 / Line 458.

Duplicates

While checking the database I found some duplicates. Each of the following Name-Domain pairs exist twice, with the only difference being the description. Thus, I think that they should be merged.

Name Domain
__atuvc .addthis.com
__atuvs .addthis.com
loc .addthis.com
obuid outbrain.com
sb facebook.com (3rd party)
uvc .addthis.com

Anyway, thank you for your nice work in piling up the database, it is really helpful for making more sense out of some cookies.

Best regards,
Raphael

Wildcard match field

Hi, first of all thanks for the effort to make this useful database.

But when I was checking the csv I've noticed the last column "Wildcard match". I've seen in some cookies like ga that subintentend that in the end of the cookie name could get the code that vary for each client, but How can I know where to complete the absent part? Its not clear for me. Have any insights?

Thanks in advance.

Duplicate Cookies

My tool reported some duplicated cookies, so I'll pass this info on (I can also fix this in a couple of days if nobody else has the time)

  • viewed_cookie_policy is contained twice, with the same information.
  • OptanonConsent is contained twice, with slightly varying information.

Additionally, these cookies are newly added with the same name of another cookie. This was bound to happen eventually (as nobody reserves cookie names), but either way, we might want to consider the implications of this for tools using the database - at least my tool currently searches cookies purely by name and will thus not see the second entry for this cookie.

  • tk_ai is set both by WooCommerce and Jetpack with the exact same purpose. Perhaps we could merge these?
  • dpm, served both by Adobe and demdex - unless one uses the other, this might not be able to be resolved
  • sp by Quantcast and Snowplow. The descriptions hint towards the same use case, which might suggest both services having some sort of overlap in whatever sets this cookie

Open for discussion on how to proceed.

Expand the cookies categories

** Description **
Currently, the Open Cookie Database is listing cookies mainly with the following categories:

  • Marketing
  • Analytics
  • Functional

The suggestion is to expand the categories to:

  • Security
  • Marketing
  • Functional
  • Personalization
  • Analytics

** Motivation **
These categories are designed with the user in mind, aiming to provide a more user-friendly and transparent experience by better-translating cookie usage.

Categories based on Google Cookies policies
https://policies.google.com/technologies/cookies?hl=en-US

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.