Service information

Privacy Policy

Review draft. The service operator’s legal identity, contact details, retention periods and contractual terms must be confirmed before this policy is final.

1. Your institution and your data

SafiriCloud is used by fleet institutions to manage operations and collections. Your institution manages user access and determines how its operational records are used. The service operator’s legal identity and privacy contact must be confirmed in the final policy.

2. Information handled

Depending on enabled features, the service handles account names and contact details, vehicle and crew records, routes and stages, activity and trip records, invoices, payments, receipts, collection sessions, deposits, approved documents and audit history. Platform billing records track configured usage charges and wallet transactions.

3. Why information is used

Information supports authentication, role-based access, fleet administration, financial records, reconciliation, auditability and configured communications. The final policy must specify applicable legal grounds, mandatory information and any additional uses agreed with each institution.

4. Devices and biometric unlock

The mobile app retains a session using native secure storage and stores pending work on the device for later review or sync. Optional biometric unlock uses the phone’s authentication system. The app receives the authentication outcome; it does not receive raw fingerprint or face templates or your device passcode. Keep the device protected and review pending work before removing the app.

5. Service providers and communications

The implementation uses Supabase for backend services and Expo services for Android builds and distribution. Configured server-side communications may use Airtouch SMS and Resend email. Provider agreements, hosting regions, cross-border safeguards and the complete provider list require operator confirmation before this policy is final.

6. Access, retention and requests

Permissions restrict institution access, and operational changes may be audited. Exact retention schedules, backup periods and deletion/export processes must be agreed and documented by the operator and your institution. Direct questions about your records or requests for access or correction to your institution administrator while the dedicated privacy contact is being confirmed.

For information about personal-data rights in Kenya, see the Office of the Data Protection Commissioner. This draft does not represent a certification of regulatory compliance.