Cookie-autodelete: Concerns related to Ambiguity of Privacy Policy

[frankclaassens]

NOTE: I have read the FAQ and consulted the documentation without remedy

Hi,

Firstly, thank you for developing this very useful Firefox addon and for maintaining support.

Interpretation

For the purpose of this discussion:

• Cookie-AutoDelete: software source code as held within the following github repository: Cookie-AutoDelete / Cookie-AutoDelete

• installation: an action performed by a person by means of downloading Auto-CookieDelete from the release page or Firefox Add-ons page

• modifiable: anything which, upon an act, changes from on thing to another.

• personal information: ANY information, irrespective of it being identifiable or not, that results from the usage by a person of Cookie-AutoDelete after installation.

• Privacy policy page: a github.com wiki page that allows anyone with authority to perform an act on the modifiable content as presented on the landing page of this link: Privacy Policy

• Privacy policy refers to all modifiable content, including but not limited to text, images and all content contained on a landing webpage should a 3rd party url/link be included in the modifiable content on the Privacy policy page. Unless otherwise corrected, the Privacy policy page contains all content relative to the subject matter of privacy and protection of personal data. Any content or 3rd party policies not included on the Privacy policy page that has an interest or seeks access to the personal information of a person protected by the Privacy policy will be in violation of the Privacy policy and subjected to legal action.

Issue: Ambiguity in Privacy Policy

I wish to highlight the ambiguous nature of the Privacy policy on the Privacy policy page.

The Privacy policy 09 October 2019 19:21 (BST) states the following modifiable content:

Cookie AutoDelete does not collect or send data out to any "home" server.

The GDPR states the following on privacy policies: (comprises of best-practices in general)

"provide people with a privacy notice that is: In a concise, transparent, intelligible, and easily accessible form. Written in clear and plain language, particularly for any information addressed specifically to a child."

The use of words in quotes on a privacy policy is discouraged. Do not use them unless you are fully aware of their meaning, and if you are, then it should be removed from the Privacy policy for it to be concise. Should you continue to refer to "home" then you need to clearly define by means of interpretation what "home" means and what is covered by "home".

Consider the following:

"home:" a place or premise of residence

You install Cookie-AutoDelete on your computer at "home". The current Privacy policy may be interpreted as not sending data to any "home" server, but you may be sending data to a dodgy 3rd party. Also, data and personal information are not the same thing. If you don't have the time to look up the legal definition of these words, then consider keeping the privacy policy as concise as possible. The less words you use, the better. But if you opt for this route, make sure it is concise, clear and unambiguous.

Suggested Remedy: Keep it short, concise, clear and easy for anyone to understand

If Cookie-AutoDelete does not collect or send data, then the following can be used instead:

1. Cookie-AutoDelete does not collect the personal information of the person using Cookie-AutoDelete. All other data and information not considered as personal information are hereby bind.

1. Cookie-AutoDelete does not collect the personal information of the individual using Cookie-AutoDelete. All other data and information not considered as personal information are hereby bind.

1. Cookie-AutoDelete does not collect data on the device it is installed. All other personal information and information not considered as data are hereby bind.

You get the picture 😄 The first sentence should be clear, and concise. Avoid using and/or in the first statement. If you wish to add additional information to a statement (as I did above) when the use or and/or is _fine_ but should be limited.

[kennethtran93]

Hmmm...

Depending on the settings used in CAD, it technically collects information (cookies, possibly localstorage) if you desire to undo that this web extension performed. However, there is no outside communication from the web extension itself. That's where the "home" portion comes in as it is localized to the computer it is installed in, and external applications (e.g. CCleaner) may be able to pick up the cookies labelled as browser cookies even though firefox itself doesn't see it.

I can change it to reflect what you suggested if you so desired.

[kennethtran93]

Updated Privacy Policy a bit. Hopefully made it less ambiguous. May need better wording on some parts.
In the meantime, I will close this issue. Feel free to comment on this for revisions.

[frankclaassens]

Updated Privacy Policy a bit. Hopefully made it less ambiguous. May need better wording on some parts. ...

@kennethtran93 will check it out. Apologies for only getting back to you now. Had a bunch of personal issues that took up months of my time but that’s mostly resolved now.

_{Sent with GitHawk}

[frankclaassens]

Privacy policy looks much better! Thanks for picking this up @kennethtran93

_{Sent with GitHawk}