Rutalto Data Processing & Retention
Version: 2026-10-09
Processors and infrastructure
| Provider | Purpose |
|---|---|
| Google Firebase | Authentication, cloud messaging, optional analytics, optional crash reporting, storage for profile photos. |
| Google Maps / Places | Route previews, geocoding, and location search assistance. |
| Google Cloud Run / Cloud SQL / Cloud Storage | API runtime, relational data storage, and operational artifacts. |
| Sentry | Backend and optional Android error monitoring. |
Retention schedule
| Data type | Retention intent |
|---|---|
| Profile and legal acceptance records | Until deletion request, then minimized or anonymized where lawful retention is not required. |
| Ride, booking, alert, review, and safety records | Retained while operationally relevant, then minimized or anonymized for dispute, fraud, and compliance records. |
| Push tokens | Removed when replaced, deleted, or no longer needed. |
| Share links and live tracking artifacts | Short-lived, operational retention only. |
| Data export bundles | 24 hours after completion, then expired and removed. |
| Deletion request records | Retained as minimal audit evidence of compliance action. |
| Telemetry and error traces | Operational windows only, with PII scrubbing and no persistent ride-history analytics expansion. |
| Administrator access and action audit events | 180 days. Records contain operator/action evidence and case metadata but do not copy revealed plaintext personal data. |
Data rights workflow
Rutalto provides in-app flows for export and deletion requests. Export bundles contain the current account profile, ride activity, notifications, messages, reviews, reports, legal acceptances, and privacy preferences associated with the requesting account.
Authorized operators may retry failed export or deletion jobs through the access-controlled administrator service. The retry, its reason, and its outcome are audited. Administrator audit cleanup runs as part of privacy maintenance after the 180-day retention window.