Your report should be useful. Your data handling should be clear.
This notice explains how PageAnalyser handles report requests, what Matomo analytics collects on the Arranz-hosted service, and how we use that information.
This notice describes the Arranz Group Ltd hosted service. The self-hosted package is shipped with Matomo disabled, it sends no analytics requests and shows no analytics-cookie modal until its operator configures an HTTPS Matomo endpoint. A self-hosted operator must update the controller details and analytics disclosures before enabling tracking.
Last updated: 19 November 2026
Who runs PageAnalyser
PageAnalyser is owned and operated by Arranz Group Ltd. Arranz Group Ltd is the data controller for PageAnalyser report requests: it decides why and how this information is used. For privacy questions or requests, email info@arranzgroup.com.
What we collect
When you request a report, we collect your name, company, business email address, and the public page URL. We use this information to review the submitted page and deliver your report by email. Your contact details are not sent to the public website you submit. Report and status emails are transactional; PageAnalyser does not send marketing emails.
To submit the form, you must check “I have read and accept the Privacy Policy.” The form verifies this acknowledgment to process your report request; we do not retain a separate consent record.
The web server receives your connection IP address to handle the request and may keep connection logs according to its own settings. PageAnalyser does not store the IP address, user-agent hash, or form-source record. It uses a random request reference and a short-lived hash-only receipt to prevent duplicate queue jobs; the receipt contains no form values.
PageAnalyser checks one public page using its initial HTTP response and a browser-based page assessment. It also makes one bounded request for robots.txt on the host that served the initial HTML response. The report can include the requested and checked URLs, selected DOM evidence such as an element excerpt, page title, headings, metadata, response timing, the robots.txt response status and same-host sitemap declarations, structured-data types, PageAnalyser category scores and lab metrics, and browser assessment version details. Sitemap files are not fetched or validated. The full HTML response and rendered page are processed temporarily, not stored. A viewport screenshot is captured in memory during the check; the image is not saved in the report.
PageAnalyser sends selected public page text to Arranz Gnome on the service server to draft the executive summary and interpret findings. This text is limited to the page title, description, selected headings, and visible link or button labels, with URLs and obvious contact details removed. The submitted URL, your contact details, and cookies are not sent to Gnome. It also receives finding IDs, fixed finding titles, priority and confidence labels, evidence kinds, and bounded numeric measurements. It cannot change measured values, source evidence, priority, other assessment data, report order, or the conditional starter scope. A report is sent only if Gnome returns a valid interpretation.
Your name, company, business email, and page URL are stored briefly in a protected server-side queue so report processing can continue if you close the page. The server processes requests in order through PageAnalyser browser checks, Arranz Gnome interpretation, PDF creation, and email. Processing can fail if a page cannot be checked or a service component is unavailable; when possible, PageAnalyser emails a status update. Requests not started within two hours expire the next time the worker runs. If the worker is interrupted, a limited recovery attempt may be made. The report and PDF are temporary and removed after processing. A hash-only request receipt, which contains no contact details, URL, findings, or PDF, is kept for up to 24 hours to prevent duplicate jobs if the browser loses its confirmation. The email does not contain a browser report link or report-access token. The request form also uses a short-lived security cookie; see Cookies.
To diagnose service failures, PageAnalyser writes a technical event log to a file outside the public website folder. It records a random reference, timestamps, processing stage, safe error codes, runtime and process results, durations, output sizes, and sanitized error output from failed child processes. Failed form requests may show a support reference; successful confirmations do not. Stack traces, server paths, and child-process diagnostics stay in the protected log. Diagnostics remove submitted form values, URLs, email addresses, configured credentials, and common token patterns. They can still include technical details from the failed process. The log remains on the server until an administrator archives or clears it.
On the Arranz-hosted service, PageAnalyser loads Matomo analytics from analytics.arranz.org on each public page. When no cookie choice has been saved, the first page view is sent without Matomo cookies before the choice appears. If you choose “Mandatory cookies only”, page views and link or download activity continue to be measured without optional cookies. If you choose “Allow optional cookies”, Matomo may use cookies to recognise returning visits.
The JavaScript tracker may collect the page address and title, referring page and campaign details, date and time, local time zone, browser language and type, operating system and device type, screen resolution, external-link clicks, file downloads, page generation time, and your IP address. It also checks browser capabilities, such as supported plugins, and creates a short-lived browser configuration identifier. The tracker code reports page views and link or download activity. It does not read or send report form fields, your name, company, business email address, the URL you submit for analysis, or report contents. It does not configure advertising, cross-domain tracking, form analytics, or session recordings.
Matomo tracking requests include your IP address. Matomo can mask IP addresses, and its default is to mask the last two bytes before storage, but we have not verified the setting on this instance. If IP-based geolocation is enabled, the full address may be used for the location lookup unless the instance is configured to use the masked address.
How we use your information
- To provide your report. We use the submitted page URL and contact details to check the page, create a report, and email it to you. A queue receipt confirms acceptance for processing, not successful email delivery.
- To protect the service, legitimate interests. The form uses same-origin and CSRF checks, a hidden honeypot field, and public-address validation for submitted pages. The scanner also limits its requests to protect the service and the sites it checks.
- To apply your required privacy acknowledgment. We verify the checkbox before starting the report. This version does not retain a consent record.
- Report communications. PageAnalyser sends transactional messages about your report request and does not send marketing emails.
- To improve PageAnalyser, Matomo analytics. We use page-view, link, and download information to understand which pages attract visits, how visitors arrive, and where they navigate or leave. Your cookie choice controls optional analytics cookies, it does not turn off cookieless tracking. We do not use Matomo for advertising or cross-site profiling. The lawful basis and settings for cookieless analytics must be confirmed for the active deployment.
We do not use the report to evaluate you or make decisions about you.
What happens when we check a page
After you submit a URL, PageAnalyser checks one public page and may follow up to three redirects to reach it. It separately requests robots.txt from that page’s initial HTML host, with a five-second time limit and a 128 KB response cap. It does not follow a robots.txt redirect to another host. The check reads the initial response, opens the page in a temporary browser profile, and runs one mobile browser lab assessment. The browser may request public page resources from the hosts referenced by that page. Those website and resource hosts may record the requests in their own logs. The scanner sends your email address and other form details to none of those hosts.
The PageAnalyser report check uses a bounded browser review and records selected DOM evidence, scores, and measurements. It does not use your logged-in browser session, crawl the whole site, or access private analytics or search accounts. The temporary browser profile is discarded after the scan. PageAnalyser creates a PDF and attempts to email it to the business email address you provided using the SMTP provider configured for that deployment. The PDF is removed from temporary server storage after the delivery attempt. The checked website does not receive your contact details. The report is a first pass; see Terms for its limits.
Arranz Gnome receives selected public page text (title, description, selected headings, and visible link or button labels, with URLs and obvious contact details removed), normalized finding data, and bounded numeric evidence. The configured service's access controls and any service logs depend on the active deployment and must be confirmed with the service operator.
Who may handle the information
PageAnalyser runs on web-server and hosting infrastructure selected for the active deployment. The providers may handle information on Arranz Group Ltd’s behalf to run and secure the service. The provider, processing region, and any applicable transfer safeguards depend on that deployment. Contact info@arranzgroup.com for the current hosting details.
When report email delivery is configured, the selected SMTP provider receives the business email address and delivers a message with the PDF report attached. If the page check cannot be completed, PageAnalyser may email an update. SMTP acceptance is not a guarantee of inbox placement. The provider, processing location, and retention of message metadata and attachments depend on the deployment’s SMTP account. Contact us for its current details.
Normalized finding data is processed by Arranz Gnome on the service server. Its access controls and log retention are deployment settings; contact us for the current details.
The PageAnalyser technical event log is stored on the service server outside the public website folder. Only the service process and authorized server administrators should have access to it.
Matomo tracking requests go to the instance at analytics.arranz.org. Arranz Group Ltd uses that instance for PageAnalyser analytics. The hosting provider, processing region, and any transfer safeguards are not identified by the tracker code and must be confirmed with the analytics administrator.
We do not sell report-request information or use Matomo analytics for advertising.
The web server may keep separate connection logs, including IP addresses. Those logs are configured outside PageAnalyser; contact us for the current log-retention period.
How long we keep it
PageAnalyser keeps the contact details and URL in the protected queue while the job is pending or processing, then removes them after completion, terminal failure, or expiry. A worker outage can delay that cleanup until the worker next runs. Temporary scan output and the generated PDF are removed after the delivery attempt. The mail provider may retain the delivered message and attachment under its terms and settings. Web-server, Gnome, SMTP, and Matomo logs are managed separately and may have their own retention periods.
The technical event log is kept on the PageAnalyser server until an administrator archives or clears it. It contains diagnostic events and references, not the report request or report content.
Matomo keeps visit records according to the settings of the instance at analytics.arranz.org. Those settings and retention periods are separate from PageAnalyser’s report processing.
Your choices and rights
Depending on the data-protection law that applies to you, you may be able to ask us for a copy of your information, correct it, delete it, restrict its use, object to its use, or receive a portable copy. PageAnalyser does not currently send marketing emails or save the optional marketing checkbox choice. You can contact info@arranzgroup.com if you have a privacy request.
When no cookie choice has been saved, the first page view is sent before the choice appears. You can choose “Mandatory cookies only” or “Allow optional cookies”. Mandatory cookies only keeps page-view and link measurement running without optional cookies. The footer’s “Cookie settings” control lets you change your choice later. This version does not provide an on-site control to stop cookieless analytics. To object to analytics processing or ask us about visit records stored in Matomo, email info@arranzgroup.com.
If you are in the UK, you can raise a concern with the Information Commissioner’s Office. If you are elsewhere, you can contact the data-protection regulator where you live.
Keeping information safe
The application uses same-origin request checks, a CSRF token, a hidden honeypot field, and bounded public-page scanning. The report is delivered as an email attachment rather than through a browser access link. Server, Gnome, and SMTP access controls are configured separately when the service is deployed. No online service can promise that information is completely risk-free.
