Privacy notice
The short version
- The website collects almost nothing. No cookies for tracking, no advertising pixels. Cloudflare's privacy-first analytics counts visits without identifying you.
- Customer deployments run in the customer's own Azure tenant. Mandates and audit records are stored in the customer's database and appear only in the customer's own Teams and Jira Cloud; meeting transcripts are read once to draft a mandate and are not stored. The software sends Governite nothing except an opt-in health heartbeat of counts and timestamps — never content. When we deploy or support a deployment we work inside the customer's tenant as its operator, with access the customer grants and can withdraw.
- The sandbox is the one place we hold your meeting content — three guest accounts, one sanitised transcript, for 14 days, in Governite's own demo tenant. It is deleted on day 14 unless you ask us to keep it.
- We never sell personal information, and we do not use it to train AI models.
1. Who we are
Governite is operated by Ridwaan Kadir, trading as Governite, Durban, KwaZulu-Natal, South Africa ("Governite", "we", "us"). For the purposes of the Protection of Personal Information Act 4 of 2013 (POPIA) we are the responsible party for the website, our sales correspondence and the sandbox, and the Information Officer is Ridwaan Kadir. For persons in the United Kingdom or the European Economic Area we are the controller for those same activities under the UK GDPR and the EU GDPR. Contact: admin@governite.ai.
If the Governite business is transferred to a company formed to carry it on, that company becomes the responsible party for the information described here, on the same terms, and we will update this notice.
2. What this notice covers
This notice explains what personal information we process, why, and what your rights are, across four situations: visiting governite.ai; corresponding with us as a prospect or customer; taking part in the free 14-day sandbox; and using the Governite app once your organisation has deployed it in its own Microsoft Azure tenant under a pilot or licence agreement. The app situation is different from the others: there, your organisation is the responsible party or controller and we act only as its operator or processor, as section 6 explains.
3. The website
governite.ai is a static site hosted on Cloudflare Pages. It sets no cookies of its own and runs no advertising or cross-site tracking. We use Cloudflare Web Analytics, which measures page views and performance without client-side state, fingerprinting or identifying individual visitors. Cloudflare, as our hosting provider, processes standard connection data (IP address, user agent, requested page, timestamp) to serve the site and protect it from abuse; Cloudflare's handling of that data is described in its own privacy policy.
The "Book a pilot call" buttons take you to our scheduling page on Cal.com. Anything you enter there (name, email, notes, chosen time) is collected by Cal.com on our behalf and shown to us; Cal.com's privacy policy applies to its platform.
4. Prospects, customers and correspondence
When you email us, book a call, connect on LinkedIn, or are introduced to us, we keep ordinary business-contact information: your name, role, organisation, work email, the notes of our conversations, and where we are in the conversation (for example "call held", "sandbox active", "not now — revisit in March"). We also record one or two publicly available facts about your organisation that explain why we thought Governite might be relevant to you.
We use this information to respond to you, to arrange and follow up calls, to run a sandbox or pilot you have asked for, and to invoice and support customers. Our lawful basis is our legitimate interest in offering Governite to organisations that are likely to need it, or the performance of an agreement with your organisation. Every message is reviewed and sent by a person, one at a time; there are no automated sequences. If you tell us you do not want to hear from us, we stop, and we keep only the minimum needed to make sure we do not contact you again.
5. The free 14-day sandbox
In the sandbox, up to three people from your organisation (a chair and two owners) receive guest accounts in Governite's own Microsoft 365 demo tenant, where a fictional firm is already running the governance loop. To run it we process:
- the three participants' names, work email addresses and the Entra object IDs that Microsoft assigns to their guest accounts;
- their actions on Teams cards (approve, acknowledge, ask a question, request more time, drift decisions) and the timestamps of those actions;
- one sanitised meeting transcript, or one decision entered without a transcript, that you choose to submit, and the mandate, Jira issue and audit records generated from it.
You agree to sanitise the transcript before submitting it: remove the names of people who are not sandbox participants, and do not include client data, special personal information (as defined in POPIA section 26) or anything confidential to a third party. The sandbox runs on Governite's Azure resources in the Microsoft region we confirm with you before day 0. On day 14 the sandbox ends automatically; we remove the guests' app installation, hand you the audit export if you want it, and delete the sandbox database unless you have asked us in writing to keep it for a stated period. Our lawful basis is your consent and our legitimate interest in demonstrating the product; you can end the sandbox early at any time by emailing us.
6. The Governite app in your organisation's tenant
When your organisation deploys Governite under a pilot or licence agreement, the software runs as one container and one database inside your organisation's own Azure subscription. It processes, on your organisation's behalf and under its instructions:
| Information | Where it comes from | Why |
|---|---|---|
| Meeting transcripts and meeting references (date, title, Teams meeting ID) | Submitted by your organisation's operator through the authenticated API or CLI | To draft a mandate: the decision, its owner, scope and time horizon. The transcript text is passed to the drafting model and is not stored; the record keeps the meeting reference, a link to the transcript and its length |
| Decisions submitted without a transcript (the decision, the reason, the success criterion, the owners) | Submitted by your organisation's operator through the authenticated API or CLI | To create a mandate for a decision made by email or circulation, with no AI drafting |
| Attendees' display names, work email addresses and Entra object IDs | Supplied explicitly with each submission; owner accounts checked through Microsoft Graph | To address approval and acknowledgement cards to the right people, and to detect disabled owner accounts |
| Card actions and free-text entered on cards (edits, questions, reasons, outcomes) | Chairs and owners in Microsoft Teams | To record approvals, acknowledgements, extensions, drift decisions and outcomes |
| Jira issue keys, statuses, due dates and summaries of linked work | Your organisation's Jira Cloud site | To track the approved work and detect drift from the decision |
| The audit log: every state change with actor, time and content | Generated by the service | To provide an immutable, exportable record for your governance and audit functions |
All of this, except the transcript text, is stored in your organisation's database, and none of it is transmitted to Governite. Approved mandates are written to your organisation's own Jira Cloud site and cards are delivered through your organisation's own Microsoft Teams. Your organisation is the responsible party (controller); Governite, where it has any access at all, acts as an operator (processor) — for example when we deploy the software, operate it for your organisation, assist with an incident, or run a rollback at your request — and only under the written terms of the pilot or licence agreement, which contains the operator provisions required by POPIA section 21 and, where applicable, Article 28 of the GDPR. The audit log is append-only by design: the application's own database role cannot delete audit rows. Requests from individuals about information held in a customer deployment should be made to that organisation; we will help it respond.
7. Health heartbeat (opt-in telemetry)
A customer deployment can, if the customer switches it on, send a periodic health heartbeat to Governite's operations dashboard. It is off by default. The payload is metadata only — the software version, counts of mandates by status, counts of audit events, and timestamps — and is pinned by an automated test so that mandate content, transcripts, names and identifiers can never be included. We use heartbeats to see whether a deployment is healthy or has gone stale, and to support the customer. Heartbeats are authenticated per customer and retained for the life of the customer relationship plus twelve months.
8. AI processing
Mandate drafting uses a large language model on Azure OpenAI inside the customer's own Azure tenant. Transcripts are sent to that model from the customer's deployment and are subject to Microsoft's Azure OpenAI data-handling commitments, under which prompts and outputs are not used to train Microsoft's models and are not available to other customers. The software sends neither the transcripts nor the drafts to Governite; where we operate a deployment for a customer, we handle them inside the customer's tenant as its operator (section 6). Owners are matched explicitly to the attendee list supplied with the transcript; the model is not permitted to guess at identities. In the sandbox the same arrangement applies within Governite's demo tenant. We do not use any personal information to train models of our own.
9. Who we share information with
We do not sell personal information and do not share it with advertisers. We use the following service providers (operators), each under its own contractual commitments:
- Microsoft — Microsoft 365, Teams, Entra ID, Microsoft Graph, Azure and Azure OpenAI, for our email, our demo tenant and the sandbox. (In a customer deployment, Microsoft is the customer's provider, not ours.)
- Atlassian — the Jira Cloud sandbox project used in the sandbox. (In a customer deployment, Jira is the customer's own site.)
- Cloudflare — hosting, DNS and privacy-first analytics for governite.ai.
- Cal.com — scheduling of calls.
We may also disclose information where the law requires it, to professional advisers under confidentiality, or to a successor that takes over the Governite business, who will be bound by this notice.
10. Where information is held
Our correspondence and demo tenant are hosted by Microsoft; the sandbox runs in the Azure region we confirm with you before it starts. Service providers may process information in other countries. Where personal information leaves South Africa we rely on POPIA section 72 (the recipient is bound by law or contract to equivalent protection); where it leaves the UK or EEA we rely on adequacy decisions or standard contractual clauses. In a customer deployment, the customer chooses the Azure region where the data is stored; it also appears in the customer's own Microsoft Teams and Jira Cloud site, wherever the customer has those hosted, and none of it is sent to Governite.
11. Security
Governite was built for regulated organisations and the security posture reflects that: the bot and the drafting model authenticate through an Azure Managed Identity, so neither has a password to leak; the remaining credentials (the Jira token, the Microsoft Graph credential, the card-signing key and the submission token) are held in Azure Key Vault; a single Microsoft Graph permission (User.Read.All); every card action cryptographically signed; an append-only audit log enforced by database roles; checksummed exports and forensic snapshots; and written incident and rollback runbooks, with the rollback steps automated and tested. We will tell affected organisations and, where the law requires, the Information Regulator or other authority, without undue delay if we become aware of a security compromise affecting personal information we hold.
12. How long we keep information
| Information | Retention |
|---|---|
| Website connection data and analytics | Held by Cloudflare for its standard periods; we see only aggregates |
| Prospect and customer contact records | For as long as there is a live conversation or relationship, and then until the revisit date we agreed or, failing that, 24 months from last contact; sooner if you ask |
| Sandbox participants and sandbox data | Deleted on day 14, unless you ask us in writing to keep it for a stated period; the audit export is yours |
| Heartbeat telemetry | Life of the customer relationship plus 12 months |
| Data inside a customer deployment | Determined by the customer; the audit log is the customer's own compliance record |
| Contracts, invoices and correspondence we must keep by law | Five years, or longer where tax or company law requires |
13. Your rights
Under POPIA you may ask us to confirm whether we hold personal information about you, to give you access to it, to correct or delete it, and you may object to processing based on legitimate interests or to direct marketing. If you are in the UK or EEA you have the corresponding rights under the GDPR, including portability and the right to withdraw consent at any time. Write to admin@governite.ai; we respond within one month and will ask for enough information to confirm your identity. If you are unhappy with our response you may complain to the Information Regulator (South Africa), or to your local supervisory authority in the UK or EEA.
14. Children
Governite is a business service. The website, sandbox and app are not directed at anyone under 18, and we do not knowingly collect information from children.
15. Changes to this notice
We will post any change here with a new version number and effective date. If a change materially affects sandbox participants or customers, we will tell them directly before it takes effect.
16. Contact
Information Officer: Ridwaan Kadir, Governite · admin@governite.ai · Durban, South Africa.