A cookie is simply a technology for remembering something about you.
Without cookies, a website is like a goldfish who loses its memory every time you visit a new page. Once you visit a new page, it doesn’t remember who you are.
Now this can be a good and a bad thing. Without any memory, a website can’t do a lot of stuff. It can’t let you log in, because it forgets who you are. It can’t let you buy anything, because it forgets what you’re buying.
Cookies aren’t automatically good or bad, but it’s worth understanding what you can do about them.
You can turn them off completely, which is a bit like banning all music to prevent another Justin Bieber album. Many websites simply won’t work.
A better option would be to turn off 3rd party cookies, which will stop most websites from sharing information about you. Some browsers – like Safari – do this automatically.
And finally, you can take a deeper look into any websites which concern you. Most websites have policies that explain what they do, if you care to look.
Find out how to disable cookies.
The formal stuff
2.1 This document was created using a template from SEQ Legal.
3. About cookies
3.1 A cookie is a file containing an identifier (a string of letters and numbers) that is sent by a web server to a web browser and is stored by the browser. The identifier is then sent back to the server each time the browser requests a page from the server.
3.2 Cookies may be either “persistent” cookies or “session” cookies: a persistent cookie will be stored by a web browser and will remain valid until its set expiry date, unless deleted by the user before the expiry date; a session cookie, on the other hand, will expire at the end of the user session, when the web browser is closed.
3.3 Cookies do not typically contain any information that personally identifies a user.
4. Cookies that we use
5. Cookies used by our service providers
5.3 We use a security plugin (WordFence) to protect the site from hacks and other attacks. No personal data is stored, but we capture IPs to protect ourselves from brute force attacks. The cookie is: wfwaf-authcookie-(followed by random string)
5.4 The “__cfduid” cookie is set by the CloudFlare service to identify trusted web traffic. It does not correspond to any user id in the web application, nor does the cookie store any personally identifiable information.