Data Residency
StackJack assigns each organization one storage home. The storage-home contract tells you where StackJack's regional application stores keep the organization's operational data. It is not a promise…
Written By Christopher Scaminaci
Last updated 3 days ago
StackJack assigns each organization one storage home. The storage-home contract tells you where StackJack's regional application stores keep the organization's operational data. It is not a promise that every processor handles every request only in that region.
Available storage homes
Each active region has its own application database, Redis cache, Blob Storage account, and Key Vault. Regional hosts use those stores for tenant records, connector credential references and secrets, MCP clients, agents and runs, usage records, support-ticket rows and ticket blobs, raw knowledge uploads, opt-in automation evaluation fixture/scenario blobs, and other tenant-scoped application state.
What the storage-home contract does not cover
Some features send selected data to service providers or shared services. Examples include identity, transactional email, payment processing, application telemetry, support AI, and tenant automation-agent prompts/tool exchanges/memory. Their processing location and retention are separate from the StackJack regional-store location.
The regional fixture store does not make later Anthropic processing regional. A fixture can contain canonical tool arguments and scrubbed response bodies, and extracted knowledge text or a live-test result can later enter a builder or agent prompt. Each provider processes and retains data under its own terms; see the processor matrix.
See External Data Processing for the processor-by- processor disclosure.
Fast decisions — an EU storage home means off until you opt in
StackJack's fast decisions features call TypeSafe AI, a second AI vendor hosted outside the European Union. If your storage home is in the EU, every one of those features — decision steps, smart filters, smart tool search, support drafting and builder assistance — is off for your organization until an administrator turns it on, and nothing is sent to that vendor before then. Each feature simply behaves the way it did before the capability existed. Organizations with a United States storage home have no such switch and use the features by default. The control, the disclosure wording and what happens when you turn it back off are in Fast Decisions and Your Own TypeSafe Key.
Cross-region directory record
StackJack can keep a small cross-region directory record so signup and sign-in can route an account to its home region. That record contains routing and identity metadata such as the owner email, account identifiers, home region, and lifecycle status. It does not contain connector credentials, ticket conversations, agent runs, or usage history.
Organization deletion marks this record deprovisioned instead of removing the routing and audit evidence entirely. A region move updates it to the destination home.
Moving between storage homes
An organization can be moved to another region. During a successful move, StackJack copies the in-scope tenant data to the destination regional stores, verifies it, and scrubs the old regional source stores. The source retains the technical migration record needed for verification and audit.
This move changes the StackJack storage home. It does not by itself relocate or delete data already handled under an external provider's terms.
Related pages
Still need help? Ask the team