OneView automatically hashes PII and never stores plaintext sensitive data, ensuring built-in privacy compliance. No actions required.
While having flexible PII handling options seems convenient, it creates unnecessary risks since sensitive data can be accidentally transmitted or stored in plaintext.OneView takes a zero-tolerance approach to privacy. We enforce automatic PII hashing that cannot be disabled - eliminating human error and ensuring consistent compliance across all data processing.This is especially critical with ad_user_data and ad_personalization consent requirements. With OneView, you simply need to:
Send the correct consent status for each conversion event
Include PII data, which can be either:
Pre-hashed by you (if you prefer to hash before sending)
Sent in plaintext (OneView hashes it instantly at the edge, before data reaches your home region)
All personally identifiable information - including emails, phone numbers, names, and addresses - is automatically hashed using before any processing or storage occurs.
What PII does OneView automatically hash?
OneView does not inspect custom fields for PIIs. Please check the implementation guides.
OneView automatically detects and hashes emails, phone numbers, names, addresses, IP addresses, and any other field containing personally identifiable information before processing or storage.
Traditional implementations require complex consent management systems to handle multiple cookies from different vendors and services.OneView simplifies privacy compliance by using only one master cookie instead of multiple tracking cookies.This dramatically reduces consent management complexity, as you only need to handle consent for a single cookie rather than managing consent for dozens of different tracking pixels and their associated cookies.
