FleetPulse

Company

Privacy practices for FleetPulse operations data.

FleetPulse handles account, fleet, route, driver, maintenance, integration, and reporting data with clear purpose, access, security, and retention expectations.

This Privacy Policy describes how FleetPulse Operations Pte. Ltd. collects, uses, shares, protects, and retains information when customers evaluate or operate FleetPulse workflows.

Document structure

Plain terms for fleet governance.

This page is written for evaluators, workspace owners, implementation teams, and reviewers who need clear responsibilities before connecting fleet systems.

01

Controller and contacts

FleetPulse Operations Pte. Ltd., 18 Cross Street, #12-104, Singapore 048423, is responsible for the FleetPulse website, evaluation, and service workflows described in this policy unless a customer agreement states otherwise.

FleetPulse maintains APAC operating presence at Treasury Tower, District 8 SCBD, Jl. Jenderal Sudirman Kav. 52-53, Jakarta 12190, Indonesia for implementation and customer operations support.

Privacy, data processing, security, and access-control questions may be sent to privacy@fleetpulse.co, dpa@fleetpulse.co, or security@fleetpulse.co.

02

Information we collect

FleetPulse may collect account and contact information such as name, work email, company, role, authentication status, support communications, and evaluation preferences.

Customers may submit operational data including vehicle identifiers, route details, hub locations, dispatch events, telemetry, driver safety context, maintenance records, fuel transactions, reporting exports, and workflow notes.

FleetPulse may collect technical information such as device, browser, session, log, API, integration, security, and usage data needed to operate, secure, and improve the service.

03

How we use information

FleetPulse uses information to provide dashboards, alerts, workflow queues, implementation support, integrations, customer support, reporting, account administration, and security monitoring.

Operational data is used to help customers evaluate fleet state, route pressure, service risk, fuel variance, driver safety context, and leadership review outputs.

FleetPulse may use aggregated or de-identified information to improve product reliability, analytics quality, implementation methods, support workflows, and platform performance.

04

Sharing and service providers

FleetPulse may share information with service providers that support hosting, infrastructure, analytics, customer support, communications, security, billing, and integration delivery.

Subprocessors are reviewed by purpose and risk category, including cloud infrastructure, authentication, customer support, transactional email, product analytics, observability, and integration transport providers.

FleetPulse does not sell customer operational data. Information may be disclosed when required by law, to protect rights and security, or as part of a business transaction subject to appropriate protections.

Customers control which internal users, teams, and connected systems receive access to operational data through their workspace configuration and role assignments.

05

Security, access, and retention

FleetPulse uses administrative, technical, and organizational safeguards designed to protect information from unauthorized access, loss, misuse, disclosure, or alteration.

Access to operational data should be limited by role, region, workflow responsibility, support need, and the customer's implementation governance model.

FleetPulse retains information for as long as needed to provide the service, meet legal or contractual obligations, resolve disputes, support audits, maintain backups, and protect platform security.

06

Rights, choices, and international transfers

Depending on location and applicable law, individuals may request access, correction, deletion, portability, restriction, or objection related to personal information processed by FleetPulse.

FleetPulse may process information in countries where FleetPulse, customers, or service providers operate, using contractual and organizational safeguards for cross-border transfers where required.

FleetPulse is not directed to children and should not be used to knowingly submit information about individuals under the age required by applicable privacy law.

07

Updates and contact

FleetPulse may update this Privacy Policy to reflect product, legal, security, or operational changes. Material updates will be communicated through appropriate channels.

Customers should route privacy, security, and data-subject requests through their authorized workspace owner or contact FleetPulse directly when appropriate.

Questions about privacy practices can be sent to privacy@fleetpulse.co or to the FleetPulse customer operations contact assigned to the workspace.

Data purpose

Operations

FleetPulse processes data to support dispatch, service, fuel, safety, analytics, and reporting workflows.

Subprocessors

Category reviewed

Infrastructure, authentication, support, email, analytics, observability, and integration providers are reviewed by purpose.

Questions

privacy@fleetpulse.co

Contact FleetPulse for privacy, security, retention, DPA, or data rights requests.

Fleet operations command center with dispatch screens and trucks visible outside.

Governance review

Review governance before connecting systems.

Use the governance review to align legal terms, data handling, access controls, integrations, and retention expectations.

Session output

Governance review brief

Access model

Roles, permissions, and workspace owners

Data handling

Fleet, route, driver, service, and reporting data

Contract review

Terms, privacy, security, and implementation scope

Role based

access model

Purpose led

data processing

Review ready

commercial governance