support
Security and privacy for transport emissions workspaces
Trust starts with clear handling of shipment data, account access, evidence artifacts, and public marketing forms.
Audience
Teams evaluating whether to upload shipment data or request product access.
Problem
Shipment exports can contain commercially sensitive routes, customers, volumes, and operational context.
Product fit
LogisticsAI keeps security and privacy information visible, routes private application areas away from public indexing, and separates public samples from real customer data.
Public vs private surfaces
Public pages, samples, and templates are separate from private dashboard, API, auth, and share surfaces. Robots rules keep operational routes out of crawler scope.
- Public sample artifacts are demo artifacts and not real customer records.
- Dashboard and API paths are excluded from the public SEO sitemap.
- Lead capture uses a dedicated marketing lead table rather than mixing inquiries into application reporting data.
Data minimization
Evaluation flows should ask for only the information needed to follow up, run a pilot, or explain API access. Shipment uploads should be reviewed before external publication.
Review before sharing
Generated artifacts should be reviewed by the responsible team before being sent to customers, auditors, or procurement portals.
Explore the evidence workflow
Frequently asked questions
Are public sample files real customer records?
No. The sample pack is a demonstration artifact and does not represent a real customer or certified calculation.
Are private dashboard pages listed in the sitemap?
No. Public SEO routes are registered separately from dashboard, auth, API, and operational routes.
Related resources
Move from content to workflow
Use the public samples and tools to evaluate the workflow, then create a workspace or request async follow-up when real shipment data is ready.