Skip to content

Legal

PAIA manual

Last updated: 11 November 2026

The manual of Black Bridge Digital (Pty) Ltd under section 51 of the Promotion of Access to Information Act, 2000 (PAIA), which also covers the processing of personal information required by the Protection of Personal Information Act, 2013 (POPIA). It explains which records we hold and how to ask for them.

Clearleave is operated by Black Bridge Digital (Pty) Ltd, a private company registered in South Africa (registration number 2026/683038/07), of 719 Sutherland Avenue, Port Edward, KwaZulu-Natal, 4278, South Africa. Contact: support@clearleave.app.

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. Company details

  • Name: Black Bridge Digital (Pty) Ltd (trading as Clearleave)
  • Registration number: 2026/683038/07
  • Physical address: 719 Sutherland Avenue, Port Edward, KwaZulu-Natal, 4278, South Africa
  • Postal address: 719 Sutherland Avenue, Port Edward, KwaZulu-Natal, 4278, South Africa
  • Telephone: +27 71 801 5292
  • Email: support@clearleave.app
  • Website: https://www.clearleave.app

2. Information Officer

Our Information Officer is Herman Coetzee, who handles requests under PAIA and POPIA. Contact them at legal@clearleave.app or at the postal address above.

3. The Information Regulator's guide

The Information Regulator publishes a guide on how to use PAIA and POPIA (section 10 of PAIA), in all official languages. It is available from the Regulator's website, inforegulator.org.za, and a copy can be inspected at our offices on request.

4. Records available without a request

These are on our website for anyone to read: the Privacy Policy, Terms of Service, Data Processing Agreement, security information and this manual.

5. Records we hold

  • Company records: incorporation documents, share register, minutes and resolutions, as kept under the Companies Act 71 of 2008.
  • Financial and tax records: annual financial statements, accounting records, invoices, and tax records kept under the Tax Administration Act 28 of 2011 and the Value-Added Tax Act 89 of 1991.
  • Staff records: employment contracts, payroll, leave and working-time records, kept under the Basic Conditions of Employment Act 75 of 1997, the Labour Relations Act 66 of 1995, the Employment Equity Act 55 of 1998, the Unemployment Insurance Act 63 of 2001 and the Skills Development Act 97 of 1998.
  • Customer records: account details, contracts, billing and support correspondence.
  • Supplier records: contracts and correspondence with our service providers.
  • Technical records: system logs, the audit log, security and backup records.

Records inside Clearleave about our customers' own employees belong to those customers. We hold them as their operator, so a request for them should go to the employer; we'll refer requests we receive to the customer concerned.

6. Processing of personal information (POPIA)

Purpose. To provide Clearleave to our customers, run and secure the service, manage our customer and supplier relationships, employ our staff, and meet our legal obligations.

Categories of data subjects and information.

  • Customers’ users and employees: name, work email, role, organisational details, leave records (which may include health information), sign-in and session details. Processed as operator for the customer.
  • Customer contacts: name, email, company, billing details.
  • Our staff: identity, contact, employment, payroll and tax details.
  • Suppliers: company and contact details, banking details.
  • Website visitors: technical request data (IP address, browser).

Recipients. Our sub-processors below; Paddle (Paddle.com Market Ltd, United Kingdom), our online reseller, which handles billing as an independent controller; our professional advisers and auditors; and public bodies where the law requires.

Sub-processors
ProviderWhat forDataWhereWhen
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 StatesAlways
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 StatesAlways
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 LLCAdding approved leave to Google Calendar.The connected account’s email, and each approved leave’s dates and title.United StatesOnly if someone connects their Google Calendar
MicrosoftMicrosoft CorporationAdding approved leave to Outlook calendars.The connected account’s email, and each approved leave’s dates and title.United StatesOnly if someone connects their Outlook calendar
SlackSlack Technologies, LLCSending 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 StatesOnly if an admin connects Slack
Microsoft TeamsMicrosoft CorporationSending 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 StatesOnly if an admin connects Microsoft Teams
Browser push servicesGoogle LLC, Apple Inc., Mozilla Corporation or Microsoft CorporationDelivering 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 StatesOnly if a person switches on notifications on a device

Cross-border flows. Clearleave is hosted in Frankfurt, Germany, and some sub-processors are in the United States. Transfers are made under POPIA section 72, as described in our Privacy Policy.

Security. The measures are set out in Annex 2 of our Data Processing Agreement and on our security page.

7. How to request a record

  • Complete Form 2 (Request for Access to Record) under the PAIA Regulations, available from the Information Regulator’s website, and send it to the Information Officer by email or post.
  • Give enough detail to identify the record, say which form of access you want, and, if you ask on someone else’s behalf, show your authority to do so.
  • The PAIA Regulations set a request fee and, if access is granted, an access fee for search, preparation and copies. We’ll tell you the amount before we do the work. People asking for their own personal information don’t pay the request fee.
  • We’ll decide within 30 days, which the Act allows us to extend once by up to 30 days, and tell you the outcome and reasons. Access may be refused on the grounds in Chapter 4 of Part 3 of PAIA (for example, to protect someone else’s privacy or commercial information).
  • If you disagree with our decision, you can complain to the Information Regulator or apply to court within 180 days.

8. Availability of this manual

This manual is on our website and can be inspected at our offices free of charge. We review it at least once a year.