Privacy Notice
How personal data is handled when you use Backoffice: who is responsible, what is processed and why, who it is shared with, how long it is kept, and your rights.
On this page
- Primeforce Tech Ltd decides what personal data goes into Backoffice and why. They are the data controller.
- The Provider runs the Service on Primeforce Tech Ltd's instructions. We are the data processor.
- Data is used only to run the Service, keep it secure and meet legal obligations. It is never sold or used for advertising.
- To use your data-protection rights, contact Primeforce Tech Ltd first. We help them respond.
1. Who is responsible for your data
Primeforce Tech Ltd (the “Customer”) uses Backoffice to run its finance, HR, payroll, procurement, sales and operations. The Customer decides whose data is entered, for what purposes and for how long. Under the Kenya Data Protection Act, 2019 (and, where it applies, the EU/UK GDPR), the Customer is the data controller.
The provider of Backoffice (the “Provider”, “we”) hosts and operates the Service for the Customer. We act as a data processor: we process personal data only on the Customer's documented instructions and under a data-processing agreement. We act as a controller only for a small amount of data we need to run our own business, such as account-security telemetry, billing contacts and support correspondence.
2. Personal data processed
| Category | Examples |
|---|---|
| Account and identity | Name, username, work email, phone, role, staff number, profile photo |
| Security and sign-in | Hashed password, two-step verification settings, sign-in times, IP address, browser and device type, failed sign-in attempts |
| Employment, HR and payroll (entered by the Customer) | Job details, leave, attendance, performance, salary, statutory numbers (KRA PIN, NSSF, SHIF), bank details, next of kin |
| Business records | Customers, suppliers, invoices, payments, journals, stock and project records, including contact people |
| Activity and audit | Who created, changed, approved or exported a record, and when |
| Support | Messages and attachments you or your administrator send to support |
Special categories of data, such as health information in sick-leave or medical-benefit records, are processed only when the Customer chooses to record them. Access to them is restricted by role and can be masked for users who do not need it.
3. Why it is processed
- To provide the Service the Customer has subscribed to, on its instructions. The Customer is responsible for having a lawful basis, such as an employment contract, a legal obligation or legitimate interests.
- To secure the Service: authentication, fraud and abuse prevention, audit trails and incident investigation.
- To support and maintain the Service: troubleshooting, backups and fixing defects.
- To meet legal obligations, for example lawful requests from authorities.
Personal data in the Service is not sold, not used for advertising or profiling for marketing, and not used to train third-party AI models.
4. Who it is shared with
- Within the Customer: people whose role allows it, as configured by the Customer's administrators.
- Sub-processors that help us run the Service, such as cloud hosting, email delivery and SMS delivery. Each is bound by a contract with data-protection, confidentiality and security obligations at least as strict as ours. The Customer can request the current list and is told about changes in advance.
- Services the Customer connects, such as banks, payment providers and tax authority systems (for example KRA eTIMS). Data is sent to them only when the Customer turns on and uses that integration.
- Authorities, when the law requires it. Where the law allows, we tell the Customer first.
Provider support staff cannot see the Customer's data by default. A support engineer needs a time-limited support session approved by the Customer's administrator, and every action taken in it is logged under that engineer's name.
5. Where it is stored
Data is stored in the hosting region agreed with the Customer. When data is transferred outside Kenya, for example to a sub-processor's infrastructure, we use the safeguards required by sections 48–50 of the Kenya Data Protection Act. These include appropriate contractual protections and transfers to countries with adequate protection.
6. How long it is kept
- The Customer controls how long business, HR and payroll records are kept, in line with its own legal record-keeping duties (for example tax and employment law).
- Audit and security logs are kept as long as the Customer's retention settings require. They are protected against changes.
- When the subscription ends, the Customer can export its data during the period set out in the Customer Agreement. After that, the data is deleted from live systems. Encrypted backups are overwritten on their normal rotation cycle.
Removing a user's access does not delete records that user created. Those records stay part of the Customer's business and audit history.
7. How it is protected
- Encryption in transit (HTTPS/TLS). Database backups are encrypted.
- Passwords are stored as salted one-way hashes. Accounts lock after repeated failed sign-ins.
- Two-step verification (authenticator app) is available, and the Customer can require it.
- One active session per account, automatic sign-out after inactivity, and secure, HTTP-only cookies.
- Role-based access is enforced on the server for every request. Sensitive fields such as salaries and bank details can be masked by role.
- Audit trails record sign-ins, security changes and record changes. Each customer workspace is kept separate from the others.
8. Your rights
Under the Kenya Data Protection Act, 2019 (and the GDPR where it applies), you have the right to:
- be told how your data is used, and get a copy of it;
- have inaccurate data corrected, and incomplete data completed;
- object to processing, or ask for it to be restricted;
- ask for data to be deleted when there is no longer a lawful reason to keep it;
- receive data you provided in a portable format, where this applies.
Because Primeforce Tech Ltd is the controller, send your request to Primeforce Tech Ltd, usually its HR department, data protection officer or system administrator. If you send a request to us, we pass it to the Customer and help them respond. You can update many profile details yourself in the Service.
You can complain to the Office of the Data Protection Commissioner (ODPC) in Kenya, or to the supervisory authority where you live.
9. Cookies and device storage
Backoffice uses only the cookies and browser storage it needs to work and to stay secure. There are no advertising cookies and no third-party tracking cookies, so you are not asked for cookie consent.
| Name | Type | Purpose | Duration |
|---|---|---|---|
CoreERP.Auth | Essential cookie | Keeps you signed in | Until you sign out or close the browser |
CoreERP.Session | Essential cookie | Remembers short-lived state between pages | Browser session |
.AspNetCore.Antiforgery.* | Security cookie | Protects forms against cross-site request forgery | Browser session |
mizani-last-user | Browser storage (this device only) | Remembers the last username for the “Recent sign-in” shortcut. Remove it with the × on the sign-in page. | Until removed |
mizani-theme | Browser storage (this device only) | Remembers light or dark mode | Until removed |
You can clear cookies and site data in your browser at any time. Removing essential cookies signs you out.
10. Personal data breaches
If a personal data breach affects the Customer's data, we notify the Customer without undue delay and give it the information it needs. This lets the Customer meet its duty to notify the Data Protection Commissioner within 72 hours, and to inform affected people where required (section 43 of the Kenya Data Protection Act).
11. Children
Backoffice is a workplace system and is not intended for children. Data about minors, such as employees' dependants, is recorded only when the Customer needs it, for example for medical benefits.
12. Changes to this notice
We update this notice when the Service or the law changes. Each version shows its number and effective date, and earlier versions are listed under Version history. We tell the Customer about material changes in advance.
13. Contact
Contact Primeforce Tech Ltd about your personal data first, through its HR department, data protection officer or system administrator. Send questions about how the Provider processes data, or about this notice, to welcome@primeforce.africa.
Version history
| Version | Effective | What changed |
|---|---|---|
| 2.0 | 4 Oct 2026 | Clarified controller/processor roles (Kenya Data Protection Act 2019, GDPR); added sub-processors, international transfers, data-subject rights, breach notification and a cookies & device-storage table. |
| 1.0 | 19 Sep 2026 | First published. |
Questions about your data?
For data held about you, contact Primeforce Tech Ltd. For questions about how the Provider processes data, contact us. We can't give legal advice.