Privacy Policy

1. Scope and responsibility

This policy explains how MySaji handles personal information across the public website, customer portal, Saji Pro, Saji Till and authorised administration and team portals. It covers browsing, accounts, listings, bookings, orders, payments, loyalty, support and communications. “MySaji”, “we” and “our” refer to the operator of this platform. Use the contact details at the end of this page to ask who is responsible for a particular use of your information.

For platform accounts, security, support and platform transactions, MySaji determines how information is used. Independent providers and merchants also make their own decisions about information they receive to fulfil a booking or operate their business. A Till owner is responsible for the customer and employee records they enter and the access they grant; MySaji provides the system used to process those records. A separate business agreement may describe these responsibilities in more detail.

2. Information you provide

• Account details: name, email address, phone number, account role, profile information and authentication details. Passwords are stored as hashes rather than readable passwords.
• Business and verification information: business profiles, trade qualifications, licences, identity or supporting documents where a verification process requires them, and the outcome of that review.
• Requests and transactions: service descriptions, addresses, delivery or visit instructions, orders, bookings, receipts, wallet ledger entries, payment references, refund requests and disputes.
• Communications and content: messages, uploaded files and images, voice notes, reviews, support enquiries and material submitted to AI-assisted features.
• Till records: products, stock movements, employee assignments, shifts, sales, customer contact details and loyalty activity where the business uses those features.

Provide only information needed for the task. Do not send payment PINs, one-time passwords, full card credentials or unrelated identity documents in a chat, review or AI prompt. If you enter information about another person, you must have an appropriate reason and authority to do so.

3. Information from your device and other sources

We process technical information needed to operate and protect the service, such as session identifiers, browser and device information, request and security logs, timestamps and delivery status. Payment providers send transaction confirmations and failure information. Other users may supply booking details, reviews, reports or messages concerning a transaction with you.

Location features can use a location you enter or device location after permission is granted. Microphone and camera access is requested when you record a voice note, take a picture or join a call. Device notifications require browser permission and a push subscription. You can revoke these permissions in your browser or operating-system settings; the related feature may then be unavailable.

4. Purposes and lawful grounds

• Providing the service: create and authenticate accounts, publish requested listings, connect customers and businesses, fulfil orders and bookings, keep transaction records and provide support. Processing necessary to perform a contract or take steps you request before a contract relies on that ground.
• Permission-based features: optional marketing, device permissions and other uses for which consent is required rely on your consent. Withdrawing consent does not invalidate earlier lawful processing.
• Safety and service operation: prevent fraud, enforce access controls, investigate misuse and improve reliability, where a legitimate interest is appropriate and does not override your rights.
• Legal duties: maintain required records, respond to lawful requests and meet applicable regulatory, accounting and dispute-handling obligations.

We use information for the purpose explained when it is collected or a compatible lawful purpose. If a new use requires consent or another notice, that step is required before the new use begins.

5. Payments, wallets and loyalty

Supported payment providers process payment instructions under their own terms and privacy notices. MySaji keeps the identifiers, amounts, statuses and account details needed to reconcile payments and provide receipts, wallet records, withdrawals and dispute support. Do not give MySaji staff your M-Pesa PIN or banking password.

When a merchant uses their own Paybill or other direct payment account, that merchant and their payment provider receive the payment details. A cashier may reconcile a payment against a sale. Entering a transaction code alone does not establish that money was received.

Where you supply a phone or points-card number for loyalty, it is used to identify the relevant customer record and record points under that business’s programme. The merchant can see the customer and sales information necessary to administer that programme. Ask the merchant about their own retention and marketing practices.

6. Messages, attachments and calls

Messages, voice notes and attachments are stored so participants can view or download them. Access is restricted through account and conversation permissions. This is not a promise of end-to-end encryption: authorised operational access may be needed for support, security, legal requests or investigation of a report.

Audio and video calls use WebRTC. Call setup processes signalling information, connection details and call history; media may pass through a relay depending on network conditions and configuration. The current in-app calling feature does not provide a call-recording function. Voice notes are separate recordings deliberately created and sent by a user.

Recipients can save, forward, photograph or otherwise retain information you send. Removing content or closing an account does not remove copies held independently by recipients. Contact support before clearing a conversation if you need evidence for a dispute.

7. AI assistance and recommendations

MySaji may use account activity, searches, selected preferences and available listing or service information to suggest relevant options. When you use an AI assistant, drafting tool or image-editing feature, the prompt, conversation context, selected image or other content needed for that request may be sent to a configured external AI provider.

AI output may be inaccurate or unsuitable. Avoid submitting sensitive information that the feature does not need. AI providers process requests under their applicable service arrangements; this policy does not promise that every provider has the same storage, training or retention rules. Ask support if you need information about the provider used for a particular feature. You may browse and choose services yourself without relying on an AI suggestion. A recommendation is not a verified fact about a person, a professional assessment or a guarantee of suitability.

8. Who receives information

• Customers, providers and merchants receive the information needed for the interaction you request. Public listings, profiles and reviews can be visible to visitors and search engines.
• Business owners and authorised employees can access records within the permissions assigned to their business role. Platform administrators and support teams receive access appropriate to their duties.
• Infrastructure, storage, email, payment, notification, communications and AI service providers process information needed to deliver their services.
• Authorities, professional advisers or other parties may receive information where lawfully required, necessary to protect rights or safety, or needed for a legal claim. A business transfer may require disclosure subject to applicable safeguards and notice obligations.

We do not sell personal information. Sharing for a transaction or with a service provider does not give the recipient permission to use it for unrelated marketing.

9. Cookies, local storage and device alerts

Authentication cookies keep you signed in and support security. Local storage and similar browser facilities can retain preferences, account-scoped interface data and, where offered, offline Till records. Some features will not work if you block essential storage. Shared-device users should sign out and avoid leaving sensitive downloads on the device.

Notification preferences and device permission are separate controls. A push subscription lets a delivery service route alerts to your browser while you are away from the app, subject to device policies. Alert previews may be visible on a lock screen or notification centre. Use your device settings to hide previews. Signing out attempts to remove this browser’s subscription and clears its active account binding; it does not erase copies or screenshots you have saved.

Newsletter subscriptions and optional promotional communications can be stopped through the unsubscribe option provided or by contacting support. Turning off marketing does not stop essential security, payment or service messages. Where optional tracking requires consent, it must be presented separately from essential storage.

Where configured, optional analytics on approved public pages loads through Google Tag Manager only after you allow it using the analytics preference control. You can reject analytics or use that control to withdraw consent. Advertising storage is disabled in the platform’s consent configuration. The analytics integration is restricted to approved public routes rather than signed-in account pages; third-party destinations and their processing depend on the configured analytics services.

10. Storage, retention and security

We use access controls, account verification and technical safeguards to reduce unauthorised access and misuse. No system can guarantee absolute security. Protect your login details, review employee permissions and report suspected compromise promptly using the contact options below.

Information is kept for as long as needed for the purpose for which it was collected, applicable legal duties, unresolved payments or disputes, fraud prevention and the establishment or defence of legal claims. The appropriate period depends on the record: a financial entry may need to outlast an account, while temporary authentication and connection information has a shorter operational purpose.

An account-closure request is not a promise to erase every record immediately. Some records must be retained, restricted or de-identified, and backup copies may persist until their normal replacement cycle. Contact support to request the retention period or criteria for a specific record. We will explain applicable limits when handling your request.

11. International processing

Hosting and service providers may process information outside Kenya. Any such transfer must have a lawful basis and the safeguards required by applicable Kenyan data-protection law, such as appropriate contractual or other recognised protections, or valid consent where required. Contact support to ask about the destinations, recipients and safeguards relevant to your information; do not assume all data is stored exclusively in Kenya.

12. Your rights and how to exercise them

Subject to applicable law, you can ask to be informed about processing, access your information, correct inaccurate information, object to processing, request deletion or restriction, and request portability where applicable. You can withdraw consent for a consent-based use and raise concerns about a decision made solely by automated processing that significantly affects you.

Use account settings for available profile, notification, export or closure controls. If a control is unavailable, contact support with the subject “Privacy request”, the account identifier and what you want us to do. Do not include a password or PIN. We may verify your identity and authority, including whether a business request concerns records controlled by a merchant. Requests are handled within applicable legal deadlines; if an exception applies, we will explain it.

You may complain to Kenya’s Office of the Data Protection Commissioner (ODPC), including if you are dissatisfied with our response. Contacting MySaji first can help resolve a concern but does not remove your right to approach the regulator.

13. Children and information about others

MySaji accounts and business tools are intended for adults aged 18 and over. Do not open an account for a child or submit a child’s information unless a lawful, necessary transaction specifically requires it and the relevant safeguards and parental or guardian authority are in place. Contact support if you believe a child has supplied information improperly so it can be reviewed and addressed.

14. Changes and contact

The revision date appears at the top of this page. Material changes will be brought to users’ attention through an appropriate service notice; where a new use requires consent, continued browsing alone is not a substitute for that consent. You can save a copy of this policy below. Use the contact panel for privacy requests, security concerns and questions about the organisation responsible for your data.