DEV / LOCAL | Environment: Port 4040  |  Sage DB: YaleloDb 2 (LIVE)  |  IBT Poster: Brilliant Link (vendor)       

Data Policy

Effective date: 7 September 2026 · Version 1.0

This Data Policy sets out how data held in the YZ OTS Portal is classified, isolated, retained and disposed of — for the operating company and for every company licensed to use the System. It complements the User Privacy Policy, which covers the personal-data side of the same obligations.

Each licensed company is the data controller for the records its users create in the System; the System operator is the processor and enforces this policy technically on every tenant.

1. Data classification

ClassExamples in the SystemHandling
Restricted Password hashes, OTP codes, session data Encrypted/one-way hashed; never exported; never shared
Confidential Account records, orders and pricing, delivery and crate data, stock levels, signatures, Sage references Access strictly by role and company; no cross-company visibility
Internal Audit logs, support tickets, system metrics Administrator and support staff only
Public Module descriptions, this policy suite Freely accessible

2. Company data isolation (multi-tenancy)

  • Every record created by a company's users belongs to that company; queries are scoped by the signed-in user's store, company and role.
  • One licensed company's users cannot view, query or export another company's records.
  • Licensing metadata (seats, license keys) is owned by the system operator and is never visible to tenant users.
  • On termination of a company's license, the company's data is exported to the company and then purged from the System according to the retention schedule below.

3. Retention schedule

DataRetentionRationale
Order, dispatch, delivery, crate and stock records 7 years Financial and audit requirements
Sage posting / IBT staging records 7 years Accounting reconciliation
User account records (including disabled accounts) Duration of employment/engagement + 2 years Access investigations, audit trail integrity
Audit logs 3 years Security investigations, dispute resolution
OTP / verification codes Deleted once used or superseded Transient security data
Support/communication records 2 years Service quality, complaint handling

Where a shorter period is agreed in a licensed company's contract, the contract prevails for that company's data. No business record is deleted while it is subject to a legal hold.

4. Access control

  • Least privilege: every user sees only their own store/company data and only the functions their role permits.
  • Strong authentication: passwords are bcrypt-hashed; verification codes (OTP) are required for account registration and password resets; repeated failed logins lock the account.
  • Administrative separation: SuperUser and admin actions (user activation, license and configuration changes) are restricted to authorized administrator accounts and are written to the audit log with the acting user's identity.
  • Accounts of departed users are disabled, not deleted, so historical records keep their attribution while the account can no longer sign in.

5. Security and backups

  • All traffic is served over HTTPS; database credentials and third-party secrets are held in server configuration, never in source control.
  • Databases are backed up on a regular schedule; backups are retained on a rolling window and are subject to the same access restrictions as live data.
  • Restores into production are performed only by authorized IT staff and are logged.

6. Third-party processors

  • Microsoft 365 (Graph mail) — sending system notification and verification emails.
  • Sage accounting platform — posting the company's transaction and stock data.
  • Hosting / database provider — running the System and its databases.

Each processor is engaged under terms that require confidentiality and data protection. No data is transferred to any processor outside the arrangements listed above.

7. Data subject and deletion requests

Requests to access, correct or delete personal data (see the User Privacy Policy, section 8) are handled by the user's company administrator together with the system operator's support team. Deletion requests are honoured where no retention obligation applies; where a record must be kept, the personal identifiers are removed/anonymised instead. Requests are completed within 30 days and the outcome is recorded.

8. Breach notification

Suspected personal-data breaches are investigated immediately by IT. Affected users and the relevant company are notified without undue delay, and the incident — cause, scope, remediation — is documented. Reportable breaches are notified to the Data Protection Supervisor as required by the Zambia Data Protection Act No. 3 of 2021.

9. Policy ownership and review

This policy is owned by the system operator's IT lead and reviewed at least annually, or on any material change to the System, its processors, or applicable law. The version and effective date above always reflect the current policy.

Checking database…