Data residency and POPIA
Every account on Gitza gets the same answer to “where is our code?”: South Africa, every layer, with the facility named rather than implied.
Where your data lives
Gitza runs on xneelo Cloud in Samrand, Gauteng. That is not only the Git repositories. The database that holds your issues, pull requests and account, the file storage behind LFS and attachments, and the backups all stay in the same country. If any part of it quietly lived offshore, the promise would be worthless, so it is not built that way.
Hosting nearby can reduce network round-trips for South African teams. Actual latency and transfer speeds depend on your network, location and repository size; we do not promise a universal response time.
Public repositories and integrations
Gitza does not use your code to train AI models. Private repositories are accessible according to the permissions you grant. Public repositories can be read by anyone; Gitza cannot promise how someone else will use a public copy.
When you connect AI tools and MCP, CI providers or webhooks, the services you choose may receive repository content and process it outside South Africa. Check those providers’ policies before connecting private code. Gitza’s hosting location does not determine where those external services process their copies.
POPIA
Hosting in South Africa is one part of a data-residency decision. It does not by itself establish your organisation’s POPIA compliance. Your use of public repositories, external integrations and exports also matters to where information goes.
On the public service, that residency is the default for every account and needs nothing from you. Teams that need it in writing can have a signed POPIA operator agreement on Gitza Enterprise, which names the hosting locations and covers return and deletion of your data on exit.
This page is context, not legal advice, and should not stand in for a compliance assessment. If you need a specific commitment for yours, email hello@gitza.co.za and we will tell you what we can commit to and what we cannot.
Proving it
The categories covered by our hosting claim are Git repositories, account and issue data, LFS objects, attachments and backups. Account email uses a South African mail service; site analytics are self-hosted in South Africa. External services you connect are outside that scope.
For a procurement review, ask hello@gitza.co.za for the current hosting and backup locations, processor details, retention information and contractual commitments for your intended use. The legal policies are still being finalised; this guide is not a substitute for an agreed operator agreement.