How Axiom Logic handles your personal information
This notice explains what personal information we process, why we process it, who receives it, and what you can do about it. It is given under section 18 of the Protection of Personal Information Act 4 of 2013 (POPIA).
1. Who we are
Responsible party: Cynvest Investments (Pty) Ltd, registration number 2019/505152/07, trading as Axiom Logic.
Address: 67 Constantia Main Road, Plumstead, Cape Town, Western Cape, 7800, South Africa.
Information Officer: Ashley Verhulp, info@axiomlogic.ai, +27 83 375 1245.
Website: https://axiomlogic.ai
2. What we collect, and why
We collect personal information from you directly, automatically when you use the website, or from a member of your workspace who invites you. We do not buy it from anyone.
| When | What we collect | Why | Our lawful basis (POPIA s11) |
|---|---|---|---|
| You visit our website | Technical data our hosting provider records to deliver and protect the site: your connection (IP) address, browser type, pages requested, date and time. Two cookies are set to deliver and protect the site; see our cookies and storage notice. | To run the site and keep it secure | Our legitimate interest in a working, secure site (s11(1)(f)) |
| You visit our website | Visitor statistics our hosting provider compiles: pages viewed, referring site, device type and country. We see them only as totals. | To understand how the site is used | Our legitimate interest (s11(1)(f)) |
| You answer our questionnaire on the website | Your answers and when you gave them. To limit misuse, we keep a scrambled (hashed) form of your connection address for up to 2 days; we cannot turn it back into the address. | To learn what problems people have at their sites, including problems outside our current services | Your consent, given when you start (s11(1)(a)). Your consent for storage outside South Africa (s72(1)(b)), given by a tick box before you start. |
| You ask us to reply about your problem (at the end of the questionnaire) | Your name, company (optional) and e-mail or telephone | To reply once, about the problem you described | Your consent (s11(1)(a)). It is used only for that reply unless you agree to more. |
| You send us a message through the contact form | Your name, e-mail, company and message. The same scrambled connection address, for up to 2 days. | To reply, and to keep a record of the correspondence | Our legitimate interest, or steps you ask us to take before a contract (s11(1)(b), (f)) |
| You use the sign-in page, ask for a password reset, send the contact form or answer the questionnaire | A check that a person, not a program, is using the form (Cloudflare Turnstile). Cloudflare's script runs in your browser on those pages only. It reads technical signals from your browser and device, and your connection address, and tells us only whether the check passed. We do not receive the signals. Where a form is refused because the check did not pass, we keep the time, the form, the reason and a shortened form of your connection address for 90 days. | To keep automated abuse off sign-in and our public forms | Our legitimate interest in keeping the service secure (s11(1)(f)) |
| You rate the site | Your rating, the reasons you tick, anything you type, the page you were on and the time. The same scrambled connection address, for up to 2 days. | To find what is unclear or broken on the site | Our legitimate interest in improving the site (s11(1)(f)) |
| You close the cookies notice or answer the questionnaire invitation | That the notice or invitation was shown and what was pressed, the page and the time. Nothing that identifies you. | To keep a record of the notice, and to see whether the invitation is useful | Our legitimate interest (s11(1)(f)) |
| You are invited to an account, or you sign in | Your e-mail address, your name and role, and when you signed in. Your password is kept only as a scrambled (hashed) value we cannot read. A record of what your account does in the portal. A record of each sign-in attempt: the account, the time, the method, whether it succeeded, and a shortened form of your connection address (for example 196.21.x.x) with a scrambled value we cannot turn back into the address, for 90 days. After a wrong password or a wrong sign-in code, a scrambled form of the account and connection address, for up to 2 days. If you use two-step sign-in: a fingerprint of each recovery code, never the code itself. If you choose "Trust this browser for 30 days", which is offered to our staff and to members of a workspace alike: a cookie in that browser, of which we keep only a fingerprint, with a description of the browser and when it was made, last used and expires. Our sign-in provider keeps a record of each session you have open: your full connection address, a description of your browser, when the session started and when it was last active. Your account's Trusted devices page shows your trusted devices and your open sessions and lets you end them; each ending is added to the record of what your account does. | To give you access, to keep accounts secure, and to show who did what | Performing the contract, or steps before it (s11(1)(b)); our legitimate interest in security (s11(1)(f)) |
| You were invited to an account and choose "Sign in with Apple" | From Apple: an identifier Apple gives our app for your Apple Account, the e-mail address Apple shares (your own, or a private relay address Apple creates if you choose "Hide My Email"), and, the first time only, the name you allow Apple to share. Apple does not give us your Apple password. If the e-mail Apple shares does not match an open invitation, sign-in is refused and no account is made; the refused attempt is recorded. | To let an invited person sign in without a separate password | Performing the contract, or steps before it (s11(1)(b)); our legitimate interest in security (s11(1)(f)) |
| You fill in your profile in the portal | Your first and last name, job title, company and time zone. If you add them: your mobile number and a photo. The photo is reduced to a small picture in your browser before it is sent; the original never reaches us. Members of a workspace you belong to can see your name and photo. The owners and administrators of that workspace can also see your e-mail address and when you last signed in. Only you can see your mobile number. | To show the members of your workspace who did what, and to reach you about your account | Performing the contract (s11(1)(b)). For the mobile number and the photo, your consent (s11(1)(a)), which you withdraw by removing them. |
| You switch on WhatsApp alerts for your own number in the portal, for example by accepting the invitation the portal shows you | Your mobile number (the portal fills in the number saved on your profile, which you may change), kept sealed (encrypted) with a fingerprint used only to recognise it; the workspace; your account; the revision of this notice you were shown; and the time you accepted. Ticking the box that says what you agree to and tapping Accept, after you have signed in, is your consent; Accept cannot be tapped until the box is ticked. We then send one WhatsApp message to that number saying that alerts are on and that whoever has the number can reply STOP if it was not them, and one e-mail to the address of your account recording what you agreed to; we keep when each was sent and its outcome. When the invitation was shown to you, dismissed or accepted, so that it is shown again only 30 days after you dismiss it, and never after you reply STOP. Each alert sent to you: the rule, the time, and the delivery reports (sent, delivered, read, failed). Your replies to our WhatsApp number. Your number stays visible only to you; members of your workspace see only that WhatsApp alerts are on or off. If you send yourself a test message, we keep its time, its result and a reference, not your number. | To tell you about an alarm or a notification your workspace has set up, and nothing else. You receive no marketing | Your consent (s11(1)(a)), and for the transfer through WasenderAPI your consent (s72(1)(b)), given by ticking the box and tapping Accept; you may withdraw both at any time by replying STOP or by switching alerts off |
| You follow a walkthrough of the portal | The walkthrough, the chapters you have completed and the one you are on, and, for the walkthrough of a measured series, the series you chose. Each step you record is also written to the record of what your account did. Nobody else in the workspace sees your progress. | So that you can pick up where you left off | Performing the contract (s11(1)(b)) |
| An owner or administrator of a workspace adds you to its WhatsApp contact list | Your name and WhatsApp number, the sites or equipment you are to receive alerts for, who added you and when. Your number is kept sealed (encrypted), with a fingerprint used only to recognise it. Members of the workspace see your name, the last 3 digits of your number, whether you are waiting to join, invited, joined or have replied STOP, and your sites or equipment; nobody in the workspace sees the full number. Being added sends you nothing. If the owner or administrator also confirms that you agreed to hear from us, we may send you an invitation. It names the workspace, says that after you accept we will send you a welcome message so that you can choose which alarm groups you receive, and asks you to reply ACCEPT to receive messages or STOP to decline (an invitation sent before revision 29 of this notice asks you to reply YES); we keep who confirmed your agreement and when, and how many invitations were sent. Each invitation carries a link of its own: if it is opened in a web browser, we record when it was first and last opened and how many times, and nothing about the device or where it was opened from. Members of the workspace see when it was first opened and how many times; that shows only that the link was opened, not that you read the invitation or agreed. An invitation stays open 7 days. At most one is sent to you in a day, and none after three have gone unanswered. Your replies and the delivery reports of each alert. | To send you the alerts that workspace has chosen to send you, once you agree | Your consent (s11(1)(a)), given by replying ACCEPT or YES or by writing JOIN with the workspace's code; replying STOP withdraws it. Before you agree, we hold what the workspace entered only so that you can join, and invite you only on the workspace's confirmation that you agreed to hear from us, and record when an invitation's link is opened so that the workspace can see whether its invitation reached you (s11(1)(f)) |
| You write JOIN with a workspace's code to our WhatsApp number | Your number, kept as above, the time, the word you wrote, and that you joined that workspace's list. You can join only a list an owner or administrator of that workspace has added you to; the chance to join lasts 7 days and they can renew it. We send you one confirmation in that chat, naming the workspace and saying how to stop alerts, and then the welcome message described below, so that you can choose your alarm groups; alerts start only after you confirm them by replying COMPLETE. | To start the alerts you asked for, and to be able to show that you asked | Your consent (s11(1)(a)), and for storage outside South Africa your consent (s72(1)(b)); replying STOP withdraws both |
| You reply ACCEPT to an invitation, choose your alarm groups and reply COMPLETE | The time, the word you sent and a fingerprint of your number, kept as your consent. We then send you one welcome message with a link of its own. The page it opens shows the alarm groups the workspace linked to you, which you may tick or untick; we keep the groups offered, the groups you choose, each version you save and when, and when you confirmed by replying COMPLETE from the same number. Saving on the page does not start alerts: you receive alerts only for the groups you confirmed by COMPLETE, and none if you confirm no group. The link works for 7 days. Within that time you can change your choices from it and confirm them again; after it, replying ACCEPT again sends you a new welcome message and link, counted under the same limits. Only you see the page; members of the workspace see the groups linked to you. | To send you alerts only for the alarm groups you chose | Your consent (s11(1)(a)), and for the transfer through WasenderAPI your consent (s72(1)(b)), given by replying ACCEPT (or, if you joined earlier, by YES or JOIN) and confirmed for each choice by replying COMPLETE; replying STOP withdraws both |
| An alarm is raised in a workspace that sends WhatsApp alerts | Alerts are sent only for alarms of critical or high priority, to members who have switched alerts on and to contacts whose confirmed alarm groups include the alarm. An alert names Axiom Logic and the workspace, and gives the alarm's reference, the measurement, its value and unit, the limit and the condition that raised it, and the time; it may also say that the alarm has cleared or is still raised. The number of alerts to one number is limited per alarm and over time; alerts held back by a limit are replaced by one grouped message giving how many were held back and a reference, which does not say whether those alarms are still raised. For each alert we keep the alarm, the recipient, a fingerprint of the number, the kind of alert, the time, the outcome, the reference WasenderAPI gives it, and its delivery reports (sent, delivered, read, failed). An alert waiting to be sent is cancelled when you reply STOP. Alarms are acknowledged in the portal, never by replying. | To tell you about an alarm you asked to hear about | The consent you gave to receive alerts, as above |
| An owner or administrator of a workspace puts you on its "When WhatsApp is down" list | Only members of the workspace can be on the list. We keep who is on it, who added and removed them, and when. If the shared WhatsApp number is disconnected, or the delivery of an alert is not confirmed within the period the platform checks, we send you an e-mail at the address of your account and show you a notice in the portal; the e-mail names the workspace and, for an unconfirmed alert, the alarm's reference, not the person it was sent to. We keep each notice, each e-mail sent and its outcome. Members of the workspace see who is on the list; each person on it sees their own notices. | So that someone in the workspace knows when WhatsApp alerts may not have reached the people they were meant for | Performing the contract (s11(1)(b)); our legitimate interest in alarms not going unnoticed (s11(1)(f)) |
| You reply to our WhatsApp number | The text of your reply, the time, and which contact or member it came from. Owners and administrators of the workspace whose list you are on can read your replies in your message history; a reply is never treated as acknowledging an alarm. | To act on STOP, ACCEPT, YES, JOIN and COMPLETE, and to let the workspace see what you wrote to it | Your consent, as above; for STOP, our legal obligation to honour your objection (s11(1)(c)) |
| You reply STOP (or UNSUBSCRIBE, OPT OUT, CANCEL, END or QUIT) to one of our WhatsApp messages | The time, the word you sent, a fingerprint of your number (not the number), each workspace and list you were removed from, and our confirmation. We remove your number from every list at once, in every workspace, and send you one reply in that chat saying that no more alerts will come and how to join again. After that nothing more is sent. | To stop every alert to you, and to be able to show that we did | Our legal obligation to honour your objection (s11(1)(c), s11(3)), and our legitimate interest in proving it (s11(1)(f)) |
| You open or answer a support ticket in the portal | The subject, what you write, any file you attach with its fingerprint, and who wrote each message and when. Members of your workspace and our support staff can read a ticket. | To help you, and to keep a record of what was asked and answered | Performing the contract (s11(1)(b)) |
| You answer the feedback prompt in the portal | Your rating, the reasons you tick, anything you type, the page and release you were on, the time, and whether we may contact you about it. It is linked to your account. Only Axiom Logic sees it; the administrators of your workspace do not. | To find what is unclear or broken in the portal | Our legitimate interest in improving the service (s11(1)(f)). You can delete any answer from your account, and we honour an objection by deleting it. |
| Your workspace uploads a document | The file, its title, kind and fingerprint, and who uploaded it and when. A document may name people; your workspace decides what it uploads. An owner or administrator of the workspace can delete a document: the file, the text of its pages and its search index, its filing proposals and its link to any instrument's calibration record are then removed, and we keep who deleted it, when, its title, fingerprint and size, and the reason given. A document that a newer revision replaces, or that a declaration of a point of delivery rests on, cannot be deleted. When an engineer or viewer tries, the attempt is refused, and we keep the account, the time and the reason for 90 days. An owner, administrator or engineer can move a document to another folder. Each move, and each time a document is read with AI, is added to the record of what that account does, with the time; any member of the workspace can see a document's history of moves and readings. | To keep the records your workspace's figures rest on | Performing the contract (s11(1)(b)). The customer agreement governs what a workspace gives us to process on its behalf. |
| Your workspace switches on AI reading, and a member uploads a document to it or presses "Read with AI" on a document already held | The document's pages are sent to an AI model, which returns the text of each page and proposes how the document is filed: its kind, title, document number, revision, date of issue, issuer, folder and tags, and whether it replaces a document already held, each with the words in the document the proposal rests on. Where the model cannot tell, the field is left empty. We keep the text of each page, a search index made from it, and each proposal with who confirmed, changed or rejected it and when. A page the model could not read is marked "Not read". Only owners and administrators switch AI reading on or off. While it is off, nothing is read. While it is on, each document is read once it has been stored, without a further press, and a document already held is read when a member presses the button. | To let members find and question their own documents | Performing the contract (s11(1)(b)). The customer agreement governs what a workspace gives us to process on its behalf. |
| You ask a question on the Ask page in the portal | Your question, your account, the workspace and the time. The passages from your workspace's documents that the search finds are sent with the question to an AI model. We keep the question, the answer, which documents and pages it cites, and which model answered. Only documents of the workspace you are in are searched or sent. | To answer questions from a workspace's own documents, with the pages that support the answer | Performing the contract (s11(1)(b)) |
| You ask the AI analyst a question in the portal, where your workspace holds the analyst module | Your question, your account, the workspace and the time. To answer it, our server gathers evidence from your workspace only: its declared assets and their roles; measured readings and their summaries, each with its time, unit and coverage grade; alarm records with their times and states (an alarm record can name the member who acknowledged or closed it); and passages of documents already read with AI, with the document's revision and page. Where the workspace has declared a point of delivery and the tariff it is billed on, the published rates of that tariff are added, each with the document and page it is printed on (Eskom's tariff booklet or the municipality's tariff schedule); published rates are not personal information. The question and that evidence are sent to an AI model. We keep the question, the answer or the refusal, the exact list of evidence sent, which model answered, the size of the request and the answer, when it started and finished, and whether a member has reviewed the answer. Only data of the workspace you are in is read or sent. A question that the evidence cannot support is refused before anything is sent. Our staff cannot ask questions in a workspace unless they are also an owner or administrator of that workspace, and then they ask as that member. | To answer questions about a workspace's own plant from its own records, with the evidence each answer rests on | Performing the contract (s11(1)(b)). The customer agreement governs what a workspace gives us to process on its behalf. |
| You press "Explain this result" in the portal | The envelope you ask about and the reasons it was refused are sent to an AI model, which words an explanation. We keep a record of the request: your account, the workspace, the time, which reasons were sent, which model answered and the size of the answer. We do not keep the envelope in that record, and we do not keep the explanation. | To help the person setting up a sender correct it | Performing the contract (s11(1)(b)); our legitimate interest in a service people can set up without help (s11(1)(f)) |
| You enter a site's address in the portal | What you type in the address box is sent by our server to Mapbox, which returns up to five matching addresses with their coordinates; we keep the address and coordinates you choose for the site, not your searches. When you open the site map, and on the Overview page, your browser loads the map directly from Mapbox, so Mapbox receives your connection address and a description of your browser and device. Mapbox says it keeps the connection address in its logs for 30 days. | To place a site accurately and show where it is | Performing the contract (s11(1)(b)) |
| Your workspace sets up a weather job for one of its declared sites | The site's coordinates are sent to Open-Meteo, which returns weather readings for that place. Nothing about any person is sent: no name, e-mail, account or connection address of a member. We keep the job, who set it up and when, each run (time, result, how many readings), and the weather readings. Weather readings are labelled as coming from an outside source and are never used as a site's measured readings, bills, statements or alarms. A workspace has one weather connection. It checks every hour, or less often if a member chooses, and never more often; each check also stores the forecast for the coming hours and days, labelled as modelled, which the Overview page shows. | To show the weather at a site beside its own readings | Performing the contract (s11(1)(b)). A site's coordinates identify the company that owns it, which POPIA treats as that company's personal information. |
| You contact us by e-mail or telephone, or we meet you in business | Your name, contact details, organisation, role and what you tell us | To reply, and to keep a record of the correspondence and of your consent choices | Our legitimate interest, or steps you ask us to take before a contract (s11(1)(b), (f)) |
| You are a customer, or your site takes part in our testing | Account holders' names, work e-mail addresses, roles and sign-in records; the site, meter and device readings you connect. Readings name no person, but they identify the company that owns the site, and POPIA treats that as the company's personal information. | To provide the service you contract for, or to test the platform with your site's readings | Performing the contract (s11(1)(b)). For testing before a contract, the site owner's written consent (s11(1)(a)), which also covers storage outside South Africa (s72(1)(b)). A separate customer agreement governs data you give us to process on your behalf. |
- When
- You visit our website
- What we collect
- Technical data our hosting provider records to deliver and protect the site: your connection (IP) address, browser type, pages requested, date and time. Two cookies are set to deliver and protect the site; see our cookies and storage notice.
- Why
- To run the site and keep it secure
- Our lawful basis (POPIA s11)
- Our legitimate interest in a working, secure site (s11(1)(f))
- When
- You visit our website
- What we collect
- Visitor statistics our hosting provider compiles: pages viewed, referring site, device type and country. We see them only as totals.
- Why
- To understand how the site is used
- Our lawful basis (POPIA s11)
- Our legitimate interest (s11(1)(f))
- When
- You answer our questionnaire on the website
- What we collect
- Your answers and when you gave them. To limit misuse, we keep a scrambled (hashed) form of your connection address for up to 2 days; we cannot turn it back into the address.
- Why
- To learn what problems people have at their sites, including problems outside our current services
- Our lawful basis (POPIA s11)
- Your consent, given when you start (s11(1)(a)). Your consent for storage outside South Africa (s72(1)(b)), given by a tick box before you start.
- When
- You ask us to reply about your problem (at the end of the questionnaire)
- What we collect
- Your name, company (optional) and e-mail or telephone
- Why
- To reply once, about the problem you described
- Our lawful basis (POPIA s11)
- Your consent (s11(1)(a)). It is used only for that reply unless you agree to more.
- When
- You send us a message through the contact form
- What we collect
- Your name, e-mail, company and message. The same scrambled connection address, for up to 2 days.
- Why
- To reply, and to keep a record of the correspondence
- Our lawful basis (POPIA s11)
- Our legitimate interest, or steps you ask us to take before a contract (s11(1)(b), (f))
- When
- You use the sign-in page, ask for a password reset, send the contact form or answer the questionnaire
- What we collect
- A check that a person, not a program, is using the form (Cloudflare Turnstile). Cloudflare's script runs in your browser on those pages only. It reads technical signals from your browser and device, and your connection address, and tells us only whether the check passed. We do not receive the signals. Where a form is refused because the check did not pass, we keep the time, the form, the reason and a shortened form of your connection address for 90 days.
- Why
- To keep automated abuse off sign-in and our public forms
- Our lawful basis (POPIA s11)
- Our legitimate interest in keeping the service secure (s11(1)(f))
- When
- You rate the site
- What we collect
- Your rating, the reasons you tick, anything you type, the page you were on and the time. The same scrambled connection address, for up to 2 days.
- Why
- To find what is unclear or broken on the site
- Our lawful basis (POPIA s11)
- Our legitimate interest in improving the site (s11(1)(f))
- When
- You close the cookies notice or answer the questionnaire invitation
- What we collect
- That the notice or invitation was shown and what was pressed, the page and the time. Nothing that identifies you.
- Why
- To keep a record of the notice, and to see whether the invitation is useful
- Our lawful basis (POPIA s11)
- Our legitimate interest (s11(1)(f))
- When
- You are invited to an account, or you sign in
- What we collect
- Your e-mail address, your name and role, and when you signed in. Your password is kept only as a scrambled (hashed) value we cannot read. A record of what your account does in the portal. A record of each sign-in attempt: the account, the time, the method, whether it succeeded, and a shortened form of your connection address (for example 196.21.x.x) with a scrambled value we cannot turn back into the address, for 90 days. After a wrong password or a wrong sign-in code, a scrambled form of the account and connection address, for up to 2 days. If you use two-step sign-in: a fingerprint of each recovery code, never the code itself. If you choose "Trust this browser for 30 days", which is offered to our staff and to members of a workspace alike: a cookie in that browser, of which we keep only a fingerprint, with a description of the browser and when it was made, last used and expires. Our sign-in provider keeps a record of each session you have open: your full connection address, a description of your browser, when the session started and when it was last active. Your account's Trusted devices page shows your trusted devices and your open sessions and lets you end them; each ending is added to the record of what your account does.
- Why
- To give you access, to keep accounts secure, and to show who did what
- Our lawful basis (POPIA s11)
- Performing the contract, or steps before it (s11(1)(b)); our legitimate interest in security (s11(1)(f))
- When
- You were invited to an account and choose "Sign in with Apple"
- What we collect
- From Apple: an identifier Apple gives our app for your Apple Account, the e-mail address Apple shares (your own, or a private relay address Apple creates if you choose "Hide My Email"), and, the first time only, the name you allow Apple to share. Apple does not give us your Apple password. If the e-mail Apple shares does not match an open invitation, sign-in is refused and no account is made; the refused attempt is recorded.
- Why
- To let an invited person sign in without a separate password
- Our lawful basis (POPIA s11)
- Performing the contract, or steps before it (s11(1)(b)); our legitimate interest in security (s11(1)(f))
- When
- You fill in your profile in the portal
- What we collect
- Your first and last name, job title, company and time zone. If you add them: your mobile number and a photo. The photo is reduced to a small picture in your browser before it is sent; the original never reaches us. Members of a workspace you belong to can see your name and photo. The owners and administrators of that workspace can also see your e-mail address and when you last signed in. Only you can see your mobile number.
- Why
- To show the members of your workspace who did what, and to reach you about your account
- Our lawful basis (POPIA s11)
- Performing the contract (s11(1)(b)). For the mobile number and the photo, your consent (s11(1)(a)), which you withdraw by removing them.
- When
- You switch on WhatsApp alerts for your own number in the portal, for example by accepting the invitation the portal shows you
- What we collect
- Your mobile number (the portal fills in the number saved on your profile, which you may change), kept sealed (encrypted) with a fingerprint used only to recognise it; the workspace; your account; the revision of this notice you were shown; and the time you accepted. Ticking the box that says what you agree to and tapping Accept, after you have signed in, is your consent; Accept cannot be tapped until the box is ticked. We then send one WhatsApp message to that number saying that alerts are on and that whoever has the number can reply STOP if it was not them, and one e-mail to the address of your account recording what you agreed to; we keep when each was sent and its outcome. When the invitation was shown to you, dismissed or accepted, so that it is shown again only 30 days after you dismiss it, and never after you reply STOP. Each alert sent to you: the rule, the time, and the delivery reports (sent, delivered, read, failed). Your replies to our WhatsApp number. Your number stays visible only to you; members of your workspace see only that WhatsApp alerts are on or off. If you send yourself a test message, we keep its time, its result and a reference, not your number.
- Why
- To tell you about an alarm or a notification your workspace has set up, and nothing else. You receive no marketing
- Our lawful basis (POPIA s11)
- Your consent (s11(1)(a)), and for the transfer through WasenderAPI your consent (s72(1)(b)), given by ticking the box and tapping Accept; you may withdraw both at any time by replying STOP or by switching alerts off
- When
- You follow a walkthrough of the portal
- What we collect
- The walkthrough, the chapters you have completed and the one you are on, and, for the walkthrough of a measured series, the series you chose. Each step you record is also written to the record of what your account did. Nobody else in the workspace sees your progress.
- Why
- So that you can pick up where you left off
- Our lawful basis (POPIA s11)
- Performing the contract (s11(1)(b))
- When
- An owner or administrator of a workspace adds you to its WhatsApp contact list
- What we collect
- Your name and WhatsApp number, the sites or equipment you are to receive alerts for, who added you and when. Your number is kept sealed (encrypted), with a fingerprint used only to recognise it. Members of the workspace see your name, the last 3 digits of your number, whether you are waiting to join, invited, joined or have replied STOP, and your sites or equipment; nobody in the workspace sees the full number. Being added sends you nothing. If the owner or administrator also confirms that you agreed to hear from us, we may send you an invitation. It names the workspace, says that after you accept we will send you a welcome message so that you can choose which alarm groups you receive, and asks you to reply ACCEPT to receive messages or STOP to decline (an invitation sent before revision 29 of this notice asks you to reply YES); we keep who confirmed your agreement and when, and how many invitations were sent. Each invitation carries a link of its own: if it is opened in a web browser, we record when it was first and last opened and how many times, and nothing about the device or where it was opened from. Members of the workspace see when it was first opened and how many times; that shows only that the link was opened, not that you read the invitation or agreed. An invitation stays open 7 days. At most one is sent to you in a day, and none after three have gone unanswered. Your replies and the delivery reports of each alert.
- Why
- To send you the alerts that workspace has chosen to send you, once you agree
- Our lawful basis (POPIA s11)
- Your consent (s11(1)(a)), given by replying ACCEPT or YES or by writing JOIN with the workspace's code; replying STOP withdraws it. Before you agree, we hold what the workspace entered only so that you can join, and invite you only on the workspace's confirmation that you agreed to hear from us, and record when an invitation's link is opened so that the workspace can see whether its invitation reached you (s11(1)(f))
- When
- You write JOIN with a workspace's code to our WhatsApp number
- What we collect
- Your number, kept as above, the time, the word you wrote, and that you joined that workspace's list. You can join only a list an owner or administrator of that workspace has added you to; the chance to join lasts 7 days and they can renew it. We send you one confirmation in that chat, naming the workspace and saying how to stop alerts, and then the welcome message described below, so that you can choose your alarm groups; alerts start only after you confirm them by replying COMPLETE.
- Why
- To start the alerts you asked for, and to be able to show that you asked
- Our lawful basis (POPIA s11)
- Your consent (s11(1)(a)), and for storage outside South Africa your consent (s72(1)(b)); replying STOP withdraws both
- When
- You reply ACCEPT to an invitation, choose your alarm groups and reply COMPLETE
- What we collect
- The time, the word you sent and a fingerprint of your number, kept as your consent. We then send you one welcome message with a link of its own. The page it opens shows the alarm groups the workspace linked to you, which you may tick or untick; we keep the groups offered, the groups you choose, each version you save and when, and when you confirmed by replying COMPLETE from the same number. Saving on the page does not start alerts: you receive alerts only for the groups you confirmed by COMPLETE, and none if you confirm no group. The link works for 7 days. Within that time you can change your choices from it and confirm them again; after it, replying ACCEPT again sends you a new welcome message and link, counted under the same limits. Only you see the page; members of the workspace see the groups linked to you.
- Why
- To send you alerts only for the alarm groups you chose
- Our lawful basis (POPIA s11)
- Your consent (s11(1)(a)), and for the transfer through WasenderAPI your consent (s72(1)(b)), given by replying ACCEPT (or, if you joined earlier, by YES or JOIN) and confirmed for each choice by replying COMPLETE; replying STOP withdraws both
- When
- An alarm is raised in a workspace that sends WhatsApp alerts
- What we collect
- Alerts are sent only for alarms of critical or high priority, to members who have switched alerts on and to contacts whose confirmed alarm groups include the alarm. An alert names Axiom Logic and the workspace, and gives the alarm's reference, the measurement, its value and unit, the limit and the condition that raised it, and the time; it may also say that the alarm has cleared or is still raised. The number of alerts to one number is limited per alarm and over time; alerts held back by a limit are replaced by one grouped message giving how many were held back and a reference, which does not say whether those alarms are still raised. For each alert we keep the alarm, the recipient, a fingerprint of the number, the kind of alert, the time, the outcome, the reference WasenderAPI gives it, and its delivery reports (sent, delivered, read, failed). An alert waiting to be sent is cancelled when you reply STOP. Alarms are acknowledged in the portal, never by replying.
- Why
- To tell you about an alarm you asked to hear about
- Our lawful basis (POPIA s11)
- The consent you gave to receive alerts, as above
- When
- An owner or administrator of a workspace puts you on its "When WhatsApp is down" list
- What we collect
- Only members of the workspace can be on the list. We keep who is on it, who added and removed them, and when. If the shared WhatsApp number is disconnected, or the delivery of an alert is not confirmed within the period the platform checks, we send you an e-mail at the address of your account and show you a notice in the portal; the e-mail names the workspace and, for an unconfirmed alert, the alarm's reference, not the person it was sent to. We keep each notice, each e-mail sent and its outcome. Members of the workspace see who is on the list; each person on it sees their own notices.
- Why
- So that someone in the workspace knows when WhatsApp alerts may not have reached the people they were meant for
- Our lawful basis (POPIA s11)
- Performing the contract (s11(1)(b)); our legitimate interest in alarms not going unnoticed (s11(1)(f))
- When
- You reply to our WhatsApp number
- What we collect
- The text of your reply, the time, and which contact or member it came from. Owners and administrators of the workspace whose list you are on can read your replies in your message history; a reply is never treated as acknowledging an alarm.
- Why
- To act on STOP, ACCEPT, YES, JOIN and COMPLETE, and to let the workspace see what you wrote to it
- Our lawful basis (POPIA s11)
- Your consent, as above; for STOP, our legal obligation to honour your objection (s11(1)(c))
- When
- You reply STOP (or UNSUBSCRIBE, OPT OUT, CANCEL, END or QUIT) to one of our WhatsApp messages
- What we collect
- The time, the word you sent, a fingerprint of your number (not the number), each workspace and list you were removed from, and our confirmation. We remove your number from every list at once, in every workspace, and send you one reply in that chat saying that no more alerts will come and how to join again. After that nothing more is sent.
- Why
- To stop every alert to you, and to be able to show that we did
- Our lawful basis (POPIA s11)
- Our legal obligation to honour your objection (s11(1)(c), s11(3)), and our legitimate interest in proving it (s11(1)(f))
- When
- You open or answer a support ticket in the portal
- What we collect
- The subject, what you write, any file you attach with its fingerprint, and who wrote each message and when. Members of your workspace and our support staff can read a ticket.
- Why
- To help you, and to keep a record of what was asked and answered
- Our lawful basis (POPIA s11)
- Performing the contract (s11(1)(b))
- When
- You answer the feedback prompt in the portal
- What we collect
- Your rating, the reasons you tick, anything you type, the page and release you were on, the time, and whether we may contact you about it. It is linked to your account. Only Axiom Logic sees it; the administrators of your workspace do not.
- Why
- To find what is unclear or broken in the portal
- Our lawful basis (POPIA s11)
- Our legitimate interest in improving the service (s11(1)(f)). You can delete any answer from your account, and we honour an objection by deleting it.
- When
- Your workspace uploads a document
- What we collect
- The file, its title, kind and fingerprint, and who uploaded it and when. A document may name people; your workspace decides what it uploads. An owner or administrator of the workspace can delete a document: the file, the text of its pages and its search index, its filing proposals and its link to any instrument's calibration record are then removed, and we keep who deleted it, when, its title, fingerprint and size, and the reason given. A document that a newer revision replaces, or that a declaration of a point of delivery rests on, cannot be deleted. When an engineer or viewer tries, the attempt is refused, and we keep the account, the time and the reason for 90 days. An owner, administrator or engineer can move a document to another folder. Each move, and each time a document is read with AI, is added to the record of what that account does, with the time; any member of the workspace can see a document's history of moves and readings.
- Why
- To keep the records your workspace's figures rest on
- Our lawful basis (POPIA s11)
- Performing the contract (s11(1)(b)). The customer agreement governs what a workspace gives us to process on its behalf.
- When
- Your workspace switches on AI reading, and a member uploads a document to it or presses "Read with AI" on a document already held
- What we collect
- The document's pages are sent to an AI model, which returns the text of each page and proposes how the document is filed: its kind, title, document number, revision, date of issue, issuer, folder and tags, and whether it replaces a document already held, each with the words in the document the proposal rests on. Where the model cannot tell, the field is left empty. We keep the text of each page, a search index made from it, and each proposal with who confirmed, changed or rejected it and when. A page the model could not read is marked "Not read". Only owners and administrators switch AI reading on or off. While it is off, nothing is read. While it is on, each document is read once it has been stored, without a further press, and a document already held is read when a member presses the button.
- Why
- To let members find and question their own documents
- Our lawful basis (POPIA s11)
- Performing the contract (s11(1)(b)). The customer agreement governs what a workspace gives us to process on its behalf.
- When
- You ask a question on the Ask page in the portal
- What we collect
- Your question, your account, the workspace and the time. The passages from your workspace's documents that the search finds are sent with the question to an AI model. We keep the question, the answer, which documents and pages it cites, and which model answered. Only documents of the workspace you are in are searched or sent.
- Why
- To answer questions from a workspace's own documents, with the pages that support the answer
- Our lawful basis (POPIA s11)
- Performing the contract (s11(1)(b))
- When
- You ask the AI analyst a question in the portal, where your workspace holds the analyst module
- What we collect
- Your question, your account, the workspace and the time. To answer it, our server gathers evidence from your workspace only: its declared assets and their roles; measured readings and their summaries, each with its time, unit and coverage grade; alarm records with their times and states (an alarm record can name the member who acknowledged or closed it); and passages of documents already read with AI, with the document's revision and page. Where the workspace has declared a point of delivery and the tariff it is billed on, the published rates of that tariff are added, each with the document and page it is printed on (Eskom's tariff booklet or the municipality's tariff schedule); published rates are not personal information. The question and that evidence are sent to an AI model. We keep the question, the answer or the refusal, the exact list of evidence sent, which model answered, the size of the request and the answer, when it started and finished, and whether a member has reviewed the answer. Only data of the workspace you are in is read or sent. A question that the evidence cannot support is refused before anything is sent. Our staff cannot ask questions in a workspace unless they are also an owner or administrator of that workspace, and then they ask as that member.
- Why
- To answer questions about a workspace's own plant from its own records, with the evidence each answer rests on
- Our lawful basis (POPIA s11)
- Performing the contract (s11(1)(b)). The customer agreement governs what a workspace gives us to process on its behalf.
- When
- You press "Explain this result" in the portal
- What we collect
- The envelope you ask about and the reasons it was refused are sent to an AI model, which words an explanation. We keep a record of the request: your account, the workspace, the time, which reasons were sent, which model answered and the size of the answer. We do not keep the envelope in that record, and we do not keep the explanation.
- Why
- To help the person setting up a sender correct it
- Our lawful basis (POPIA s11)
- Performing the contract (s11(1)(b)); our legitimate interest in a service people can set up without help (s11(1)(f))
- When
- You enter a site's address in the portal
- What we collect
- What you type in the address box is sent by our server to Mapbox, which returns up to five matching addresses with their coordinates; we keep the address and coordinates you choose for the site, not your searches. When you open the site map, and on the Overview page, your browser loads the map directly from Mapbox, so Mapbox receives your connection address and a description of your browser and device. Mapbox says it keeps the connection address in its logs for 30 days.
- Why
- To place a site accurately and show where it is
- Our lawful basis (POPIA s11)
- Performing the contract (s11(1)(b))
- When
- Your workspace sets up a weather job for one of its declared sites
- What we collect
- The site's coordinates are sent to Open-Meteo, which returns weather readings for that place. Nothing about any person is sent: no name, e-mail, account or connection address of a member. We keep the job, who set it up and when, each run (time, result, how many readings), and the weather readings. Weather readings are labelled as coming from an outside source and are never used as a site's measured readings, bills, statements or alarms. A workspace has one weather connection. It checks every hour, or less often if a member chooses, and never more often; each check also stores the forecast for the coming hours and days, labelled as modelled, which the Overview page shows.
- Why
- To show the weather at a site beside its own readings
- Our lawful basis (POPIA s11)
- Performing the contract (s11(1)(b)). A site's coordinates identify the company that owns it, which POPIA treats as that company's personal information.
- When
- You contact us by e-mail or telephone, or we meet you in business
- What we collect
- Your name, contact details, organisation, role and what you tell us
- Why
- To reply, and to keep a record of the correspondence and of your consent choices
- Our lawful basis (POPIA s11)
- Our legitimate interest, or steps you ask us to take before a contract (s11(1)(b), (f))
- When
- You are a customer, or your site takes part in our testing
- What we collect
- Account holders' names, work e-mail addresses, roles and sign-in records; the site, meter and device readings you connect. Readings name no person, but they identify the company that owns the site, and POPIA treats that as the company's personal information.
- Why
- To provide the service you contract for, or to test the platform with your site's readings
- Our lawful basis (POPIA s11)
- Performing the contract (s11(1)(b)). For testing before a contract, the site owner's written consent (s11(1)(a)), which also covers storage outside South Africa (s72(1)(b)). A separate customer agreement governs data you give us to process on your behalf.
Giving us information is voluntary. If you do not give it, we cannot answer an enquiry or provide a service that depends on it. No law requires you to give it to us for these purposes.
Special and children's information. We do not process special personal information (such as health, religion or biometrics) or children's information on purpose. The questionnaire and the contact form are for adults; if you are under 18, please do not use them. Information about a child that reaches us is deleted when we find it.
3. What we do not do, and direct marketing
- We do not sell or rent personal information.
- We do not make decisions about you by automated means alone (s71).
- We do not use your answers or messages to train AI models.
- AI help is advice only. Where the portal offers an AI explanation, a filing proposal or an answer, it is labelled as such and changes nothing by itself. A filing proposal takes effect only when a member confirms it, and the platform's own check remains the authority. A drafted mapping for a connection takes effect only when a member saves it, and no AI takes part when readings are then taken in. An answer from the AI analyst is not a record, is shown as unreviewed until a member reviews it, and never states a saving.
- Direct marketing. We send it only to people who have consented (s69). We may approach a business contact once to ask for that consent, using the Information Regulator's Form 4, as amended on 17 April 2025, or a form substantially similar to it. We never approach anyone who has refused. We keep a list of refusals so that we never contact those people again. Every message we send says who it is from and how to stop further messages.
4. Who receives it
- Lovable hosts our website and portals and builds our software. It processes information on our behalf as the website and portals run. The written agreement that POPIA sections 20 and 21 require with it is not in force: Lovable offers its data processing agreement only on plans other than the one we hold (section 7). Until we remove it, about two weeks after our database moved, Lovable also keeps our former database in Frankfurt, Germany, unused, as a fallback; it is deleted with its backups when we remove it. The network that delivers the site for Lovable is run by Cloudflare.
- Supabase holds our database, our account records (including the secret keys of two-step sign-in) and the files stored for workspaces (documents, ticket files and profile photos), in Ireland, under its data processing agreement with us. It keeps its own backup copies of the database for 7 days.
- Cloudflare also provides Turnstile, the check on our sign-in page and public forms that a person is using them. This is a service on our own Cloudflare account, separate from the network that delivers the site. It receives, directly from your browser, the technical signals described in section 2 and your connection address. What Cloudflare keeps from a check, for how long, and where it processes it are still being recorded in our transfer register.
- Our e-mail service provider carries and stores the e-mails you send us and our replies. It is Microsoft (Microsoft 365). Where Microsoft stores our mailbox is still to be read from our account; if it is outside South Africa, we will name the place, and the section 72 ground we rely on, here.
- Anthropic (Claude) hosts our private business tools: our pipeline of business contacts and consent choices. Its AI model is behind the assistant that builds our software, which sees our project files. It also assists us in drafting and analysis. It receives the information those tools hold.
- Anthropic, reached directly from our server under our own account with it, provides the AI model behind "Explain this result", "Read with AI", the Ask page, the AI analyst and "Draft the mapping" in the portal. It receives what a member of a workspace chooses to send by pressing one of those buttons: the envelope and its reasons, the pages of the document being read, the question with passages from that workspace's own documents, or a question to the AI analyst with the evidence gathered from that workspace's assets, readings, alarm records and documents, and the published tariff rates for its declared point of delivery, or, for "Draft the mapping", one body that a connection of that workspace received, as it was kept, and nothing else from the connection. Where an owner or administrator has switched AI reading on for a workspace, it also receives the pages of each document uploaded to that workspace, as it is uploaded. Each request carries one workspace's information and no other. Anthropic deletes requests and answers within 30 days, and keeps them longer only where it needs them to enforce its usage policy (up to 2 years) or the law requires it. Anthropic does not use them to train its models. No other provider stands between our server and Anthropic.
- Resend sends the e-mails our portal itself sends, from mail.axiomlogic.ai: invitations, password resets and password-change notices sent by the portal, notices to our staff, emergency-access notices, and the notice to our own mailbox that an enquiry, a module request or a support ticket has arrived; the e-mail confirming a member's acceptance of WhatsApp alerts; and the e-mails to the members on a workspace's "When WhatsApp is down" list. A notice about an enquiry or a ticket carries none of its content; a notice about a module request names the person who asked and nothing else about them. Resend receives the recipient's address and name and the message. From revision 28 it also sends the e-mails of our sign-in service (sign-up confirmation, change of e-mail address, re-authentication, invitations and password recovery).
- Apple provides "Sign in with Apple". When you choose it, Apple confirms who you are and shares with us only what is listed in section 2. Apple's own handling of your Apple Account is governed by Apple's privacy policy, not this notice. Apple learns that you signed in to our service. Sign in with Apple is not offered while it is moved from Lovable's managed setup to our own; this notice will say how it works before it is offered again. Apple says it generally stores the personal information it collects with Apple Inc. in the United States.
- Mapbox provides address search and maps in the portal. Our server sends it the text typed in the address box. A member's browser loads maps from it directly, which gives it the member's connection address and a description of the browser and device. Mapbox states that it processes personal information in the United States, with copies cached in other regions. Which terms apply to our account, and whether its data processing agreement is in force for it, is still being recorded in our transfer register.
- WasenderAPI sends our WhatsApp alerts, from one WhatsApp number linked to it, and passes back your replies and the delivery reports. It receives your WhatsApp number, the text of each alert and your replies. It is not part of WhatsApp: its terms say it is not affiliated with WhatsApp Inc., and WhatsApp may restrict the number without notice. WhatsApp also carries each message under its own terms. WasenderAPI gives a London address; it does not say where its servers are, and it has not given us written terms (transfer register, revision 21). We use it only for people who have switched alerts on, replied ACCEPT or YES or written JOIN, and for the invitations described in section 2. The invitation, the welcome message and the confirmation after JOIN say that our messages go through WasenderAPI, outside South Africa, and give the address of this notice.
- Open-Meteo provides weather readings. It receives a site's coordinates and nothing about any person. While our platform is in testing and has no paying customers, we use Open-Meteo's free service; whether its terms for non-commercial use cover testing is still to be confirmed with Open-Meteo. We will move to its paid service, and update this notice, before we offer weather to a paying customer.
- Our professional advisers (attorneys, auditors) receive information under a duty of confidence, when needed.
- Authorities receive information where the law requires it.
5. Transfers outside South Africa
Lovable, Supabase, the network that delivers the site, Cloudflare (for Turnstile), Anthropic, Resend, Apple, Mapbox, Open-Meteo and WasenderAPI process information outside South Africa. For WasenderAPI we rely on your consent (s72(1)(b)), which you give when you switch WhatsApp alerts on or accept the portal's invitation, reply ACCEPT or YES or write JOIN, and which you may withdraw by replying STOP. Apple says it generally stores personal information in the United States. Where Open-Meteo processes information, and the section 72 ground we rely on for Apple and for Open-Meteo, are still being recorded in our transfer register; we will name them here once they are. Open-Meteo receives only a site's coordinates. Supabase stores our database, accounts and files in Ireland, where the EU General Data Protection Regulation applies; the section 72 ground we rely on, Supabase's data processing agreement, is recorded in our transfer register. Our former database at Lovable, kept unused until it is removed, is in Germany, where the same Regulation applies. Anthropic stores information in the United States and may route requests to the United States, Europe, Asia and Australia. The AI model behind "Explain this result", "Read with AI", the Ask page, the AI analyst and "Draft the mapping" is Anthropic's, reached directly from our server, and the same applies to it. Resend sends our e-mails from its service in Ireland, where the EU General Data Protection Regulation applies; the section 72 ground we rely on is recorded in our transfer register. No binding agreement with Lovable, which hosts the website and portals but no longer holds our database, is in force (section 7). The grounds in POPIA section 72 that we use are:
- a binding agreement that gives protection substantially similar to POPIA; and
- your consent, which we ask for before the questionnaire starts.
Our transfer register shows the ground each transfer relies on, and any ground still being put in place.
Our transfer register lists the providers, their locations and the ground relied on, and shows any ground still being recorded. It is available from the Information Officer.
6. How long we keep it
| Information | Kept for |
|---|---|
| Questionnaire answers, and any reply details given with them | 12 months, then deleted by a daily database job that logs each deletion |
| Site ratings | 12 months, then deleted by a daily database job that logs each deletion |
| Notice and invitation records | 12 months, then deleted by a daily database job that logs each deletion |
| Contact form messages | 3 years after the last contact, unless a longer period is needed for a legal claim |
| The scrambled connection address used to limit misuse | Up to 2 days |
| Records of wrong-password and wrong-code attempts | Up to 2 days |
| Sign-in records (account, time, method, outcome and a shortened connection address) | 90 days, then deleted by a daily database job that logs each run |
| Records of "Explain this result" requests (who, when, which reasons, which model) | 90 days, then deleted by a daily database job that logs each run |
| The Apple identifier and e-mail Apple shares | While the account is open, then as for other account records |
| Our record of a refused "Sign in with Apple" attempt | 90 days, as for other sign-in records. How long our sign-in provider keeps its own log of the attempt is still being recorded. |
| Weather jobs, and who set each up and when | While the workspace is open; a job is closed, not deleted, and the closed record is kept for 3 years |
| Records of each weather job run | 90 days, then deleted by a daily database job that logs each run |
| Weather forecasts | 7 days from when each was issued, then deleted by a daily database job that logs each run |
| Weather readings | As for readings from a site, under our storage and retention rule |
| Fingerprints of two-step recovery codes | While the account is open |
| The record of a trusted browser (a fingerprint of its cookie, never the cookie itself) | Until it expires after 30 days or you revoke it; the record is deleted by a daily database job within 30 days after that |
| Our sign-in provider's record of each open session: your full connection address, a description of your browser, when it started and when it was last active | Until you sign out or end the session from your account. No limit on how long a session may stay open is set yet. |
| Profile details, mobile number and photo | While the account is open, or until you remove them |
| A WhatsApp contact's name and sealed number | Until 30 days after an owner or administrator removes the contact or the contact replies STOP, then cleared by a daily database job that logs each run |
| The rest of a WhatsApp contact's entry: the fingerprint and last 3 digits of the number, its state and dates, who confirmed the person's agreement and when, and the invitation counts | 3 years after removal or STOP, so that a STOP keeps the number from being added again in that time |
| Each WhatsApp invitation sent to a contact: when it was sent, whether it was delivered, and when its link was first and last opened and how many times | 90 days after the invitation was sent, then deleted by a daily database job that logs each run |
| A test message a member sends to their own number: the time, the result and a reference, without the number | 90 days, then deleted by a daily database job that logs each run |
| A member's request to receive WhatsApp alerts that was started but not accepted: the sealed number and its fingerprint | The request lapses after 7 days; its sealed number is cleared within 30 days after it lapses or is withdrawn, by a daily database job that logs each run |
| When the portal's WhatsApp invitation was shown to a member, dismissed or continued | 12 months, then deleted by a daily database job that logs each run |
| Consent to WhatsApp alerts, given by ticking the box and tapping Accept, or by ACCEPT, YES or JOIN, and its withdrawal | While the consent is in force, then 3 years after it is withdrawn, as for other consent records. The entry in the record of what an account did, which never holds the number, is kept as that record is |
| Your progress through a walkthrough of the portal | 90 days after your last recorded step, then deleted by a daily database job that logs each run. The entries in the record of what your account did are kept as that record is |
| Each WhatsApp alert waiting to be sent or sent, with the recipient and the number it went to | 90 days, then deleted by a daily database job that logs each run |
| Delivery reports for WhatsApp messages (sent, delivered, read, failed) | 90 days after each report arrives, then deleted by a daily database job that logs each run |
| Alerts held back by a limit, waiting for the grouped message | 90 days, then deleted by a daily database job that logs each run |
| The alarm groups offered to a contact, the groups chosen, each saved version and the COMPLETE confirmation | While the contact receives alerts; 90 days after the contact replies STOP or is removed, then deleted by a daily database job that logs each run |
| The text of a reply to our WhatsApp number | 90 days after it arrives, then cleared by a daily database job that logs each run; the record that a reply arrived is kept with the contact's entry |
| The "When WhatsApp is down" list: who is on it, who added or removed them and when | While the workspace is open; an entry for someone removed from the list is kept 3 years after removal |
| Notices to the members on that list, by e-mail and in the portal, and each e-mail sent and its outcome | 90 days from when the notice was made, then deleted by a daily database job that logs each run |
| The e-mail confirming a member's acceptance of WhatsApp alerts, and the WhatsApp message sent to the member's number: when each was sent and its outcome | 90 days, then deleted by a daily database job that logs each run |
| The record of an opt-out (reply STOP), and of switching alerts off or removing a contact | 3 years after the opt-out, as for other consent records; then the fingerprint of the number is removed |
| Support tickets, their messages and files | While the workspace is open, then as the customer agreement states |
| Answers to the portal feedback prompt | While your account is open, or until you delete them |
| Documents a workspace uploads | While the workspace is open, or until an owner or administrator deletes the document, then as the customer agreement states. A superseded revision is kept beside the current one and cannot be deleted. |
| The record of a deleted document: who deleted it, when, its title, fingerprint and size, and the reason given | As for the record of what an account did |
| A refused attempt to delete a document: the account, the time and the reason | 90 days, then deleted by a daily database job |
| The text of each page of a document read with AI, and its search index | While the document is held. When an owner or administrator switches AI reading off, the text and index of every document in that workspace are deleted at once, and each deletion is logged. |
| Filing proposals, and who confirmed, changed or rejected each one and when | While the document is held |
| Questions asked on the Ask page, and their answers | 90 days, then deleted by a daily database job that logs each run |
| Questions asked of the AI analyst, its answers and refusals, and the list of evidence sent | 90 days, then deleted by a daily database job that logs each run. A record that a question was asked (the account, the workspace, the time and the outcome) stays in the record of what an account did. |
| Requests to the AI model and its answers, kept by Anthropic | Deleted within 30 days; up to 2 years where Anthropic needs them to enforce its usage policy, or longer where the law requires |
| Readings from a site, and the messages that carried them | As the customer agreement or the consent for testing states, under our storage and retention rule, which the Information Officer gives on request |
| The fingerprint of a password-reset link (never the link itself) | Up to 7 days |
| Account records | While the account is open, then as the customer agreement and the law require. |
| The record of what an account did (our access log) | 7 years from each entry. Twelve months after a person leaves a workspace, the link from their entries to their name is cut and they are shown as "Former member" with a code. The entries themselves are never changed. |
| Business contacts and consent records | While the contact is relevant to us; consent records for 3 years after consent is withdrawn |
| Refusals ("do not contact") | Permanently, holding only what is needed to honour the refusal |
| Enquiries and correspondence | 3 years after the last contact, unless a longer period is needed for a legal claim |
| Customer account records | For the contract, then as the customer agreement and tax law require |
| Website security logs | As kept by our hosting provider, and no longer than needed for security |
| Backup copies of the database | Kept by our database provider (Supabase) for 7 days, on its own schedule. Our former database at Lovable and its backups are deleted when we remove it, about two weeks after the move. |
- Information
- Questionnaire answers, and any reply details given with them
- Kept for
- 12 months, then deleted by a daily database job that logs each deletion
- Information
- Site ratings
- Kept for
- 12 months, then deleted by a daily database job that logs each deletion
- Information
- Notice and invitation records
- Kept for
- 12 months, then deleted by a daily database job that logs each deletion
- Information
- Contact form messages
- Kept for
- 3 years after the last contact, unless a longer period is needed for a legal claim
- Information
- The scrambled connection address used to limit misuse
- Kept for
- Up to 2 days
- Information
- Records of wrong-password and wrong-code attempts
- Kept for
- Up to 2 days
- Information
- Sign-in records (account, time, method, outcome and a shortened connection address)
- Kept for
- 90 days, then deleted by a daily database job that logs each run
- Information
- Records of "Explain this result" requests (who, when, which reasons, which model)
- Kept for
- 90 days, then deleted by a daily database job that logs each run
- Information
- The Apple identifier and e-mail Apple shares
- Kept for
- While the account is open, then as for other account records
- Information
- Our record of a refused "Sign in with Apple" attempt
- Kept for
- 90 days, as for other sign-in records. How long our sign-in provider keeps its own log of the attempt is still being recorded.
- Information
- Weather jobs, and who set each up and when
- Kept for
- While the workspace is open; a job is closed, not deleted, and the closed record is kept for 3 years
- Information
- Records of each weather job run
- Kept for
- 90 days, then deleted by a daily database job that logs each run
- Information
- Weather forecasts
- Kept for
- 7 days from when each was issued, then deleted by a daily database job that logs each run
- Information
- Weather readings
- Kept for
- As for readings from a site, under our storage and retention rule
- Information
- Fingerprints of two-step recovery codes
- Kept for
- While the account is open
- Information
- The record of a trusted browser (a fingerprint of its cookie, never the cookie itself)
- Kept for
- Until it expires after 30 days or you revoke it; the record is deleted by a daily database job within 30 days after that
- Information
- Our sign-in provider's record of each open session: your full connection address, a description of your browser, when it started and when it was last active
- Kept for
- Until you sign out or end the session from your account. No limit on how long a session may stay open is set yet.
- Information
- Profile details, mobile number and photo
- Kept for
- While the account is open, or until you remove them
- Information
- A WhatsApp contact's name and sealed number
- Kept for
- Until 30 days after an owner or administrator removes the contact or the contact replies STOP, then cleared by a daily database job that logs each run
- Information
- The rest of a WhatsApp contact's entry: the fingerprint and last 3 digits of the number, its state and dates, who confirmed the person's agreement and when, and the invitation counts
- Kept for
- 3 years after removal or STOP, so that a STOP keeps the number from being added again in that time
- Information
- Each WhatsApp invitation sent to a contact: when it was sent, whether it was delivered, and when its link was first and last opened and how many times
- Kept for
- 90 days after the invitation was sent, then deleted by a daily database job that logs each run
- Information
- A test message a member sends to their own number: the time, the result and a reference, without the number
- Kept for
- 90 days, then deleted by a daily database job that logs each run
- Information
- A member's request to receive WhatsApp alerts that was started but not accepted: the sealed number and its fingerprint
- Kept for
- The request lapses after 7 days; its sealed number is cleared within 30 days after it lapses or is withdrawn, by a daily database job that logs each run
- Information
- When the portal's WhatsApp invitation was shown to a member, dismissed or continued
- Kept for
- 12 months, then deleted by a daily database job that logs each run
- Information
- Consent to WhatsApp alerts, given by ticking the box and tapping Accept, or by ACCEPT, YES or JOIN, and its withdrawal
- Kept for
- While the consent is in force, then 3 years after it is withdrawn, as for other consent records. The entry in the record of what an account did, which never holds the number, is kept as that record is
- Information
- Your progress through a walkthrough of the portal
- Kept for
- 90 days after your last recorded step, then deleted by a daily database job that logs each run. The entries in the record of what your account did are kept as that record is
- Information
- Each WhatsApp alert waiting to be sent or sent, with the recipient and the number it went to
- Kept for
- 90 days, then deleted by a daily database job that logs each run
- Information
- Delivery reports for WhatsApp messages (sent, delivered, read, failed)
- Kept for
- 90 days after each report arrives, then deleted by a daily database job that logs each run
- Information
- Alerts held back by a limit, waiting for the grouped message
- Kept for
- 90 days, then deleted by a daily database job that logs each run
- Information
- The alarm groups offered to a contact, the groups chosen, each saved version and the COMPLETE confirmation
- Kept for
- While the contact receives alerts; 90 days after the contact replies STOP or is removed, then deleted by a daily database job that logs each run
- Information
- The text of a reply to our WhatsApp number
- Kept for
- 90 days after it arrives, then cleared by a daily database job that logs each run; the record that a reply arrived is kept with the contact's entry
- Information
- The "When WhatsApp is down" list: who is on it, who added or removed them and when
- Kept for
- While the workspace is open; an entry for someone removed from the list is kept 3 years after removal
- Information
- Notices to the members on that list, by e-mail and in the portal, and each e-mail sent and its outcome
- Kept for
- 90 days from when the notice was made, then deleted by a daily database job that logs each run
- Information
- The e-mail confirming a member's acceptance of WhatsApp alerts, and the WhatsApp message sent to the member's number: when each was sent and its outcome
- Kept for
- 90 days, then deleted by a daily database job that logs each run
- Information
- The record of an opt-out (reply STOP), and of switching alerts off or removing a contact
- Kept for
- 3 years after the opt-out, as for other consent records; then the fingerprint of the number is removed
- Information
- Support tickets, their messages and files
- Kept for
- While the workspace is open, then as the customer agreement states
- Information
- Answers to the portal feedback prompt
- Kept for
- While your account is open, or until you delete them
- Information
- Documents a workspace uploads
- Kept for
- While the workspace is open, or until an owner or administrator deletes the document, then as the customer agreement states. A superseded revision is kept beside the current one and cannot be deleted.
- Information
- The record of a deleted document: who deleted it, when, its title, fingerprint and size, and the reason given
- Kept for
- As for the record of what an account did
- Information
- A refused attempt to delete a document: the account, the time and the reason
- Kept for
- 90 days, then deleted by a daily database job
- Information
- The text of each page of a document read with AI, and its search index
- Kept for
- While the document is held. When an owner or administrator switches AI reading off, the text and index of every document in that workspace are deleted at once, and each deletion is logged.
- Information
- Filing proposals, and who confirmed, changed or rejected each one and when
- Kept for
- While the document is held
- Information
- Questions asked on the Ask page, and their answers
- Kept for
- 90 days, then deleted by a daily database job that logs each run
- Information
- Questions asked of the AI analyst, its answers and refusals, and the list of evidence sent
- Kept for
- 90 days, then deleted by a daily database job that logs each run. A record that a question was asked (the account, the workspace, the time and the outcome) stays in the record of what an account did.
- Information
- Requests to the AI model and its answers, kept by Anthropic
- Kept for
- Deleted within 30 days; up to 2 years where Anthropic needs them to enforce its usage policy, or longer where the law requires
- Information
- Readings from a site, and the messages that carried them
- Kept for
- As the customer agreement or the consent for testing states, under our storage and retention rule, which the Information Officer gives on request
- Information
- The fingerprint of a password-reset link (never the link itself)
- Kept for
- Up to 7 days
- Information
- Account records
- Kept for
- While the account is open, then as the customer agreement and the law require.
- Information
- The record of what an account did (our access log)
- Kept for
- 7 years from each entry. Twelve months after a person leaves a workspace, the link from their entries to their name is cut and they are shown as "Former member" with a code. The entries themselves are never changed.
- Information
- Business contacts and consent records
- Kept for
- While the contact is relevant to us; consent records for 3 years after consent is withdrawn
- Information
- Refusals ("do not contact")
- Kept for
- Permanently, holding only what is needed to honour the refusal
- Information
- Enquiries and correspondence
- Kept for
- 3 years after the last contact, unless a longer period is needed for a legal claim
- Information
- Customer account records
- Kept for
- For the contract, then as the customer agreement and tax law require
- Information
- Website security logs
- Kept for
- As kept by our hosting provider, and no longer than needed for security
- Information
- Backup copies of the database
- Kept for
- Kept by our database provider (Supabase) for 7 days, on its own schedule. Our former database at Lovable and its backups are deleted when we remove it, about two weeks after the move.
Backups and deletion. When we delete a record, at the end of its retention period or at your request, it is removed from our live database at once. It stays inside the backup copies our database provider made before the deletion until those copies are themselves deleted, within 7 days, and inside our former database at Lovable until that is removed. Backup copies are used only to recover the service.
7. How we protect it
- Access. Only the operator can open questionnaire records and contact messages; the database itself enforces this. A workspace's tickets, documents and photos are reached only through the server, which first checks that the person belongs to that workspace. Our staff read a workspace's data only under a support grant that the workspace can see and revoke. The AI analyst reads only the workspace of the person asking, through the server, which first checks that the person belongs to that workspace and that the workspace holds the analyst module.
- Passwords. We never see your password. It is kept only as a scrambled value, and a new password is refused if it appears in lists of passwords known to have leaked.
- Two-step sign-in. Staff accounts, and the owners and administrators of every workspace, need a code from an authenticator app as well as the password. The authenticator's secret key is kept by our sign-in provider, not by us; we keep only fingerprints of the recovery codes. If you tick "Trust this browser for 30 days" when you sign in with a code, that browser signs in without the code for 30 days, or until you revoke it from your account. This applies to our staff and to members of a workspace alike.
- Deletion. A questionnaire answer is deleted only by the daily retention job or, when you ask us, by our deletion procedure, which keeps a note of the deletion (the record's number and the date, nothing else).
- Encryption. Information is encrypted in transit.
- Our providers. Supabase, which holds our database, accounts and files, is under its written data processing agreement with us. Lovable, which hosts our website and portals, offers its agreement only on plans other than the one we hold, so no such agreement is in force with it. Our transfer register records the terms each provider is under.
- If a compromise affects you and you can be identified, we will tell you and the Information Regulator as soon as reasonably possible (s22).
8. Your rights
You may:
- ask whether we hold personal information about you, which is free, and for a copy (s23);
- ask us to correct or delete it (s24);
- object, on reasonable grounds, to our processing based on legitimate interest (s11(3)(a)). For a questionnaire answer, we honour an objection by deleting it;
- withdraw consent where we rely on it (s11(2)(b)), including consent to be contacted;
- complain to the Information Regulator (s74): Woodmead North Office Park, 54 Maxwell Drive, Woodmead, Johannesburg, 2191; POPIAComplaints@inforegulator.org.za; inforegulator.org.za.
Finding your record. We do not record who answered anonymously. We find the record by the words, the date and the approximate time you give us.
How to ask. Objection, correction and deletion requests are free. You may make them by e-mail, by telephone, by SMS or WhatsApp to +27 83 375 1245, by post, or by hand at our address. You may use the Information Regulator's Form 1 (objection) or Form 2 (correction or deletion), but you do not have to.
Response time. We tell you in writing what we have done within 30 days. Access to records is also governed by our PAIA manual.
9. Changes
We publish any change to this notice on this page, with its date. A change that affects how we use information already collected is notified before it takes effect.
Last updated: 24 October 2026.