Want to read Slashdot from your mobile device? Point it at m.slashdot.org and keep reading!

 



Forgot your password?
typodupeerror
Privacy The Internet Your Rights Online

W3C Proposes Unified "Do Not Track" Privacy Standard 93

Posted by Unknown Lamer
from the federal-legislation-due-in-2013 dept.
In his first submission, kierny writes "A W3C working group is crafting two standards, due out by summer 2012, to enable consumers to opt out of online tracking. Numerous big players are involved, including Google, Facebook, IBM, Mozilla, Microsoft, plus the Center for Democracy and Technology, Electronic Frontier Foundation, and Federal Trade Commission. The first standard is Tracking Preference Expression, 'to define a standard for a how a browser can tell a website that a user wants more privacy,' says W3C working group co-chairman Dr. Matthias Schunter of IBM Research. 'So you send a signal, and you get a response from the website which tells you that the request has been honored.' The second standard, meanwhile, is the Tracking Compliance and Scope Specification, which details how websites should comply with Do Not Track preferences. But, don't expect Do Not Track to be active by default."
This discussion has been archived. No new comments can be posted.

W3C Proposes Unified "Do Not Track" Privacy Standard

Comments Filter:
  • by EdIII (1114411) on Wednesday November 16, 2011 @01:52AM (#38070956)

    You can't compare the two.

    Telemarketers (Debt Collectors are not bound by it) are required to show proof that they checked the number against the list within 14 days of contact. If they cannot, and they made contact, it is a 50k USD fine the last time I checked per infraction .

    Of course, the only way the FTC knows about it is complaints. What does the FTC have? Phone records. Everything they need to assess the fine, and they love to do it.

    This is completely different, and completely retarded, if it has no such teeth. How does the consumer even know to complain in the first place?

    The consumer does not know:

    - What information I am storing server side in my databases.
    - If I am even processing the privacy requests in the first place. That's all new code. Once that standard is in place I will have to go back to every website I am responsible for and enact the new policies.
    - If, and when, I sold the information to 3rd parties.
    - If, and when, I was hacked and the information copied. Unless new laws mandate disclosure.
    - If, and when, affiliates were provided the information.

    It is kind of hard to compare the two together. This new standard puts an awful lot of responsibility on website developers and owners, of which many, are ill equipped to comply with new standards like this immediately. There is a significant percentage that will not even upgrade to a new web server capable of processing the requests.

    What about foreign web servers? At least the FTC can nail telemarketers in the US regardless of where the call came from as long as the profit was made in the US.

Old programmers never die, they just branch to a new address.

Working...