KENYA · GUIDE 0597 · EDITION 4.2
Customer database setup in Kenya: Registration and Activity Checks
Define the activity that authorities need to assess
Configure a customer database using minimal fields and approved access.
Create the customer database around actual service needs, defining identifiers, permitted fields, consent information where relevant, user roles, and duplicate resolution responsibility.
Describe that exact operation when checking requirements. State where the work takes place, whether customers enter the premises, who performs technical tasks and whether you manufacture, resell, deliver or coordinate the service. Requirements can change with these facts; a broad business category is not a complete permit determination.
Sector questions to investigate
- Assess data-controller/processor duties and registration requirements for systems handling personal data.
- Obtain written authority for access, backups, testing and changes.
- Use properly licensed software and assets; document responsibility for third-party renewals and processor contracts.
Keep registration separate from permission to operate
A registered business name does not itself establish approval of premises, products or professional work. Use the Business Registration Service to check the appropriate registration route. Ask the relevant county office which premises and trading checks apply to the actual activity. Confirm tax and invoicing obligations with KRA for your circumstances rather than copying another trader's treatment.
Prepare a written enquiry
| Information to provide | Business-specific starting point |
|---|---|
| Proposed output | Configure a customer database using minimal fields and approved access. |
| Scope and exclusions | Create the customer database around actual service needs, defining identifiers, permitted fields, consent information where relevant, user roles, and duplicate resolution responsibility. |
| First operating step | Define the customer-data purpose, authorized fields, access roles and retention, then demonstrate search and permissions using fictional records before any import. |
| Quality and acceptance | Ask staff to find a customer, record an interaction, update contact details, and handle a duplicate without exposing records unrelated to their duties. |
Add the county, location, premises arrangement, scale, equipment and responsible person's qualifications. Ask which authority handles an issue if it falls outside the first office's remit. Record the answer, reference link, date checked and any renewal or inspection condition. A guide's reference list is a route to verification, not an approval document.
Decide what must wait
Do not offer a regulated service or make a safety, accreditation or certification claim that you cannot substantiate. Resolve an unanswered prerequisite before accepting work that depends on it. A demand interview can often precede trading; a paid or physical trial still needs the appropriate permissions and safe arrangements.
A database fails when staff create fresh records for every interaction or collect sensitive details nobody needs, making accurate customer history harder to maintain.
No universal licence package, current fee or exemption is asserted here. The official links below support only their stated scope.
Prepare a precise activity enquiry
Describe this actual operating scope to the relevant authority or competent adviser: Fictional database CRM-97 organises 100 business contacts with ContactID, organisation, approved contact channel, relationship owner, enquiry status and permission/source note. SampleC0042 belongs to a business contact supplied by client, not scraped leads. Output is restricted database, duplicate-review queue and staff exercise. Marketing sends, identity enrichment, credit scoring and unlimited retention are excluded.
Use these operating details to make the enquiry specific:
| Detail to disclose | Why it can affect the answer |
|---|---|
| Client-owned platform - Role/access and export controls. | Explain the actual premises, scale, use and who will perform the task. Ask which current rule applies to these facts. |
| Source records - 100 authorised rows with purpose/source. | Explain the actual premises, scale, use and who will perform the task. Ask which current rule applies to these facts. |
| Test accounts - Separate editor/viewer fixtures. | Explain the actual premises, scale, use and who will perform the task. Ask which current rule applies to these facts. |
Keep the reply date, official source, exact activity facts and any conditions together. This is an enquiry preparation method, not a determination that a licence, exemption or fee applies. The earlier source dates do not mean legal requirements were rechecked today. Resolve these outstanding checks before relying on a broad business description:
- Actual data purpose, access platform and retention policy unverified.
- No contacts imported or contacted.