Data Processing Addendum
Last updated · 6 November 2026
This Data Processing Addendum (DPA) supplements the Kafu terms when your organization acts as a "controller" of personal data belonging to respondents, employees, or customers and uses Kafu as a "processor". It describes roles, obligations, security warranties, and breach notification requirements under the Saudi Personal Data Protection Law. This is Kafu's current text. Kafu prepared it with reference to the Saudi Personal Data Protection Law and SDAIA's published guidance, and no independent lawyer has reviewed it. We will tell you 30 days ahead of any material change.
Parties & roles
Parties: the customer ("Controller") and Kafu World Inc (Saudi company) ("Processor"). Kafu acts as a "controller" only with respect to the account, billing, support, security-log and marketing data of its users, and as a "processor" with respect to the data the Controller enters about its own customers, students, guardians, staff and respondents.
Scope of processing
- Subject matter: operating the Kafu apps the Controller uses to run its business (sales and customers, point of sale, finance and invoicing, human resources, inventory and procurement, projects, appointment booking, and academy management: students, guardians and classes), and the surveys and market research it starts.
- Duration: for the term of the agreement between the parties + the retention period in the Privacy Policy.
- Nature: storage, hosting, AI processing at the Controller's request, transmission to respondents and contacts, statistical aggregation.
- Data subjects: the Controller's employees, customers and appointment clients, pet owners and their pets' records, students (who may be children) and their guardians, contacts and suppliers, survey respondents and verified panel members.
- Children: where the Controller records a child's data, the Controller is responsible for holding the guardian's consent and for telling the guardian what is done with the data. Kafu stores the data in the Controller's workspace, limits it to the roles the Controller names, and processes it only on the Controller's instructions.
- Categories of personal data: whatever the Controller elects to enter or collect in the platform, such as names and contact details, employee records (job title, hire date and national ID number where the Controller records one), customer, transaction and invoice data, and survey answers (age, gender, region, free-text answers, etc.). Sensitive data only with explicit consent from the data subject or the guardian.
Controller instructions
The Processor processes personal data only on documented instructions from the Controller and the in-product configuration. If the Processor considers an instruction to violate PDPL, it notifies the Controller before proceeding.
Sub-processors
The Processor is authorized to use the sub-processors listed below, each only for the function named beside it.
- Alibaba Cloud — hosting of databases and uploaded files. Data received: everything stored in your workspace. Processes data in: to be confirmed. SDAIA Standard Contractual Clauses signed: to be confirmed.
- Resend and Google Workspace — sending e-mail. Data received: the recipient address and the message. Processes data in: to be confirmed. SDAIA Standard Contractual Clauses signed: to be confirmed.
- Unifonic and Twilio — sending text messages. Data received: the phone number and the message text. Processes data in: to be confirmed. SDAIA Standard Contractual Clauses signed: to be confirmed.
- Anthropic, together with the optional KafuAI gateway when it is switched on — AI model provider. Data received: only the prompted content, under a contractual no-training commitment. Processes data in: the United States. SDAIA Standard Contractual Clauses signed: to be confirmed.
- OpenAI — speech-to-text for voice memos and voice orders only. Data received: the recording of the memo or order. Processes data in: to be confirmed. SDAIA Standard Contractual Clauses signed: to be confirmed.
- Adobe Firefly — image generation, only when you ask for it. Data received: the image description you type. Processes data in: to be confirmed. SDAIA Standard Contractual Clauses signed: to be confirmed.
- Wathq — Commercial Registration lookups, only when you ask to verify a business. Data received: the registration number you look up. Processes data in: to be confirmed. SDAIA Standard Contractual Clauses signed: to be confirmed.
- Web search providers (Bing, Brave, SerpAPI and DuckDuckGo) — web search, only when the web search feature is used. Data received: only the search query. Processes data in: to be confirmed. SDAIA Standard Contractual Clauses signed: to be confirmed.
- The payment gateway Kafu selects, listed here when it is enabled.
We publish a list of our sub-processors showing what each one does, what data it receives, where it processes data, and whether SDAIA's Standard Contractual Clauses are signed. We e-mail the workspace owner and show a notice in the product at least 30 days before a new sub-processor starts handling your data. You may object on reasonable data-protection grounds within those 30 days; if we cannot resolve it, you may stop using the affected feature, or end the agreement and receive a refund for the unused part of the period you paid for.
Change log:
- 2026-11-05 — The list was rewritten to show each provider's function, the data it receives, where it processes data and the status of SDAIA's Standard Contractual Clauses; providers not yet confirmed as in use were removed.
Security measures
The Processor commits to applying the following technical and organizational controls as a minimum:
- Encryption in transit (TLS 1.2 or higher). Backup copies taken off the server are encrypted (AES-256). Secrets we store for you, such as authenticator keys and connected-service credentials, are encrypted in our database.
- Role-based access control and separation of production and test environments.
- Two-factor authentication (a code from an authenticator app) is available to every account, administrators included, and is required at every sign-in once you turn it on; it is not mandatory.
- Audit logging of sign-ins, changes, exports and support access.
- We review our code and configuration for security issues as part of our regular engineering work.
- Logical isolation of controller data (multi-tenant isolation) to prevent cross-tenant leakage.
Audit rights
The Controller may, once per year or upon reasonable suspicion of breach, request an audit of the Processor's operations. The audit is conducted by a mutually agreed independent third party, during business hours, without disrupting service. The Controller bears the audit cost unless a material breach is found.
Breach notification
The Processor commits to notifying the Controller without undue delay — and in any case within 72 hours of discovery — of any breach affecting the Controller's personal data. The notification includes:
- Description of the incident, categories of affected data subjects, and approximate number.
- Likely consequences of the incident.
- Measures taken or proposed to mitigate.
- Contact details for the DPO or another point of contact for further information.
The duty to notify SDAIA and the affected data subjects for the Controller's data rests with the Controller. The Processor gives the Controller, as soon as it knows them and in stages if needed, the facts it needs for those notices: when and how the breach happened, the categories and approximate numbers of people and records, the likely consequences, the measures taken and a contact point.
Cross-border transfer
Any cross-border transfer (e.g. to our AI model provider) is governed by contractual safeguards equivalent to Standard Contractual Clauses, under PDPL Article 29 and SDAIA controls.
Data subject requests
The Processor assists the Controller in responding to data subject requests (access, rectification, erasure, portability, objection) within 10 business days of the Controller's request. Tools: a data export from account settings; correction inside each app; removal of the identifying details of one person, and restriction of processing, carried out by our team together with the Controller's owner or administrator on a request to dsr@kafuapp.com (there is no self-service screen for these yet). If the Processor receives a request directly from a data subject, it forwards it to the Controller within 2 business days instead of answering it.
Return & deletion on termination
Upon termination, the Controller may export its data within 30 days in a structured, open format (JSON), either itself from account settings, where the file's manifest lists what it holds and what it does not cover and each export uses 1 Kafu Credit, or by request to dsr@kafuapp.com, free of charge, for anything the file does not cover.
After that window, and within 30 days, the Processor deletes the Controller's data from production and confirms it in writing. Copies in backups leave the rotation on their own schedule: within 14 days on the hosting server and within 60 days at most for the encrypted copy kept off the server, unless the law requires longer retention.
The export includes the Controller's invoices. The Controller remains responsible for keeping its own tax records for as long as the law requires (the VAT rules ask for at least 6 years); the Processor does not keep them for it after the deletion described in this section.
The Processor provides a written certificate of deletion upon request.
Confidentiality
The Processor ensures that every person authorized to process Controller data is bound by a written confidentiality agreement. This obligation survives the end of employment or the agreement.
Term & jurisdiction
This addendum forms part of the terms of service for every business customer. It takes effect on the day the customer first accepts the terms, or signs a Kafu agreement that refers to it, whichever is earlier, and continues until the agreement ends and all data has been deleted or returned. Kafu records the acceptance (who, when and which version). If this addendum and the terms differ on personal data, the addendum prevails. Saudi law applies. The parties first try to settle a dispute by talks for 30 days; then the competent courts in Riyadh have jurisdiction.
Execution & acceptance
This addendum is accepted electronically when the customer first accepts the terms of service. The sign-up screen tells the customer that by creating the account they agree to the Terms of Service, the Privacy Policy and, for their business, this Data Processing Addendum. Kafu records the acceptance (who, when and which version). Enterprise customers requiring a hand-signed copy may request one via sales@kafuapp.com.