Privacy at EyRoad.

This policy covers the EyRoad website. It does not describe a deployed product, because EyRoad has no commercial product in service. When the commercial EyRoad device exists, it will have its own product privacy documentation, published before anyone uses it.

If you join early access, we collect the name and email address you give us, plus any optional details you choose to add: phone, country, city, vehicle, how often you drive and your main interest.

If you request a fleet pilot, we collect your company, contact person, business email and fleet details, plus anything you write in the use case or notes fields.

If you contact us, we collect your name, email and message.

In all three cases we also record the language you used, the campaign parameters in the link you arrived through (utm_source, utm_medium, utm_campaign), and the website that referred you. We do not record the full URL you came from.

We use it to contact you about EyRoad and nothing else. We do not sell it. We do not share it with advertisers. We do not use it to build a profile of you.

If analytics are enabled on this site, they record how the site is used — which pages are viewed, which buttons are pressed — with IP anonymisation where the provider supports it. Names, email addresses, phone numbers and anything you type into a form or into the assistant are never sent to analytics.

The assistant answers from a fixed set of approved information about EyRoad. Your question is processed to select an answer and is not stored as part of a profile, and its text is not sent to analytics.

Lead information is stored in a managed database used only by EyRoad. Access is limited to people working on EyRoad who need it to reply to you.

You can ask us what we hold about you, ask us to correct it, or ask us to delete it. Write to us using the contact page and we will act on it.

EyRoad is being designed around privacy-conscious driver monitoring, including investigation of on-device processing approaches that can reduce unnecessary transmission of driver imagery. Storage, connectivity, retention and fleet-data architecture are not finalised. We will not promise how driver imagery is handled until that architecture is decided — and when it is, it will be published here in plain language.

If this policy changes we will update the date at the top of the page.