Wakazi — Privacy Policy

Last updated: 15 October 2026
Data controller: Muslim Path Inc., the company that operates Wakazi
Privacy contact: support@wakazi.app

Wakazi ("Wakazi", "we") is a worldwide, location-based marketplace that connects customers who need work done with nearby skilled workers through mutual, swipe-based matching. This policy explains, in plain language, what we collect, why we collect it, and exactly who can see it.

1. What we collect

Account and sign-in

Email address. You sign in with your email address and a password, or with your Google or Apple account. Your email address is stored on your account and is never shown to other users.
Password-recovery and transactional emails are delivered by our email provider, Resend.

Profile information

Your role (customer or worker), your name (workers may use a display name), and your area details: county, town, estate.
Workers additionally provide: occupation, skills, bio, years of experience, expected rate and rate type, travel radius, languages, and availability.
Ratings and completed-job counts accumulated from platform activity.

Identity verification

Email verification. Before you post a job or swipe, you verify your account email address with a one-time code we email to you (delivered by our email provider, Resend). We store the fact and time of verification, and the method used — never the code itself.
ID check (workers). Every worker needs a current ID check approved by a Wakazi human reviewer before their profile is visible to customers, they publish or connect through the marketplace, or they begin new work, including remote work. A worker awaiting approval can sign in to submit or correct evidence, appeal, contact support and delete their account. The worker uploads a photo of the front of a government ID and a live selfie. Customers see "ID checked by Wakazi" after approval; the check is valid for 24 months. A trained human reviewer makes the final decision; a separately controlled document advisory may provide limited hints when enabled, as described in section 5. ID images are deleted 7 days after the decision (immediately when you delete your account). We retain a limited non-image verification record as described in section 5; we do not store full ID numbers.
Police clearance, licences and qualifications (workers). Every selected service must meet its applicable current document rules. Some services require an official DCI police clearance or a licence with the exact class and scope needed for the task. Those service categories remain unavailable until Wakazi can verify the required document through its official source and the relevant legal programme is activated. Workers may separately add optional qualifications such as NITA trade tests. For a submitted document, the worker uploads a photo and types its reference number. We store the image privately, the reference number only as an irreversible hash plus its last four characters, the issuer, class or scope, issue and expiry dates, the reviewer's check result and, for a police clearance, the worker's Sexual Offences Act section 30 declaration. A Wakazi reviewer checks the document on the issuer's official verification page. Customers see only short dated facts (for example "EPRA electrical licence · current until [date]"), never the document, the number or any record content. If review fees are enabled, Wakazi may charge separately for its human review of one new identity or document case through an Apple or Google in-app purchase. The purchase covers corrections to that same case but does not guarantee approval, a badge, faster review, rank or an exemption from a requirement. Existing approved checks are not charged again. Police clearance and licence review purchases are unavailable while those programmes are held. Any fee for obtaining an official document is paid directly to its issuer, not to Wakazi. See section 9 for retention.
Profile photo (avatar). Required for workers, optional for customers. Photos are kept in private storage that only signed-in Wakazi users can access, and only where described here. A worker's photo is shown to signed-in users on the worker's cards, offers and profile, and publicly on the worker's share page (wakazi.app/w) when the worker shares it. A customer's photo is shown only to the workers they connect with.

Location

Precise GPS location you provide for your profile and for each job you post, stored as a geographic point.
We use it to compute distances and rank nearby jobs and workers for matching. How much of it other users can see is described in section 3.
User-initiated live arrival tracking. During an entitled active Work Session, a worker may tap “On my way” and grant location permission so the matched customer can see arrival progress. If the worker grants iOS “Always” location access, this sharing may continue while Wakazi is in the background or the screen is locked so the worker can use navigation. It stops at verified arrival, when the worker taps stop, or when the Work Session ends. Wakazi never uses background location for discovery, advertising or off-duty tracking.

Jobs

Title, description, budget and payment type, category and skills, photos, schedule, urgency, and both an approximate and an exact location point.

Activity

Swipes (likes, passes, saves), matches, and reviews (a 1–5 rating and comment, one review per participant per match).
In-app notifications generated for you (new matches, messages, unlocks).

Messages

Chat text and any photos you send, stored on our servers so both participants can read the conversation history.

Purchases

Digital purchases are processed by Apple (App Store) or Google (Play Billing). No card or bank details ever touch Wakazi. We record the store, transaction and product identifiers and payment or refund status to verify and deliver purchases. For some products we also record the amount and currency. If worker review fees are enabled, we also link a server-created order to the worker and the specific review case so one purchase covers that case and its corrections. Store transaction identifiers are used to prevent a purchase from being redeemed more than once.

Reports and moderation data

When you file a report we store: who reported, which user or job was reported, the reason (for example scam, no-show, inappropriate behavior, or other), its severity, your details, and the report's status.
When a report or case is about a Work Session we also keep the other person's response, the decision and its reason category, and any appeal. Both people are told the outcome and its reason category in plain words; these notices never include the text of the report or the reviewer's private note.
A serious report (violence, sexual misconduct or child safety) restricts the other account straight away until a person reviews it, and its evidence is held. When we restrict or suspend an account we record the reason category, the dates, who decided and any appeal; the person is told the reason category and how to appeal.

Push notifications

A device push token, used only to deliver notifications to your device via Firebase Cloud Messaging (Google). Tokens are stored in our database under your account and are readable only by you and our notification service.

App version

When you are signed in, newer versions of the app tell us which app version (build number) and platform (iOS or Android) you are using, so we can tell you when an update is needed. We keep only your latest version for each platform, and it is deleted with your account.

Public website analytics

Our public website uses Vercel Web Analytics to measure page views, estimated visitors, referring websites, and clicks to the Apple App Store and Google Play. These clicks do not confirm an installation or purchase. It runs only on our public marketing, help, legal and service-category pages — never on share, invite, job-status, account-deletion or staff pages. Website tracking uses no cookies and does not send account IDs, email addresses, form contents or private console/share-link URLs. We remove query strings and fragments before reporting page URLs, and share pages tell your browser to pass on only our site name, never the share link, when you leave them. We respect browser Global Privacy Control and Do Not Track signals. Aggregated reports help us understand how people discover Wakazi.

Usage analytics and crash reports

Product analytics. We record product-usage events (for example: the app opened, a job posted, a match created, an unlock completed, a review submitted) together with safe metadata only — internal record ids, counts, yes/no flags, category slugs, your app language, and the platform (iOS/Android). Events are processed by Firebase Analytics (Google).
Crash reports. Release builds of the app send crash reports (error type, stack trace, device and OS class, app version) to Firebase Crashlytics (Google) so we can find and fix bugs. Development builds never send crash reports.
When you are signed in, analytics events and crash reports may carry your opaque internal user id (a random UUID) so we can understand funnels and diagnose account-specific crashes. It is never your email, phone number, or name.
Analytics and crash payloads never contain: email addresses, phone numbers, message contents, job description text, exact coordinates or addresses, photos, ID information, passwords, payment receipts, call audio, or referral-recipient identities. The app enforces this in code: every event passes a fixed per-event allowlist of parameter keys, and a second filter drops anything resembling an email, phone number, message text, or location before anything leaves the device.
Opt-out: Profile → Data & privacy → “Share usage & diagnostics”. Turning it off stops analytics events and crash reports from leaving the app. The choice is stored on your device.

Security and audit logs

Records of account and payment events used for security, fraud prevention, and debugging.

Android availability list (website)

If you ask on wakazi.app to be told when Wakazi is available for Android, and tick the consent box, we store your email address, the website language you used and the time you agreed. We use it only to send you one email when the Android app is available.
We delete your email from the list after sending that message. You can ask us to delete it sooner by writing to the contact address below. It is never shown to other users, sold, or used for marketing.

2. How we use your information

Create and secure your account with your email address (a one-time code or a password).
Verify that accounts belong to real people: email verification before posting or swiping, a current human-approved ID check before a worker's marketplace participation or new work, and the current document checks required for each selected service.
Show you nearby jobs or workers and rank them by distance and other matching signals.
Create a match when both sides like each other, and unlock chat, contact details, and exact location after the customer's purchase.
Deliver in-app and push notifications about matches and messages.
Keep the platform safe: investigate reports and prevent payment fraud. Purchase receipts are verified server-side with Apple/Google before any unlock, and the app itself is never trusted.
Understand how the app is used (which funnels work, where flows break) and diagnose crashes, using the analytics events and crash reports described in section 1.
Maintain security and reliability through audit logs.

We do not sell your personal data, and we do not use it for advertising profiles.

3. Location: who sees what

Before a match is unlocked, no user ever sees your exact location.
Worker cards shown to customers display only the worker's area (estate, town, county) and a location snapped to a grid of roughly 1 km — never the exact point.
Job feeds show the job's approximate area, snapped to the same kind of grid. The exact job location is revealed to the matched worker only after the customer unlocks the match.
These rules are enforced at the database level (row-level security and restricted views), not merely hidden in the app.

4. Phone numbers and contact details

Your phone number is contact information only — it is never used to verify your account (account verification happens over email).
Phone numbers are hidden from other users until a match is unlocked.
After an unlock, the two participants can see each other's contact details so they can arrange the work.

5. Identity verification

Email verification (required for posting and swiping)

Verification is a one-time code sent to your account email address, delivered by our email provider, Resend. Resend processes your email address to deliver the code.
We store the verification result (whether and when you verified, and via which method) on your profile — never the code itself. The verification flag is written only by our server-side function — never by the app.

Face Data used for worker ID checks

Every worker needs a current human-approved ID check before public visibility, publishing, new connections or beginning new work, including remote work. Registration and the verification, appeal, support and account-deletion paths remain available while approval is pending. Workers give explicit, separate consent (unticked by default) and upload a photo of the front of a government ID plus a selfie. A completed check is valid for 24 months.
Face Data collected. The only uploaded Face Data is the face visible in the final selfie and the portrait visible on the government-ID image. While the selfie is captured, on-device face detection checks framing and the requested blink/head turn. Those temporary camera frames stay on the device, are never uploaded and are discarded immediately; Wakazi does not create or retain a faceprint or biometric identification template from them.
Purpose. The final selfie and ID portrait are used only to check image quality, possible tampering, liveness signals and whether the two images appear to show the same person, so a trained human can decide whether the ID check is complete. Face Data is never used for advertising, tracking, ranking, personalization or training a face-recognition model.
Storage. The two final images are stored in a private, access-controlled Supabase Storage bucket in Wakazi's hosted Supabase project in the EU Central (Frankfurt) region. Other users cannot read them. They are not stored in the public profile or used as the worker's avatar.
Processing and sharing. The final ID and selfie images are available in private storage to authorized trained Wakazi reviewers, who make the ID-check decision. A separate document advisory is off unless specifically enabled. If enabled, it receives only the final front-of-ID image through Vercel AI Gateway to suggest limited image quality, layout and printed-date checks. It does not receive the selfie, compare faces, infer liveness or decide the check. Its model provider and processing terms must be reviewed before activation. Face Data is never sold, licensed or shared with advertisers, data brokers or other users.

Face Data retention and deletion

The final ID and selfie images, including the Face Data in them, are deleted by a scheduled server-side purge once 7 days have passed since the human decision (a short dispute window). Images uploaded for an attempt that was never submitted are not reviewed and stay in the private bucket until that attempt is submitted or the account is deleted. Deleting the account (in the app or at wakazi.app/account-deletion) deletes all ID and selfie images immediately, before the account is removed.
Wakazi keeps a non-image record of each attempt — badge status and reason, decision time and reviewer, consent version and time, birth year, document type and printed expiry text, automated quality/tampering/liveness flags, and irreversible SHA-256 image hashes — for audit, duplicate and fraud prevention while the account remains active. The name read from the ID is removed at the decision; the reviewer note is removed by the 7-day purge. No ID numbers or full dates of birth are extracted.
Account deletion does not erase these records: they remain, no longer linked to a profile, and the deletion flow adds an irreversible keyed hash of each attempt's internal reference with its outcome (a "tombstone"). If an attempt was still awaiting review, its extracted name remains in that unlinked record until a reviewer closes it. A scheduled retention job deletes an unlinked verification record two years after its decision or latest recorded activity and deletes its remaining ID images, if any. The separate keyed-hash tombstone is deleted after five years.
If a reviewer rejects an ID as suspected fraud, Wakazi keeps that ID image's SHA-256 hash in the verification record to help prevent the same image from earning approval through another account. The hash leaves with that record under the retention schedule above. None of these records contains an image or can reconstruct a face.

6. Payments

All purchases are processed by Apple or Google under their own privacy policies; Wakazi never sees, processes, or stores your card data.
Receipts are verified server-side (Apple App Store Server API / Google Play Developer API) before a digital purchase is fulfilled. A review purchase, when enabled, pays for review of a case, not for an approval or other trust outcome. Failed or unverified purchases grant nothing.
Payment status is written only by our server-side verification function — never by the app.
Refunds are handled through the store refund flows (Apple / Google). When a store notifies us of a refund, the unlock is reversed: the match is re-locked and any credits earned from the purchase are withdrawn.

7. Chat

Messages are stored on our servers and are visible only to the two participants of an unlocked match, enforced by database row-level security.
Messages are not end-to-end encrypted. We may review message content where needed to investigate a report or safety issue; reports filed in the app are reviewed by the Wakazi team.

8. Who we share data with

We share data only with:

Other users, strictly limited by the visibility rules in sections 3, 4 and 7.
Apple and Google, for payment processing; Google (Firebase) additionally for push-notification delivery (Cloud Messaging) and for product analytics and crash reporting (Firebase Analytics and Firebase Crashlytics — only the allowlisted events, safe metadata and crash diagnostics described in section 1, and only while your “Share usage & diagnostics” switch is on).
Vercel AI Gateway (Vercel Inc.) and configured model providers, for AI features such as job drafts, profile suggestions, photo analysis and translation. The separate worker ID-document advisory described in section 5 is off unless specifically enabled. Workers consent separately to ID-image processing before submitting evidence. When the advisory is enabled, only the final front-of-ID image is sent through Vercel AI Gateway to its approved model provider; the selfie is not sent. Wakazi does not sell prompts or images or log their content in its own telemetry (request metadata only). The model provider and its processing terms must be reviewed before this advisory is enabled. A human reviewer makes the final ID-check decision.
Cloudflare, for the Turnstile anti-abuse check on signup and sign-in.
Our backend provider (Supabase), which hosts the database, authentication, file storage, and server functions that run the service.
Vercel (Vercel Inc.), which hosts this website (wakazi.app) and is our website analytics processor. As our web host it processes the technical request data needed to deliver each page (such as IP address and browser details). On the pages listed under “Public website analytics” in section 1, our script sends Vercel Web Analytics the page address with any query string and fragment removed, the referring website when you arrive from another site, and a fixed “Apple download click” or “Google download click” event (no other details) when you follow a link to the official Wakazi store listing. From the request, Vercel estimates unique visitors without cookies and derives coarse country, device, browser and operating-system information. Collection is off when your browser sends Global Privacy Control or Do Not Track. Wakazi receives only aggregated reports (visitors, page views, store clicks and referring websites) and stores no visitor IDs or IP addresses from them.
An email delivery provider (Resend), to deliver verification codes, password-recovery and transactional emails (receipts, match alerts).

9. Data retention

We keep your data while your account is active.
When you delete your account (section 10), your profile, jobs, matches, account-linked payment records, swipes, and reviews are deleted with it. Store transaction references and review-order records needed to prevent replay or reconcile refunds may remain detached from the account. Your conversations are deleted too — for both participants, so the other person also loses that conversation, including their own messages in it. Reports you filed are deleted; reports other people filed about you are kept for safety investigations with your account reference removed.
If one of your Work Sessions has an open safety case or appeal, a serious report (violence, sexual misconduct, child safety, fraud or theft) or a safety hold when you delete your account, a copy of that Work Session's safety record is kept for up to two years so the other person's case can still be decided: its timeline of events, the accepted terms, and the case, appeal and report records. In that copy your account is replaced by a role ("customer" or "worker") and a one-way code; your messages are never part of it. A serious report you filed, or that was filed about you, outside a Work Session is kept the same way. Only Wakazi's safety reviewers can see these copies, and they are deleted after two years.
Security and audit logs of account and payment events are kept for fraud prevention and debugging.
Identity-verification retention is described in section 5.
Police clearance, licence and qualification document images are scheduled for deletion 30 days after the reviewer's decision, except while an appeal or further adverse review remains open. Withdrawn documents are removed at the next retention run; account deletion removes the images sooner. The check results stay with your account while it is active and are deleted with it.

Optional Peleza registry checks — not yet available

These optional paid checks remain disabled pending pricing, provider agreements and release approval. They are separate from contact access, job payments and Wakazi's human ID/selfie decision. National ID, passport and Alien ID lookups compare registry records; a driving-licence lookup uses the holder's National ID and returns registry licence facts. A KRA check concerns taxpayer registration and its recorded status. None proves that the presenter owns the document, establishes liveness, provides criminal clearance, certifies tax compliance or grants work eligibility.

For a chosen live check, explicit service-specific consent will cover the selected identifier sent to Peleza. Document photos stay in Wakazi's private evidence storage and are not sent by this registry integration. Authorized human reviewers independently read the named captured pages and compare the bound result before recording that check's outcome.

Wakazi schedules these captures for deletion after 30 days and private returned names, validity, licence and registry details after seven days; account deletion removes them sooner. Minimal purchase, refund and audit references remain for financial and security records. These periods do not describe Peleza's own retention. Before live checks are enabled, the approved service notice must state the provider's retention, deletion, international processing and rights arrangements under the agreed DPA.

The store total must be shown before purchase. A not-found response can consume a paid lookup; it does not automatically fail a person. Uncertain network outcomes go to support and reconciliation rather than an automatic repeat lookup. Confirmed unbilled failures may retry the same paid order. Corrected captured pages can return to human review on the same paid order without a second provider request. Refunds follow the applicable store process; no automatic cash refund is promised.

10. Account deletion

You can delete your account and personal data at any time directly in the app, from the profile screen. Deletion runs server-side via our delete-account function and removes your auth account, which cascades by design to your profile and related personal rows in our database.
You can also delete your account without reinstalling the app at wakazi.app/account-deletion. The secure page verifies the account before it sends the same permanent deletion request used by the app.
Limited records survive deletion: reports other people filed about you (with your account reference removed), the pseudonymised Work Session safety records described in section 9 (kept for up to two years), security and audit logs, the detached store transaction and review-order records described in section 9, and the identity-verification records and tombstones described in section 5. The store (Apple/Google) keeps its own receipt of each purchase under its own policies. Your messages do not survive: conversations are deleted for both participants (section 9).

11. Security

Sensitive fields (phone numbers, exact locations, messages) are readable only under the database row-level-security rules described in this policy.
Trust data (ratings, verification status, credit balances) can be written only by server-side functions — never by the app or by other users.
All traffic between the app, this website, and our backend uses encrypted connections (HTTPS/TLS).

12. Age requirement (18+)

Wakazi is for adults only. You must be 18 or older to create an account or use the service. We do not knowingly collect data from anyone under 18; if you believe a minor has an account, contact support@wakazi.app and we will remove it.

13. International use

Wakazi operates worldwide. Your information may be processed in countries other than your own, including where the providers listed in section 8 operate; where data crosses borders it is handled under those providers' data-processing terms.

14. Changes to this policy

We will update this policy as the product evolves and post the new version on this page with a revised "last updated" date. Material changes will be flagged inside the app.

15. Contact

Privacy questions, data-access or deletion requests, and report follow-ups: support@wakazi.app

← Back to home