Privacy policy
Last updated: 8 September 2026
Data requested by the diagnostic form
Name, work email, company, country, operating challenge, and preferred contact channel, with optional role, company size, and current-system fields. Phone is required only when phone or WhatsApp is selected.
How form data is processed
The same-origin form reaches a Cloudflare Worker and then the locale-specific HubSpot form. This includes filtered campaign tags and a referring-page path with its query and fragment removed. Its sole purpose is to assess and respond to the request. Application logs contain no name, email, phone, or challenge text.
Abuse protection
The endpoint uses a honeypot, request-rate limit, and random idempotency reference. The browser keeps only that reference in session storage; Cloudflare keeps its salted hash and state without form fields. An uncertain outcome remains until operational reconciliation so it is never resubmitted automatically. A network address may be used transiently as a hashed rate-limit key and is not added to the lead record.
Analytics are disabled
This build loads no analytics tool. If Plausible is enabled in production, events are limited to page, language, placement, and campaign—never form data.
Calculator
The ERP seat-cost calculator runs in your browser and does not send the values you enter.
Processors, retention, and rights
Cloudflare processes transport and protection and HubSpot processes sales requests under the applicable account settings and agreements. We retain data as long as needed to assess the request, respond, and perform legitimate follow-up, then delete or anonymize it when that need ends or after a valid request, unless law requires retention. Access, correction, or deletion requests go to the official email below.
Contact and data rights
For access, correction, or deletion requests: [email protected]