Comments on Privacy is UX

9 Reader Comments

Back to the Article
  1. It would be sweet of you guys to replace the “(here, here, here, here, here, and here)” set of links in the 3rd paragraph with domain names or something, for screen-readers and mobile users.

    As far as privacy goes, is there any data on how people feel about the “green lock” for HTTPS? Yellow or broken ones?

    Copy & paste the code below to embed this comment.
  2. I’m in total agreement with this. There should be a workflow designated for handling sensitive data that is overseen by someone who is qualified to handle this data and understands the risks. For example this could be the HIPAA ambassador who makes sure that are requirements are met using a checklist. All data used in testing should be fake, and in a separate database, and only people who need to see any real data should ever have access to see it.

    To sum it all up:

    Least Privileged Access
    Proper Workflows that follow PCI/HIPAA compliance
    Separate data for testing vs real use cases
    Proper Auditing Process for validating security (Be Proactive)

    Copy & paste the code below to embed this comment.
  3. Alex, thank you for writing this article.  There is so much good information in here.

    Copy & paste the code below to embed this comment.
  4. Thank for this article, great!

    Copy & paste the code below to embed this comment.
  5. Great article. I actually read it several times, which is for me pretty rare thing to do these days. I wanted to also say that I have mentioned you at my latest blog post (https://goo.gl/4KxjEa). I hope you appreciate it.

    Thanks and keep up the good work!

    Copy & paste the code below to embed this comment.
  6. I noticed myself with the same issues many times. I’ve personally started using Men

    Copy & paste the code below to embed this comment.
  7. Sorry, commenting is closed on this article.