Data Processing Agreement
Last updated: 15 November 2026
This agreement is between the Customer named in the Appsentia account and Appsentia (Pty) Ltd, of Cape Town, South Africa ("Appsentia"). It forms part of the Appsentia Terms of Service ("Terms") and is accepted with them (clause 20.6 of the Terms). Contact: Kgothatso Matlala, Information Officer, kgothatso@appsentia.com.
1. Definitions and roles
1.1 "UK GDPR" and "DPA 2018": the UK General Data Protection Regulation and the Data Protection Act 2018. "POPIA": the Protection of Personal Information Act 4 of 2013 (South Africa). "Data Protection Law": whichever of these applies to the processing.
1.2 "Customer Personal Data": personal data in the Customer Data (as defined in the Terms) that Appsentia processes for the Customer. Annex 1 describes it.
1.3 For Customer Personal Data, the Customer is the controller (UK GDPR) and the responsible party (POPIA). Appsentia is the processor (UK GDPR) and the operator (POPIA).
1.4 For account, billing, website and support data about the Customer's Users and contacts, Appsentia is the controller. Appsentia's Privacy Notice covers that data, not this agreement.
1.5 Partners. Where a Partner manages the Customer's account, the Partner is the Customer's own service provider and acts on the Customer's instructions. The Partner is not Appsentia's subprocessor. The Customer is responsible for the Partner's access to Customer Personal Data and for its own agreement with the Partner. A Partner that creates a client company accepts this agreement on the Customer's behalf. A Partner linked to a company that already has an account acts under that company's acceptance. If a UK client company has not accepted the current version, a Partner that starts a subscription checkout for it accepts that version on the Customer's behalf.
1.6 Terms used here and defined in Data Protection Law have the meaning given there. "Personal data" includes "personal information", "controller" includes "responsible party", "processor" includes "operator", and "special category data" includes "special personal information".
2. Instructions
2.1 Appsentia processes Customer Personal Data only on the Customer's documented instructions. The instructions are: the Terms, this agreement, and the Customer's use and configuration of the Service (uploads, integrations it connects, settings, scheduled reports and their recipients).
2.2 Appsentia may process Customer Personal Data outside those instructions only where the law requires it. Appsentia will tell the Customer first unless the law forbids it.
2.3 Appsentia will tell the Customer if it believes an instruction breaches Data Protection Law.
2.4 Appsentia does not sell Customer Personal Data, does not use it for its own purposes, and does not combine it with other customers' data. Appsentia does not use Customer Personal Data, alone or combined with other data, to calculate benchmarks. The benchmark figures in the Service come from published sources.
3. Health data and other special category data
3.1 Customer Personal Data includes health data: sick leave records, leave type names (which may describe a condition), and absences the Customer marks as pregnancy-related or disability-related.
3.2 The Customer is responsible for having a lawful basis and, for UK employees, a condition under Article 9 UK GDPR and Schedule 1 of the DPA 2018 (including any appropriate policy document), and for South African employees, a ground under sections 26 to 33 of POPIA.
3.3 The Customer is responsible for telling its employees about the processing, including the risk scores, Bradford Factor scores and alerts the Service calculates.
3.4 The Service calculates risk scores, Bradford Factor scores and alerts (including "flight risk", threshold, pattern and Bradford trigger alerts) about individual employees. Appsentia does not make decisions about employees. The Customer is responsible for any decision and for meeting Article 22 UK GDPR and section 71 POPIA where they apply.
3.5 The Service stores each uploaded file in full. The Customer should remove columns the Service does not need before upload.
4. Appsentia personnel
4.1 The people with access to Customer Personal Data are Appsentia's own staff in South Africa who need it to provide or support the Service. They are bound by confidentiality.
4.2 Appsentia's administrator role can see all customer accounts for support and billing. Changes that administrators make to companies, users and subscriptions are recorded in the audit log. Viewing data is not logged.
5. Security
5.1 Appsentia applies the measures in Annex 2.
5.2 Appsentia may change the measures if the overall level of protection does not fall.
6. Subprocessors
6.1 The Customer gives general authorisation for Appsentia to use the subprocessors in Annex 3.
6.2 Appsentia will give at least 30 days' notice by email of a new or replaced subprocessor. The Customer may object on reasonable data protection grounds within that period. If the parties cannot resolve the objection, the Customer may cancel its subscription under clause 10 of the Terms.
6.3 Appsentia imposes on each subprocessor data protection terms that give at least the protection in this agreement, and remains liable to the Customer for its subprocessors.
6.4 HR and payroll systems the Customer connects (for example PaySpace) are the Customer's own providers, not Appsentia's subprocessors. A Partner is not a subprocessor either (clause 1.5).
7. International transfers
7.1 Customer Personal Data is stored in Amazon Web Services (AWS) in the United States (US East, N. Virginia, us-east-1). Web pages are delivered through AWS locations in North America and Europe. Email, including scheduled reports, is sent through an email hosting provider whose server is in Frankfurt, Germany. Appsentia's staff access the data from South Africa. There is no UK or South African hosting.
7.2 For UK customers, the transfers are (a) from the Customer in the UK to Appsentia in South Africa, and (b) onward from Appsentia to the subprocessors in Annex 3.
7.3 The parties make transfer (a) under the International Data Transfer Addendum to the EU Standard Contractual Clauses, issued by the UK Information Commissioner ("UK Addendum"), with Module 2 (controller to processor) of the EU Standard Contractual Clauses ("SCCs"). The UK Addendum and the SCCs are incorporated into this agreement by reference. Annex 4 completes the tables of the UK Addendum from Annexes 1 to 3.
7.4 Appsentia makes transfer (b) to AWS under the AWS Data Processing Addendum and its UK GDPR Addendum. The email hosting provider is in Germany, which is covered by the UK's adequacy regulations for the European Economic Area. PayFast is in South Africa, as Appsentia is.
7.5 Appsentia gives the Customer the information it reasonably needs for its own transfer risk assessment.
7.6 For South African customers, Appsentia transfers Customer Personal Data outside South Africa under section 72(1)(a) of POPIA: to AWS in the United States under a binding agreement, the AWS Data Processing Addendum, and to the email hosting provider in Germany, where the EU General Data Protection Regulation applies.
8. Data subject requests
8.1 The Service lets company admins view, correct and delete employee records, and export employee data and analyses to Excel. Deleting an employee deletes their leave records, scores, alerts and reports. It does not remove their rows from uploaded files, which are stored in full.
8.2 If Appsentia receives a request from a data subject about Customer Personal Data, it will pass it to the Customer within 5 business days and tell the person that it has done so. Appsentia will not answer the request itself.
8.3 Appsentia will give the Customer reasonable help to answer requests that the Customer cannot answer with the Service.
9. Personal data breaches
9.1 Appsentia will notify the Customer without undue delay, and in any event within 48 hours, after becoming aware of a personal data breach affecting Customer Personal Data. For POPIA, this is the notice required by section 21(2).
9.2 The notice will give, as far as known: what happened, the categories and approximate numbers of data subjects and records, the likely consequences, the measures taken or proposed, and a contact person. Appsentia will add information as it becomes available.
9.3 Appsentia will take reasonable steps to contain the breach and help the Customer meet its own duties to notify the Information Commissioner's Office, the Information Regulator and data subjects.
10. Impact assessments
10.1 Appsentia will give reasonable help with the Customer's data protection impact assessments and any prior consultation with a regulator, by providing information about the Service. Because the Service scores individual employees using health data, the Customer may need a data protection impact assessment.
11. Deletion or return
11.1 During a trial or subscription the Customer can export its data and delete employee records itself.
11.2 When a trial or subscription ends, the Customer Personal Data stays in the Service until the Customer asks Appsentia to delete it. Appsentia deletes it within 30 days of the request. Deleting a company removes its database records and its uploaded files. Copies in database backups expire 7 days after the deletion. Application logs are kept for 90 days.
11.3 Appsentia sends the Customer an export of the Customer Personal Data on request at any time, including after the subscription ends, free of charge. Exporting in the Service itself needs an active trial or subscription.
11.4 Appsentia may delete the Customer Personal Data after 12 months with no trial or subscription, after giving 30 days' notice by email.
11.5 Appsentia may keep Customer Personal Data that the law requires it to keep.
11.6 Appsentia will confirm deletion in writing on request.
12. Information and audits
12.1 Appsentia will make available the information needed to show it meets this agreement, including answers to reasonable security questionnaires.
12.2 The Customer may audit Appsentia's compliance once in any 12 months, on at least 30 days' notice, during business hours, at its own cost, and subject to confidentiality. An audit of a subprocessor is met by that subprocessor's own audit reports where available.
13. Liability and term
13.1 Liability under this agreement, including for data protection claims, is subject to the limits in clause 15 of the Terms. There is no separate limit.
13.2 This agreement lasts as long as Appsentia processes Customer Personal Data.
13.3 If this agreement and the Terms conflict on personal data, this agreement applies. If the UK Addendum or the SCCs conflict with this agreement, the UK Addendum and the SCCs apply.
Annex 1. Details of processing
| Item | Details |
|---|---|
| Subject matter | Hosting and analysis of the Customer's employee and leave records to provide absence analytics. |
| Duration | The trial and the subscription, and after they end, until the Customer Personal Data is deleted under clause 11. |
| Nature | Storage, import from files or a connected HR system, calculation, scoring, display, export, PDF report generation, and email delivery of reports the Customer schedules. |
| Purpose | To provide the Service to the Customer. |
| Data subjects | The Customer's employees and former employees. Recipients of scheduled reports. |
| Employee data | Employee number, surname, initials, department, sub-department, date of employment, date of termination, employment status, payroll cycle. Any other columns in an uploaded file, which is stored in full. |
| Leave data | Leave type as recorded and as normalised, whether it counts as sick leave, start and end dates, number of days, identifiers and status from a connected HR system, exclusion flag and reason (pregnancy, disability, other). |
| Calculated data | Absence rates, estimated absence cost (from the company's average daily salary, not individual pay), pattern flags, risk score and level with contributing factors, Bradford Factor score, alerts and their status, PDF and Excel reports. |
| Special category data | Health data in sick leave records and leave type names. Pregnancy and disability as exclusion reasons. |
| Other personal data | Names and email addresses of scheduled report recipients. Previous and new values of changed records in the audit log. |
| Frequency | Continuous during the subscription. |
| Retention | Until the Customer deletes it, or as clause 11 sets out. Uploaded files stay on the application server disk until the next deployment of the application or until the company is deleted, whichever comes first. |
Annex 2. Security measures
Technical measures, as the code and infrastructure configuration show:
- TLS 1.2 or later between the browser and Appsentia's servers
- The database is stored encrypted
- Passwords are stored only as bcrypt hashes
- Sign-in sessions expire after 10 minutes without activity
- Role-based access, with each company's data kept separate and members limited to their departments
- The audit log described in section 4 of the Privacy Notice
- Daily backups, kept for 7 days
Organisational measures: access to Customer Personal Data is limited to Appsentia staff who need it.
Annex 3. Subprocessors
| Subprocessor | Service used | Customer Personal Data processed | Location |
|---|---|---|---|
| Amazon Web Services, Inc. | Database, application servers, uploaded files, logs, backups, and delivery of web pages | All Customer Personal Data | United States (us-east-1). Web pages are delivered through AWS locations in North America and Europe. |
| Email hosting provider | Sending email: invitations, verification, password reset, invoices, alerts and scheduled reports | Recipient email addresses. Scheduled reports attach PDFs that contain employee absence data. | Germany (Frankfurt) |
| PayFast | Card payments | Billing contact data only: company name and the payer's email address | South Africa |
Annex 4. UK transfer terms
For transfers from UK customers, the UK Addendum (version B1.0, issued under section 119A of the Data Protection Act 2018) applies to Module 2 of the SCCs, with these tables:
| UK Addendum table | Completed as |
|---|---|
| Table 1. Parties | Exporter: the Customer, as named in its Appsentia account, controller. Importer: Appsentia (Pty) Ltd, Cape Town, South Africa, processor; contact Kgothatso Matlala, Information Officer, kgothatso@appsentia.com. Start date: the date the Customer accepts the Terms. |
| Table 2. Selected SCCs, modules and clauses | Module 2 (controller to processor). Clause 7 (docking clause) does not apply. Clause 9(a): general authorisation, with 30 days' notice of changes (clause 6.2). Clause 11: the optional language does not apply. Clause 13: the competent supervisory authority is the Information Commissioner. Clauses 17 and 18: the law and courts of England and Wales. |
| Table 3. Appendix information | Annex I.A, list of parties: as Table 1. Annex I.B, description of the transfer: Annex 1 of this agreement. Annex II, technical and organisational measures: Annex 2 of this agreement. Annex III, list of subprocessors: Annex 3 of this agreement. |
| Table 4. Ending the UK Addendum when the Approved Addendum changes | Neither party may end it. |