Privacy Compliance Information Request

33 views
Skip to first unread message

Bedig

unread,
Jul 7, 2025, 4:02:25 AM7/7/25
to Google Ads API and AdWords API Forum

Hello,
I have a few questions from the DPO regarding the implementation of Enhanced Conversions:

  • Which hashing algorithms are used? Do they ensure irreversibility (e.g., with salting)?

  • Are there any external certifications (e.g., ISO 27701) regarding data security in Enhanced Conversions?

  • How does Google mitigate the risk of re-identification from hashed data?

  • Does the hashing process occur within the logical perimeter of Assidai/Praesidium, or within Google’s systems?

  • What is the exact data retention period for hashed data before deletion? How can we verify that the data has been effectively deleted after matching?

Thank you.

Google Ads API Forum Advisor

unread,
Jul 7, 2025, 10:00:25 AM7/7/25
to bedi...@gmail.com, adwor...@googlegroups.com

Hi,

Thank you for contacting the Google Ads API support team.

Please find the answers to your queries below:

  • Which hashing algorithms are used? Do they ensure irreversibility (e.g., with salting)?

Answer: As per the Normalize and hash user-provided data documentation, the algorithm being used for hashing is SHA256. You can also refer to this Help Center article for more information.

  • Are there any external certifications (e.g., ISO 27701) regarding data security in Enhanced Conversions?

Answer: Please note that your concern is out of scope for our team as our team only provides support for Google Ads API related concerns and technical implementations. In order to help you further, I'm adding another support team for their expertise in troubleshooting your issue. You should receive an email to assist you shortly. 

  • How does Google mitigate the risk of re-identification from hashed data?

Answer: You can refer to this Help Center article for getting an answer to this query.

  • Does the hashing process occur within the logical perimeter of Assidai/Praesidium, or within Google’s systems?

Answer: Please elaborate more on this concern as this query does not seem to be related with Google Ads API. Kindly note that our team as our team only provides support for Google Ads API related concerns and technical implementations. 

  • What is the exact data retention period for hashed data before deletion? How can we verify that the data has been effectively deleted after matching?

Answer: As per this Help Center article, Google Ads data retention policy states that beginning on November 13, 2024, reporting data collected by Google Ads will be available for 11 years. After that period, the data will not be accessible via the Google Ads interface or APIs.

You can send the details via Reply privately to the author option, or direct private reply to this email.

Thanks,
 
Google Logo Google Ads API Team

Feedback
How was our support today?

rating1    rating2    rating3    rating4    rating5
[2025-07-07 13:59:17Z GMT] This message is in relation to case "ref:!00D1U01174p.!500Ht01rhH6C:ref" (ADR-00317682)



Bedig

unread,
Jul 7, 2025, 10:39:10 AM7/7/25
to ads...@forumsupport.google, adwor...@googlegroups.com
Hello, thank you for the prompt response.
The last link to the referenced article is not accessible - could you provide additional sources?
Thank you.

Google Ads API Forum Advisor

unread,
Jul 7, 2025, 1:37:42 PM7/7/25
to bedi...@gmail.com, adwor...@googlegroups.com
Hi,

Could you please confirm whether you are not able to access this Help Center article, this contains the information as 'Beginning on November 13, 2024, reporting data collected by Google Ads will be available for 11 years. After that period, the data will not be accessible via the Google Ads interface or APIs'.

If this is not what you are looking for, provide us with the link that you are not able to access then you can assist you further.

Thanks,
 
Google Logo Google Ads API Team

Feedback
How was our support today?

rating1    rating2    rating3    rating4    rating5

[2025-07-07 17:36:30Z GMT] This message is in relation to case "ref:!00D1U01174p.!500Ht01rhH6C:ref" (ADR-00317682)



Reply all
Reply to author
Forward
0 new messages