Privacy notice
Draft · pending legal reviewThis is a draft.
It has not been reviewed by a legal practitioner and it is not a customer privacy policy. It describes what this website does today, and the data-protection controls the SolaDesk product is being built around. A ratified customer notice will be published before the service processes any real customer's information.
1. This website
This website is a set of static pages. SolaDesk asks you for nothing and stores nothing about you — there is no form, no account and no analytics. Our hosting provider does process ordinary technical request data in order to serve the page, which is covered below.
- There is no contact form, newsletter signup, comment field or any other input on this site.
- There are no analytics, no advertising pixels, no tag managers and no session recording.
- No cookie is set by this site. There is no cookie banner because there is nothing to consent to.
- No third-party script, font, stylesheet or image is loaded. Every asset comes from this domain, and the site's Content-Security-Policy forbids anything else.
- No account, login or session exists on this website.
Our hosting provider processes ordinary technical request data - the IP address a request came from, the time, the page requested and the browser's user-agent string - in order to deliver the page and to protect the service from abuse. That is a normal function of serving a website rather than something this site chooses to gather, and it is not used to build a profile of you, combined with anything else, or shared for marketing.
2. The SolaDesk product (in development)
SolaDesk is a service operations platform. When it serves real customers it will process personal information, and it is being designed around the Protection of Personal Information Act rather than having compliance retro-fitted to it. The controls below are implemented in the protected staging build today, with synthetic data only:
- Purpose limitation
- Personal information is held to deliver a service case - to diagnose a fault, arrange a visit, or report to the party that holds the service mandate. It is not repurposed for marketing.
- Consent as a record, not an assumption
- Consent to contact is recorded per customer and per purpose in an append-only record, so what was agreed and when can be shown rather than asserted. Service consent and marketing consent are separate.
- Data minimisation and identity masking
- A customer's name, telephone number and email address stay masked in the interface until the agent has been verified for that specific case. Delivery partners see the work, not the customer's identity.
- Structural redaction in logs
- Operational logs deny personal information by field name and by value shape - contact details, addresses, credentials and network identifiers are dropped before a log line is written, rather than being removed afterwards.
- Tenant and mandate isolation
- A portfolio manager's data is isolated from every other portfolio manager's, and an agent can reach only the mandates they are assigned.
- Auditability
- Contact attempts, state changes and approvals are recorded, so a customer or a mandate holder can be told what happened and who did it.
What we do not claim.Describing these controls is not a declaration of legal compliance. That is a determination about a real operation handling real data, and nobody has made it — SolaDesk is not yet operating with real customer data at all. The current environments contain synthetic test data only.
3. Your rights
Under POPIA a data subject may ask what personal information is held about them, request correction or deletion, object to processing, and complain to the Information Regulator of South Africa. Those rights will be exercisable through the published contact route and an appointed Information Officer.
Outstanding: SolaDesk has not yet published a public contact route or named an Information Officer, so this notice cannot give you an address to write to. Rather than print one that does not work, this section is deliberately incomplete and will be completed before the service handles any real personal information.
4. Changes to this notice
This draft will be replaced, not quietly edited, when a reviewed notice is published. The build identifier in the footer of every page identifies the version you are reading.