Draft for legal review. Retention periods, service-region details and provider terms must be confirmed before production use. This document is not legal advice.
Privacy notice
Responsible party / service operator: Isibuko Digital Solutions · South Africa
Who to contact
For privacy questions or requests, contact isibukodigital@gmail.com. A final publication should identify the correct legal entity, postal address and privacy contact.
Information the service processes
- Account and workspace information: Supabase Auth user identifiers and account email, identity-provider details, workspace name/type, membership, roles and group assignments.
- Organization setup information: Microsoft tenant identifiers, organization name and verified domains, selected Entra group identifiers/names, and the requester email submitted during onboarding. Microsoft Graph access tokens are used for the request and are not stored by this application.
- Documents: uploaded files are parsed and processed temporarily. The original upload is not retained by the application. Extracted text chunks, document names, access groups and vector embeddings are stored in Supabase.
- Questions and activity: by default, query audit records store a SHA-256 hash of the question rather than its text. Hashing is pseudonymization, not anonymization; predictable questions may be guessed. The
DOCQA_AUDIT_QUESTIONSsetting can explicitly select full text or no question text. Audit records can also contain user ID, document names retrieved/cited, action, outcome and timestamp. Sign-in events are not written to this audit stream.
How information is used and shared
Supabase provides authentication and the persistent Postgres/pgvector data store. If hosted language models are enabled, the question and authorized retrieved document passages may be sent to any configured provider in the chain. The starting provider is chosen at random, and the remaining configured providers are tried if it fails. OpenRouter requests ask providers not to collect prompt data, but this request is not a guarantee of provider retention behavior. See the subprocessor list.
When a local or extractive model is configured, model prompts are not sent to Groq, OpenRouter, Cerebras or NVIDIA NIM by this application. The workspace administrator should confirm the active deployment configuration before users submit sensitive information.
Data location, retention and security
The Supabase project region and any model-provider processing locations depend on deployment and provider configuration and must be confirmed before publication. Retention periods for audit records, offboarding records, provider logs and backups are not yet set; these periods must be documented before production onboarding. Supabase backup expiry and provider-side retention are subject to the applicable service settings and agreements.
The application uses tenant-scoped access controls and server-side authorization. These controls do not by themselves establish legal compliance or guarantee that every provider or backup has erased data.
Export, deletion and offboarding
A workspace administrator can download a JSON export containing workspace metadata, member identities and emails, group/role assignments, organization setup and request history, indexed document text, audit events and offboarding-request history. The export does not contain original uploaded files, which the application does not retain, or vector embeddings, which can be regenerated from the exported text.
A workspace administrator can request offboarding. The workspace remains available until a platform administrator reviews the request. If approved, the active workspace, documents and indexed chunks, memberships, groups, query audit events, and linked organization setup records are deleted; associated workspace claims are cleared from Supabase Auth metadata. Supabase Auth accounts are not deleted because an account may be used elsewhere. A minimal offboarding decision record is retained; its retention period is still to be determined. Provider-side copies and backups may persist until their applicable retention periods expire.
Data subject requests
Contact isibukodigital@gmail.com to ask about access, correction, deletion or other rights that may apply under South African law, including POPIA. The applicable lawful basis, response periods, complaint contact and any jurisdiction-specific terms must be confirmed by the responsible party and legal counsel before this draft is used as a final notice.
Changes and unresolved publication items
Before release, confirm the legal entity and address, lawful processing conditions, actual Supabase region and agreements, provider/model retention terms, backup expiry, audit/offboarding retention, and effective date. Do not treat this draft as a final legal policy.