Privacy Statement

This Privacy Statement is about information a visitor gives the public Lumin website, and about what the website code does with it.

Operational data that a customer controls inside Lumin software is different. Access to that software and those services is governed by separately executed agreements, including a Master Services Agreement and applicable order forms. This Privacy Statement does not describe that processing, and it does not incorporate those agreements.

A review of the website source found no analytics library, tag manager, or cookie-setting code. This Privacy Statement therefore does not list cookies or analytics tools. If none are implemented, there is no inventory to publish.

The site names Las Vegas as global headquarters, Belfast as technology and engineering, and San Francisco as a planned strategic expansion, not an established office. It does not publish a street address or a privacy contact email, so neither is stated here.

The demo form requires a first name, last name, work email, phone number, company, and company website. Job title and industry are optional. Industry choices in the code are Casinos & Gaming, Enterprise Security, Public Safety, and Other. The form does not ask for a street address.

The browser checks those fields, then sends them to a server action. The server checks them again. The page shows a request as received only after HubSpot confirms the contact and inquiry note. When a company website is provided, HubSpot must also confirm the company. If HubSpot does not confirm that, the page shows an error and the visitor can submit again. The code does not save the request in the browser's session storage or in server memory.

A confirmed request is written to HubSpot portal 247079814 as a contact matched on the work email. When a company website is provided, a company is matched on that domain and linked to the contact. An existing company name is not replaced. Blank optional fields are not written over existing contact values. The inquiry note is linked to the contact, and to the company when one was matched. The note records the provided details, the website as the lead source, and the time of submission. The code does not create a deal. The HubSpot access token is read from the server environment. If that token is missing, the page does not treat the request as received.

Retention periods, subprocessors, individual-rights procedures, and a privacy contact are not in the repository.