Enquiries and support requests
When you submit a form, we store your name, email address, company or team, request category, optional topic, message, and the page from which you submitted it. A submission identifier prevents a retry from creating a duplicate record. A reference number lets the team locate your request.
This information is used to review and respond to your enquiry, investigate website or documentation issues, and manage the request’s status. Do not send credentials, personal information about other people, production documents, or confidential customer records. The website does not accept file uploads.
After a successful submission, the website displays a reference number for your enquiry. Keep it for any follow-up with the team.
Optional aggregate analytics
Analytics are off by default. You can allow or withdraw them through Analytics preferences in the footer. When enabled, the website records counters for a small set of events—page views, demo and documentation visits, searches, and successful form submissions—grouped by known page and UTC day.
The analytics table does not contain names, email addresses, form contents, search terms, IP addresses, visitor IDs, referrers, or user-agent strings. Search runs in your browser using a public index; search queries are not sent to a search service. Analytics requests are suppressed when your browser sends Do Not Track or Global Privacy Control.
Your theme and analytics preferences are stored locally in your browser. These preference values are not visitor identifiers and are not used to link visits. You can remove them by clearing this site’s local browser storage.
Infrastructure and abuse protection
Cloudflare hosts the website and its request database. Serving and protecting an internet request necessarily involves network information such as an IP address. The form and event endpoints use Cloudflare’s short-lived rate-limiting mechanism to limit abuse; the application does not put IP addresses in enquiry or analytics tables.
Infrastructure and security processing are separate from optional analytics. Cloudflare may process technical request metadata as part of hosting and protecting the service. The application does not log form payloads. Access to saved enquiries is through authorized Cloudflare operator access; there is no public ticket lookup endpoint.
Retention and your questions
Daily cleanup is configured to remove enquiry records older than 90 days and old aggregate counters from the application database. Removal happens during the scheduled cleanup, rather than at the exact instant a record reaches that age. Provider recovery copies may follow their own retention schedule.
To ask about access, correction, or deletion of information you submitted, contact the team through the website form and include your request reference if available. Do not include another person’s private information. The team may need to confirm that the request concerns your own submission before acting.
Links to ERP.AI or other external sites take you to separate services with their own notices. This notice covers the website. API data handling is subject to the applicable service agreement.
Missing a detail or found a problem?
Send a documentation question →