Skip to content

Terms

Clear scope before critical systems change.

These public terms set the working commercial boundary for Sufrone Technologies Limited. They are a launch draft: final terms, data-processing language, regulated-sector clauses, and liability wording still require founder and advocate review before production.

Last updated: 24 August 2026

01

Written agreement controls paid work

Public pages describe starting ranges and possible configurations, but paid work is governed by a signed proposal, statement of work, invoice, service agreement, or other accepted commercial document. Scope, exclusions, dependencies, responsibilities, fees, payment, timelines and acceptance criteria must be agreed before delivery starts.

02

Assessment comes before prescription

The Sufrone Technology & Operations Assessment reviews the operating environment and produces the Sufrone Technology Health Report. A selected public technology or industry path records context only; it does not expose, preselect or activate the full implementation catalogue.

03

Self-registration creates a prospect workspace

Creating an account verifies access to the supplied email and creates a prospect workspace only. It does not prove authority over an existing client, activate products or hardware, approve commercial scope, begin billing, or grant production access. Sufrone may reconcile, suspend, merge, or reject duplicate or unauthorized registrations.

04

Cash and equipment rules

Hardware and equipment are 100% client-funded before procurement. Normal projects use 50% mobilisation, 30% progress and 20% acceptance milestones. Managed services are billed monthly in advance. Sufrone does not extend client credit for equipment, licences or third-party services.

05

Technology and provider boundaries stay visible

Advantage Engine modules, provider connectors, open-source platforms, commercial licences, cloud accounts and client-owned systems retain distinct ownership and operating boundaries. Third-party availability, usage, certification, licensing and provider charges are separately disclosed where applicable.

06

Production access requires safeguards

Before Sufrone handles production systems, the client and Sufrone must agree access control, backups, incident handling, offboarding, data processing duties, and who can approve risky changes.

07

Change and acceptance remain controlled

Material changes to scope, price, timeline, dependencies or acceptance require a written change request. Delivery is completed against agreed tests, customer acceptance, documentation and credential handover—not informal assumptions.

08

Fees and payment evidence

Quoted engineering fees, assessment fees, Engine deployment and managed-operation charges, Managed Technology tiers, taxes, provider costs, payment milestones, refund boundaries and due dates must be stated in the accepted commercial document. Payment records require a captured bank, M-Pesa, Paystack, or approved manual reference.

09

Client responsibilities

Clients must provide accurate information, authorized access, timely approvals, responsible users, lawful data, and internal decision-makers. Delays in access, data, approvals, or third-party provider readiness can change timelines.

010

Offboarding and continuity

When a service ends, the offboarding path should cover final invoices, data export, credential handover, backup retention, system shutdown or transfer, outstanding support items, and records Sufrone must retain.

This page is not legal advice and does not replace a signed agreement. Final terms, privacy policy, data-processing language, regulated-sector clauses, and dispute/liability terms remain founder and advocate sign-off items before production launch.