A clear approach to your registration.
This page describes the early-access website. It does not certify or describe security controls for the separate operational application.
Only the information needed to start.
The owner form asks for contact and business details, fleet size and province. Additional interests and notes are optional. We do not ask for payment credentials, passenger records, employee documents or account passwords.
Validation and abuse controls.
Submissions are checked on the server, with limits on field lengths and request size. The form uses a hidden spam trap, request-origin checks and rate limiting. A bot challenge can also be enabled. These measures reduce abuse; they are not a guarantee that every unwanted submission is stopped.
Private registration records.
Registrations are saved through a private server-side destination. This site has no public lead directory or lead-download endpoint. A success message appears only after storage accepts the submission. If saving fails, the form lets you retry.
Deployment matters.
The public website must be served over HTTPS. Access to stored registrations, backups and retention must be managed by the service operator. No security certification or independent security audit is claimed. The marketing site does not establish the security of future booking or staff-account features.
Questions about your details.
Read the Privacy Policy for uses and choices. You can reply to FleetLK communications to request correction or removal. Contact options are listed when available.