Pre-start records can contain far more than a ticked checklist. They may include photos, hours or kilometre readings, operator activity, and information tied to specific vehicles, plant, and equipment, so security becomes part of the buying decision once those records move into software.
Asset Manager Pro applies documented controls to data in transit, stored information, passwords, organisation accounts, backups, and offline access. For an operations manager or IT reviewer, those controls provide specific points to assess rather than relying on broad claims that fleet data is simply “secure”.
Protect Data While It Moves and While It Is Stored
Inspection information moves between field devices and the Asset Manager Pro platform as operators submit records and managers access them. Asset Manager Pro uses Transport Layer Security (TLS) encryption for data in transit, protecting information while it travels between the device and the service.
Data at rest is also encrypted. That covers the other side of the information lifecycle: records stored within the platform rather than actively moving across a network.
These controls address different exposure points. Encryption in transit protects communication with the service, while encryption at rest protects stored data, giving an organisation two concrete security measures to include in its technical review.
Passwords Are Hashed Rather Than Stored as Plain Text
Account credentials deserve separate attention because password handling is different from encrypting inspection records. Asset Manager Pro uses bcrypt hashing for passwords rather than storing them as readable plain text.
Hashing is a one-way credential-protection method used to verify a password without needing to retain the original password in readable form. For a business evaluating the platform, that provides a more useful security fact than a vague assurance about password protection.
It does not remove the organisation’s responsibility for sensible account practices. Users still need appropriate passwords and controlled access to the accounts they are authorised to use.
Organisation Data Is Kept Separate
A cloud platform serving multiple businesses needs to maintain boundaries between their records. Asset Manager Pro isolates data by organisation so one organisation’s asset and inspection information is separated from another organisation’s data.
That control is relevant when the platform contains operating records for vehicles, plant, sites, operators, and pre-starts. The business is not placing its information into one shared operational view with unrelated Asset Manager Pro customers.
Within its own account, the organisation can still determine which operators work with particular assets. That is an access-management function inside the organisation rather than a substitute for the platform-level separation between organisations.
Backups Add Another Layer to Record Protection
Inspection records can accumulate quickly once pre-starts become part of daily operations. Asset Manager Pro uses automated daily backups, with backups retained for 30 days.
For a buyer reviewing data protection, the useful questions are therefore concrete: how often backups are taken and how long those backups are retained. Asset Manager Pro provides defined answers to both.
Backups should still be understood for what they are. Their presence supports data resilience, but it should not be turned into a promise that no information could ever be lost or that every recovery scenario will have an identical outcome.
Hosting Can Be Considered During the Buying Process
Asset Manager Pro provides a choice of hosting region, adding another consideration for organisations reviewing where their operational records will be hosted. The specific region selected can form part of an internal IT, governance, or procurement discussion before wider rollout.
The platform should not be given unsupported certifications or data-residency claims simply because hosting choice exists. The relevant decision is whether the available hosting arrangement satisfies the organisation’s own requirements once the current options have been reviewed.
That keeps the security conversation factual. Hosting region, encryption, password handling, account separation, and backups can each be considered on their own merits rather than being bundled into an undefined promise of total protection.
Offline Access Has Its Own Device Safeguards
Asset Manager Pro’s offline-first design creates a security question that many conventional office systems do not face: what happens when an operator needs access without being connected to the service?
After an operator has logged in online and configured offline access, Asset Manager Pro uses a four-digit PIN for offline unlocking. The PIN is hashed and stored only on that device rather than being kept as readable text.
After five incorrect PIN attempts, the cached offline login is wiped. If the operator moves to a new phone, they need to log in online and configure a new PIN rather than carrying the cached offline access automatically to another device.
These controls support the specific way Asset Manager Pro is intended to work in low-signal environments. They protect the local access mechanism without changing the organisation’s responsibility for controlling its physical devices and user accounts.
Security Controls Follow the Record From Field to Office
The security picture becomes more useful when viewed alongside the actual Asset Manager Pro workflow. An operator may complete a pre-start, add a photo, and enter hours or kilometres against an asset before that information becomes part of the record managers review.
When connectivity is available, TLS protects data moving between the device and the platform. Stored records are encrypted at rest, while organisation isolation maintains a boundary between separate customer accounts.
That makes the controls easier to evaluate in context. They apply to the same field-to-office records the business is considering moving away from paper forms, spreadsheets, and separate image files.
Data Can Still Leave the Platform When Required
Protecting records does not mean locking an organisation into one interface. Asset Manager Pro allows admins to export asset, scan, and operator data as CSV or PDF.
That portability can matter during governance reviews because businesses may have their own requirements for retaining, analysing, or transferring records outside the operational platform. Export provides a defined route for taking supported data out when another internal process requires it.
The ability to export should be considered alongside access controls rather than as a contradiction to them. Authorised administrators can work with the organisation’s records outside Asset Manager Pro when necessary, while the business remains responsible for how exported files are subsequently stored and shared.
Ask Security Questions Before the Fleet Is Fully Loaded
Security review is most useful before an organisation has moved its whole fleet and inspection process into a new platform. Operations, IT, and management can identify the controls they need to understand while the proposed rollout is still manageable.
For Asset Manager Pro, that review can cover TLS encryption in transit, encryption at rest, bcrypt password hashing, organisation-level data isolation, daily backups with 30-day retention, hosting-region choice, and offline PIN controls. Those are specific product characteristics that can be checked against the organisation’s own requirements.
The review can also identify questions that belong to the business rather than the software. Device management, staff access policies, internal handling of exported records, and approval requirements remain decisions for the organisation adopting the platform.
Frequently Asked Questions
How does Asset Manager Pro protect data in transit?
Asset Manager Pro uses Transport Layer Security encryption for data moving between devices and the platform. Stored data is also encrypted at rest.
These controls protect two different stages of the record lifecycle: information being transmitted and information being stored.
How does Asset Manager Pro store passwords?
Asset Manager Pro uses bcrypt hashing for user passwords rather than storing passwords as readable plain text.
Password hashing forms part of the platform’s credential protection, while individual organisations remain responsible for appropriate user access and account practices.
Does Asset Manager Pro back up inspection data?
Asset Manager Pro performs automated daily backups and retains backups for 30 days.
That provides a defined backup schedule and retention period for organisations assessing how their asset and inspection records are protected.
How is Asset Manager Pro offline access protected?
Asset Manager Pro uses a four-digit PIN after offline access has been configured. The PIN is hashed and stored only on the device, and five incorrect attempts wipe the cached offline login.
A new device requires an online login and a newly configured PIN. This keeps offline access tied to the device on which it was established.
Put the Security Controls Through Your Own Review
Security due diligence is stronger when it starts with specific controls instead of a general promise that operational data is protected. Asset Manager Pro gives businesses documented measures to assess across encryption, credentials, organisation separation, backups, hosting, and offline device access.
Book a live 7-minute demo and include your security and data-handling questions alongside the fleet workflow you want to see. Reviewing those controls against your organisation’s own requirements gives operations and IT a firmer basis for deciding whether Asset Manager Pro is ready for a wider rollout.
