Hello,
I work for Capital One and I am reaching out because we are seeing instances of our authentication tags being blocked inadvertently.
Capital One is a leading bank in North America that provides banking, credit, and financial services to consumers and businesses.
As a bank, we are required to perform strong authentication to comply with US and Canadian banking regulations. Authentication tags are critical for keeping customer information secure.
The tags in question are used exclusively for authentication and fraud prevention. If they are blocked on our site (capitalone.com), it interferes with our ability to detect fraudulent access patterns and degrades the customer experience by creating additional friction.
These are the specific filter rules that are matching two of our tags:
https://github.com/easylist/easylist/bl ... c.txt#L125
Code: Select all
||bfp.capitalone.com^https://github.com/easylist/easylist/bl ... c.txt#L147
Code: Select all
||capitalone.com/collector/
I appreciate the intent of EasyPrivacy and would be interested to know the project maintainers’ perspective about potentially easing these two rules?
Sincerely,
Salman
