The agreement places an affirmative technical obligation on Customer to prevent the transfer of any visitor Personal Data beyond the defined Permitted Personal Data categories (IP address, cookie ID, behavioral data, technical data) to Contentsquare, using blocking Scripts or other available tools across all relevant areas of Customer Sites and Apps.
This analysis describes what Heap's agreement states, permits, or reserves. It does not constitute a legal determination about enforceability. Regulatory applicability and practical outcomes may vary by jurisdiction, enforcement context, and individual circumstances. Read our methodology
This provision places the technical and operational responsibility for data minimization on the Customer rather than Contentsquare, covering keystroke data, prefilled form data, HTML-displayed data, and API error logs. Failure to implement blocking mechanisms creates both contractual liability under Section 9.2 and potential regulatory exposure under applicable data protection laws.
Under this clause, Customer bears the affirmative obligation to configure and maintain technical controls that prevent Contentsquare from receiving visitor Personal Data beyond IP addresses, cookie identifiers, and behavioral data. The agreement states that if non-Permitted Personal Data is processed, Contentsquare may delete broader Visitor Data in the remediation process.
Cross-platform context
See how other platforms handle Customer Obligation to Block Non-Permitted Personal Data and similar clauses.
Compare across platforms →"Customer agrees and acknowledges that the CS Service is not intended for the processing of any Personal Data of Visitors other than the Permitted Personal Data. Therefore, Customer shall prevent the transfer of any Personal Data of Visitors (other than the Permitted Personal Data) to Contentsquare, including, but not limited to, by implementing the appropriate blocking Scripts as stated in the CS Documentation or by using other available tools and methods, on such relevant areas of the Customer Site(s) and browser back-end where Personal Data of Visitors (other than the Permitted Personal Data) may be: (a) collected through Customer's use of the CS Service (e.g., via cookies, JS or API Error logs or other network communication);(b) inputted by a Visitor (e.g., through keystrokes); or (c) displayed (e.g., prefilled, data within the HTML).Excerpt from Heap's Contentsquare Master Service Agreement
1) REGULATORY LANDSCAPE: This provision directly engages GDPR data minimization obligations (Article 5(1)(c)) and purpose limitation requirements, as well as the e-Privacy Directive's requirements regarding cookies and similar technologies.
Enforcement risk, jurisdiction flags, contract triggers, and due diligence action items.
Get the weekly coverage letter
Companies change their terms without announcing it. We capture governance documents, compare each new version with the last, and publish what changed, with the source text behind it. One email a week on what we found and what we could not reach.
This provision places the technical and operational responsibility for data minimization on the Customer rather than Contentsquare, covering keystroke data, prefilled form data, HTML-displayed data, and API error logs. Failure to implement blocking mechanisms creates both contractual liability under Section 9.2 and potential regulatory exposure under applicable data protection laws.
Under this clause, Customer bears the affirmative obligation to configure and maintain technical controls that prevent Contentsquare from receiving visitor Personal Data beyond IP addresses, cookie identifiers, and behavioral data. The agreement states that if non-Permitted Personal Data is processed, Contentsquare may delete broader Visitor Data in the remediation process.
No. ConductAtlas is an independent monitoring service. We are not affiliated with, endorsed by, or sponsored by Heap.