Transportation data requires trust.
How customer information is handled, what AI can access, how permissions are controlled, and how human escalation works.
Information Access
AI can access only the approved information and data sources configured for each organization. Access is scoped to what workflows require.
System Permissions
Permissions are controlled per workflow. RCIQ does not assume broad access to transportation records by default.
Connected-System Authentication
Integrations authenticate through the interfaces each connected system makes available. Configuration depends on those systems.
User Access
Staff access to interactions, summaries, and reporting can be configured around organizational roles.
Data Retention
Retention of conversation and interaction data is configured according to each organization's approved policies and requirements.
Data Export / Deletion
Where applicable, customer data can be exported or deleted according to configured organizational and contractual requirements.
Access Revocation
Access can be revoked when relationships change or when configured policies require it.
Third-Party Processing
Where third-party providers are involved, they are disclosed where appropriate. RCIQ does not imply all providers are used by default.
Student-related information
For student transportation, implementations involving student information must be configured around the organization's privacy, security, contractual, and legal requirements. RouteConnectIQ does not claim FERPA, HIPAA, SOC 2, ISO 27001, or specific security certifications unless formally verified.
Automation with human oversight
RouteConnectIQ automates approved routine processes. Transportation staff remain involved when safety issues arise, decisions require authorization, a parent requests staff, AI lacks approved information, an issue requires investigation, a complaint requires management, or an unusual circumstance occurs.
Book a Strategy Demo