Privacy policy

Safirisha privacy policy

Effective 31 October 2026. Safirisha is operated by Boniface Michuki, P.O. Box 1347, Limuru 00217, Kenya. This policy covers the Safirisha app and safirisha.co.ke. Contact acmichuki@gmail.com for privacy, access, correction or deletion requests.

Information we handle

• Accounts: name, email, phone number, profile information, sign-in identifiers and authentication/session records. Google sign-in supplies the identity information needed to authenticate you. We do not receive your Google password.
• Deliveries: pickup/destination addresses and coordinates, sender and recipient contact details, parcel descriptions, instructions, status, delivery evidence and order history. Only provide another person's details when you are entitled to do so.
• Location: addresses or locations you enter, and device location when you permit a location feature. You can deny or revoke Android location permission in device settings. Courier background location tracking is disabled in the initial Play release.
• Contacts, messages and files: contact details you select for a delivery, messages you send and photos, documents or attachments you choose to upload. The contact picker supplies the selected contact; we do not upload your entire address book. Courier identity or eligibility documents are handled when submitted through verification features.
• Transactions: delivery charges, wallet balances/history, payment references, refunds and payout/bank details when the corresponding features are used. The initial release has no configured external payment gateway; available methods depend on service availability.
• Technical/security records: account/device/session identifiers, network addresses, access and audit records needed to operate the service, investigate errors and prevent abuse. Firebase Analytics, Crashlytics collection and optional push notifications are disabled in the initial Play release. Separately, Google's Maps SDK collects request/device metadata, network addresses, an SDK-specific identifier, crash metrics and map interactions to operate and improve Google services. Disabling Firebase Analytics or Crashlytics does not disable the Maps SDK's own collection.

Why we use information

We use information to create and secure accounts, authenticate sign-in, arrange and administer deliveries, display maps, communicate about orders and support, maintain transaction records, verify couriers, prevent fraud and resolve disputes. Optional permissions and uploads are used for the feature you choose. Declining a permission can limit that feature.

Who receives information

Senders, recipients, assigned couriers and authorized business participants receive the details needed for their delivery. Authorized staff access information needed for support and operations. Hostinger hosts the service; Google/Firebase provides authentication, cloud chat/storage services and maps. Support email is handled through Google's email service. These providers may process data outside Kenya under their applicable terms and safeguards. We do not sell personal information or use it for advertising. No external payment gateway or optional Crisp support chat is enabled in the initial configuration. A material change to providers or data use will be reflected in this policy before that change is introduced.

Security and your choices

The configured service uses HTTPS and account access controls. No system guarantees complete security. You can manage Android permissions, correct profile information through the app, or ask us to access or correct information. We may verify account ownership before acting. Do not send passwords, OTPs, identity-document images or payment credentials by email.

Request account and data deletion

You can request deletion without reinstalling or signing into the app. Email acmichuki@gmail.com with the subject “Safirisha account and data deletion”, preferably from your registered email address. Include the registered email or phone number needed to locate the account. If you no longer control that address, explain this so we can arrange proportionate ownership verification.

In the app, Account → Delete account closes access after password confirmation. You can also contact support from the app to request removal of associated personal data. Closing access alone does not immediately erase retained delivery or identity records. If you use Google sign-in and have no app password, you can request deletion by email directly; you do not need to create a password to send the request.

We verify ownership, close account access and revoke sessions, then review and remove or de-identify personal information that is no longer required within 30 days of a verified request. We explain any specific information that must remain, the reason and the applicable retention period. Active deliveries, unsettled balances, withdrawals or disputes may require resolution first; support will explain these steps. A deletion request does not itself authorize a payment or forfeiture of a balance.

Retention

• Unneeded profile, contact, device/location, uploaded-media and message data: removed or de-identified within 30 days after a verified deletion request, except specific material needed for an unresolved delivery, dispute, security investigation or legal obligation.
• Necessary delivery, financial and accounting evidence: retained for five years from the end of the reporting period to which it relates. This is limited to the records and identifying details needed for accounting, fraud prevention and resolving claims; it is not a reason to retain all profile information or continuous location history.
• Security and deletion-request evidence: retained for up to 12 months after resolution, unless it forms part of a specific unresolved investigation or required accounting record. Access is restricted.
• Specific legal holds: relevant records may be retained longer where a legal obligation or unresolved proceeding requires it. We explain the exception where permitted and remove or de-identify the data when it ends.
• Backup copies: deletion may take longer in restricted backup copies until the hosting provider's backup cycle overwrites them. They are not used for routine operations. If a backup is restored, recorded deletion requests must be reapplied before the data is used again.

Deletion is reviewed by support; it is not an automatic promise that every record disappears when the in-app closure button is pressed. Retained information is limited to the stated purposes and is reviewed when its retention period ends.

Children and concerns

Safirisha is intended for adults aged 18 and over and is not directed to children. If you believe a child has supplied information inappropriately, or information about you has been submitted without authority, contact us so we can investigate. You can also raise a concern with Kenya's Office of the Data Protection Commissioner.

Changes

We publish updates here with a revised effective date and explain material changes through the service where appropriate.