Which websites may be scanned, what is forbidden, how the scanner behaves, how to ask to be excluded, and enforcement.
Copyright © 2026 Safe and Informed S.R.L. All rights reserved.
This Acceptable Use Policy ("AUP") forms part of the ConsentVeil Monitor Terms of Service (the "Terms") between the Customer and Safe and Informed S.R.L. ("Safe & Informed", "we", "us"). Capitalised terms have the meaning given in the Terms. It sets out which websites may be scanned with ConsentVeil Monitor (the "Service"), what the Service may be used for, and what is forbidden.
1.1 The Service exists to let an organisation observe, in a repeatable way, what the public pages of its own website do before, during and after a visitor's consent choice.
1.2 Permitted uses are: checking your own website; checking a client's website with the client's written authorisation; comparing behaviour across browsers and locales; and producing evidence for your own internal review or for your legal adviser.
1.3 Any use outside that purpose is prohibited unless we agree to it in writing. If you are unsure, ask us at [email protected] before ordering.
2.1 You may order a Scan only of a Website for which you have completed Verification under section 3 of the Terms by exactly one of four methods:
(a) DNS TXT record (dns_txt): the verification token we send you placed in a DNS TXT record at _consentveil.<host>;
(b) Well-known file (well_known_file): the token placed in a file at /.well-known/consentveil-verify.txt on the Website (read over TLS only, at the address the scanner checked, without following redirects, at most 4096 bytes);
(c) Domain e-mail (domain_email): the Order sent from an e-mail address at the Website's registrable domain, which our staff pass to the scanner so that it can check that the domain matches;
(d) Written order (written_order): a signed or otherwise documented order from the organisation responsible for the Website, recorded by reference.
Our scanner will not proceed unless exactly one of these methods has been recorded, and the Report names the method used.
2.2 Verification is a technical check, not a legal one. Completing it does not make a Scan lawful if you are not in fact entitled to have the website scanned. By ordering, you authorise Safe and Informed S.R.L. to perform the public-page loading, consent interactions, observations and screenshots described in the agreed Methodology on the domains and pages identified in the Order. You confirm your authority to grant that permission, including any necessary client or hosting permissions. This does not authorise access to unrelated systems, authentication or circumvention. A material breach occurs where you neither control the Website nor hold the required written authorisation.
2.3 Agencies and service providers may order a Scan of a client's website only with the client's written authorisation covering the loading, interactions, observations and screenshots described in section 2.2, which you keep for the life of the engagement and provide to us when we ask for it. An agency holding that authorisation is authorised for the purposes of section 2.2 and Terms section 5. If the client withdraws the authorisation, tell us at once.
2.4 Pages. Scans are limited to public pages served under the verified domain. A cross-domain navigation of the page itself is recorded and refused.
2.5 Exclusion register. We keep a register of domains whose verified owners have asked us not to scan them. Our staff check every Website against it before every Scan, and the scanner refuses an excluded domain. A verified domain owner may ask to be added to the register by e-mail to [email protected] (section 6).
You must not order a Scan, or attempt to use the Service, to:
3.1 scan any website, domain, host or page you do not control and are not authorised to have scanned, including through a verification record you placed without the owner's authority;
3.2 scan a competitor's website, a supplier's, a customer's or any other third party's website without that party's written authorisation;
3.3 scan internal networks, private address ranges, loopback or link-local addresses, cloud-metadata endpoints, intranet hosts, staging or administrative systems not meant to be public, or any host reachable only from inside a network;
3.4 probe for vulnerabilities, test security controls or perform any form of penetration testing. The Service is not a security scanner;
3.5 have the scanner authenticate into, circumvent or bypass paywalled or otherwise access-controlled areas, or send us credentials, session cookies or tokens with the aim of reaching such areas;
3.6 use Findings or screenshots to collect, profile or identify visitors of any website, or to build datasets of personal data;
3.7 present a Report, score or Finding as a certification, seal, guarantee or statement of legal compliance, or alter a Report so that it no longer shows all Findings, limitations and the Methodology reference;
3.8 use the Service to harass, intimidate, defame or exert pressure on any website operator, or publish Findings about a third party's website as if they were authoritative;
3.9 resell or offer the Service to others as a service of your own without our written agreement;
3.10 use the Service in breach of any applicable law, including computer-misuse, data-protection and unfair-competition law.
4.1 The scanner loads one public page at a time, waits for the page to settle, and performs only the interactions described in the Methodology: locating and clicking consent controls (accept, reject, withdraw). It may also open the banner's settings layer and press keyboard keys (Tab, Escape) to measure whether the banner can be operated without a mouse; it reads the toggles in that layer and never changes them, and it never uses an accept, reject, save or close control for those measurements. On sites that implement the IAB TCF API or Google Consent Mode, it reads the consent signal's state in its own browser (counts and flags only, never the consent string or vendor identifiers). It does not modify source code, CMS content or server configuration. Ordinary page loads and interactions with consent controls may create server or CDN logs, cookies, consent records, analytics events or similar operational records on your side. The scanner does not sign in, create accounts, complete business forms or place orders. It does not authenticate into, circumvent or bypass paywalled or otherwise access-controlled areas.
4.2 The scanner identifies itself with a dedicated User-Agent header containing ConsentVeilMonitor/<version> (+https://www.safeandinformed.com/monitor), so that a website operator can recognise Monitor traffic. The string is printed in every Report, including the PDF.
4.3 For HTTP and HTTPS requests intercepted by the browser-context route (the document, every frame, every sub-resource), supported request types are judged against the same rules as the scan target before the scanner fetches them: local, private, link-local and cloud-metadata addresses are refused, and a navigation of the page itself to another registrable domain is refused. Requests eligible for fetching are fetched by the scanner's own client with redirects disabled, so the browser does not make the connection; a redirect has its destination judged hop by hop before it is followed, and a refused hop is aborted before any connection and listed in the Report. Media, event-stream and unsupported request types are refused without fetching; WebSockets are refused separately; service workers are blocked. For requests eligible for fetching, hostname checks use fresh DNS resolution by default, and the scanner's client resolves the name again when it fetches. These are application-layer controls, not a complete browser-network sandbox or socket-level IP pinning: a name that answers differently to two consecutive lookups can still reach a different address than the one checked, and browser traffic outside these routing controls (WebRTC) is removed in every scanner context by a script whose required protections are verified on a startup probe, in the supported browser configurations only, and, on the documented server deployment, by host-level egress rules bound to the scanner's user that reject the listed prohibited address ranges while those rules remain intact. Chromium runs only as Playwright's bundled headless shell. WebKit is supported. Firefox is used only where available, included in the Order and passing the required startup checks. Browser-channel and executable-path overrides are refused. Engine settings supplement the checked initialisation protections where available. Asking us to route a Scan to such an address is a breach of section 3.3 whether or not the attempt would succeed.
4.4 If a website or its provider blocks the scanner, the Scan is reported as inconclusive. You must not ask us to evade such blocking, and we will not do so.
5.1 Reports and evidence may contain personal data of visitors to, or persons named on, the scanned website. You are the controller of that data, or the processor acting for its controller, under the Data Processing Agreement. Share it only with people who need it and delete it when you no longer need it.
5.2 Findings refer to third-party services by host name and classification. A classification is a technical observation from packaged provider lists; it is not an allegation against the third party, and you must not present it as one.
6.1 If you believe the Service has been used to scan a website without authorisation, write to [email protected] from an address at that domain or otherwise reasonably evidencing your authority. Tell us the domain and the approximate time. We investigate, stop any Scan concerned where appropriate, and reply within 10 business days.
6.2 A website operator may ask us not to scan its domain. Write to [email protected] from an address at that domain, or complete one of the verification methods in section 2.1 for it. Once we have verified that you are responsible for the domain, we add it to the exclusion register and the scanner refuses it until you lift the exclusion in writing.
7.1 We may investigate a suspected breach of this AUP and may review the Order, the verification record, the exclusion register and our scan logs for that purpose.
7.2 Depending on the seriousness of the breach we may warn you, decline further Orders, or end the Order or subscription with immediate effect. Ordering a Scan of a Website where you neither control it nor hold the required written authorisation (section 2.2 and 2.3) is a material breach and is grounds for immediate termination. Where we terminate for unlawful use, we explain the reason where the law permits and refund the portion of the fees that corresponds to the part of the Service not performed. A Consumer's paid period is never forfeited automatically. Any retention of fees for the part of the Service performed applies to the extent permitted by law.
7.3 We may report unlawful conduct to the relevant authorities and may preserve relevant records for that purpose. Where a breach causes loss to a third party, the indemnity in the Terms applies to Customers acting for purposes relating to their trade, business, craft or profession.
We may update this AUP. The "Last updated" date above changes and the current version is available at its published URL. Changes apply to Orders placed after the effective date; for a running subscription we give at least 30 days' notice of material changes by e-mail.
Safe and Informed S.R.L. Aleea Slt. Adrian Cârstea, Nr. 13, Bl. 37, Sc. 2, Et. 8, Ap. 141, Sector 3, Bucharest, Romania Email: [email protected]