Skip to main content
Privacy and data

Using your own storage as the main store

By default StackJack keeps the text of the AI prompts and answers it records (for the keep time you chose) in its own storage. With the main store, the text goes to storage you own instead. StackJack…

Written By Christopher Scaminaci

Last updated 2 days ago

By default StackJack keeps the text of the AI prompts and answers it records (for the keep time you chose) in its own storage. With the main store, the text goes to storage you own instead. StackJack proves that each piece of text is in your storage, and then deletes its own copy. StackJack keeps facts and findings, and nothing else of the text. Your records follow the main store too: the organization's report packs are written to your storage, and so is the audit trail when the storage belongs to your own organization (the audit trail is one record for your whole account).

At a glance

  • What it does: keeps your AI text only in your own storage after StackJack proves it is there.
  • Plan: every plan, at no charge. The Free plan stores no text, so on Free the storage holds records only: the audit trail and the report packs.
  • Who: an Administrator.
  • Where: AI Governance → Privacy and data → Storage archive: step 4 of Connect your storage, or Use as main store on a storage's card.

Your own storage is free on every plan. Text in your own storage is not stored with StackJack, so it is not charged; text stored with StackJack is charged for each GB on Pro and Business, and the Billing page shows the price. The main store uses the same kinds of storage as an extra copy (Azure Blob Storage, Amazon S3, an S3-compatible store, Google Cloud Storage or an SFTP server), the same create-only permissions and the same Test. Copying AI Governance text to your own storage describes them.

What you need to know first

  • If your storage is lost, that text is lost. After StackJack has proven a piece of text in your storage it deletes its own copy. StackJack keeps facts and findings only. Back up your storage the way you back up anything you cannot lose.
  • 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 text is encrypted, and only StackJack can open it. Your storage holds the encrypted text, byte for byte as StackJack made it. If your StackJack account is deleted, no one can open it again. To keep a readable copy, use AI Governance's exports before you leave.
  • StackJack never deletes or overwrites your files. You give it permission to create and read, and nothing more.
  • A main store cannot be combined with extra copies. An organization has one main store, or extra copies, never both.

Set it up

  1. On Storage archive, select Connect your storage. Steps 1 to 3 are the same as for an extra copy: choose the kind, say where it is and how StackJack signs in, then select Save and test. The Test must pass, and its fourth line must say StackJack cannot overwrite a file.
  2. Step 4, Choose how to use it, shows two cards: Main store and Extra copy. Each says what it costs, what happens to your records and what happens if the storage is lost. Choose Main store and select Use as main store.
  3. A dialog asks Use (your storage) as your main store? It says what happens to your text and to your records. Type USE AS MAIN STORE and select Use as main store.

A storage you connected earlier can become the main store too: select Use as main store on its card, or in its menu (the ... button), and confirm in the same dialog.

The Main store card cannot be chosen, and says why, while:

  • StackJack has the main store switched off on its side;
  • the Test has not shown that the storage refuses to overwrite a file;
  • the organization already has a main store;
  • another storage of the organization is connected. Remove it first.

The storage card

Each storage has one card on Storage archive. It shows the role (Main store or Extra copy), one state, one sentence that says what is happening to your text right now, and three figures. For a main store that runs, the figures are:

  • In your storage: how many items are in your storage, and how many of these are kept only there.
  • Waiting at StackJack: new text in StackJack's buffer, waiting to be proven in your storage, against the size of the buffer.
  • Older text still to copy: text from before the main store was on that is not in your storage yet, and how old the oldest of it is. It counts the stored originals too: each AI record as it arrived, which StackJack keeps beside the text it read from it.

For a main store that is chosen and not running, the last two are Still to copy and Oldest text not yet in your storage, with a bar of the keep time and its two warning days.

Under the figures the card says what to do when there is something to do, and warns you when text is close to the end of the keep time. The foot of the card says StackJack never deletes or overwrites your files. and when the last Test ran. More counts opens the other counts, such as the last good copy, conflicts and items removed by the keep time before they were copied. Sign-in details says how StackJack signs in.

The states, in the order in which they win when more than one is true:

StateWhat it means
Text capture pausedStackJack's buffer for your storage is full. New text is not stored until it drains. See below.
Needs attentionYour storage refuses StackJack. The card says what to fix. New text waits at StackJack until the storage 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 troubleWrites fail for now, and StackJack is trying again. New text waits at StackJack until a write works.
Chosen, not runningYou chose this storage, and StackJack has the main store switched off on its side. Your text is copied here on a schedule, and StackJack keeps its own copy until the main store runs.
PausedSomeone paused the storage. Nothing is written or copied to it, and StackJack keeps your text meanwhile. After you resume it, StackJack deletes its copy of each item once it is proven there.
Not tested yetWriting starts after the first Test that passes.
Catching upNew text goes straight to your storage. Older text is still being copied, and StackJack deletes its copy of each older item once it is proven in your storage.
Up to dateNew text goes straight to your storage, and nothing older is still to copy.

StackJack alerts your administrators when the oldest text that is not in your storage yet reaches half of the keep time, and again at 80 percent. At the end of the keep time StackJack deletes its own copy whether or not the text reached your storage, and the card counts what was lost. The panel Keep times and what happens when on the same page shows these days for your own keep time.

What StackJack keeps and what it deletes

StackJack keepsStackJack deletes
Facts and findingsYes: the record that a call happened, who and which tool, the findings, the counts
The text of prompts and answersOnly until it is proven in your storageIts own copy, right after the proof
An index of where each piece livesYes (a pointer, not the text)At the end of your keep time
The audit trail, when this is the main store of your own organizationThe last 400 daysOlder days, once each day is proven in your storage
Report pack files90 days after the pack was madeAfter 90 days, the file, once it is proven in your storage
The daily integrity record of the audit trail, and each report pack's fingerprint6 years
Your files in your storageNever. StackJack creates and reads; it does not delete or overwrite.

The proof is a check of the size and the hash of what is in your storage. If a write fails, StackJack tries again later (after 30 seconds, then 2 minutes, then 10 minutes, then every 30 minutes) and keeps its copy until a write is proven. A write that finds different bytes already at that name does not overwrite them; StackJack keeps the text.

Text from before the main store was on is copied to your storage on a schedule, and so are the stored originals (each AI record as it arrived). An extra copy never gets the stored originals; a main store gets them like the rest of your text, so once they are proven there StackJack keeps none of them. Before StackJack deletes its copy of an older item, it checks the item in your storage once more, and writes it again if it is missing. If your storage holds a different file at that place, StackJack does not overwrite it and keeps its own copy. While the main store is chosen and not running, paused, needs attention or is not tested yet, or while its text capture is paused, StackJack keeps its copy, and that copy counts as stored with StackJack.

Records work the same way. Before StackJack removes its copy of a day of the audit trail or of a report pack file, it checks again that the record is in your storage. If your storage lost it, StackJack writes it there again from its own copy. If your storage holds another file where a day belongs, or does not answer, StackJack does not remove that day or any later day, and the storage card says that the trim is held and why. If it holds another file where a pack belongs, StackJack keeps its copy of that pack's file, and the card counts the record as not written. If it does not answer, StackJack keeps the pack's file and checks again later. A legal hold stops every removal.

The audit trail is one record for your whole account, so it follows the main store of your own organization. A report pack follows the main store of its own organization.

What it costs

Text that goes to your storage does not count toward the stored-text figure of your bill or toward your stored text cap. That covers text that already lives in your storage and text still waiting in the buffer on its way there. The cap does not stop text that goes to your storage.

While the main store does not run (it is chosen and not running, or it is paused), new text is stored with StackJack, and it is charged like any text stored with StackJack. The cost panel says so: New text is stored with StackJack while the main store is not running.

Older text is stored with StackJack until StackJack deletes its copy, and until then it is charged like any text stored with StackJack. StackJack deletes its copy of an older item only after the item is proven in your storage, a batch at a time, so a large backlog takes a while. Once StackJack has deleted its copy of all your older text, a main store that runs pays nothing for stored text.

The panel What your stored text costs at the top of Storage archive shows what you store with StackJack and what it costs, beside your own storage. The Billing page shows the price.

If the buffer is full

StackJack holds new text only while it waits for your storage to confirm it. It holds a limited amount for each organization, and the card shows how much of the buffer is in use. If your storage is slow or down for long, the buffer fills. When it is full the card says Text capture paused:

Your storage has refused writes for too long. StackJack stopped storing new text for this organization. Facts and findings continue.

StackJack writes the waiting text first. Capture of new text starts again by itself when the buffer falls below 80 percent of its size. Your administrators get an alert when it fills. Nothing already in the buffer is lost. Fix what the card says (a credential that expired, a permission, a full bucket), then run the Test, and the buffer drains.

Reading the text

The content viewer and the exports read the text from your storage when it lives there. A read that does not get an answer says: Your storage did not answer. Try again in a minute. That says nothing about the text. If someone deleted the object in your storage, the text shows as missing. A data-subject export waits for your storage and tries again, rather than being made with pieces missing.

Reading always works while the storage is connected, whatever your plan and whatever StackJack's switch says, because that storage holds the only copy.

Older records are read the same way. On the Audit trail page, Show the day reads an older day from your storage. On Report packs, Download reads a pack file from your storage. StackJack checks each one against what it kept, and tells you when it does not match.

Erasing a person

Your text lives in your own storage. Erasing this person makes their text unreadable at once, but the unreadable ciphertext stays in your storage. StackJack does not delete files in your storage, so the encrypted files stay there; nobody, including StackJack, can read them. See Erasing a person.

If you change plan

Your own storage is on every plan, so a plan change does not turn the main store off. Text already in your storage stays there and stays readable here while the storage is connected. If you move to the Free plan, no new text is stored anywhere, because Free stores no text of prompts or answers; your storage then receives records only. Text stored before the move is still copied to your storage until its keep time ends.

Stop using it as the main store

Select Stop using as main store in the storage's menu. A dialog asks first; there is nothing to type. The storage becomes an extra copy:

  • New text is stored with StackJack again and copied to this storage on a schedule.
  • Text that was on its way to the storage is still written there, and then StackJack deletes its copy of it. StackJack deletes no other copy of its own.
  • Text already in this storage stays there, and StackJack reads it from there when you ask.
  • Your records are still copied to the storage, and StackJack removes no more of its own copies of them.

Removing the storage

Remove is in the storage's menu, and it asks first.

  • A storage that holds text StackJack no longer keeps cannot be removed by an administrator, because the removal would delete the only way to read that text. Contact support.
  • A storage that holds records StackJack no longer keeps asks you to type REMOVE STORAGE. The dialog says which records are only there. They stay in the storage, and StackJack can no longer read them for you after you remove it.
  • Any other storage asks you to type its name.

Related: Copying AI Governance text to your own storage, Capture levels and privacy, Privacy, notices and retention settings.