Operating Guide: Approve a Private AI Use Case

Approve AI by examining information, decision consequence, evidence, provider behaviour, human authority and reversibility.

The answer

Approve a use case, not an impressive demo. The same model may be acceptable for public research and unacceptable for analysing private correspondence. Write one sentence: “The system will use X information to produce Y output for Z person, who will use it to make or support Q decision.

Approve a use case, not an impressive demo. The same model may be acceptable for public research and unacceptable for analysing private correspondence.

Step 1 — state the job

Write one sentence: “The system will use X information to produce Y output for Z person, who will use it to make or support Q decision.” If the sentence cannot be completed, the use case is not defined.

Step 2 — classify the inputs

- Public or licensed information.

- Internal operational information.

- Private personal, legal, financial, health or relationship information.

- Secrets, credentials, authentication data or privileged material.

The final class should usually be excluded unless a deliberately controlled architecture and legal basis exist.

Step 3 — set the consequence

Name the worst plausible outcome if the model is wrong, reveals data or is manipulated. Distinguish reversible inconvenience from money movement, legal position, personal safety, reputation or authority change.

Step 4 — inspect the provider chain

- Where inference and storage occur.

- Whether inputs or outputs train models.

- Retention and deletion behaviour.

- Subprocessors and jurisdiction.

- Administrative access and incident notification.

Step 5 — design human authority

Name the person who checks output, the evidence they see, the action the system cannot take and the escalation rule for uncertainty. “Human in the loop” is meaningless unless the human has time, competence and power to reject.

Step 6 — preserve evidence

For consequential use, retain source references, model/version, relevant prompt or configuration, output, human edits and final decision. The record must let another expert reconstruct why the result was trusted.

Step 7 — prove exit

Test data export, deletion, provider disablement and the manual fallback. Approval without an exit path is dependency acquisition.

Approval card

Record owner, job, information class, consequence, provider, human control, evidence, prohibited actions, expiry date and shutdown method. Approve for a defined period, then review real performance—not promised capability.

Sources

  1. Swiss FDPIC — AI and data protectionSwiss FDPIC

    Primary authority

  2. Swiss FDPIC — Data protection impact assessmentSwiss FDPIC

    Legislation

  3. NIST — AI RMF Generative AI ProfileNIST

    Primary authority

Ross BelhommePartner, Svperior / Legal

Jonathan P. De Collibus

Jonathan co-founded Svperior in 2014 and leads its cyber practice. His work sits where adversarial pressure, technical architecture, and consequential decisions meet, with experience across clinical, financial, public-sector, and private-client systems where confidentiality, continuity, and technical correctness carry material consequences.

Cyber strategy / Adversarial assessment / Security architecture / Private systems

Need to apply this to a specific situation?

Send us the initial context. If the matter fits, we will respond directly.

Send private inquiry
Operating Guide: Approve a Private AI Use Case