PRIVACY NOTICE

How we handle website inquiry data.

This notice explains the current EVBBC website data flow in plain language: what is collected, why it is used, where it goes and how to request access, correction or deletion.

Current system notice — updated 11 August 2026

The short version

You choose what to send

The quotation form sends your work email and the project selections shown in the configurator.

A backend receipt is created

The site stores the submission in its protected inquiry database and may forward it to the configured sales destination.

You can make a data request

Use the request form on this page for access, correction or deletion. Identity and the exact record are verified before action.

01 — DATA COLLECTED

The form sends only the contact and project context needed to handle the request.

For a quotation inquiry, the site records the work email you enter and the configuration assembled from your selected site type, destination market, charging spaces, AC/DC mix and connectors.

The receipt also records the page and language used, submission time and an operational business-email signal. The privacy-request form below records your email and selected request type.

Work email
Selected project and equipment context
Source page and language
Submission timestamp
Request type when using this page

02 — PURPOSE

We use the data to receive and follow up the request.

The data is used to create a backend receipt, understand the requested charging project, prepare a response or quotation, route the request to the responsible operator and troubleshoot delivery failures.

The website does not treat a page view or button click as a received inquiry. A success message appears only after a backend destination acknowledges receipt.

03 — STORAGE AND SHARING

Inquiry receipts stay in protected project systems.

The primary receipt is stored in the site database. If a sales Webhook is configured, the same email and configuration may also be sent to that configured sales destination.

Access is limited to the project owner and designated sales operators using protected administration credentials. Hosting, database and delivery providers process data only as needed to operate those systems.

04 — RETENTION AND DELETION

The current system has no automatic deletion schedule.

Stored receipts remain in the protected database until the controller completes an approved record-level deletion. Working exports are removed after the related review or approved handoff is complete.

A deletion request does not delete data automatically. The operator first verifies the requester and the exact receipt, performs the controlled deletion and verifies that the record is no longer returned.

05 — YOUR REQUESTS

Ask for access, correction or deletion through the receipt-backed form.

Select a request type and provide the email associated with the inquiry. The form creates a protected receipt so the operator can verify and follow up the request.

Submitting this request adds one minimal receipt containing the email, request type, language, source page and timestamp.

06 — SCOPE AND UPDATES

This notice describes the website system; transaction terms are confirmed separately.

This website notice does not assign one governing jurisdiction to every visitor or transaction. Where governing law or transaction-specific privacy terms apply, they are confirmed in the relevant contract or order documents.

We will update this page when the collection fields, destinations, retention process or approved company policy changes.

PRIVACY REQUEST

Create a privacy request receipt

Choose the request type and use the email connected to the original inquiry.