Data processing addendum
How Bizitel Solutions processes personal data on behalf of its customers, as the Kenya Data Protection Act, 2019 requires between a data controller and a data processor.
1. Parties, scope and definitions
This addendum is between the business that uses Bizitel Solutions (the Controller, “you”) and BIZITEL SOLUTION, Nairobi, Kenya, completing its registration with the Data Protection Commissioner (the Processor, “we”). It forms part of the agreement made under our Terms of service, and applies to all personal data we process for you in providing the Service.
“Personal data”, “processing”, “controller”, “processor”, “data subject”, “personal data breach” and “Commissioner” have the meanings in the Data Protection Act, 2019 of Kenya and the regulations made under it (together, the “Data Protection Law”). Where you also have customers in another country, that country’s data protection law applies as well, and this addendum applies to it to the extent it requires the same terms.
2. The processing: what, why, whose, how long
| Subject matter | Providing Bizitel Solutions: marketing intelligence, content drafting and publishing, lead and consent management, messaging, measurement and billing. |
|---|---|
| Nature and purpose | Storing, organising, matching, analysing and displaying data; generating draft content; sending messages and posts you approve; recording consent; producing reports; and supporting and securing the Service. For no other purpose. |
| Duration | The term of the agreement, then the closing period in section 12. |
| People (data subjects) | Your leads, customers and enquirers; people who comment on or message your accounts; and your own staff who use the Service. |
| Kinds of personal data | A shortened name; phone number and email address (stored encrypted, with a keyed hash for matching); consent records (channel, purpose, wording version, time, withdrawal); messages exchanged and delivery status; purchase and enquiry events; hashed identifiers of public commenters; and your staff’s names, emails, roles and activity. |
| Special categories | None intended. You must not send us sensitive personal data (such as health, biometric, ID numbers, religion, or children’s data without lawful consent) or card or bank details. The Service refuses to import them. |
3. Your duties as controller
You confirm that you:
- decide the purposes and means of processing, and that your instructions comply with the Data Protection Law;
- have a lawful basis for the personal data you give us or collect through the Service, including any consent you need to message people, and have given people the notices the law requires;
- are registered with the Commissioner where the law requires you to be;
- use the Service’s settings, retention periods, access controls and consent tools properly, and limit personal data to people who need it; and
- will not ask us to process data unlawfully, and will tell us if an instruction seems to us to break the law (we may then pause that instruction).
4. Our duties as processor
We will:
- process personal data only on your documented instructions, which are your use of the Service, its settings and this addendum, unless the law requires otherwise (in which case we tell you first where we may);
- keep each customer’s data separate from every other customer’s, and make it inaccessible to our staff: our platform staff cannot open your content, and there is no “sign in as the customer” function;
- make sure everyone who can reach the data is bound by confidentiality;
- not use your personal data for our own purposes, not sell it, and not combine it with other customers’ data, except for anonymous service statistics that identify no person;
- apply the security measures in Annex A;
- help you meet your duties on requests from people, breaches, impact assessments and prior consultation, taking into account what we know (sections 8, 9 and 10); and
- give you what you need to show that we comply (section 11).
5. Security
We implement technical and organisational measures that fit the risk, including those in Annex A. We review them regularly and may improve them, but will not reduce the level of protection during the agreement.
6. Sub-processors
You give us general authorisation to use the sub-processors in Annex B. Each is bound by a contract that requires protection no weaker than this addendum, and we remain responsible for them. We will tell you at least 30 days before we add or replace a sub-processor, by email to your owner or in the product. If you reasonably object on data protection grounds within that time, we will work with you to avoid using it for your data; if we cannot, you may end the affected part of the Service and receive a pro-rata refund of prepaid fees for it.
Some providers in Annex B are used only if you connect them (for example your own social accounts or a messaging channel). In that case you also have your own relationship with the provider and you remain responsible for it.
7. International transfers
Our servers are in EU. Some sub-processors, in particular AI providers, process data outside Kenya. We will transfer personal data out of Kenya only where the Data Protection Law allows: where the recipient is bound by a contract or rules giving the protection Kenyan law requires, where the country or provider offers adequate protection, with your instruction and the data subject’s consent where consent is needed, or where it is necessary for the contract. We minimise what is sent (for example, contact details of your leads are not sent to AI providers), and we choose zero-retention and no-training settings where a provider offers them. Annex B states where each provider processes data. On request we will give you a copy of the safeguards for a transfer.
8. Requests from people
If a person asks us to access, correct, delete, port or object to the processing of data we hold for you, we will not answer on your behalf: we will tell you without undue delay and refer the person to you. The Service gives you the tools to meet your own deadline: an access export of everything held about a person, ways to withdraw consent, opt a person out and correct what is recorded about them (a correction the product does not offer, we make on your written instruction), and an erasure that removes the person, their events, their messages and the raw rows carrying their hashed contact, across your workspace, with a due date you set in Settings. You can also set the retention periods for messages and inactive contacts, and the Service deletes data after them.
An erasure keeps only what is described in Annex C.
9. Personal data breaches
If we become aware of a personal data breach affecting your data, we will tell you without undue delay and within 24 hours. We will tell you what happened, what data and roughly how many people are affected, the likely consequences, and what we have done and are doing about it, and we will update you as we learn more. We will take steps to contain it and help you to investigate.
You decide whether to notify the Commissioner and the people affected, and we will help. You should know that the Data Protection Act requires a controller to notify the Commissioner within 72 hours of becoming aware of a breach, unless it is unlikely to put people’s rights at risk. We keep a register of incidents with a 72-hour clock.
10. Impact assessments and the regulator
We will give you reasonable help with data protection impact assessments and any prior consultation with the Commissioner that your use of the Service needs, and tell you if the Commissioner or another authority contacts us about your data (unless the law forbids it). Our template impact assessment is available to customers on request.
11. Proving compliance and audits
On request we will give you the information needed to show that we comply with this addendum, including our security measures and sub-processor details. You may audit us, or have an independent auditor bound by confidentiality do so, once a year and after any breach, on at least 30 days’ written notice, during business hours, at your cost, in a way that does not disrupt our business or touch other customers’ data. We may satisfy an audit by providing a recent independent report or certification where one covers the same ground.
12. When the agreement ends
Before or on the end of the agreement, the owner of your account can export the whole workspace from Administration. After the closing period (30 days unless we have agreed another), we delete your workspace’s content, people, files, sessions and data keys, and a closed workspace cannot be reopened. Data in backups is deleted as the backups expire, and is kept encrypted and unused until then. On request we will confirm the deletion in writing. We keep only what Annex C says, or what the law requires us to keep, and we will protect it and use it only for that purpose.
13. Liability, term and law
Each of us is liable for its own breach of this addendum and of the Data Protection Law, to the extent the law makes it so. Liability between us under this addendum is subject to the limits in our Terms of service, except where the law does not allow a limit. This addendum starts when the agreement starts and continues for as long as we process personal data for you. If the Data Protection Law changes, we will agree any update the law requires. If this addendum conflicts with the Terms on personal data, this addendum applies. It is governed by the laws of Kenya, and the dispute provisions of the Terms apply to it.
Annex A: security measures
| Area | Measures |
|---|---|
| Access | Two-step sign-in for every account; Argon2 password hashing; limits on repeated attempts and account lock-out; sessions with idle and maximum lengths; roles and permissions; personal data limited to owners and administrators; no support or staff access to customer content. |
| Separation | Each customer’s data is isolated in the database by row-level security, enforced and tested; each session is bound to exactly one company. |
| Encryption | TLS in transit; secrets and contact details encrypted at rest with a separate key for each company; keys held apart from the data; hashed identifiers for matching. |
| Application | Protection against forged requests; rate limits; signed, replay-protected webhooks; the Service reads, and never writes to, your own systems. |
| Logging and monitoring | Append-only audit logs of important actions, readable by the account owner and by our platform owner only; structured logs with personal data removed; an incident register with a 72-hour clock. |
| Resilience | Daily encrypted backups, with a restore that is tested; backups are kept for a limited time and then replaced. |
| People | Confidentiality commitments for everyone with access; access limited to what the role needs; two-step sign-in for platform staff. |
| Messaging safeguards | Every send passes a gate that checks recorded consent, “STOP”, age, quiet hours and frequency; a “do not message” list that survives erasure in hashed form only. |
Annex B: sub-processors
| Sub-processor | What it does | Where | Data kept |
|---|---|---|---|
| Contabo GmbH | Servers, storage and encrypted backups. | EU | Yes, encrypted. |
| Resend | Sends invitations, password resets, alerts and statements to your staff. | Where the provider operates. | Delivery records, for the period its terms set. |
| OpenAI, Anthropic, Google (AI model providers), and any other we announce under section 6 | Draft posts and captions from prompts. Prompts do not carry your leads’ contact details. | Mainly the United States. | As the provider’s terms and the zero-retention settings we choose allow. |
| Safaricom PLC (M-Pesa) | Takes and confirms payments for the wallet and subscription. | Kenya. | Payment records. |
| Meta (WhatsApp Business, Facebook, Instagram) | Delivers messages and posts from your connected accounts. Only if you connect them. | Where Meta operates. | As Meta’s terms provide. |
| TikTok, X, LinkedIn | Publishes posts to your connected accounts. Only if you connect them. | Where each operates. | As each provider’s terms provide. |
| Africa’s Talking | Delivers SMS from your account. Only if you use SMS. | Kenya and where its network partners operate. | Delivery records. |
| Cloudflare, Inc. (Turnstile) | Optional bot check on our public demo form (not used on your workspace). | Worldwide. | Technical data only. |
The current list is also shown to our platform owner in the console, which includes whichever AI providers are enabled. We will tell you of changes as section 6 says.
Annex C: what we keep after deletion
When data is erased or the workspace is deleted, we keep only:
- a one-way hash of a contact on the “do not message” list, so that the person is never contacted again;
- the ledger of consents given and withdrawn, as hashes, as proof of what was agreed;
- the audit log, which records the fact and time of the deletion, not the content deleted;
- our own billing and accounting records, for the period the law requires; and
- encrypted backups until they expire.
None of these is used for any other purpose.