- From: François Légaré <flegare@gmail.com>
- Date: Wed, 12 Aug 2015 13:42:39 -0400
- To: public-privacy@w3.org
- Message-ID: <CAGhQHrj5vyyd0oz+pdgVBRKfp4w494ZEXGgCcKfG2J1_Hz7oyQ@mail.gmail.com>
Hi I work for a big telecom company in Canada that currently give various sponsorship for mental health organisations. Part of the sponsorship is making sites and mobile applications to help individual get online help and access information and resources that are often sensible. One example is http://www.kidshelpphone.ca/ they provide anonymous phone line for kids that may have issue or problem in their family. This lead to a sensitive problem, a kid visiting this site need to know how to clean browsing history since a adult seeing the browsing history might challenge the kids about the visit and lead to more stress or bigger problems. They did explain on the site header how to flush history and train visitor about the anonymous tab, this isn't perfect at all, because it really entirely on the user actions and the assumption that he read and understood the section. Since not all internet user are tech savvy and are aware of the anonymous tabs, so my suggestion for the W3C would be the following: A head meta tag that could help define sensitivity level of the online html content. This tag once detected by the browser could apply various policy to increase anonymity and reduce potential problems, ideally default policies would implicitly insure higher privacy for the end users. For instance browser that detect the meta tag could automatically go in "anonymous mode" and don't track browsing history, remove cached content, etc. This will insure a more anonymous browsing experience for such site for users that are less aware of the already available privacy features. Content rating meta tag to some extends could be used but this is a bit far fetch but could be less involving since tags already exist. Of course I'm quite sure, site with adult content would also be like such features but this is not really the issue I'm trying to resolve at this point. According to some of the W3C members this is a valid place to submit this suggestion, I hope this will be well received. Regards, Francois
Received on Thursday, 13 August 2015 13:58:23 UTC