Skip to main content
Privacy and data

Copying AI Governance text to your own storage

AI Governance keeps the AI text your people send and receive (the prompts and replies of the tools it watches) for the keep time your organization chose. An extra copy is a second, verified copy of…

Written By Christopher Scaminaci

Last updated 4 days ago

At a glance

  • What it does: keeps an extra, verified copy of your AI text and your records in storage you own.
  • Plan: every plan. Your own storage is free. The Free plan stores no text, so on Free a storage holds records only.
  • Who: an Administrator.
  • Where: AI Governance → Privacy and data → Storage archive. Connect your storage adds the first one; Add storage at the top of the page adds another. Each storage has its own card with its state and warnings.
  • Needs: a storage account of your own.

What an extra copy is

AI Governance keeps the AI text your people send and receive (the prompts and replies of the tools it watches) for the keep time your organization chose. An extra copy is a second, verified copy of that text in storage you own: Azure Blob Storage, Amazon S3, an S3-compatible store (Wasabi, Backblaze B2, MinIO), Google Cloud Storage or an SFTP server. Your records are copied there too: the organization's report packs, and the audit trail when the storage belongs to your own organization. The audit trail is one record for your whole account, so it follows the storage of your own organization. It is part of every plan, at no charge.

StackJack copies on a schedule (about every 15 minutes while there is something to copy), writes each item once, under its own name, and then checks that your storage holds exactly the bytes StackJack sent, by size and by hash. Each run also writes one small manifest file that lists what was verified. If a copy fails, StackJack tries again later, and the storage's card says what is wrong.

StackJack never deletes or overwrites your files. You give it permission to create and read only.

Two things to know before you rely on it. The page says both beside the cards, under Where your text goes:

  • Where it lives is your choice, and our regional promise does not follow it. You choose where this storage is. StackJack's promise to keep AI Governance data in your StackJack region does not cover it.
  • The copies are encrypted, and only StackJack can open them. The copies are encrypted, and only StackJack can open them. If your StackJack account is deleted, no one can open them again. To keep a readable copy, use AI Governance's exports.

StackJack keeps its own copy until its keep time ends. An extra copy does not shorten that and does not lengthen it. If StackJack's keep time ends for an item before your copy of it is verified (for example because your storage was unreachable for weeks), StackJack still deletes its own copy, counts the item on the storage's card as lost, and alerts you at half and at 80 percent of the keep time. A short keep time together with a storage that keeps failing therefore loses text, which is why those warnings matter. (The warnings start when copying starts: while StackJack has copies switched off for everyone, nothing is warned about, but items the keep time removes are still counted.) An extra copy does not reduce the stored-text figure on your bill: StackJack still holds its own copy until its keep time. The panel What your stored text costs at the top of the page shows what you store with StackJack and what it costs; the Billing page shows the price. StackJack keeps its own copy of your records for six years.

You can go further, on every plan. You can make one storage your main store: StackJack then deletes its own copy of the text once it has proven the text is in your storage, instead of keeping it until the keep time ends. A main store cannot be combined with extra copies. See Using your own storage as the main store.

Connect your storage

On Storage archive, select Connect your storage (or Add storage at the top of the page once you have one). An organization can have two extra copies. The panel has four numbered steps:

  1. Choose the kind: Azure Blob Storage, Amazon S3, S3-compatible storage, Google Cloud Storage or SFTP server.

  2. Say where it is and how StackJack signs in: a name that only you see, the place (the folder, or the base directory on SFTP) and the sign-in. The step shows What to allow in your storage for the kind and the sign-in you chose, ready to copy. StackJack keeps the secret in its vault and never shows it again.

  3. Test it: select Save and test. StackJack saves the storage, then tests it. The Test shows four lines, each with its word (Passed, Failed, Waiting, Not known or Not run):

    • Sign in, with the sign-in you entered.
    • Write a test file, a small file that holds no customer data.
    • Read it back: the file must come back exactly as it was written.
    • Try to overwrite it: the storage must refuse a second write to the same name.

    If a line fails, the step says what to fix for your kind of storage, and Test again runs it again. While StackJack has copies switched off, the storage is saved and the Test runs once they are on.

  4. Choose how to use it: opens once the Test passes. The two cards, Main store and Extra copy, say what each costs, what happens to your records and what happens if the storage is lost. Select Use as an extra copy. (A storage whose Test shows that it allows an overwrite can still be an extra copy; it cannot be the main store.)

How "create-only" is kept differs by kind, and step 2 shows the sentence for yours:

KindHow an overwrite is prevented
Azure Blob StorageAzure has no permission that refuses an overwrite. StackJack writes each item only if nothing is at its name, and the Test checks that your storage honors this.
Amazon S3The policy below makes AWS refuse any write that could overwrite an item.
Google Cloud StorageThe Storage Object Creator role cannot overwrite an item.
S3-compatible storeChecked before every write: StackJack looks that nothing is already at the name. (A server that proves it refuses an overwrite is still checked first; the check is the guarantee.)
SFTPChecked before every write: StackJack checks that the final name does not exist before it uploads, and again before it renames the finished temporary file into place.

For each kind you give StackJack the smallest permission it needs. No template below grants a delete, and the read right is there only so StackJack can check what it wrote.

Azure Blob Storage

Either of two ways of signing in.

  • A shared access signature (SAS) link for the container: create it with the permissions Read, Add, Create and Write and no Delete, with an expiry you can live with, and paste the whole link. StackJack alerts you 14 days before it expires, and the card's Sign-in details say when it expires. Rotate it on the storage's card before it does.

  • A service principal (Entra application): assign it a custom role at the container that has only these data actions, and give StackJack the directory (tenant) id, the application (client) id and a client secret:

    • Microsoft.Storage/storageAccounts/blobServices/containers/blobs/read
    • Microsoft.Storage/storageAccounts/blobServices/containers/blobs/write
    • Microsoft.Storage/storageAccounts/blobServices/containers/blobs/add/action

    Step 2 shows the role definition ready to paste, with your account and container filled in.

Amazon S3

Give StackJack an access key of an IAM user (or use the role option below) with this permissions policy on the bucket folder. Replace <bucket> and <folder>. It allows s3:PutObject only when the request carries the If-None-Match header (which every StackJack write does), so S3 itself refuses to overwrite, and s3:GetObject for the read-back. It allows no delete and no list.

{
  "Version": "2012-10-17",
  "Statement": [
    {
      "Sid": "StackJackCreateOnlyWrite",
      "Effect": "Allow",
      "Action": "s3:PutObject",
      "Resource": "arn:aws:s3:::<bucket>/<folder>/*",
      "Condition": { "Null": { "s3:if-none-match": "false" } }
    },
    {
      "Sid": "StackJackReadBack",
      "Effect": "Allow",
      "Action": "s3:GetObject",
      "Resource": "arn:aws:s3:::<bucket>/<folder>/*"
    }
  ]
}

The role option (no key to store). If StackJack has switched it on for your region, step 2 offers AWS role (no stored key). After you save the storage, its card shows StackJack's AWS account, an external ID made for this storage, the trust policy and the permissions policy above, ready to paste. Create a role in your own AWS account with them, enter the role's ARN on the card and select Save role; StackJack tests it as soon as you save it. The external ID is made by StackJack for this storage, so another StackJack customer cannot use your role. A role in StackJack's own AWS account is refused.

An S3-compatible store (Wasabi, Backblaze B2, MinIO)

Give StackJack an access key with permission to create and read objects under the folder, and no delete. Use your store's own policy tool; the documents differ from store to store. Enter the store's address (an https:// name, no path), the bucket, the region the store signs for and the folder.

The access key ID can be any key ID your store gives you (1 to 128 characters, no spaces); it does not have to start with AKIA. If your store reports a checksum (an ETag) that is not the item's own MD5, for example for an encrypted object, the Test says that your storage returned a file whose checksum StackJack could not match to what it sent. StackJack cannot use that store to verify a copy, so the storage stays on Needs attention. Contact support.

Google Cloud Storage

Create a service account, grant it these two roles on the bucket and nothing else, and paste its JSON key (StackJack reads the project and the service-account address from the key):

  • Storage Object Creator (create only: Google refuses to replace an object when the account has no delete permission, and this role has none).
  • Storage Object Viewer (so StackJack can read back what it wrote).

SFTP

Give the account write and read on the base directory (list, create files, read files) and no delete. Sign in with a password or a private key (with its passphrase, if it has one). A private key is chosen as a file in step 2 (an OpenSSH or PEM key, up to 16 KB), never typed or pasted: the browser does not show the key, and StackJack reads the file on its server.

  • On some SFTP servers a rename needs one more directory right. StackJack uploads each item under a temporary name and renames it into place once the upload is complete. If the Test says that your server refused to rename a file StackJack just wrote, grant the right your server needs to rename a file StackJack itself just wrote. StackJack still never deletes or overwrites a file.
  • The first Test shows you the server's key. Check that it is your server's, and select Confirm this key; StackJack then pins it and refuses to talk to a server that later shows a different key (the card says so). You can also enter the fingerprint in step 2.
  • The server must be reachable from the internet at a public address. A storage on a private address cannot be reached.

The Test, and what StackJack leaves behind

The Test writes one small file named with a random id under stackjack-archive-test/ inside your folder, reads it back, compares it, and tries to write it a second time to learn whether your storage refuses an overwrite (it only ever repeats the same bytes to its own probe file). The file says it holds no customer data and that you may delete it.

What StackJack leaves behind in your storage:

  • the copies of your items, under <folder>/<account id>/<organization id>/<day>/<item id>, and the run manifests under <folder>/<account id>/<organization id>/manifests/<day>/<run id>.json. These are yours. When you remove the storage, they stay;
  • your records, under <folder>/<account id>/<organization id>/records/: the organization's report packs, and, in a storage of your own organization, the audit trail as one file per day;
  • the Test files under stackjack-archive-test/;
  • on SFTP, now and then a temporary .sjpart- file left by an interrupted upload. StackJack never deletes it (it never deletes anything); you may.

The storage card

Each storage has one card. It shows the role (Extra copy or Main store), one state, one sentence that says what is happening, and three figures: In your storage, Still to copy and Oldest text not yet in your storage, with a bar of the keep time and its two warning days. A count of nothing says None or Nothing yet. The card also says what goes into the storage and how many of your records are in it.

The buttons on the card are Test, Rotate the credential when the storage needs attention, Resume after a pause, and Use as main store when it can be the main store. The menu (the ... button) holds Rename, Rotate the credential, Pause, Use as main store and Remove; an item that cannot be used now says why. More counts and Sign-in details open at the foot of the card.

The states of an extra copy:

StateWhat it means
Needs attentionYour storage refuses StackJack, for example a refused credential, a missing permission, an unknown server key or a refused rename. The card says what to fix. Copies are stopped until it is fixed and tested.
Close to the keep timeSome text that is not in your storage yet is past half of StackJack's keep time.
Having troubleCopies fail for now, and StackJack is trying again.
PausedSomeone paused the storage. Nothing is copied to it until it is resumed.
Not tested yetCopies start after a Test passes.
Catching upSome text has waited a day or more to be copied. Copies continue on a schedule.
Up to dateCopies run on a schedule, and nothing has waited long.

What the warnings mean

  • Alerts at half and at 80 percent of the keep time. The oldest item not yet verified in your storage has been waiting for that share of your keep time. At the end of the keep time StackJack's own copy is deleted. Fix what the card says (a credential that expired, a permission, a full bucket) before the next warning. The panel Keep times and what happens when shows these days for your own keep time.
  • Lost so far. The count of items whose keep time ended before your copy was verified. They are gone from both places.
  • Already in your storage with different content (under More counts). The count of items whose name already held something else. StackJack never overwrites it; the item is recorded as a conflict and the storage keeps going.

Removing a storage

Remove is in the storage's menu, and it asks first. Type the name of the storage to confirm. StackJack stops copying, and deletes the credential it holds for the storage. The copies already in your storage stay there, and so do the Test files and, on SFTP, any temporary .sjpart- file. A removed storage stays on the page as a quiet card for 30 days.

A storage that holds records StackJack no longer keeps (with a main store) asks for the phrase REMOVE STORAGE instead. See Using your own storage as the main store.

How fast it is

Object storage (Azure, S3, Google and the S3-compatible stores) keeps up with any organization. SFTP is slower: StackJack copies about 3 to 6 items a second to one SFTP server (about 10,000 to 20,000 an hour), because every item costs several round trips over at most two connections and is checked before it is written. A 100-person organization of heavy coding-agent users can produce up to about 14 items a second, so its SFTP backlog would grow during the working day. Such an organization should use object storage.

Allow-listing StackJack's addresses

If your storage allows access only from known addresses, ask support for StackJack's current addresses. StackJack gives them out by support ticket only; they are not published.

If you leave

The copies are unreadable without StackJack. If your StackJack account is deleted, no one can open them again. To keep a readable copy, use AI Governance's exports before you leave.