Tenant isolation
Server-resolved authorization and row-level isolation scope tenant-bearing access paths through explicit organizational authority.
Security and trust
Operational trust
has to be designed in.
LogiTraq’s security architecture starts with isolation, explicit authority, durable evidence, narrow provider boundaries, and tested recovery paths for operational continuity.
Our security program is organized around documented controls, reviewable evidence, and safeguards that scale with the platform.
Security postureProtected by default
Sensitive actions require verified access and a reliable audit trail, keeping critical work controlled and reviewable.
Defense in depth
Controls around the work and the people doing it.
Security is built into the real operating paths: booking, field evidence, money, exports, support, hierarchy, and offline devices.
Least privilege
Standard roles separate owner, admin, dispatch, office and billing, driver, and read-only work. Sensitive actions require narrower capabilities and stronger checks.
Encryption boundaries
Transit encryption, encrypted host and object storage, protected contact values, and encrypted offline queues reduce exposure across server and mobile paths.
Audit and correction
Material mutations, sensitive attempts, exports, support access, money actions, and policy changes are designed to leave typed, reviewable audit evidence.
Payment separation
Hosted processor fields and payment links keep raw card and bank credentials out of LogiTraq application storage.
Recovery discipline
Backups, restore testing, independent evidence copies, incident roles, and explicit recovery objectives are part of the operational design.
Boundaries that stay visible
Sensitive work gets a narrower lane.
The architecture distinguishes ordinary operations from actions that move money, expose evidence, alter access, or cross organizational scope.
Short-lived access is bound to the right contact and resources for each customer interaction.
Ticket-bound, time-boxed, visible sessions use authority separated from deployment operations.
Scoped, audited delivery includes field masking and spreadsheet-injection protection.
Minimal route horizon, encrypted local state, session expiry, revocation, and controlled purge.
Evidence-led assurance
Clear controls make trust reviewable.
- Specific control scope.Security measures are described by data class and system boundary so reviewers can see where each control applies.
- Protected payment boundaries.Card and bank entry stays within hosted processor surfaces.
- Accountable support access.Support sessions use narrow authority, time limits, ticket context, and reviewable records.
- Aligned security documentation.Architecture, operating controls, and available evidence stay connected to the product as it evolves.
Security questions
Review the architecture behind the product.
A focused security discussion can cover tenant isolation, identity, offline data, payments, audit, retention, backups, and incident readiness.
Security review
Bring the controls that matter.
Tell us about your operating model, customer commitments, and review priorities through the secure contact form.
Start a security reviewPilot with confidence
See the workflow and the controls behind it.
A pilot conversation brings the operator journey and your security review priorities into one practical discussion.
Request pilot access 30-day sandbox · No card required · Guided setup