Jueni Afrika Limited — Security & trust overview (draft for procurement)
================================================================================
Document version: 0.1 (2026-03-28)
Status: DRAFT — for discussion with your security and legal teams. Final terms,
policies, and architecture details are defined in executed agreements and
counsel-reviewed documents. Not a warranty or certification.

Contact: hello@jueniafrika.com

1. ORGANISATION
---------------
Jueni Afrika Limited is a Kenyan technology company. JINA BIASHARA is our
enterprise operations and finance workspace. The product is in beta; features,
controls, and documentation evolve. Buyers should run their own diligence.

2. DATA & RESIDENCY (HIGH LEVEL)
--------------------------------
- Most commercial tiers are operated as Jueni-managed cloud services; exact
  regions, subprocessors, and data flows are specified in your order form,
  data processing agreement, and published policies once counsel-approved.
- Mbunifu Huru (sovereign deployment) is scoped per customer with sales and
  engineering; architecture and residency follow the agreed design — not a
  one-size public template.

3. ACCESS CONTROL
-----------------
- Role-based access and audit expectations are product direction; maturity
  increases by tier during beta. Your administrators should configure least
  privilege and review access periodically.

4. AI & HUMAN REVIEW
--------------------
- AI assists with drafting and organisation; high-stakes outputs should be
  reviewed by qualified humans in your organisation. Beta behaviour may vary;
  do not treat model output as legal, tax, or financial advice without review.

5. INCIDENT RESPONSE
--------------------
- We maintain internal processes for security issues. Customers should report
  suspected incidents to hello@jueniafrika.com with as much detail as possible.

6. COMPLIANCE FRAMING
---------------------
- Kenya-first context (e.g. KES, local business practice) is product direction.
  Specific regulatory attestations (e.g. sectoral compliance) require scoped
  contracts and evidence packs negotiated per deployment.

7. CHANGE LOG
-------------
- 0.1 — Initial downloadable summary for procurement conversations (draft).