Slashdot Mirror


Writing Privacy Policies – Lessons From Indymedia

somebody-with-too-much-time writes "Privacy policies have recently come up quite a bit on Slashdot. One Indymedia administrator explains why privacy policies are so complicated to understand, shows some examples of good ones, and shows you how to roll your own."

10 comments

  1. Honestly... by religious+freak · · Score: 4, Insightful

    Does anyone read these things? I can say though I may have read over a few, I don't do so on a regular basis.

    It's rather pointless when every single one of them (of the few I've read) says "subject to change at our discretion without notification".

    Does anyone not use Google (for example) because of their privacy policy, or their use of beacons?

    --
    If you can read this... 01110101 01110010 00100000 01100001 00100000 01100111 01100101 01100101 01101011
    1. Re:Honestly... by corbettw · · Score: 2, Funny

      Does anyone not use Google (for example) because of their privacy policy, or their use of beacons?

      I know this one guy who doesn't. I can't reveal his name due to privacy concerns, however.

      --
      God invented whiskey so the Irish would not rule the world.
    2. Re:Honestly... by Kingrames · · Score: 2, Funny

      You mean Joe?

      --
      If you can read this, I forgot to post anonymously.
    3. Re:Honestly... by vux984 · · Score: 2, Interesting

      Does anyone not use Google (for example) because of their privacy policy, or their use of beacons?

      Yes. I don't avoid google entirely; their search engine is too useful, but I block their scripts, and don't use a single one of their services.

      Ok ok... I do have a gmail account (along with other webmail accounts) that I use from time to time to confirm that an html newsletter I send (yes, to double-opt-in-subscribers) renders correctly, but that's it.

    4. Re:Honestly... by story645 · · Score: 1

      Does anyone read these things?

      Yes, but only forum ToS's, and even then it's so that I can explain why something's not allowed. Forums that don't use a boilerplat ToS tend to have really clear and understandable ones cause it's less of a headache if a mod can just quote the ToS when banning someone.

      --
      open source modern art: laser taggi
  2. Privacy != Security by Zero__Kelvin · · Score: 3, Funny

    "You mean Joe?"

    I know his password !!! ...

    --
    Guns don't kill people; Physics kills people! - John Lithgow as Dick Solomon on Third Rock From The Sun
    1. Re:Privacy != Security by Kingrames · · Score: 1

      Well, knowing is half the battle.

      --
      If you can read this, I forgot to post anonymously.
  3. Dupe: CmdrTaco doesn't read Timothy's posts by Anonymous Coward · · Score: 0

    That's no surprise. The bigger question is why Firehose didn't catch the dupe.

  4. privacy by mlc · · Score: 3, Informative
    Here is a lesson from Indymedia on how to really protect users' privacy: http://riseuplabs.org/privacy/apache/

    Odd that the author of the linked article seems not to use it.

  5. tenth psot by Anonymous Coward · · Score: 0

    !toow