YOUR INFORMATION. HANDLED WITH CARE.

A little clarity
about your privacy.

Siaka is an Arttribute shared mobility project. This is the MVP privacy notice for its pilot environment. The operating entity’s final contact details and launch policies must be published before public paid service begins.

What we collect

Account details such as your name, verified phone number, email, and authentication identifiers; ride timestamps, vehicle identifiers, vehicle location, service-area checks, selected membership, usage, payment references, support reports, and operational security logs. We request your phone’s location to help you find bikes and scooters and validate parking. Camera access is used to scan QR codes or attach issue photos.

Why we use it

To authenticate you, operate and secure vehicles, calculate charges, maintain your membership, process and reconcile payments, provide receipts and support, prevent misuse, and understand fleet performance. Operational staff access is limited by role and sensitive changes are audited.

Who processes information

Supabase provides authentication and Google provides maps; AWS hosts platform services and uploaded files; Vercel hosts the website; Stripe and Paystack process payments. Relevant bike device suppliers process lock commands and telemetry. Data may be processed outside Kenya by these services.

Payment and device security

Siaka does not request your M-PESA PIN, and the app does not store permanent lock master keys. Card details are entered on payment-provider checkout pages. We store provider references and payment status so payments can be verified.

Your choices

You can update your profile, export your account data, manage linked sign-in methods, cancel a membership, and request account closure through your account. Permission to use your camera or location can be withdrawn in your device settings, which may affect scanning or parking validation.

Retention

Ride, payment, and audit records are retained for operational and accounting needs. Raw telemetry and operational caches have configured retention periods. Closing an account removes direct contact details from the active profile; records required for unresolved balances, disputes, security, or legal obligations may be retained.

Questions and requests

Use the account support form for privacy and access requests during the pilot.

Updated 16 October 2026.