We’ve all been asked a thousand times recently if we “consent to cookies”. It does seem a bit unreasonable to assume that everyone is in-the-know and can make that decision.
So, what is a Cookie anyway?See our work
Are cookies bad? If they’re not, then why would there be so much fuss about them in the recent GDPR legislation?
In its simplest form.
An HTTP Cookie is a small piece of data stored on your computer by your web browser. A cookie is created from instructions in website code.
Give me an example.
How are they used?
Cookies are often used to ‘remember’ a user’s preferences or presence on a website. When a website is loaded, the cookies created on that page are used to personalise the content and experience of the page. Cookies can also be used to track a user’s journey on a website, revealing browsing habits and potentially personal information.
An analogy of cookies could be a restaurant with numbered tables. The appropriate food (content) is delivered to each table (user) based off a table number (cookie). It is possible for each table to receive individual treatment due to the unique table number. This unique table number does mean however that the restaurant staff can track the entire order history of a table and deduce other things such as whether the table may want dessert.
The analogy above highlights both the functionality advantages and potentially negative privacy impacts cookies can have. An online shop can save items in a basket for you to purchase all at once thanks to a cookie, but this same technology is also used by social media sites such as Facebook and affiliate marketing networks to track what websites you visit and then target you with relevant advertising based off your browsing interests. Because this data is tied to your cookie on your device, this makes this data personally identifiable and subject to legislation.
Do you accept cookies?
About the author.
Rob Strover is a Web Developer at Fuel Integrated.