Legal
Data Processing Agreement
Last updated: 11 November 2026
This agreement forms part of the Terms of Service between Black Bridge Digital (Pty) Ltd ("Clearleave", the processor) and the Customer (the controller). It applies automatically when the Customer accepts the Terms. If you need a signed copy for your records, email support@clearleave.app and we'll send one with the same wording.
Not yet reviewed by a lawyer. This document describes how Clearleave works and the billing policy that applies from launch, and it may change after legal review.
1. Scope and roles
The Customer is the controller (under POPIA, the responsible party) of the personal data it and its users put into Clearleave. Clearleave is its processor (operator). This agreement meets UK GDPR and EU GDPR Article 28, and sections 20 and 21 of South Africa's Protection of Personal Information Act, 2013 (POPIA). The details of the processing are in Annex 1.
2. What Clearleave commits to
- Process the personal data only on the Customer’s documented instructions (these Terms, and the Customer’s use and settings of the service), unless the law requires otherwise, in which case we’ll tell the Customer first unless the law forbids it.
- Make sure everyone authorised to process the data is bound by confidentiality.
- Keep the security measures in Annex 2 in place, and improve them over time without lowering the overall level of protection.
- Use sub-processors only as set out in section 3.
- Help the Customer answer data subject requests. The service already lets the Customer’s admins export all data, export one person’s data, correct records and erase leavers; for anything else we’ll help on request.
- Help the Customer with security, breach notification, data protection impact assessments and prior consultation, taking into account the information available to us.
- At the end of the service, delete the personal data as set out in section 5.
- Make available the information needed to show compliance with this agreement, and allow audits as set out in section 6.
- Tell the Customer straight away if we think an instruction breaks data protection law.
3. Sub-processors
The Customer authorises the sub-processors listed in Annex 3. We'll email the account owners at least 30 days before adding or replacing one. If the Customer objects on reasonable data protection grounds and we can't address the objection, the Customer may close its account before the change and pay nothing for the period after closure. We impose the same data protection obligations on every sub-processor by written contract and remain responsible for them.
Paddle (Paddle.com Market Ltd, United Kingdom) isn't a sub-processor. As our online reseller and Merchant of Record it sells the subscription to the Customer, and it is an independent controller for the payment and billing data it collects at checkout, under its own privacy notice. Paddle receives no Customer Data about the Customer's people: we give it only the account owner's email address, the company name and the number of people to bill.
4. International transfers
Customer Data is hosted in Frankfurt, Germany. Where a sub-processor processes it in a country without an adequacy decision, the transfer is covered by the EU Standard Contractual Clauses (Module 3, processor to processor) with the UK International Data Transfer Addendum, or by the provider's certification under the EU-US and UK-US Data Privacy Framework. For South African Customers, transfers out of South Africa are made under POPIA section 72(1)(a) and (b): to recipients bound by law or binding agreements that give substantially similar protection, and as necessary to perform this contract.
5. Breaches, deletion and return
We'll notify the Customer without undue delay after becoming aware of a personal data breach affecting its data, with the information it needs to meet its own notification duties, and update it as we learn more.
The Customer can export its data at any time. When the Customer closes its account, or the paid period of a cancelled subscription ends, owners and admins can still export for 30 days; a trial account that ends without a plan can export for 12 months. Then the data is deleted from the live service, and drops out of our hosting provider's encrypted backups as those expire, normally within a further 7 days, unless the law requires us to keep it. During the service, data is deleted on the retention schedule below, which the Customer controls.
- Leave requests, balances and their history, approval decisions and the audit log
- Six years after the leave ends, by default (seven for Australian companies). An admin can set anything from the legal minimum for their country up to ten years. Older records are deleted automatically every night.
- People who have left (archived)
- Their name and details stay alongside their records until the retention period has passed since they were archived; then they are anonymised automatically. An admin can erase a leaver’s personal data earlier at any time.
- A cancelled subscription
- When the paid period ends, the account is suspended. Owners and admins can sign in and download the data export for 30 days. We email the owners before deletion; then the company and everything in it is deleted.
- A trial that ended without a plan, or a subscription stopped for non-payment
- The account is suspended. Owners and admins can still sign in to subscribe or download the data export. If no one subscribes, the company and everything in it is deleted 12 months after it was suspended. We email the owners 30 days and 7 days before deletion.
- A closed account
- Owners and admins can sign in and download the data export for 30 days after closing. Then the company and everything in it is deleted.
- Notification records and queued email content
- 90 days.
- Free template downloads from this website
- 30 days, then deleted automatically, unless you asked for Clearleave news when you downloaded. Then we keep the record with your place on the early access list.
- Sign-in sessions (device and IP address) and emailed links
- 30 days after they expire or are used.
- Backups
- Our hosting provider keeps encrypted backups for about 7 days, so deleted data drops out of them as they expire.
6. Audits
We'll answer reasonable written security questionnaires, and provide this agreement's annexes and any relevant reports we hold. If that isn't enough to show compliance, the Customer may audit us once a year, with 30 days' notice, at its own cost, through an independent auditor bound by confidentiality, in a way that doesn't expose other customers' data.
7. POPIA operator terms
As operator we process personal information only with the Customer's knowledge and authorisation, treat it as confidential and don't disclose it except as required by law or in the proper performance of the service, keep the security safeguards required by POPIA section 19 (Annex 2), and notify the Customer immediately where there are reasonable grounds to believe the personal information has been accessed or acquired by an unauthorised person (section 21(2)).
8. General
Liability under this agreement is subject to the limits in the Terms, except where the law doesn't allow them. If this agreement and the Terms conflict on data protection, this agreement wins; if the Standard Contractual Clauses apply and conflict with it, the Clauses win.
Annex 1: Details of the processing
- Subject matter and purpose: providing Clearleave, leave-management software: recording leave, approvals, balances and their history, notifications and calendar, Slack and Microsoft Teams updates.
- Duration: for as long as the Customer uses Clearleave, then until deletion under section 5.
- Data subjects: the Customer's employees, workers, contractors and former staff, and its users (owners, admins, managers).
- Personal data: name, work email, employee reference, role, manager, department, location, job role, skills, working pattern, employment dates, optional birthday (day and month), start date and photo; leave requests, dates, types and reasons; approval decisions; balances and ledger entries; sign-in sessions (IP address and browser); calendar connection email; Slack and Microsoft Teams account identifiers; push notification addresses for the devices where a person switched notifications on; notification records; audit log entries.
- Special categories: health information implied by sickness and similar leave types, and any the Customer's users enter as a reason. Restricted leave types are hidden from colleagues.
- Nature of processing: storage, organisation, retrieval, display to authorised users, calculation, transmission (email, calendar, Slack, Microsoft Teams and push notifications), export, anonymisation and deletion.
Annex 2: Security measures
- Hosting on Render in Frankfurt, Germany, on a private network; encryption at rest for the database, its backups and stored files; HTTPS with HSTS for all traffic.
- Isolation between companies enforced by PostgreSQL row-level security (forced for every company-owned table) as well as in application code; the application connects as a database role without superuser or bypass rights.
- Four least-privilege roles checked on every API route, with the current role loaded on every request; restricted leave types masked for colleagues.
- Passwords hashed with Argon2id; rotating refresh tokens with reuse detection; sessions revoked on password change, password reset and archiving; rate-limited sign-in.
- Calendar and Slack tokens encrypted with AES-256-GCM; Slack webhooks limited to Slack’s own addresses; requests from Slack and Microsoft Teams accepted only once verified as theirs; push notifications sent only to the browser makers’ push services.
- Append-only ledger, approval decisions and audit log, enforced by database triggers; an audit trail of exports, erasures, role changes, archiving, retention runs, account closure and refused access.
- Encrypted backups on the hosting platform: point-in-time recovery for the database and daily snapshots of stored files, each kept for about 7 days.
- Error monitoring without personal data (ids only); security headers and a content security policy on the web app.
- Access to production limited to the people who need it to run the service.
Annex 3: Sub-processors
| Provider | What for | Data | Where | When |
|---|---|---|---|---|
| RenderRender Services, Inc. | Hosting: the web app, API and background worker, the PostgreSQL database, stored files such as profile photos, the Redis queue that holds emails waiting to be sent, and backups of all of these. | All Customer Data. | Frankfurt, Germany (EU) | Always |
| ResendResend, Inc. | Sending notification emails (requests, approvals, invites, password resets). | Recipient name and email address, and the content of the notification (for example the dates and type of leave). | United States | Always |
| SentryFunctional Software, Inc. | Error monitoring, so we can find and fix faults. | Technical error details with internal ids. Names, emails and IP addresses are not sent. | United States | Always |
| PostHogPostHog, Inc. | Product analytics inside the Clearleave app: which features are used and where people get stuck, including session recordings. | Internal user and company ids, role and plan, page paths with ids removed, and usage events. Recordings mask every typed value and all on-screen text; names and emails are not sent. Not used on this website. | Frankfurt, Germany (EU) | Always |
| GoogleGoogle LLC | Adding approved leave to Google Calendar. | The connected account’s email, and each approved leave’s dates and title. | United States | Only if someone connects their Google Calendar |
| MicrosoftMicrosoft Corporation | Adding approved leave to Outlook calendars. | The connected account’s email, and each approved leave’s dates and title. | United States | Only if someone connects their Outlook calendar |
| SlackSlack Technologies, LLC | Sending leave updates to Slack: posts in the channel the Customer chooses, including a daily summary of who is off, and private messages to people about their own leave and to approvers about requests waiting for them. | Names, leave dates and leave type. In a channel, restricted types are shown only as “Absent” and the daily summary shows no leave type. A private message to the person or their approver shows the leave type and any reason given for a decline, as the emails do. Each person’s work email address is sent to Slack to find their Slack account. | United States | Only if an admin connects Slack |
| Microsoft TeamsMicrosoft Corporation | Sending leave updates to Microsoft Teams: posts in the channel the Customer chooses, including a daily summary of who is off, and private messages to people about their own leave and to approvers about requests waiting for them. | Names, leave dates and leave type. In a channel, restricted types are shown only as “Absent” and the daily summary shows no leave type. A private message to the person or their approver shows the leave type and any reason given for a decline, as the emails do. To match people to their Teams accounts, we read the names and email addresses of the members of the team the app is added to. | United States | Only if an admin connects Microsoft Teams |
| Browser push servicesGoogle LLC, Apple Inc., Mozilla Corporation or Microsoft Corporation | Delivering notifications to a phone or computer. Each notification goes through the push service of the browser it is sent to: Google (Chrome, and browsers such as Edge, Brave, Opera and Samsung Internet), Apple (Safari, and Clearleave added to the home screen of an iPhone or iPad), Mozilla (Firefox) or Microsoft (Edge on Windows). | A short notification about a leave request: the dates and length of the leave, the leave type, the name of the person asking (when it goes to an approver) and any reason given for a decline. For restricted leave types, such as sick leave, the leave type and the reason are left out. The notification is encrypted for the device it is sent to. | United States | Only if a person switches on notifications on a device |
Paddle handles billing as an independent controller, not a sub-processor (section 3).