3 ms·

If you go to the Chase login page, it loads js from demdex.net. DemDex "captures behavioral data on behalf of Websites and advertisers and stores it in a 'beha

• type0 7y ago
  > this shit could harvest banking credentials?? It's not that it happens or could happen, the problem is that when credentials are leaked the user gets all the blame: "not our fault, you probably had a virus on your device", and most users will believe it.
  • giancarlostoro 7y ago
    We need a sort of GDPR law but not as... Broad or unclear as it is. The problem is big tech companies would never draft a bill that puts them in a bad spot. For the People has become For the Corporations and it really does suck.
    • AstralStorm 7y ago
      GDPR is actually very narrow, specific and clear, as far as privacy laws go. The only unclear thing is the distinction between processor, manager and collection of data. That's because it's narrow in scope.
• danielhughes 7y ago
  Demdex is a DMP from Adobe that is used by companies to manage their first-party data so this particular example with Chase is very likely not an example of third-party ad serving abuse. Chase would have presumably put Adobe through a security review during an RFP process and would have no reason to harvest their own customers' login credentials. Their use case is probably something benign like wanting to segment customers for targeting based on their site usage patterns. Chase has different login pages but the one I'm looking at doesn't appear to have any third-party JS loading from advertisers.