Chrono Wise Production software. Dakar.

Public sector & institutions

Designed not to hold the data.

The question is not how we protect your sensitive data. It is why our system does not hold any.

A concrete example, in service

For an HR consultancy we built a job-weighting module. The exercise starts from the client’s payroll file: salaries, named individuals, the organisation’s most sensitive document.

  1. 01

    The file never leaves the device

    The workbook is parsed in the browser. It is never uploaded. It reaches no server, so there is no backup, no log, no subprocessor.

  2. 02

    Only one column is read

    The job titles. Names and salaries are not filtered out after reading — they are never read.

  3. 03

    What is kept is a count

    "This organisation has n occurrences of this title." Nothing else is persisted.

  4. 04

    The client view returns no names

    Title, expected, received, remaining, status, history. Individual tracking is impossible by construction — a cost we accepted.

The answer to "where is our salary data stored in your system?" is: nowhere. No privacy policy can match that answer, because a policy describes an intention and an architecture describes a constraint.

See the full architecture

What we can document

Auditable security model

Row-level policies, isolated authorization functions reviewed one by one, an explicit role model. Access control is readable, not scattered through application code.

WCAG 2.1 AA accessibility

Contrast, full keyboard navigation, semantic structure, reduced-motion preferences respected. A procurement requirement as much as a principle.

Delivery methodology

Written scope, visible weekly deliveries, versioned and reversible database migrations, handover documentation.

Reversibility and handover

The code, the database and the access are yours. We document third-party takeover at delivery, not at departure.

Decision traceability

Override justifications are persisted, timestamped and attributed. A later audit can reconstruct who approved what, and on what grounds.

Service continuity

Automatic failure alerts, scheduled backups, client-side error capture with a user-facing reference code.

Capability dossier

A formal document made to circulate internally: legal identity, methodology, data posture, accessibility, references. It carries the named personnel that procurement procedures require.

In preparation. Available on request by email.

Request the dossier

Procurement correspondence

For consultations, requests for information and administrative documents:

chronowiseai@gmail.com

Operator
UNIVR 360
Registered office
9 rue Félix Faure, Dakar, Sénégal
NINEA
007377478 2A2
RCCM
SN-DKR-2019-B-15512

A formal discussion?

We can attend a scoping meeting or respond in writing to a request for information.