Privacy Policy

The exact information depends on the workflow and features selected by the company. Manager-managed trips can contain office-entered results without phone proof. Mixed and Driver-assisted trips may contain additional checkpoint evidence.

• Account and profile information, including name, work email, contact number, job title, organization membership, role, and authentication records.
• Company and billing information, including company profile, plan, vehicle count, invoice and subscription references, and payment status. Fleetlyf does not store complete card details.
• Vehicle and driver records, including registration or license references and expiry dates entered by the company.
• Trip, route, schedule, mileage, fuel, maintenance, issue, review, correction, notification, and audit records.
• Checkpoint latitude, longitude, accuracy, time, and related device metadata when a person intentionally captures a checkpoint.
• Odometer scan text, confidence, confirmed mileage, correction reason, and temporary validation image when phone-camera proof is used.
• Technical and security information such as IP address, browser or user-agent information, session activity, request identifiers, and server logs.

Fleetlyf does not continuously track a driver and does not run background GPS surveillance. Location is requested only when a user chooses a checkpoint, issue-location, or Share current location action. During an active trip, each current-location share replaces the previous shared snapshot and the snapshot is removed when the trip is completed. Start, end, break, and issue location evidence follows the applicable fleet record and retention workflow. A nearby saved-location label is only a display convenience.

An odometer image is temporary validation evidence. It is available while the submitted mileage needs management review, then Fleetlyf clears the image reference and deletes the file when management accepts the result. Unattached temporary uploads are scheduled for deletion after 24 hours. The confirmed mileage, OCR result, correction reason, decision, and audit history remain as structured records.

• Create and secure accounts, sessions, organizations, roles, and access controls.
• Plan trips and preserve office-entered or driver-submitted operational records.
• Connect mileage, fuel, maintenance, issues, decisions, corrections, and printable vehicle history.
• Surface factual differences, incomplete evidence, upcoming deadlines, and records that require human review.
• Provide support, prevent misuse, investigate errors, monitor reliability, and satisfy legal obligations.
• Administer trials, subscriptions, invoices, and payment access.

Fleetlyf applies deterministic rules to route distance, duration, mileage continuity, fuel evidence, checkpoint accuracy, OCR confidence, maintenance dates, and related records. Fuel and maintenance patterns can appear in reports, reminders, or Needs action; qualifying trip and issue records can enter a manager queue. These rules do not accuse a driver, impose employment consequences, or make the final operational decision.

Plus customers may request a plain-language Fleetlyf explanation. Selected structured record context may be sent to the configured Google Gemini service for that request. A manager still reviews the underlying evidence and records the final decision.

Fleetlyf is designed for customers in supported countries worldwide. Fleetlyf shares information only as needed to operate the service, follow a company instruction, complete a transaction, protect the service, or comply with law. Fleetlyf and its providers may process information outside the user’s or customer’s country. Where applicable law requires a transfer mechanism or additional safeguards, Fleetlyf will use the appropriate contractual or legal measure.

• Infrastructure and database hosting providers used to run Fleetlyf.
• Google services used for sign-in, maps, routes, geocoding, and requested Fleetlyf explanations.
• Email delivery providers used for invitations, verification, support, and operational notices.
• Dodo Payments and its payment partners for checkout, subscriptions, invoices, and the customer billing portal.
• Professional advisers, authorities, or other parties when disclosure is legally required or necessary to protect rights and security.

Fleet records are retained while the customer maintains the workspace and for a reasonable period needed for account recovery, audit continuity, disputes, security, and legal obligations. Expired or unpaid workspaces can become read-only rather than silently losing their records.

Temporary odometer images follow the shorter lifecycle described above. Session, security, billing, and server logs are retained only as long as reasonably needed for their operational, security, accounting, or legal purpose. Fleetlyf securely deletes or anonymizes information when it is no longer required, subject to lawful retention and the rights of other people whose records are connected.

Depending on location and applicable law, a person may request information about processing, access, correction, objection, restriction, portability, erasure or blocking, or may withdraw consent where consent is the legal basis. Fleetlyf may need to verify identity and coordinate with the company that controls the relevant fleet workspace.

• Use Fleetlyf’s profile, company, correction, export, archive, and feedback tools where available.
• Contact the company that created the fleet record for workplace-record requests.
• Contact Fleetlyf at support@fleetlyf.com for an account or privacy request.
• Raise a concern with the relevant privacy regulator, including the Philippine National Privacy Commission where applicable.

Fleetlyf uses organization-scoped authorization, role controls, secure password hashing, HttpOnly sessions, request validation, rate limiting, security headers, audit history, structured server logging, and restricted access to temporary evidence. No service can promise absolute security, so customers must also protect accounts, devices, invitations, and exported records.

Fleetlyf uses an essential session cookie to keep users signed in and local browser storage for preferences such as appearance and selected workspace state. Fleetlyf does not currently use advertising cookies. If non-essential analytics or advertising technology is introduced, this policy and any required consent controls will be updated first.

Fleetlyf may update this policy when the product, providers, or legal requirements change. Material changes will be dated and communicated through the service or account contact information where appropriate.