TransitOS Privacy Policy
Effective Date: January 1, 2026. Applicable to all licensed transport corporations, municipal transit authorities, and authorized operator personnel.
1. Scope and Organizational Roles
TransitOS provides multi-tenant operations software designed for municipal transport undertakings, regional bus authorities, and licensed transit operators. Under relevant data protection regulations (including the Digital Personal Data Protection Act and General Data Protection Regulation):
- The Customer (Transit Authority / Corporation) acts as the Data Controller with respect to all crew records, vehicle manifests, driver shift rosters, and passenger trajectory logs.
- TransitOS acts strictly as the Data Processor, maintaining isolated tenant databases and executing automated optimization algorithms on behalf of the customer.
2. Data Categories Processed
TransitOS processes the following operational datasets:
Operator and Crew Data
Full name, employee badge number, heavy passenger vehicle driving license details, shift availability, and duty rest intervals for Motor Vehicle Act compliance.
Fleet Telematics and Geospatial Logs
Vehicle registration numbers, chassis identifiers, GPS coordinate streams, speed telemetry, odometer readings, and depot maintenance status.
Route and Stop Geometry
GeoJSON corridor coordinates, bus stop lat/long identifiers, official timetable departure timestamps, headway spacing, and disruption records.
Administrative Access Logs
Operator IP addresses, HTTP-only session tokens, user role assignments, password hashes (Bcrypt/Argon2), and audit log timestamps for every schedule publish.
3. Purpose of Processing
Data ingested into TransitOS is utilized solely for:
- Executing mathematical duty pairing via Mixed-Integer Linear Programming.
- Enforcing mandatory statutory rest ceilings under Motor Vehicle Act 1988 sections.
- Calculating real-time plan versus actual departure variances.
- Generating algorithmic disruption recovery recommendations during vehicle breakdown.
- Maintaining immutable audit trails for depot management and government compliance.
TransitOS does not sell, broker, or monetize transit telemetry. Ingested operational data is never utilized for third-party commercial advertising.
4. Multi-Tenant Boundary Isolation and Security Controls
Security and tenant isolation are enforced at the architectural foundation:
- Database Query Bounds: Every SQL statement is scoped with mandatory tenant foreign keys. Cross-tenant leakage is prevented programmatically.
- Encryption: All telemetry in transit is encrypted using TLS 1.3. Persistent database volumes utilize AES-256 block encryption.
- Authentication: Session credentials reside exclusively in secure, HTTP-only, SameSite cookies to protect against cross-site scripting (XSS).
- Role-Based Access: Access is segmented across Organization Admin, Chief Scheduler, Depot Manager, Route Planner, and Management roles.
5. Data Retention and Deletion
Customer transit data is retained for the duration of the active service contract plus thirty (30) calendar days. Upon written contract termination or customer request, database tenant partitions and linked telemetry tables are permanently purged following verified multi-pass cryptographic erasure procedures.
6. Legal and Compliance Inquiries
For data protection officer correspondence, data processing addendum (DPA) execution, or government audit queries, contact:
Attn: Data Protection Officer
Email: legal@transitos.internal
Security Inquiries: security@transitos.internal