Skip to content

Welcome to Tabzone.

Join our newsletter for new arrivals, thoughtful finds, sales and the occasional note worth opening.

By joining, you agree to receive Tabzone emails. Unsubscribe at any time.

Legal / Core

Security and Trust

How Tabzone Africa protects accounts, orders, payments and personal data, and what you can do to stay safe.

Effective 8 November 2026Last updated 8 November 2026

SUMMARY

  • We use layered technical and organisational controls across the storefront, API, database and payment flow.
  • Card data is handled by our payment provider, not stored on our servers.
  • If you see something suspicious or believe you have found a vulnerability, contact us with the subject line "Security report".
01

Our security commitment

Tabzone Africa handles personal data, account credentials, order details and payment references. We treat the security of that information as part of the product, not as an afterthought. Our approach is to collect only what we need, limit who can access it, protect it in transit and at rest, monitor for abuse and respond quickly when something goes wrong.

This document explains our security programme in plain language. It is not a warranty that no incident can occur. It is a statement of the controls and expectations we apply to the store, the API and the people who operate them.

02

Scope of this document

This document covers the tabzoneafrica.com storefront, the Tabzone customer applications, the Go API that serves catalogue, account, bag and checkout data, the PostgreSQL database, the media and content pipeline, and the third-party services that support payment, delivery, hosting, email and security.

It does not cover third-party payment pages, delivery partners' own systems or services you access through an external link. Those providers are responsible for their own security programmes, and we review them as part of our vendor-management process.

03

Security principles

  • Least privilege: people and systems receive only the access needed for their role.
  • Defence in depth: multiple independent controls protect the same asset.
  • Data minimisation: we avoid collecting and retaining data we do not need.
  • Secure by default: features are built with authentication, validation and safe defaults.
  • Separation of duties: development, deployment and production access are controlled and reviewed.
  • Accountability: actions on production systems are logged and attributable.
  • Continuous improvement: incidents, tests and reviews feed back into the programme.
04

How the store is built

The public storefront is a Next.js application served behind a reverse proxy and a CDN/WAF layer. The API is a Go service that exposes catalogue, customer, bag and checkout endpoints. The primary database is PostgreSQL. Uploaded media is stored separately from application code and served through controlled delivery paths.

Production services run on hardened Linux hosts with network access restricted to the ports and services required for operation. Administrative access uses SSH keys rather than passwords. Application secrets are kept outside source control and are restricted to the processes that need them.

05

Encryption and data protection

Traffic between your browser or app and the store is protected with TLS. Traffic between the edge, reverse proxy and origin is configured to preserve encryption and trusted forwarding information. Sensitive credentials and tokens are handled as secrets and are not logged in plain text.

We apply access controls and encryption appropriate to the storage layer, protect database credentials, and avoid storing payment card numbers or card security codes. Backups and exported data are protected with the same access discipline as production data.

06

Authentication and access control

Customer passwords are stored as salted hashes using an industry-standard password-hashing algorithm. We never display or email a customer's existing password. Sessions use revocable tokens, and authentication flows include rate limits and abuse controls.

Administrative access is limited to authorised personnel. Accounts are individual, privileges are role-based, and access is reviewed when responsibilities change. Production access requires a secure connection and is logged. We do not share administrative credentials between people.

07

Payment security and PCI scope

We do not collect or store full card numbers or card security codes on Tabzone servers. Online payments are redirected to, or processed by, an authorised payment provider. The provider handles sensitive payment credentials under its own PCI DSS programme and security controls.

We receive only the payment status, reference, amount, currency and limited transaction metadata needed to confirm, reconcile and support an order. We do not claim to be PCI DSS certified ourselves; our goal is to keep our systems out of scope for cardholder data wherever the payment flow allows it.

08

Data minimisation and retention

We collect the information needed to create an account, fulfil an order, take payment, deliver a product, provide support and meet legal obligations. We do not ask for payment card details through email, chat or phone.

Retention periods are tied to the purpose and to legal requirements. Order and tax records are kept for the required period. Account, support, marketing and security data are kept only as long as needed, then deleted, anonymised or aggregated.

09

Backups and service resilience

We maintain backup and recovery arrangements for the database and critical configuration so that the store can be restored after accidental deletion, corruption or a service failure. Backups are access-controlled and tested periodically.

The production environment is monitored for availability and errors. We use process supervision, restart policies and health checks to recover services. Capacity and dependencies are reviewed as traffic and catalogue size grow.

10

Logging, monitoring and detection

Application, access and security logs record the events needed to operate the store, investigate errors and detect abuse. Logs are protected against unauthorised access and retained for a limited period. We monitor for failed authentication, unusual order patterns, payment anomalies, error spikes and other signals of compromise or fraud.

We do not log full payment card data, passwords or unnecessary personal data. Where diagnostic data is needed, we aim to use identifiers and redaction rather than sensitive content.

11

Vulnerability management

We keep frameworks, libraries, operating-system packages and container images patched. Dependencies are reviewed for known vulnerabilities, and changes to production are tested before release. Security-relevant configuration is version-controlled where practical.

We welcome reports from security researchers and customers. Our Responsible Disclosure Policy explains the scope, rules and reporting process. We ask that researchers avoid privacy violations, service disruption and data destruction while investigating.

12

Incident response and notification

We maintain an incident-response process that covers detection, triage, containment, eradication, recovery and review. An incident lead coordinates the response, preserves evidence and keeps decision-makers informed.

If a personal-data breach is likely to result in a risk to individuals' rights and freedoms, we will assess the risk, notify the relevant regulator and affected individuals where required by law, and take steps to reduce harm. We will not delay notification to protect reputation.

13

Vendor and supply-chain security

We use third-party providers for payment, hosting, delivery, email, security and infrastructure. Before engaging a provider that handles personal data or payments, we consider its security posture, data location, subcontracting, incident history and contractual commitments.

Providers are required to process data only for the agreed purpose, apply appropriate safeguards, notify us of relevant incidents and support our obligations to customers. We review critical providers periodically and when their service or ownership changes.

14

Physical and environmental security

Production infrastructure is hosted in data-centre environments managed by our providers. Those providers are responsible for physical access control, power, cooling, fire suppression and environmental monitoring. We restrict logical access to the services and data we control.

Paper records containing personal data are minimised. Where they exist, they are stored securely and disposed of confidentially when no longer needed.

15

Customer responsibilities

  • Use a unique, strong password and do not reuse it on other sites.
  • Keep your email account secure; it is used for sign-in, order and security messages.
  • Do not share passwords, one-time codes or account access with anyone.
  • Be cautious of messages that ask for your password, full card number or payment outside the official checkout.
  • Keep your phone number and delivery address current so we can reach you about orders.
  • Sign out of shared devices and report lost or compromised credentials promptly.
  • Use the official Tabzone website or app for payments; we do not ask for payment to a personal account.
16

Security testing and responsible disclosure

We authorise good-faith security research under the rules in our Responsible Disclosure Policy. Testing must not disrupt the store, access other people's data, use social engineering against staff or customers, or involve denial-of-service, malware or physical attacks.

If you believe you have found a vulnerability, contact us privately before disclosing it. We will investigate, keep you informed and work with you on a coordinated disclosure.

17

No certification claims

Unless a specific certification is stated in writing, we do not claim ISO 27001, SOC 2, PCI DSS or another third-party certification for the Tabzone store. Our payment provider maintains its own compliance programme for payment-card processing. We describe our controls honestly rather than implying certifications we do not hold.

18

Security contact

Report suspicious activity, suspected account compromise, phishing or a vulnerability to [email protected] with the subject line "Security report". Include enough detail for us to reproduce and assess the issue. For urgent account or payment concerns, call +256 704 504 652.

RELATED DOCUMENTS

QUESTIONS

If something here is unclear, ask before you order.

Contact support for order, payment, delivery, return or account help. For privacy requests, use “Privacy request”. For security reports, use “Security report”.

[email protected]