Know where an enquiry goes before sending it.

This notice describes enquiry data handling and operator responsibilities. The receiving API, notifications, retention and attachment support depend on the deployed configuration.

Information you choose to provide

The enquiry form collects the name, email, phone number, company, project type, budget, target date, description and privacy consent you enter. Optional fields are identified in the form. These details support a response and requirement assessment. Submission timing, an idempotency identifier and anti-abuse checks are also processed to limit abuse and duplicate delivery.

Provide only what the discussion needs. Do not submit passwords, keys, access tokens, identity documents, payment details or third-party data you are not entitled to share.

Transmission and recipients

The website receives the form and any attachment at /api/website/leads. In local mode it saves the enquiry in the operator’s private database and the attachment in restricted storage. If the operator configures an external receiving service, the website server forwards the submission to that service.

Once the enquiry is accepted, the website displays a reference number. If a connection or receiving service fails, follow the message on the form to check the submission status.

Attachment restrictions

The current form accepts at most one PDF, PNG or JPEG file. The server also checks that its type matches its contents. The size limit comes from operator configuration and is shown using the value returned by the API; the server also limits total request size. Passing browser validation does not guarantee acceptance by the receiving API.

Do not attempt uploads when the receiving API does not support attachments. Remove sensitive personal information and trade secrets first. Receipt of a filename, size or type is not evidence that the file contents were uploaded.

Notifications, access and retention

When email notifications are enabled, the mail service sends the enquiry and any attachment to an address configured by the operator. Access should be limited to people handling the enquiry, and mail and storage credentials should be protected.

Retention periods, backup locations and deletion procedures for enquiries, attachments and operational logs are set by the operator according to actual purposes and applicable requirements. No unimplemented fixed period or automatic deletion is promised. Logs should avoid secrets and unnecessary form contents.

Browser preferences and external services

Language and theme choices may be stored in cookies or local browser storage to remember display preferences. Analytics, anti-abuse measures, mail delivery and other providers depend on the live deployment and their disclosed use.

Unverified tracking settings are not described as disabled, and external provider policies are not presented as promises made by this website.

Access, correction and deletion requests

Use the enquiry route to request access, correction or deletion, identifying the email address previously used and the scope of the request. Do not add sensitive identity documents merely to make the request. The operator should verify the connection to a record and respond according to actual storage and applicable obligations.

Before submitting, ask the operator if you need confirmation of recipients, retention or file handling. This notice should be updated when deployment settings or processing practices change.