Privacy policy
Effective and last updated: 18 October 2026
CentraPoint is a trading name of Global Software Services (Pty) Ltd, registration number 2021/476309/07.
1. Who we are
CentraPoint is a payments and billing platform of Global Software Services (Pty) Ltd, registration number 2021/476309/07 ("GSS", "we", "us"). This policy explains how we process personal information under the Protection of Personal Information Act 4 of 2013 ("POPIA") on this website, in the CentraPoint app and API, and on the payment pages and customer portal we host for merchants.
- Responsible party: Global Software Services (Pty) Ltd, 7 Kromiet Avenue, Waldrift, Vereeniging, 1939, Gauteng, South Africa.
- Information Officer: Nathan Avis (Director), at the same address.
- Email for privacy and PAIA requests: . Phone: .
2. Our two roles
Responsible party. We decide how and why we process the personal information of visitors to this website, people who send us enquiries, and the businesses that use CentraPoint ("merchants") and their users. This covers sign-up, business verification, support, security and the billing of our plans.
Operator. Merchants use CentraPoint to bill and collect from their own customers ("payers"). For payers' information, the merchant is the responsible party and we are its operator: we process the information only on the merchant's instructions, under our data processing terms. If you are a payer, the merchant's privacy policy applies to you, and you should contact the merchant first. We will help the merchant answer your request, and you can also write to us.
3. Personal information we collect
3.1 Website visitors and enquiries
- Contact form: your name, email address, company and phone number (both optional), topic and message, and your consent to be contacted. With them we receive the page address, the referring page, form timing (to stop spam) and a Google reCAPTCHA score when reCAPTCHA is on.
- WhatsApp: if you click the chat button, you talk to us on WhatsApp. Your WhatsApp number and messages reach us there.
- This website uses no analytics or advertising cookies (see our cookie notice).
3.2 Merchants and their users
- Sign-up and profile: company name, your name, work email address, password (stored only as a one-way bcrypt hash), and your phone number and job title if you add them. If you turn on two-factor authentication, we also store its secret (encrypted) and backup codes (hashed).
- Your users: name, email, role and sign-in history.
- Company settings: company name, email, phone, address and VAT number, as shown on your documents.
- Connections: gateway credentials, accounting system tokens and your own mail server password. All are stored encrypted.
3.3 Business verification
Before live payments are switched on, we collect your registered and trading names, CIPC registration number, VAT and tax numbers, phone number and physical address. We also collect the name, role and South African ID or passport number of your representative, and the documents the app asks for. These can include an ID document, proof of address, a bank confirmation letter, a CIPC certificate, a trust deed and letters of authority, a partnership agreement, a VAT certificate and a tax clearance certificate. We store the documents and the representative's ID number encrypted. You sign a declaration with your typed name.
3.4 Paying for your CentraPoint plan
- Netcash processes plan payments. We receive the payment reference, amount and status. For automatic renewals we may also receive Netcash's card token with the card type, last four digits, expiry date and cardholder name. We never receive the full card number.
- If you pay by EFT, we keep the proof of payment you upload.
- Receipts, your referral link, and the referrals and credits you earn.
3.5 Information collected automatically
- API request logs: time, method, path, response status, IP address and browser or client name. We do not log request or response bodies.
- Audit log: the actions users take in CentraPoint, with IP address and browser name.
- Email log: the emails CentraPoint sends (recipient, subject, content and status). The content of emails with sign-in links or codes is not stored.
- Error reports from the app: what went wrong, on which page, and in which browser.
- Gateway notifications (webhooks) as the gateway sent them, with any card fields removed, and the sender's IP address.
- The cookies listed in our cookie notice.
3.6 Payers' information (we act as operator)
We receive this from the merchant, from payers on our payment pages and customer portal, and from gateways:
- Names, email and billing email addresses, phone numbers, company names, addresses and VAT numbers, and any notes or custom fields the merchant adds.
- Invoices, quotes, credit notes, statements, subscriptions and the emails sent about them.
- Payment records: payer name and email, amount, reference, status and gateway.
- Saved cards: the gateway's token (encrypted), card type, masked number with the last four digits, expiry date and cardholder name. Card numbers are entered on the gateway's page and never stored by us.
- Debit order mandates: account holder, bank, branch code, account type, account number (stored encrypted), South African ID or passport number where given, and the amounts and dates of the debits. If the payer signs a mandate online, we also keep the signer's name, email, drawn signature, IP address and signing time.
- Payouts: the beneficiary's name and email, and bank details (stored encrypted).
- Customer portal: one-time sign-in codes, sent by email, and the IP address used.
4. Why we use it, and our lawful basis
- To open and run your account, provide the service, support your users and bill your plan. This is necessary to perform our agreement with you (POPIA section 11(1)(b)).
- To verify your business before live payments, prevent fraud and meet the requirements of the gateways, Netcash and banks. This protects legitimate interests of ours, yours and your payers (section 11(1)(f)), and it also follows the declaration you give.
- To keep CentraPoint secure, investigate errors and abuse, and keep audit trails. This protects our legitimate interests and yours (section 11(1)(f)).
- To answer enquiries, with your consent given on the form, or because you asked us to (sections 11(1)(a) and (b)).
- To keep financial records and to comply with tax law, court orders and other legal duties (section 11(1)(c)).
- To process payers' information as instructed by the merchant, who must have its own lawful basis.
We do not sell personal information, and we do not use it for advertising.
5. What you must give us
To open an account you must give your company name, your name, a work email address and a password. To take live payments you must complete business verification. On the contact form we need your name, email address and message. Phone number and company are optional. If you do not give us the required information, we cannot open your account, switch on live payments or answer you. On payment pages, the merchant decides what payers must give. Email and name are always needed, a phone number is needed for mobile money, and bank details are needed for a debit order.
6. Who we share it with
We share personal information only as far as each recipient needs it:
- Netcash: our payment provider for plan fees. For merchants who connect their own Netcash account, Netcash also provides Pay Now payments, debit orders, electronic mandates (Netcash emails or sends an SMS to the account holder), statements and payouts.
- Payment gateways the merchant connects, for payments made through them: PayFast, Ozow, Yoco, Peach Payments, PayGate, Paystack, Flutterwave, DPO Pay, Pesapal, M-Pesa (Safaricom) and MTN MoMo.
- Banks: through Netcash, for debit orders and payouts, and for EFT payments.
- Accounting systems the merchant connects: Xero, QuickBooks (Intuit), Zoho Books, Sage Business Cloud Accounting, Sage (South Africa) and Invoice Ninja, which can be hosted by Invoice Ninja or self-hosted by the merchant. We also record plan payments in our own Invoice Ninja accounting system. If you sign up for accounting software through a referral link in the app, the vendor's partner programme receives an anonymous reference so that the referral is credited to us.
- GSS Support, our help desk at support.globalsoftwareservices.co.za, which we operate ourselves. It receives contact form enquiries. It also receives each CentraPoint user's name, email and company, so that you can get support.
- Google (reCAPTCHA v3), on the contact page, to keep out spam. Google's privacy policy and terms apply to it.
- Meta (WhatsApp), if you choose to chat with us on WhatsApp.
- Email delivery: our outgoing email service sends CentraPoint's emails from [email protected]. If a merchant connects its own mail server, emails to its payers go through that server instead.
- Hosting: CentraPoint runs on servers we administer, with a Microsoft SQL Server database. Uploaded files are stored in the database.
- Others, where required: our professional advisers and auditors, authorities and courts when the law requires it, and a buyer of our business, who would be bound by this policy.
7. Information sent outside South Africa
Some of the services above process information outside South Africa. Paystack and Flutterwave operate from Nigeria and other countries. Pesapal and M-Pesa operate from Kenya. DPO Pay and MTN MoMo operate in the African country where the merchant's account is held. Xero, QuickBooks, Sage Business Cloud Accounting and hosted Invoice Ninja run on international servers. Zoho Books hosts South African organisations in its United States data centre. Google and Meta process information internationally, including in the United States. We send information to the payment and accounting services only when you or the merchant use them, because the transfer is needed to perform the agreement or the payment that the data subject asked for (POPIA section 72(1)(c) and (d)). Google processes reCAPTCHA data, and Meta processes WhatsApp chats, under their own privacy policies and data protection commitments. WhatsApp is used only if you choose it.
8. How long we keep it
- API request logs: 90 days, then deleted automatically.
- Error reports from the app: 180 days after the problem was last seen, then deleted automatically.
- Customer portal sign-in codes and sessions, rate-limit counters and API idempotency keys: deleted daily once they expire.
- Accounts, users, customers, payments, invoices, mandates, payouts, receipts, audit logs, email logs and gateway notification logs: kept while the account exists. When an account is closed it is deactivated, not erased, and it can be restored. We keep financial records for as long as tax and financial laws require (generally 5 years). We do not yet delete closed accounts automatically. Ask us and we will delete or de-identify the information once no law or legal claim requires us to keep it.
- Business verification documents: until you ask us to delete them and we no longer need them to show that we verified you, or for a legal claim.
- Contact enquiries: until we no longer need them to deal with your enquiry and any follow-up.
9. Security
We protect personal information with reasonable technical and organisational measures (POPIA section 19). These include:
- HTTPS on every site.
- Passwords stored as bcrypt hashes, with optional two-factor authentication using an authenticator app.
- AES-256-GCM encryption of gateway credentials, card tokens, bank account numbers, business verification documents, representatives' ID numbers, two-factor secrets, accounting tokens and mail server passwords.
- Signed (HMAC) payment links and verified gateway notifications.
- Rate limits on sign-in and the API.
- Role-based access, and an audit log of user actions.
See our security page for more.
If we have reasonable grounds to believe that someone has accessed or acquired personal information without authority, we notify the Information Regulator and the people affected as soon as reasonably possible (POPIA section 22). Where the information belongs to a merchant's payers, we notify the merchant without undue delay, so that it can notify them.
10. Cookies
We use only the cookies and browser storage needed to sign you in, keep you secure and remember simple settings. We use no analytics or advertising cookies. Our cookie notice lists every one.
11. Direct marketing
We do not send marketing emails or SMSes today. The emails we send are service messages, such as sign-up, receipts, security and billing notices. If we start direct marketing, we will contact people who are not our customers only with their prior consent, and our customers only about similar services. Every message will include a free way to opt out, as POPIA section 69 requires. Merchants are responsible for their own marketing to their payers.
12. Automated decisions
We do not make decisions about you based solely on automated profiling (POPIA section 71). Business verification is reviewed by a person. Some steps follow fixed rules in our terms: a plan payment that is 3 days late limits an account to billing, and a debit order mandate pauses after 3 unpaid debits in a row. You can ask us to review any of these.
13. Children
CentraPoint is for businesses, and users must be at least 18. We do not knowingly collect children's personal information for our own purposes. A merchant whose payers include children, or who processes a child's information (for example for school fees), must have the consent of a competent person or another lawful basis under POPIA section 35.
14. Special personal information
We do not ask for special personal information, such as health, religious beliefs, biometric information or criminal behaviour. Please do not put it into notes or custom fields unless the law allows it.
15. Your rights
Under POPIA you may:
- ask whether we hold personal information about you and request a copy (section 23);
- ask us to correct, update or delete it (section 24);
- object to processing based on legitimate interests, or to direct marketing (section 11(3)), and withdraw consent at any time;
- ask for a review of a decision made by automated means (section 71); and
- complain to the Information Regulator.
Email us with "Privacy request" in the subject at . We will verify your identity and reply within 30 days. For a formal request for access to records, see the PAIA manual of Global Software Services (Pty) Ltd at globalsoftwareservices.co.za/paia-manual. Payers should first contact the merchant, who is the responsible party for their information.
16. The Information Regulator
You can complain to the Information Regulator (South Africa) at inforegulator.org.za, through its eServices portal at eservices.inforegulator.org.za, or by email to [email protected] (POPIA complaints), [email protected] (PAIA complaints) or [email protected] (general enquiries). Its address is Woodmead North Office Park, 54 Maxwell Drive, Woodmead, Johannesburg, 2191.
17. Changes to this policy
We will update this policy when our processing changes. The date at the top shows the current version. We will tell merchants about material changes by email or in the app.