Merkle Inc
This captured Texas registry record for Merkle Inc aggregates recorded filing fields, including consumer-rights, data-category, and contact information; it does not independently verify current provider practices or request outcomes.
Legal context: Texas Business & Commerce Code Chapter 510 (redesignated from Chapter 509, effective September 1, 2025) sets the registration and disclosure framework. Verify the live registry and provider route before relying on this snapshot.
Registry contact
- Website
- https://www.merkle.com
- Privacy contact
- americas.dpo@dentsu.com
- Address
- 7001 Columbia Gateway Drive , Columbia , Maryland , 21046 , United States
- Texas Registration ID
- 20240149
What Merkle Inc's Texas filing tells you
Merkle Inc's captured Texas registry entry identifies the business as a data broker under Texas Business & Commerce Code Chapter 510 (redesignated from Chapter 509 effective September 1, 2025), filed with the Texas Secretary of State. Registration ID: 20240149. This record aggregates the broker's own filing fields; it does not independently verify current operation, legal identity, or the current request route.
On the categories of data it processes and transfers, Merkle Inc's filing states: "(a) Name (b) Email address (c) Phone number (d) Mailing address (e) General location (Identifiers: personal data; professional or employment related information) (f) Commercial and Preference Information (responses to surveys, details of your attendance at our events, interest in our services, information about our contact history with you and your other transactions and preferences) (g) Technical…" This is the broker's own filed description, not an independent audit of its current practices.
Merkle Inc lists a consumer-rights page at its filing: https://www.merkle.com/en/privacy-policy/data-product-privacy-notice.html. Depending on your location and the request type, the CCPA or EU GDPR may separately provide deletion rights; a Texas filing field does not by itself determine legal coverage or outcome.
The filing reports 1 security breach in its disclosure: No Consumers effected - like most large organizations today, we’ve had to investigate unusual activity on our network on a few occasions. In this case, once the unusual activity was identified, we were generally able to quickly take action to respond by initiating our incident response protocols so we could immediately contain and address the issue. This is a self-reported registry field, not an independent current incident assessment.
To review a removal request, check Merkle Inc's current provider route and the captured registry contact at americas.dpo@dentsu.com. Cite CCPA § 1798.105 or GDPR Article 17 only if that authority applies to your circumstances. OfflistMe can generate an email draft using the recorded contact; you review it and send it from your own account.
Generate requests in under 60 seconds
Generate requests for 1000+ brokers, including Merkle Inc, for $9
FAQ
What does Texas's registry record say about Merkle Inc?+
The captured Texas registry entry identifies Merkle Inc as a data broker record filed under Business & Commerce Code Chapter 510. Registration ID: 20240149. Verify the live Secretary of State record before treating the contact fields as current.
Does Merkle Inc provide a consumer-rights route?+
Merkle Inc's Texas filing lists a consumer-rights page at https://www.merkle.com/en/privacy-policy/data-product-privacy-notice.html. Depending on your location and the request type, the CCPA or EU GDPR may separately provide deletion rights; check the current page before relying on it.
How do I remove my data from Merkle Inc?+
Review Merkle Inc's current provider route and the captured registry contact at americas.dpo@dentsu.com. Cite CCPA § 1798.105 or GDPR Article 17 only if it applies to your circumstances. You can use OfflistMe to generate a pre-filled request draft for $9, then review and send it yourself.
Other Texas registered brokers
Entries in this captured Texas dataset. Each is a separate registry entry; legal obligations and current request routes should be checked individually.