Disclaimer
Companion documents: Terms of Service; Data Processing Agreement; Privacy Policy
Last updated: September 17, 2026
This Disclaimer is published by Finsweet Inc. ("Finsweet"), the provider of the Consent Pro service (the "Service"). It is a public summary provided for transparency and supplements, but does not replace or modify, the Terms of Service and the Data Processing Agreement between Finsweet and Customer. If this Disclaimer conflicts with the Terms of Service or the Data Processing Agreement, the Terms of Service and the Data Processing Agreement govern. Capitalized terms not defined in this Disclaimer have the meanings given in the Terms of Service.
1. No legal advice. Consent Pro is software. Finsweet is not a law firm and does not provide legal advice. Nothing in the Service — including its default configuration, tracker categorisations, generated policy or notice text, documentation, or support communications — constitutes legal advice or an assurance that Customer's use of the Service satisfies any legal obligation. Customer is responsible for obtaining its own advice on whether its configuration and deployment meet the requirements applicable to it.
2. Customer's implementation and configuration. Finsweet is not responsible for non-compliance arising from Customer's implementation, configuration, or operation of the Service, including: placement, wording, or language of the banner as configured by Customer; category assignments Customer accepts, overrides, or publishes; scripts, tags, pixels, or tag-manager containers that fire independently of the Service's blocking logic; installation of the Service's script in a manner inconsistent with Finsweet's documented setup instructions, including asynchronous loading that allows other scripts on the page to execute before the Service's blocking logic initialises; deployment on properties, subdomains, or regions outside the configured scope; failure to re-publish a configuration after change; and continued reliance on a scan result after the site has changed. Separately from Customer's own implementation errors, even a correct installation is subject to the known limitations of automatic detection and blocking described in ToS §3.5, including browser discovery and preloading of page resources, whether the request begins before or after the Service's blocking logic initialises, and requests that automatic blocking does not intercept, including requests made with fetch, XMLHttpRequest, or sendBeacon, or by an image constructed in script.
3. What Finsweet does not disclaim. Nothing in this Disclaimer excludes or limits Finsweet's responsibility for defects in the Service itself, including failure to record a choice validly submitted through the banner, failure to apply a blocking rule as configured (other than the known limitations of automatic blocking described in ToS §3.5), failure of the banner to behave as documented on load, or loss or corruption of consent records held by Finsweet. Consistent with ToS §3.4, blocking behaviour during a Service outage or period of unavailability depends on how a tracker is configured to be blocked: trackers Customer has manually tagged for blocking, or gated on Finsweet's consent-management trigger in a tag-manager container, are designed to remain blocked without the Service being reachable, while trackers that rely on the Service's own automatic detection and blocking may run, since the client-side script cannot identify or block them without the Service being reachable. Finsweet does not warrant that any non-essential tracker will remain blocked during such an outage or period of unavailability. Consistent with ToS §3.5, automatic detection and blocking is also not a guarantee that every tracker, request, or resource will be intercepted before it begins. Even where the client-side script is installed correctly, a browser may discover, preload, or otherwise initiate a network request for a page resource before the Service's blocking logic has initialised, or for a resource further down the page after that logic has initialised and before the Service can intercept the element, and a third party that receives such a request may process data or set cookies. Automatic blocking also does not intercept a request the page or a script makes without loading such an element, including a request made with fetch, XMLHttpRequest, or sendBeacon, or by constructing an image in script and setting its source; such a request can be made after that logic has initialised. Finsweet does not warrant that automatic blocking will prevent every pre-consent request, and is not responsible for a pre-consent request that a browser initiates for a page resource, whether before or after the Service's blocking logic has initialised, or for a request that automatic blocking does not intercept, including a request made with fetch, XMLHttpRequest, or sendBeacon, or by an image constructed in script. Customer is responsible for determining whether this behaviour is appropriate for its Properties, applicable laws, and risk requirements, and for implementing any additional safeguards it considers necessary. Finsweet's responsibility for such defects is governed by the Terms of Service and the Data Processing Agreement.
4. AI-assisted features. Parts of the Service use AI models supplied by a third party to propose categories and purpose descriptions for detected trackers and to assist in completing configuration forms, as described in Terms of Service §7. AI-assisted output is provided for Customer review and may be incomplete, inaccurate, or inappropriate for Customer's particular circumstances. Finsweet does not warrant the completeness or accuracy of AI-assisted categorisations, purpose descriptions, or configuration suggestions. Customer is responsible for reviewing and approving AI-assisted output before relying on it or publishing a configuration. Category assignments may affect how trackers are treated by the Service, including whether consent is required before a tracker is permitted to operate.
5. Consent records. Consent records evidence consent events that were successfully submitted to and recorded by the Service on Properties where the Service is correctly deployed, from the time of deployment. Consent Pro does not warrant that every consent event attempted through the Service will be successfully recorded — for example, if a network interruption or temporary service disruption occurs at the time of submission. Consent records are not a complete record of every signal or interaction relating to an End User, and do not evidence compliance for any period before deployment or for any property outside configured scope. Consistent with DPA §4.2 and ToS §8.8, consent records also do not currently evidence whether a Global Privacy Control signal was received or applied to the choices recorded. Customer remains the controller of Consent Data and remains responsible for demonstrating valid consent under Art. 7(1) GDPR.
6. Non-excludable liability. Nothing in this Disclaimer, the Terms of Service, or the Data Processing Agreement excludes or limits liability that cannot be excluded or limited under applicable law, including liability for death or personal injury caused by negligence, fraud or fraudulent misrepresentation, and non-excludable statutory rights of consumers and data subjects under applicable law.
For contact and data protection officer details, see the Privacy Policy (§10, Contact).