SECURITY AND TRUST

Security you can read, not just be told about.

Every control on this page is built into the service and cannot be switched off by accident. We describe what each one does so that you can map it against your own obligations. We make no claims about standards.

ACCESS

Four layers on every request.

Every request is checked four times, and a single explicit deny overrides everything.

Every time someone opens, changes or exports a record, the service makes four checks. It confirms who the person is, then what their role permits, then how much of the organisation’s work that role is allowed to see: their own, their team’s, what has been shared with them, or everything. Finally it looks at the record itself, which can carry its own allow and deny rules. Where those rules conflict, deny wins.

These decisions are made on the server, not only on the screen, so the rules do not depend on what an interface chooses to display.

CLASSIFICATION

Classification and clearance.

Sensitive information is hidden by default and shown only to people cleared to see it.

Records and individual fields can be classified by sensitivity, and people hold a clearance that sets what they may see. Someone can open a record and still not see a sensitive field inside it, because that field is hidden or masked for their clearance. The audit trail records what each person was cleared to see on the date they acted, so you can show later whether a given access was within their entitlement at the time.

IDENTIFIERS

Protected identifiers.

Full values are revealed only with a permission and a stated reason, and every reveal is logged.

National and tax identifiers, passports, licences and similar details are encrypted and replaced by a token, so the rest of the system never handles the raw value. On screen, staff see a masked value. Revealing the full value requires a specific permission and a reason given at the time, and the reveal is recorded in the audit trail. Encryption keys can be rotated, and if protection is ever misconfigured, the service fails closed and withholds the value rather than exposing it.

EMERGENCY ACCESS

Emergency and temporary access.

Access can be raised in an emergency or for a short time, but it always expires and is always recorded.

Real work sometimes needs access that a person’s role does not normally allow, and the service handles those cases deliberately, not by loosening permissions informally. It supports break-glass access for emergencies, requests that go through an approval workflow, scheduled access, and just-in-time access. All of them are time-limited and end automatically. Approving access is a permission in its own right, with a higher tier for the highest clearance. Delegation lets a colleague cover for someone on leave, within a ceiling tied to clearance so that cover cannot be used to reach beyond a set level.

AUDIT

A record that proves itself.

Each audit entry includes the one before it, so any edit or deletion breaks the chain.

The audit trail covers every security-relevant event: sign-ins and refusals, reads and changes, exports, field reveals, elevated access and delegation, consents, privacy requests, breaches, and changes to configuration and classification. Each entry carries the fingerprint of the entry before it, so altering or removing an earlier entry breaks the chain, and an integrity check shows exactly where.

If the audit entry cannot be written, the action itself is rolled back, so nothing happens without a record. Exports are permission-gated and audited like everything else.

Before: every link intact
  1. 1Signed inf101479852Intact
  2. 2Opened matter M-1042bfa7bcbce0Intact
  3. 3Revealed identifier. Reason: identity check35ec21c707Intact
  4. 4Moved stage from Intake to Review67afb9c08bIntact
  5. 5Exported report R-17ade3f2f41dIntact
  6. 6Signed in86dc2c9e88Intact
After editing entry 3: entries 3 to 6 fail
  1. 1Signed inf101479852Intact
  2. 2Opened matter M-1042bfa7bcbce0Intact
  3. 3Revealed identifier. Reason: none given0646f1d3d0Broken
  4. 4Moved stage from Intake to Reviewc6b0703831Broken
  5. 5Exported report R-175935175259Broken
  6. 6Signed in86dcd312abBroken

Each audit entry includes the fingerprint of the one before it, so changing one entry changes every fingerprint after it, and the integrity check shows exactly where the chain broke.

PRIVACY

Privacy operations.

Consent, requests, breaches and assessments are managed in one place.

The service gives privacy teams the working tools they need. Consent is recorded when it is granted and when it is withdrawn. Requests for access, correction, deletion and portability are tracked from receipt to completion, whether they arrive by email, through the portal, by phone or by letter. A breach log and privacy impact assessments sit alongside them, and the security officer and the privacy officer are notified of key events in the app and by email.

RETENTION

Retention and lawful disposal.

Records are kept for as long as the rules require, never disposed of under a hold, and disposal leaves proof.

Retention periods are set by jurisdiction and document type, with clocks that show how long a record must be kept. Where more than one rule applies, the longest wins. A legal hold overrides disposal, so a record under hold cannot be destroyed whatever its clock says.

Disposal follows separation of duties: it is carried out by a dedicated role and needs a second person to authorise it, and a series of checks must pass before anything is destroyed. Afterwards the service keeps a fingerprint of what was destroyed and issues a disposal certificate, so you can demonstrate later what was disposed of and that it was done properly.

PORTAL

The portal is a separate trust domain.

Clients use a portal of their own, distinct from the staff application.

Clients sign in to a different application, on a different route, from staff. The portal’s code is mechanically prevented from using staff code, and a staff session is refused there, so a change on one side cannot quietly reach the other. What a client can see is based on their relationship to the business record.

SERVICE

How the service is run.

Alaflow is delivered as a service. Questions about where data is held and how the service is run are best answered in a conversation, and we are glad to go through them with you.

Talk to us