All features

Decide and assign

AI use policy: from template to published version

A policy kept in a loose document leaves no record of which version applies or who has read it.

What it is for

Alethexis turns your AI use policy into a document with a lifecycle: it starts from a template for your sector, is edited section by section, goes through review, has its approval recorded and is published by the Owner. Each publication is a new version, and earlier ones are kept.

Your internal policy ready to publish, covering BYOAI and shadow AI. Generated as a PDF to circulate; the acknowledgement panel records who has confirmed reading it.

The policy is an internal methodological control: it sets out your internal rules on the use of AI and keeps a record of how it was circulated. It does not replace legal advice.

How it works

Start from a template for your sector

The platform creates the first version with starting text for your sector. Everything is editable: scope and definitions, acceptable and prohibited uses, BYOAI rules, shadow AI prevention, human oversight, incident procedure, training and review schedule.

A draft to review before publishing

While you edit, you can download a draft PDF with a “BORRADOR” (draft) watermark to review internally. The policy cannot be published with empty sections: each one needs minimum content.

Review and recorded approval

The policy moves from draft to review, from review to approval recorded, and then to published. The Owner or the AI Officer records the approval; only the Owner publishes. Each step is kept in the approval history with the person, their role and the date.

Publication with a hash

On publication the final PDF is generated, the platform records the SHA-256 integrity hash of the file as it is downloaded and adds it to the organisation's evidence. Whoever publishes ticks the section's closing statement.

Staff acknowledgements

Each member acknowledges the current version from the section itself, and the block shows how many have done so, for example “4 of 6 members have acknowledged it”. A new version is acknowledged afresh; earlier acknowledgements are kept.

What you get

  • Policy PDF with a SHA-256 hash

    An A4 document with a cover page, table of contents, the policy sections and the approval history recorded up to the moment it was generated. Annex A lists the active AI systems in the inventory (VIS-1) and Annex B those classified as P5 or P6 in VIS-2, levels of Alethexis's internal taxonomy, not the AI Act's nomenclature.

  • Acknowledgement record

    How many members have acknowledged the current version, and the date of each acknowledgement, in the platform.

Basis

The controls in the Alethexis catalogue that this feature helps to document, with their legal basis where they have one, and their nature.

  • IMInternal methodological control
IMInternal methodological controlM1-VIS-033

Foundation acceptable use policy for AI

Publish a first (Foundation) version of the acceptable use policy for AI: which tools are permitted, internal prohibitions, data that must not be entered into external GPAI systems, and the incident channel. It is the basis on which Module 2 will build the full governance framework.

Legal basis

No direct basis in law.

IMInternal methodological controlM1-VIS-034

Internal communication of the governance programme

Inform the whole workforce that the programme exists, who the AI Officer is (if one has been appointed), which policies are current and where the incident channel is. A programme the workforce does not know about is unlikely to be applied.

Legal basis

No direct basis in law.

Data from the controls catalogue. The labels show the regulatory nature of each control; they are not a statement of compliance.

Available in

  • M1Visibility
  • M2Governance
  • M3High-Risk Ready

Modules build on each other: M2 includes everything in M1, and M3 includes M1 and M2.

FAQ

Who can publish the policy?
Only the Owner. Recording its approval beforehand falls to the Owner or the AI Officer.
Can I edit a policy that's already published?
A published version can't be edited: a new version is created instead. The previous one is kept as evidence.
How do I check that the PDF has not been modified?
Download the PDF, compute its SHA-256 and compare it with the recorded hash; any later modification of the file gives a different value. The hash is not printed inside the document, because a file cannot contain its own hash.
Do I need the inventory before drafting it?
You can draft it without an inventory, though it will be more generic. With the inventory (VIS-1) and classification (VIS-2) in place, the PDF annexes list your actual systems.

Try it with your own systems