KrazyBuildsPAIA manual

PAIA Manual: KrazyBuilds (Pty) Ltd

Last updated: 18 November 2026 (pre-launch version)

This manual is prepared under section 51 of the Promotion of Access to Information Act 2 of 2000, as amended. It follows the Information Regulator's PAIA Manual Template for Private Bodies.

About KrazyBuilds

KrazyBuilds (Pty) Ltd ("KrazyBuilds", "we", "us", "our") is a private company. It was registered with the CIPC on 1 October 2026, under registration number 2026/784933/07. It trades as KrazyBuilds, and its financial year ends in February.

We are a one-person company. Keagan Christians is our only director and our only shareholder. We have no employees.

We build our own software products, including a consumer mobile app we are developing, which has not launched. We are testing it with a small group of people we know. We don't build software, websites or apps for other people, and we don't take on client work. Our company website, https://krazybuilds.com, gives our company details and has a contact form.

We will update this manual before the app launches, to describe the information it handles.

Contents

  1. List of acronyms and abbreviations
  2. Purpose of this PAIA manual
  3. Key contact details for access to information of KrazyBuilds (Pty) Ltd
  4. Guide on how to use PAIA and how to obtain access to the Guide
  5. Categories of records of KrazyBuilds which are available without a person having to request access
  6. Description of the records of KrazyBuilds which are available in accordance with any other legislation
  7. Description of the subjects on which KrazyBuilds holds records and categories of records held on each subject
  8. How to request access to a record
  9. Processing of personal information
  10. Availability of the manual
  11. Updating of the manual

1. List of acronyms and abbreviations

Term Meaning
CIPC Companies and Intellectual Property Commission
DIO Deputy Information Officer (we have none; see 3.2)
Guide The Regulator's Guide on how to use PAIA (section 10 of PAIA)
IO Information Officer
Minister The Cabinet member responsible for the administration of justice (section 1 of PAIA)
PAIA Promotion of Access to Information Act 2 of 2000, as amended
PAIA Regulations Regulations relating to the Promotion of Access to Information, 2021 (Government Notice R. 757, Government Gazette 45057, 27 August 2021)
POPIA Protection of Personal Information Act 4 of 2013
POPIA Regulations Regulations relating to the Protection of Personal Information, 2018 (Government Notice R. 1383, Government Gazette 42110, 14 December 2018), as amended by Government Notice 6126 (Government Gazette 52523, 17 April 2025)
Regulator Information Regulator (South Africa)
Republic Republic of South Africa
SARS South African Revenue Service

2. Purpose of this PAIA manual

This manual helps you to:

3. Key contact details for access to information of KrazyBuilds (Pty) Ltd

3.1 Information Officer

As our only director, Keagan Christians runs the company as its chief executive officer or equivalent officer, so he is the head of KrazyBuilds under PAIA (section 1 of PAIA, definition of "head"). That also makes him our Information Officer under POPIA (section 1 of POPIA, definition of "information officer"). We registered him with the Regulator as our Information Officer on 21 October 2026, as POPIA section 55(2) requires.

Name Keagan Christians, Sole Director
Telephone 076 042 8300
Email hello@krazybuilds.com
Fax None
Postal address 961 Steinkopf Street, Saron, Western Cape, 6812
Street address 961 Steinkopf Street, Saron, Western Cape, 6812

3.2 Deputy Information Officer

We have no Deputy Information Officer. We are a one-person company with no employees, so every request goes to the Information Officer. POPIA section 56 provides for "such a number of persons, if any," as deputy information officers as is necessary.

3.3 Access to information general contacts

Email: hello@krazybuilds.com. Please write "PAIA request" or "POPIA request" in the subject line.

3.4 National or head office

Our registered office is our only office.

Postal address 961 Steinkopf Street, Saron, Western Cape, 6812
Physical address 961 Steinkopf Street, Saron, Western Cape, 6812
Telephone 076 042 8300
Email hello@krazybuilds.com
Website https://krazybuilds.com

Please email or phone before you visit, so that someone is there to help you.

4. Guide on how to use PAIA and how to obtain access to the Guide

4.1 Under section 10(1) of PAIA, the Regulator has updated and made available the revised Guide on how to use PAIA (the "Guide"). It is written in an easy-to-understand way for anyone who wants to use a right under PAIA or POPIA. The Regulator's website lists it as the October 2021 version.

4.2 The Regulator says the Guide is available in each of the official languages and in braille.

4.3 The Guide describes (section 10(2) of PAIA):

4.4 You can inspect the Guide at our registered office during normal office hours. Inspection is free (regulations 3(1) and 3(3) of the PAIA Regulations).

4.5 You can also get the Guide:

4.6 Regulation 3(1) of the PAIA Regulations requires us to keep a copy of the Guide in at least two official languages at our registered office, for public inspection during normal office hours. We keep it in:

4.7 The Regulator's contact details:

Website https://inforegulator.org.za
Address Woodmead North Office Park, 54 Maxwell Drive, Woodmead, Johannesburg, 2191
Telephone 010 023 5200
Toll-free 0800 017 160
General enquiries enquiries@inforegulator.org.za
PAIA complaints PAIAComplaints@inforegulator.org.za
POPIA complaints POPIAComplaints@inforegulator.org.za

5. Categories of records of KrazyBuilds which are available without a person having to request access

We choose to make the records below available without a PAIA request (section 52(1) of PAIA and regulation 5 of the PAIA Regulations). You don't need a form. Download them, or ask us by email, by phone or by letter. We update this list as soon as practically possible after it changes, and we make it available to the Regulator, on our website, and for inspection at our registered office during normal office hours (regulation 5(2)).

Category of records Types of the record Available on website Available upon request
About the company Company name, registration number and contact details Yes Yes
PAIA This manual Yes Yes
Company information and website terms Our company details and the terms for using our website (https://krazybuilds.com/company/) Yes Yes
Privacy notice How we handle the personal information of visitors to our website and people who contact us (https://krazybuilds.com/privacy/) Yes Yes
Our website The pages of https://krazybuilds.com Yes Yes
PAIA Guide The Regulator's Guide on how to use PAIA (see section 4) Yes, through the Regulator's website Yes, free

Downloaded and emailed copies are free. For a printed copy, we may charge the reproduction fees in items 2 to 8 of Annexure B to the PAIA Regulations, for example R2.00 per A4 page (section 52(3) of PAIA; regulation 5(3)).

PAIA asks a manual to include the latest notice under section 52(2), if any. There is none: POPIA deleted section 52(2).

6. Description of the records of KrazyBuilds which are available in accordance with any other legislation

Some laws require us to keep certain records, and some give certain people a right to see them. Where another law gives you access, you may use that law. This list isn't complete, and it doesn't mean that anyone may see every record in it.

Category of records Applicable legislation
Memorandum of Incorporation; record of directors; securities (share) register; annual financial statements and accounting records; notices, minutes and resolutions of shareholder meetings; minutes and resolutions of the director. Section 26 of the Companies Act sets out who may inspect or copy the securities register and the register of directors, and on what terms. Companies Act 71 of 2008 (sections 24 and 26)
Tax registration, returns, assessments and the records behind them Income Tax Act 58 of 1962; Tax Administration Act 28 of 2011
This PAIA manual; PAIA requests and our decisions Promotion of Access to Information Act 2 of 2000
Information Officer registration; POPIA requests, objections and complaints Protection of Personal Information Act 4 of 2013

Some of these records only exist once they fall due, such as our first annual return and annual financial statements.

7. Description of the subjects on which KrazyBuilds holds records and categories of records held on each subject

7.1 What we hold

Subjects on which we hold records Categories of records
Company administration Memorandum of Incorporation; CIPC registration certificate and filings; share register and share certificate; director's resolutions; beneficial ownership filing; Information Officer registration; correspondence about the company's D-U-N-S number
Finance and tax Invoices, receipts and payment records; bank records; accounting records and financial statements; SARS registrations, returns and correspondence
Suppliers and platforms Agreements, terms and account records with suppliers such as Google (including Google Play and the Play Console), Cloudflare, Supabase, GitHub, Web3Forms, Resend (which sends our replies from the support mailbox of a second product we are building), Anthropic (the AI assistant we use to build our software and run the company), RevenueCat (for our app's subscriptions, once they start) and Amazon Web Services (see 9.4); domain records for krazybuilds.com; supplier invoices
Our app: the product Source code and technical documents (kept on GitHub); designs; app releases; our draft Google Play listing; every version of the app's privacy policy and terms of service
Our app: information about testers that we hold Test data that testers share with each other, and the anonymous cloud accounts behind it (see 9.2); emails from testers, such as support or deletion requests
Website and enquiries Website content; contact-form messages; emails; phone, SMS and WhatsApp messages. These include any enquiries about the client services our website used to offer.
PAIA and POPIA This manual and its earlier versions; requests we receive and our replies; complaints
Employees None. We have no employees, so we hold no employee records.

7.2 How long we keep records

8. How to request access to a record

8.1 Who can ask

Anyone may ask, whether or not they are South African (the Guide, paragraph 12.1). Because we are a private body, you must show that you need the record to exercise or protect a right (section 50(1) of PAIA). This includes a record with personal information about you (section 50(3)). POPIA also gives you rights to your own personal information (see 9.6).

8.2 The form

Use Form 2, "Request for Access to Record" (regulation 7(1) of the PAIA Regulations). Download it from the Regulator at https://inforegulator.org.za/wp-content/uploads/2020/07/InfoRegSA-PAIA-Form02-Reg7.pdf, or ask us and we'll send you one.

On the form you (section 53(2) of PAIA):

The form asks for proof of your identity. Please don't email a copy of your ID document: our mailbox is a Google (Gmail) account that isn't under business data processing terms (see 9.5). Send that copy by post or by hand instead, or ask us and we'll confirm who you are by video call. For the rest of the form, we accept a scan or photo of the signed form, or a form you sign electronically.

8.3 Where to send it

Send the form to our Information Officer (section 53(1) of PAIA):

We don't have a fax number.

8.4 Help with your request

We must help you make your request (regulation 7(2)(a)). If you can't write it yourself because of illiteracy or a disability, you can make it orally. We will then complete Form 2 for you and give you a copy (regulation 7(2)(b)). The Regulator may also help you, free of charge, if it reasonably can (the Guide, paragraph 17.3).

8.5 Fees

These are the fees for private bodies in Annexure B to the PAIA Regulations. The Regulator publishes the same table at https://inforegulator.org.za/paia-fees-structure-2/.

Item What it is for Amount
1 Request fee, paid by every requester R140.00
2 Photocopy or printed black-and-white copy of an A4 page R2.00 per page or part of a page
3 Printed copy of an A4 page R2.00 per page or part of a page
4 Copy in computer-readable form: on a flash drive you provide / on a CD you provide / on a CD we provide R40.00 / R40.00 / R60.00
5 Transcription of visual images, per A4 page Outsourced; depends on the service provider's quote
6 Copy of visual images Outsourced; depends on the service provider's quote
7 Transcription of an audio record, per A4 page R24.00
8 Copy of an audio record: on a flash drive you provide / on a CD you provide / on a CD we provide R40.00 / R40.00 / R60.00
9 Searching for and preparing the record, for each hour or part of an hour after the first hour R145.00 an hour, up to R435.00 in total
10 Deposit, if the search will take more than 6 hours One third of the amount, calculated using items 2 to 8
11 Postage, email or any other electronic transfer Actual cost, if any

How the fees work:

8.6 How long it takes

8.7 Why a request may be refused

We may refuse only on the grounds in Chapter 4 of Part 3 of PAIA. In broad terms, they protect:

Even then, we must release a record if it would reveal a substantial breach of the law, or an imminent and serious risk to public safety or the environment, and the public interest clearly outweighs the harm (section 70). If only part of a record may be withheld, we release the rest (section 59).

If a record can't be found, or doesn't exist, we'll tell you by affidavit or affirmation, with the steps we took to look for it (section 55).

PAIA doesn't apply to a record requested for criminal or civil proceedings that have already started, if another law provides for access to it (section 7).

8.8 If you are unhappy with our decision

Private bodies have no internal appeal. You can:

9. Processing of personal information

Under POPIA we are the "responsible party" for the personal information we decide to process. This section gives the information that section 51(1)(c) of PAIA requires.

9.1 Purpose of processing personal information

We process personal information to:

We don't sell personal information or use it for advertising. Our app has no ads, no advertising ID, no analytics, no crash reporting and, so far, no AI processing of testers' data (see 9.4 for what we plan).

9.2 Description of the categories of data subjects and of the information or categories of information relating thereto

Categories of data subjects Personal information that may be processed Where it is held
Testers: information on their phone The information a tester enters or saves in the app, what the app works out from it, and their consent choices On the tester's phone only. We never receive it, except the test data a tester chooses to share (next row).
Testers who share test data with each other (only with their consent) Display name; the label, code, values and status of the test data they share; an anonymous identifier for the phone; the IP address the phone connects from Supabase, hosted in Ireland (EU)
People named in shared test data (who may not be testers) The display name the tester typed; the values and status recorded for them Supabase, only while the data is shared
People who contact us Name; email address; phone or WhatsApp number; the message, and anything else you send. The website form asks for your name, email address and message, and records that you ticked its consent box (see 9.4). Our mailbox at Google (Cloudflare routes hello@krazybuilds.com mail to it, and Web3Forms delivers website messages to it); Web3Forms' own copy of website messages (see 7.2); WhatsApp chats on the director's phone. For the support mailbox of a second product we are building: a second Gmail account of our director's (Cloudflare routes that mail to it), and Resend, which sends our replies (see 9.4)
Website visitors IP address, and technical details such as browser, device and pages visited Cloudflare, which hosts and protects krazybuilds.com, keeps its own security logs, and gives us cookie-free visit statistics (Cloudflare Web Analytics, which it adds to the site's pages itself)
Suppliers and service providers Company names; names and business contact details of the people we deal with; account, contract and billing records Company records
Our director and shareholder Full name; identity number; contact details; address; tax number; shareholding and appointment records Company records; CIPC; SARS; our bank
People who make PAIA or POPIA requests Name; proof of identity; contact details; the request; our correspondence Company records

9.3 The recipients or categories of recipients to whom the personal information may be supplied

Category of personal information Recipients or categories of recipients
Shared test data Supabase, which hosts our sync service. The other testers sharing it, who see its label, display names, values and status.
Information a tester sends from our app to the phone's built-in services, or to another app they open from ours Those services (Google's, on Android) and that app, which handle it under their own terms and privacy policies. It doesn't come to us.
Anything a tester chooses to share from our app Whoever the tester picks in the phone's share sheet or messaging app
Enquiries and emails Cloudflare (website hosting and email routing); Google (our mailbox, and the second mailbox described in 9.2); Web3Forms (delivers website form messages), and the services it uses (see 9.4); WhatsApp (carries WhatsApp messages); Resend (sends our replies from that second mailbox); Anthropic, through Claude, which can at times see a message when it helps us with our mailbox or accounts (see 9.4)
Website visits Cloudflare
Company, director, tax and finance records CIPC; SARS; our bank; professional advisers we appoint, such as an accountant or a lawyer; Google (to verify the company as a Google Play developer); Dun & Bradstreet, through TransUnion (for the company's D-U-N-S number); Anthropic, through Claude, the AI assistant we use to build our software and run the company (see 9.4); RevenueCat (the account for our app's subscriptions, still in our director's name)
Information from users of our app, once it launches (planned) Amazon Web Services, for an optional AI assistant in the app, only with the user's consent; Supabase, for the anonymous sign-in the assistant uses; Google, for an app check; RevenueCat and Google Play, for subscriptions (see 9.4)
Any of the above, when the law requires it Courts, law enforcement, the Regulator and other authorities acting under a law

9.4 Planned transborder flows of personal information

Where it goes What goes there Why, and on what basis
Supabase (Supabase Pte. Ltd., Singapore), on AWS eu-west-1 in Ireland (European Union) Shared test data, the anonymous identifier and IP address To show shared test data live on the phones of the testers sharing it. Only with the tester's consent (POPIA section 72(1)(b)). The app asks separately for consent to share and for "Processing outside South Africa". Switching either off removes the test data the tester shared, their entry in test data others shared, and their anonymous cloud account from the server, and signs the phone out. Supabase's data processing terms apply to the service; our director accepted its terms in his own name when he set it up, before the company existed, and we are moving the account to the company.
Cloudflare, a United States company with a worldwide network Website visits; emails sent to hello@krazybuilds.com, and to the support mailbox of a second product we are building To host our website and to route our email to our mailboxes, under Cloudflare's terms and data processing terms, which bind it to protect the information (POPIA section 72(1)(a)). Its data processing terms apply to all the Cloudflare services we use, including Email Routing; we saved a dated copy of them on 18 November 2026. The account is still in our director's name; we are moving it to the company. Once email reaches our mailbox, see the next row.
Google (our mailbox, a consumer Gmail account; and a second consumer Gmail account of our director's, which receives the support mailbox of a second product we are building), which processes data in the United States and other countries Emails and contact-form messages To read and answer messages that people choose to send us. For contact-form messages, the sender agrees, by ticking a box on the form, that the message goes outside South Africa (POPIA section 72(1)(b)). For emails, our mailbox isn't under business data processing terms, so we can't yet point to a section 72(1) ground for this transfer. If you'd rather your message didn't leave South Africa, send it to us by post or by hand instead (see 3.1).
Web3Forms (Web3Creative, India), a form service that uses Amazon Web Services, Cloudflare and Hetzner (Germany and Finland), with spam checks by CleanTalk and Akismet (United States). Its full list of sub-processors is in its data processing addendum, https://web3forms.com/dpa. Contact-form messages, with the sender's name, email address and IP address, which the spam checks also see. Web3Forms keeps its own copy of each message for 7 days (our setting; see 7.2). To deliver website messages to our mailbox, with the sender's consent, which they give by ticking a box on the form (POPIA section 72(1)(b)). Anyone who doesn't want to give it can write to us by post or by hand instead. We haven't yet put data processing terms in place with Web3Forms in the company's name. The form's account is still under our director's own login; we are moving it to the company.
WhatsApp (Meta), outside South Africa WhatsApp messages people send us, and their phone numbers To read and answer them. WhatsApp's own terms apply; they aren't data processing terms in our name, so we can't yet point to a section 72(1) ground for this transfer.
Resend, United States (sends our replies from the support mailbox of a second product we are building) The replies we send, and the recipients' email addresses To answer people who write to that mailbox. We can't yet point to a section 72(1) ground for this transfer. We have still to save a dated copy of Resend's terms.
GitHub, United States Source code and project documents. We don't keep testers' personal information there. To store and manage our code.
Anthropic, United States (Claude, the AI assistant we use to build our software and run the company) Company records, including our director's own details, and at times the details of people we correspond with, when it helps with our accounts. We keep our app's testers' and users' personal information away from it. For our director's own details, his consent (POPIA section 72(1)(b)); for a contact-form message, the sender's consent on the form (section 72(1)(b)); for anyone else's details, we can't yet point to a section 72(1) ground. The Claude accounts our director uses are in his own name, shared with his other work, and under Anthropic's consumer terms, which aren't data processing terms in our name, so we keep other people's personal information away from it as far as we can, and we are checking that each account is set not to let Anthropic use our chats to train its models.
Google, which processes data in the United States and other countries (Google Play developer verification) Our director's identity documents and contact details, and the company's details To verify the company as a Google Play developer. With our director's consent (POPIA section 72(1)(b)).
Amazon Web Services: a gateway in Cape Town (South Africa), with an AI model on Amazon Bedrock in AWS's European Union Regions (planned, not yet active) Text that a user of our app chooses to send to an optional AI assistant in the app, after the phone removes the identifying details it recognises. It can include health information. With it, the app uses an anonymous sign-in held by Supabase (above) and an app check from Google. The AWS accounts, which we opened in November 2026, hold our director's own sign-in and payment details. To answer the user. Only with the user's separate consent (POPIA section 72(1)(b)), and under AWS's data processing terms (section 72(1)(a)). It won't start before the Information Regulator's prior-authorisation process for it has ended. For our director's own details, his consent (section 72(1)(b)).
RevenueCat, United States (planned, once our app's subscriptions start) An anonymous app-user identifier, and Google Play purchase and subscription records. The account there, still in our director's name (we are moving it to the company), holds his own sign-in details. To manage subscriptions bought in our app (POPIA section 72(1)(c)). For our director's own details, his consent (section 72(1)(b)).

These are the transfers we make now, and the ones we plan for our app. Before a product we are building goes live, or any other new transfer starts, we'll update this manual (and, for our app, its privacy policy) to name each provider, and to say what it receives, why, and on what basis.

9.5 General description of information security measures to be implemented by the responsible party to ensure the confidentiality, integrity and availability of the information

No system is perfectly secure. That's why we keep what we collect to a minimum on purpose.

9.6 Your rights to your own personal information

10. Availability of the manual

10.1 A copy of this manual is available (section 51(3) of PAIA):

10.2 A printed copy costs R2.00 per A4 page, the photocopy rate in Annexure B to the PAIA Regulations, plus the actual cost of postage if we post it.

11. Updating of the manual

The head of KrazyBuilds will update this manual regularly, as section 51(2) of PAIA requires. We review it at least once a year, and whenever our contact details, records, service providers or processing change, or the law changes. The "Last updated" date at the top shows the current version.


Issued by

Keagan Christians Sole Director and Information Officer KrazyBuilds (Pty) Ltd

Date: 18 November 2026