Skip to main content
Prove it

Report packs, templates and verification

A report pack is a dated file that you hand to an auditor, an insurer, a client or a regulator. This page covers the four packs, how to request one, how anyone can check that StackJack issued it, and…

Written By Christopher Scaminaci

Last updated 3 days ago

A report pack is a dated file that you hand to an auditor, an insurer, a client or a regulator. This page covers the four packs, how to request one, how anyone can check that StackJack issued it, and the document templates on the same page. It also covers the settings the packs and templates are filled from.

At a glance

  • What it does: builds dated, write-once evidence packs and fills in document templates.
  • Plan: the privacy pack and the templates are on every plan, unsigned below Business. The auditor, insurer and per-client packs and the signature need Business or above.
  • Who: Administrator or Auditor requests and downloads packs and templates. Any governance role reads the page.
  • Where: AI Governance → Compliance → Report packs. The page checking a pack is public.
  • Needs: evidence, from the other pages. The packs list gaps instead of hiding them.

The four packs

A pack is a dated ZIP file: a PDF to read and CSV files with the underlying rows. Every pack states which sources it covers and lists the gaps. A gap is a source that was off, or a lane that dropped records. A pack never holds the text of a prompt or an answer, a matched value or a masked token. The per-client pack never names staff.

PackWhat it isPlan
Privacy packHow your organization handles staff data: notices, monitoring, access to records and data-subject requests. For a regulator or a works council.Every plan
Auditor packControls and the evidence behind them, mapped to SOC 2, ISO 27001 and ISO 42001. For an auditor.Business and above
Insurer packThe answers a cyber-insurance questionnaire asks about AI: inventory, policy, training, data-loss controls, monitoring and incidents.Business and above
Per-client packWhat AI use touched one client's data, which tools, and any incident that involved them. Never names staff. For the client.Business and above

Request a pack

  1. Open Compliance → Report packs.
  2. In Request a pack, choose the pack and the period.
  3. Request it. The status moves from Waiting to be built to Ready.
  4. Select Download.

Each pack shows its signature state and its fingerprint (SHA-256):

  • Signed. StackJack signed the pack.
  • Not signed (this plan does not sign). The pack was built on a plan below Business.
  • Not signed (the signing key was unavailable). Request it again later. The privacy pack never waits on signing.

If a pack fails, the page says why:

  • The pack was larger than the limit. Choose a shorter period.
  • The pack could not be built after several tries. Request it again.
  • The plan no longer includes this pack.

StackJack keeps the record of every issued pack, its fingerprint and its signature, for six years. It stores the pack's file write-once while it holds the file: six years, or 90 days when your own storage is a main store that runs and the file is proven there. After that the file is in your storage, under whatever protection you gave that storage. StackJack's copy is removed within two days.

Packs issued between 2026-11-15 and the move show "Stored without a write-once policy" until StackJack moves them into write-once storage, which happens on its own.

Where the file is

The pack list has a column Where the file is:

  • StackJack, with "Stored write-once until ": StackJack holds the file.
  • StackJack and your storage, with "StackJack keeps its copy until ": the copy in your storage is proven, and StackJack keeps its own copy until that day. Once the day has passed it says "StackJack may remove its copy from ".
  • In your storage, with the name of your storage: only your storage holds the file.

Before StackJack removes its copy of a pack file, it checks the file in your storage once more. If your storage lost it, StackJack writes it there again from its own copy. If your storage holds another file at that place, StackJack keeps its copy of the pack's file, and the storage's card on Storage archive counts the record as not written. If your storage does not answer, StackJack keeps the file and checks again later. A legal hold stops every removal. Without a main store of your own nothing changes.

While StackJack keeps less because your main store runs, the rail card What StackJack keeps says so. It is shown to Administrators and Auditors.

Download works the same for every row. For a file that is only in your storage, StackJack reads it from there and checks its fingerprint first. The row says "Reading the file from your storage", then:

  • From your storage. Checked against the fingerprint StackJack kept for this pack. The download has started.
  • The file in your storage does not match the fingerprint StackJack kept for this pack. StackJack did not download it.
  • StackJack could not read your storage. Select Try again, or Open Storage archive to check the storage.

A file in a storage that was removed has no Download button: StackJack can no longer read it, and it is still in that storage. The files are under <folder>/<account id>/<organization id>/records/packs/<year>/<pack id>.zip in your storage. See Using your own storage as the main store.

Check a pack

Anyone can check that StackJack issued a pack. Open the public check page, Check a report pack. Choose the pack's ZIP file, or paste its fingerprint. The page tells you whether StackJack issued it and whether its signature is genuine.

  • The file stays on your computer. The page works out the file's fingerprint in the browser and sends only that fingerprint (a SHA-256 hash).
  • A fingerprint that is not a whole fingerprint, and one no pack has, get the same answer. The page cannot be used to guess at packs.
  • For an offline check, the public signing keys are listed on the page.
  • StackJack keeps every pack's fingerprint for six years, so the check works for a file that comes from your storage too.
  • A pack issued from 2026-10-28 also carries a signature over the fingerprint of its ZIP file. A valid answer then means the file is the exact one that was signed.
  • A pack issued before that is marked "issued before ZIP signing". Its manifest signature is checked as before.
  • The details the page shows are the kind, the period, the issue date, your organization's name and the region. They come from the manifest StackJack signed. A pack whose signed manifest belongs to another pack does not verify.
  • A privacy pack that StackJack recovered after an interruption, at a time when signing was not available, is shown as "Not signed". The file is still the one that was issued.

If you see "Too many checks from this address. Try again later." wait and retry. If you see "The check could not be made right now. Try again in a few minutes.", try again.

Templates

Nine templates are prefilled from your organization's own settings. An Administrator or an Auditor can download each one as a document (Markdown) or a PDF:

  • a data-protection impact assessment,
  • a legitimate-interest assessment,
  • a works-council information pack,
  • staff notices for the EU and UK, New York, Connecticut, Delaware, New South Wales and Quebec.

The AI use policy template is separate. It is the starting text of the policy editor.

Your organization is the controller. Read every statement, complete what only you can answer and decide the outcome. A template never names a staff member.

Until StackJack's legal review approves a template, it starts with this line, on screen, in the document and in the PDF:

Template for your review. Not legal advice.

The second line tells you what to do:

Prepared from the organization's current AI Governance settings. Check and complete it before use.

Evidence settings

The Evidence settings panel holds the facts the templates and packs are filled from, such as the accountable executive and their title, the policy owner, the default client notice period in hours, the dates and references of your impact assessment and legitimate-interest assessment, and whether the NIS2 directive applies. Only an Administrator changes them. Client notice periods records how many hours a client's contract gives you to tell them about an incident that involves them.

What you will see

  • A list of the packs you requested, newest first.
  • In the readiness view, the pack that holds each piece of evidence.

Troubleshooting

What you seeWhat to check
A pack stays "Waiting to be built"Select Refresh. If it stays, request it again.
"The plan no longer includes this pack."The pack needs Business.
A pack is marked "Not signed"See the signature states above.
"StackJack could not start the download. Reload the page and try again."Reload the page and select Download again.
"StackJack could not read" your storageSelect Try again in a few minutes. Check the storage on Storage archive.
The check page does not know the packCheck that you chose the ZIP file exactly as StackJack gave it to you. A changed file has a different fingerprint.
A template has a draft lineExpected until legal review. Check and complete it before use.

Next