Last updated 29 September 2026
Privacy notice
This notice covers the IFTFC Master Console — the tool through which Innovation for the Future Consultants operates client intake forms. It is written for the firms whose forms we run, and for their staff whose details appear in it.
1. Who we are
- Registered name
- Innovation for the Future Consultants
- Address
- 6 Silver Tree Close, Silver Lakes, Pretoria
- Information Officer
- Richard Hayes, richard@iftfc.co.za
2. The short version
We operate forms that collect other people's confidential information — accident details, medical particulars, legal instructions. We built this console so that we cannot read any of it. Not by policy. By construction.
The database behind this console has no field capable of holding a submission's contents. There is nothing to disable, no permission to revoke, and no setting that could be changed to make it visible. Section 4 explains exactly how.
3. The two roles we occupy
POPIA distinguishes the party who decides how information is used (the responsible party) from the one who processes it on their behalf (the operator). We are both, for different information.
| Information | Our role | What that means |
|---|---|---|
| Claimants' and clients' submissions | Operator | The firm decides. We only move it, on their instruction, and never store it. |
| Firm staff details held here — names and addresses forms deliver to, and client logins | Responsible party | We decide how this is handled, and we answer for it. |
4. What this console holds
About each form submission
Eight values. Five are sent by the form; the console adds three of its own that the form never sends. Recorded automatically when a form is used:
Sent by the form:
- which form
- whether it reached the firm
- an error code if it did not
- an approximate size band for the document
- whether it was a test
Added by the console, and never accepted from the form:
- which company — taken from the key the form signed with
- the date and time — taken from the database
- a short reference, generated at random
That is the complete record. There is no name, no identity number, no contact detail, no reference of the firm's own, no answer to any question, no photograph, no signature, no document, and no IP address.
Why that cannot quietly change
- The table storing these records has only number, date and fixed-choice columns. There is no free-text field for a sentence to be written into.
- The endpoint that receives them accepts exactly those five fields and refuses anything else outright, naming the offending field, rather than accepting and discarding it. The company, the date and time, and the reference are not accepted from the caller at all — the company comes from the key the form signed with, the date and time from the database, and the reference is generated at random.
- A test script checks both of these and fails if either stops being true. It is run against the live database after every change.
About the firms we work with
The company name, a contact name and address, the email addresses each form delivers to and a label for each, and settings such as whether a form is live or paused.
About people who sign in
An email address, a password stored only as a one-way hash, and a record of when the account was created and last used. Every action taken in the console is written to an audit log that nothing signed in to the console — including us — can edit or delete: the database refuses those operations outright. The only way to alter it would be direct database access with our server key, which is why that key is held only by scheduled server code and never by a browser.
5. What we can see that we would rather not
Honesty is worth more here than a tidy claim.
Completed forms are emailed to the firm through an email provider on our account. That provider retains the covering email — which includes the person's name, the firm's reference, and their email address — though not the completed document itself. We can therefore see who submitted a form, but not what they said.
Savage Jooste & Adams were told this and are content with it on that basis. Any firm that would prefer otherwise can have the email sent through their own provider instead, at which point we can see neither. Ask and we will arrange it.
6. Who else is involved
| Who | What for | Where |
|---|---|---|
| Netlify | Hosts the console and the form sites | United States |
| Supabase | The console's database and sign-in | Germany |
| Resend | Delivers completed forms to firms | United States |
Each processes information outside South Africa. That is permitted under section 72(1)(a) of POPIA on the basis of the contractual protections in each provider's terms, which IFTFC has accepted for all three.
7. How long things are kept
- Submission records
- Kept for 90 days by default, then deleted by a maintenance routine that runs every six hours. The period is configurable per installation, from 7 days to two years. This console first ran in September 2026, so no record has yet reached that age.
- Audit log
- Kept for the life of the account. Nothing signed in to the console can edit or delete it, which is what makes it worth showing a client.
- Company and recipient details
- While we work with that firm, and deleted on request when we stop.
- Submission contents
- Never held, so never retained.
8. Security
- Sign-in is by email and password over an encrypted connection. Sessions created by an emailed link are refused by the database, so access to an inbox alone is not enough to reach any data.
- Every record is protected at the database level, not merely hidden in the interface.
- Where a form delivers is constrained to a fixed list of domains held outside this console, so even a full compromise of the console cannot redirect a firm's intake to an unrelated address.
- Security reviews are carried out regularly. The most recent ran on 29 and 30 September 2026 and examined this console and the four claimant forms it serves. It raised findings that are tracked individually and are being worked through; some are still open. We would rather say that than claim a clean bill of health.
The console holds no submission contents, so the worst case for a breach is the exposure of firm contact details and delivery statistics — not anyone's personal or medical information.
9. Your rights
If we hold your details — as a member of staff at a firm we work with — you may ask what we hold, have it corrected or deleted, or object to it being held. Write to the Information Officer in section 1.
If you are a claimant or client of one of those firms, your information is the firm's responsibility, not ours. Ask them. We will assist them in answering you.
10. Complaints
The Information Regulator (South Africa)
Woodmead North Office Park, 54 Maxwell Drive, Woodmead, Johannesburg, 2191
010 023 5200 · 0800 017 160 (toll free)
POPIAComplaints@inforegulator.org.za
inforegulator.org.za
The Regulator asks that POPIA complaints be lodged through its eServices Portal at eservices.inforegulator.org.za, which requires registering a profile first.
11. Changes
If this notice changes, the date at the top changes with it, and any firm we work with is told before the change takes effect.
This notice describes how the console works, accurately and in plain words. It is not legal advice and should be reviewed before being relied upon.