Platform security
- ✓ Controls designed toward SOC 2 alignment (not certified)
- ✓ SSO / SAML 2.0
- ✓ Role-based access control (RBAC)
- ✓ HTTPS/TLS in transit and AES-256-GCM application encryption for selected secrets and sensitive fields; hosting/storage controls require current deployment evidence
- ✓ Per-tenant data isolation enforced by server-side organization scoping on every query
- ✓ Tenant-scoped activity history for state-changing actions; integrity coverage and cryptographic verification are release-specific
- ✓ Configured providers that receive customer data, voice audio, or location traces must be configured with training and secondary-use exclusions consistent with their commercial terms
Helps you comply with
- ✓ DOT evidence workflows
- ✓ FMCSA / ELD record support
- ✓ Accepted-provider HOS and ELD evidence
- ✓ Internal waste and chain-of-custody records
- ✓ PCI DSS-scoped payments through configured Stripe
- ✓ TCPA consent and opt-out workflows
Deployment
Multi-tenant workspaces, isolated by design.
Single operators get one secure workspace; franchise, multi-location, and regional operators get a workspace per site with centralized roll-up and access control. The operator console and driver app run on the Haultro platform, separate from this marketing site.
Request pipeline
Five checks before data is touched.
Layer 1
TLS / HTTPS
API endpoints, WebSockets, client portal access, and IoT ingestion run over encrypted transport.
Layer 2
JWT authentication
Signed tokens carry role, organization, and expiration claims and are validated on every request.
Layer 3
Role check
Admin, Manager, Driver, Client, and Enterprise Admin permissions are enforced server-side.
Layer 4
Organization scope
Every data query is scoped by organization, so one tenant cannot read another tenant record.
Layer 5
Activity history
State-changing actions are designed to record timestamp, user, action type, and affected resources for tenant-scoped review. Cryptographic linkage, coverage, and verification are release-specific and are not claimed by this public page.
Trust package
The artifacts your security reviewer will ask for.
No certification is claimed. What is published is what can be verified: the provider list, the processing terms, the use policy, and the AI disclosure posture. Request current owner evidence for any control statement before relying on it in procurement.
Subprocessor list
A dated list of the service providers behind this website and the Haultro product, split into configured and activation-gated providers, with a 30-day change-notification commitment.
Data processing agreement
The standard DPA for contracted deployments is published for review and covers the processor role, security measures, subprocessor terms, rights support, incidents, and deletion duties.
Acceptable Use Policy
Prohibited uses of the voice, SMS, and automation capabilities, and the consent, recording, and monitoring-notice responsibilities the operating customer holds.
AI transparency
How AI-assisted features are scoped, disclosed to callers, reviewed by humans, and governed, including the automated-decision and human-review posture.
Breach notification commitment
If a security breach affecting customer data is confirmed, we notify affected customers without undue delay, and no later than 72 hours after confirmation, and we update findings as verification proceeds. Report a suspected issue to contact@trunnion.ai or through security.txt.
Subservice organizations
The controls described on this page rely in part on subservice organizations: Render (application and static hosting and the managed PostgreSQL database), Cloudflare (edge network in front of this site), and Google Workspace (business email). They are treated on a carve-out basis: physical, environmental, and infrastructure control families sit with those providers and are evidenced by their own current attestations rather than inherited or restated here.
Sensitive data categories
Precise location and voice audio, stated plainly.
The Haultro product processes two categories that CPRA and similar state privacy laws treat as sensitive personal information: precise geolocation (GPS position refreshed as often as every 15 seconds where the configured telematics provider supports it, tied to vehicles and their named drivers) and voice audio (calls handled by the AI receptionist and speech captured by the in-cab copilot).
These categories are collected for service delivery only: route execution and dispatch, fleet safety and compliance records, call handling, quoting, scheduling, and the records the operating customer's own workflows require. They are not sold, not used for advertising, and not used for any purpose incompatible with delivering the service. PII redaction for batch transcripts runs after capture, so configured telephony, transcription, voice synthesis, and telematics providers must carry training and secondary-use exclusions consistent with their commercial terms, the same requirement that applies to model providers.
Retention and deletion for product data, including these categories, are governed by the customer agreement and the operator's configuration; no universal retention period is published without owner-approved operational evidence. Before activation, the operating customer must give drivers, employees, and callers the notices and obtain the consents required for location monitoring, recording, transcription, and automated voice interactions in the relevant jurisdiction. The customer must also approve a documented retention schedule and a deletion or de-identification path for these categories. To ask that sensitive categories be limited to service delivery, contact contact@trunnion.ai or the operating customer directly; drivers and callers can also route requests through their operator. The website itself collects no sensitive personal information; see the Privacy Notice.
FAQ
Security, answered.
How is my data isolated?
Haultro is multi-tenant with per-tenant data isolation. Each operator (and each location for multi-site accounts) has its own workspace, with role-based access control governing who sees what.
What compliance does Haultro help with?
Haultro provides evidence and record workflows for DOT evidence workflows, FMCSA / ELD record support, Accepted-provider HOS and ELD evidence, Internal waste and chain-of-custody records, PCI DSS-scoped payments through configured Stripe, TCPA consent and opt-out workflows. It does not determine legal compliance, certify a fleet, submit records to an agency, or replace the operator's ELD, agency portal, or counsel.
Is the platform SOC 2 certified?
No certification is claimed. The product has controls designed toward SOC 2 alignment; request current owner evidence before relying on any procurement or certification statement.
Is customer data used to train third-party AI models?
No LLM provider is currently configured in production. When a customer enables one, its commercial agreement and settings must exclude customer data from model training; confirm the selected provider terms during activation. The same training and secondary-use exclusion requirement applies to configured telephony, transcription, voice synthesis, and telematics providers that receive call audio or location data.
Does Haultro train its own models on customer data?
No. Customer operational data, call audio, and transcripts are not used to train shared or cross-tenant Haultro or Trunnion models. Learning features such as predictive fill and route optimization operate on the customer's own operating data inside that customer's tenant only. A customer can further restrict tenant-scoped processing through its written agreement.
Do callers know they are speaking with an AI?
Yes. The voice agent identifies itself as automated at the start of a call, and callers have a path to reach a human. Operators configure the human handoff for their operation; see the AI Transparency Notice for the full disclosure posture.
Will we be notified if there is a security breach?
Yes. We commit to notifying affected customers without undue delay, and no later than 72 hours after confirming a security breach affecting their data, with findings updated as verification proceeds.
What happens to my data if I cancel?
Retention, export, deletion, legal-hold, and reactivation terms are confirmed in the current written agreement and operating policy. Haultro does not publish a universal post-cancellation deletion period without owner-approved operational evidence.
Where does the app live?
The Haultro web console is hosted separately from this marketing site at https://platform-haultro.com/login. Native iOS/Android source is built, but Apple and Google distribution is pending.
Get started
Talk to us about your security needs.
We'll walk your team through isolation, access, and compliance.