Skip to main content
Security, Privacy & Data

External Data Processing

Your organization's storage home locates StackJack's regional application stores. Some features also send selected data to another service, or to a StackJack service that is shared across regions. A…

Written By Christopher Scaminaci

Last updated 3 days ago

Your organization's storage home locates StackJack's regional application stores. Some features also send selected data to another service, or to a StackJack service that is shared across regions. A feature that starts on a regional Portal, MCP, or automation-runner host does not keep that data regional once it is sent onward. This page lists the external services StackJack sends data to, what is sent, and when.

Processor matrix

Service and purposeData involved and whenWhere it is processed and how long it is kept
Microsoft Azure regional stores — core StackJack hostingTenant database rows, cached state, ticket and diagnostic blobs, raw knowledge-upload blobs, opt-in automation evaluation fixture and scenario blobs, and tenant secrets are stored in the organization's assigned region. Evaluation fixtures can contain canonical tool arguments and scrubbed JSON read-response bodies or write-response skeletons; a non-JSON body can remain verbatim after the fixture scrubber runs.US home: East US for the application, cache, blob storage and key vault, and Central US (primary) with a West US 2 replica for the database. EU home: Sweden Central. Retention rules vary by feature; see Usage Data Retention and Customer Data & Privacy.
Twilio: AI Governance text alertsOnly for an organization that adds a text message channel to its AI Governance alerts, and only for a person who agreed to texts on their own phone. Twilio receives that person's mobile number and the text. An alert text carries the alert title, the severity and the organization name, with no link and no prompt text. A summary or test text carries the organization name and, for a summary, a count and the highest severity. Twilio also carries the one-time verification code text (six digits, valid for 10 minutes), the enrollment confirmation text, and the STOP and HELP replies a person sends. If an organization connects its own Twilio account, its texts are sent through that account instead of StackJack's, using credentials stored in the organization's region key vault.Twilio processes and retains these texts and replies under its own terms. For a text sent through an organization's own Twilio account, that account's terms apply and Twilio bills the organization directly. StackJack's regional store keeps the number in the person's consent record, and keeps one ledger row per text with the masked last four digits, a hash of the number, the status and the cost. The ledger never holds the message text.
SendGrid — transactional email delivery and invite-delivery diagnosticsWhen StackJack sends tenant, support, partner-provisioning, billing, migration, or deletion email, it transmits the recipient address and name, the subject, the rendered plain-text and HTML content, embedded action links, and any reply-to or header metadata. A deletion-confirmation message contains the organization name, the expiry, and the full single-use confirmation link. The Team invite-delivery diagnostic also queries SendGrid Email Activity with a normalized recipient address and reads matching message subjects, delivery status, and last-event time.SendGrid processes and retains this email under its own terms.
Featurebase — support ticketing, product feedback, and changelog deliverySupport conversations are exchanged with Featurebase: ticket subject and body text, support replies (including internal notes drafted with AI assistance), and your contact identity (name, email, organization) are transmitted and stored there, and attachments submitted through the support widget are uploaded to it directly. A nightly directory sync also registers every active organization as a Featurebase company (name, organization identifiers, plan, region, billing customer ID, an estimated monthly spend figure, and the organization's creation date) and every active member as a contact (user ID — or email for an invited user who has not signed in yet — plus email, name, region, and organization ID), whether or not anyone ever contacts support. The support and feedback widget loads on every signed-in Portal page and sends a signed identity payload (user ID, email, name, profile picture, roles, and company) wherever it loads. Changelog publishing sends release-note content; StackJack always disables Featurebase's subscriber emails on publish.Featurebase processes and retains this data under its own terms.
Anthropic: support-AI research, drafting, and refinementThis research does not run automatically. Creating a ticket or replying to one starts no research run. StackJack's AI assistant, which may answer your conversation, is the next row. A run happens only when StackJack support staff deliberately start one (from the support console, a support-workflow action, or StackJack's operator tooling), or when a partner escalates a managed ticket. When a run does happen, StackJack sends the ticket subject and customer text plus selected evidence. Evidence can include tenant diagnostics, relevant product documents and past tickets, Sentry and Azure Monitor results, and billing context. Draft refinement can send the current draft, the support engineer's refinement instruction, distilled corrections or feedback, and supporting evidence.Anthropic processes and retains this data under its own terms. This is a StackJack support path, separate from your own automations' Anthropic workspace. If your organization chose to run StackJack's AI help on its own Azure Foundry, the run and the draft refinement go to that Foundry deployment instead of Anthropic (see the Azure Foundry row). If that deployment cannot serve the request, StackJack refuses it. It does not send the run to Anthropic or to your own Anthropic key in its place.
Anthropic: StackJack's AI assistant for support. This assistant always runs on Anthropic, also for an organization that runs StackJack's AI help on its own Azure Foundry.When you open or update a support conversation, or ask for help in StackJack's Discord, StackJack's AI assistant may read the conversation and answer it. Anthropic receives the conversation and what the assistant looks up to answer it: public StackJack documentation and platform status, and, for a conversation tied to your organization or a Discord member who verified by signing in, your organization's diagnostics and account details.Processed in the United States for every storage home, the EU included: the conversation passes through StackJack's US region and Anthropic. StackJack deletes its stored copy of the conversation text within 30 days, and deletes the assistant's Anthropic session 30 days after its last activity. Anthropic processes and retains this data under its own terms. This is a StackJack support path, separate from your own automations' Anthropic workspace.
Anthropic — automation builder, AI assist, and token countingWizard turns send the conversation history and latest user message, the current draft and readiness state, the plan-visible tool catalog and metadata, and—when available—recent run status, tool sequence, and cost. AI-assist sends either the automation description plus tool names or the full system prompt, depending on the requested suggestion. Token counting sends the selected model, full system prompt, and messages. The builder also runs live tool tests against your real connectors, and their results go to Anthropic. During an interview the model can execute eligible read-only tools against your live connector credentials — real systems, real data, capped per interview — and up to 4,000 characters of each raw result is placed into the conversation for later turns. So genuine ticket, asset, device, and client data from your own systems can reach Anthropic through the builder, not only text you typed. Write and destructive tools are never executed during an interview.StackJack picks where one wizard turn or AI-assist suggestion runs in a fixed order. First, your organization's own Azure Foundry, when it chose that for StackJack's AI help (see the Azure Foundry row). Second, your organization's own Anthropic key, when it has one (BYOK); the call then costs you zero credits. Third, StackJack's Anthropic key, billed in credits. A choice that cannot serve is refused and never moved down the list: if Foundry cannot answer, the call is not sent to your Anthropic key or to StackJack's, and if your own key cannot be read or Anthropic rejects it, the call is not sent to StackJack's key. Token counting is the one exception: it always uses StackJack's own Anthropic key, generates nothing, and costs no credits. Anthropic processes and retains this data under its own terms.
Anthropic — tenant automation agentsProvisioning sends the agent name, description, model and effort, composed system instructions, enabled native and MCP tool configuration, StackJack MCP endpoint, restricted environment host, and a StackJack MCP bearer credential stored in the Anthropic vault. Instructions can contain tenant-authored prompt text, tool policy and chains, knowledge display names, full source URLs, fetched URL text, and server-extracted text from uploaded files. Each run sends agent and task context, current time and dry-run instructions where applicable, user or default context or the webhook body, and only the outputs of preparation gathers bound to that run. Managed-agent native and MCP tool arguments and results, model responses, session events, and the full session transcript pass through Anthropic; post-run verification results are evaluated outside that session and are not sent as run input. If memory is enabled, memory-store identifiers, paths, content, and version operations are also handled there. StackJack does not inspect or sanitize the contents written to the Anthropic memory store.Anthropic processes and retains this data under its own terms. Anthropic keeps the full session transcript and StackJack fetches it live. StackJack's regional store does not hold the full transcript or full tool-result bodies, but it does hold a filtered trigger payload, session ID and provenance, summary, error and usage, pending tool input, and transcript-derived tool names, bounded arguments, order, and status. The raw bytes of uploaded knowledge files remain in the regional blob store; StackJack sends extracted text, not those raw bytes. Raw connector credentials remain in StackJack, but tool exchanges can contain provider data. With BYOK, managed agent, environment, vault, session, transcript, and memory resources use your own Anthropic account, workspace, and key; the payload categories do not change. Normal automation deletion archives sessions and memory, while hard memory erasure is a separate operation. BYOK migration copies memory into the new workspace and then archives the old store. An automation that you set to run on your own Azure Foundry does not use Anthropic's managed agents: its model calls go to your Foundry deployment instead (see the Azure Foundry row).
Microsoft Azure AI Foundry: your organization's own Azure subscription (optional)Only after an owner or administrator connects Foundry under Automations, and only for what they switch to it. Three things can run there instead of on Anthropic. An automation set to run on your Azure Foundry: its instructions, run context, tool arguments and results, and model responses, the same categories as the Anthropic row for tenant automation agents. An AI thinking step whose AI provider is "Your Azure Foundry": the question the step asks and the run values composed into it. StackJack's AI help, when the box "Run StackJack's AI help on your Azure Foundry" is ticked: the automation builder's assistant, its AI-assist suggestions, and the research and refinement StackJack's support team runs on your organization's tickets, the same categories as the two Anthropic rows for the builder and for support. StackJack signs in to your Foundry with a stored account key held in your region's key vault, or keylessly through StackJack Foundry Runner.Processed in your organization's own Azure subscription. Azure bills your organization, and StackJack charges no credits for the model usage. Data at rest is in the Azure region your organization picks (Sweden Central for an EU storage home). StackJack sets up Global Standard deployments, which Microsoft may process in any Azure region, and Claude on Azure has no EU-only processing option, so an EU organization acknowledges that before it connects Foundry. Microsoft and Anthropic process and retain the data under the terms your organization accepted for its Azure subscription and its Claude deployment. When your Foundry cannot serve a request, StackJack refuses the request and sends nothing to Anthropic in its place. See Running automations on your Azure Foundry.
TypeSafe AI — fast decisions (typed judgements)A second AI vendor, separate from Anthropic and used for short typed judgements rather than generated text. Five paths send it data. Decision steps: when an automation's fixed start steps include one, StackJack sends that step's composed state, which can carry the run's trigger payload and the results of earlier gather steps (a whole list or object one returned, up to 64 KiB in all), plus the author's own question text. Smart filters: when a webhook trigger carries one, StackJack sends the automation's filtered trigger payload — the same payload the run would have received, never the raw body — for every inbound delivery. Smart tool search and tool suggestions: your search text, plus tool and connector names and short tool descriptions. Support AI: the ticket text and classification context, on the same deliberate-trigger rule as the Anthropic support path above. The automation builder assistant: the conversation transcript, to repair a field the text model left blank or invalid. Answers are probabilities and short typed values, not generated prose.TypeSafe AI processes and retains this data under its own terms. It is hosted outside the European Union. Organizations with a US storage home use it by default. Organizations with an EU storage home must opt in per organization — until they do, nothing is sent on any of these paths and each feature behaves the way it did before fast decisions existed; see Fast Decisions and Your Own TypeSafe Key. An organization can supply its own TypeSafe key, which changes the account the decision-step and smart-filter calls are made on but not what is sent. StackJack's own regional store keeps a record of each call — the surface, the organization, timing, token counts and the outcome — and, for decision steps and smart filters, the judgement itself so a restarted run replays it. For a decision step it also keeps the exact values that were sent, so you can see them on the run's detail page; deleting the run's transcript deletes them.
Zitadel — identity and accessStackJack's management client sends organization names and IDs, user names, email addresses, user IDs, and roles for organization and user provisioning, invitations and password setup, and ownership and role management. Sign-in itself happens on the identity provider's own hosted pages through OIDC, so the session and authentication-factor data in that flow is handled by the provider rather than by StackJack.The identity provider processes and retains this data under its own terms.
Cloudflare Turnstile — signup abuse protectionCompleting the signup challenge runs on Cloudflare's widget, and StackJack's server-side verification then sends the challenge response token and the signup request's IP address to Cloudflare. This happens at signup only.Cloudflare processes and retains this data under its own terms.
Sentry — application error and performance telemetryStackJack's Portal, MCP server, automation runner, and operator console send application telemetry to Sentry. Errors, traces, logs, tags, correlation IDs, tenant IDs, and surrounding application context can be transmitted when captured. Support AI can query Sentry events scoped to your organization or to a correlation ID as evidence.Sentry processes and retains this telemetry under its own terms.
Discord — staff support notifications and release notesWhen a ticket is filed through an AI assistant or a support reply is posted, a notification is sent to StackJack's staff Discord channel carrying the ticket subject, up to the first 1,024 characters of the message or description, the organization name, the requester's email address, priority, status, and the ticket ID. Release-note publishing posts patch-note content, which carries no customer data.Discord processes and retains this data under its own terms.
Azure Monitor / Log Analytics — optional support evidenceSupport AI can read error logs scoped to your organization as evidence. This evidence source is off by default.Microsoft processes and retains this data under its own terms.
OpenTelemetry destination — application telemetryStackJack exports application logs, traces, and metrics to an OpenTelemetry destination only when one is configured.The destination service processes and retains this telemetry under its own terms.
Paddle — current subscription and payment processingCheckout, customer and subscription management, transactions, invoices, and webhooks exchange billing identity, price, payment, subscription, and transaction and event data. Support AI can read matching Paddle event history as evidence.Paddle processes and retains this data under its own terms.
WooCommerce — legacy subscription handlingStackJack still reads, reconciles, and attempts cancellation of linked legacy WooCommerce subscriptions, which involves tenant and subscription identifiers and billing state.WooCommerce processes and retains this data under its own terms.

Support diagnostics in external processing

StackJack assembles a diagnostic report on the server when a support ticket is created for your organization — both for a ticket opened through the in-product Support widget and for one an AI assistant files on your behalf. This section is the notice.

The default report contains more than health counters: it can include member and invite identity details, tool permissions, credential validation state and errors, MCP client metadata, recent usage and error text, and subscription state. Recent usage and error text can carry vendor error messages, which are not guaranteed to be free of customer detail — see What usage records contain. A separate MCP log bundle is collected when available. The report is meant for StackJack support staff; signed-in members of your organization and your managing support partner can also retrieve it. Closing the ticket deletes it. See Submitting a Support Ticket for the complete disclosure.

An automation has two separate opt-ins here, and both are off by default: whether it may file a support ticket when it errors, and whether that ticket's diagnostic report carries the identity detail. They are set per automation and are independent of each other.

Those files are stored in StackJack's ticket storage. If support AI runs, selected diagnostic content can become evidence in the prompt sent to Anthropic. When the ticket is closed, StackJack deletes those diagnostic files, together with any attachment files it stores for that ticket. Deleting your organization deletes all of them, for open tickets too.

Automation-agent sessions are a separate Anthropic processing path. Treat prompt and knowledge text, webhook or manual run context, bound gather outputs, tool arguments and results, generated messages, session events and transcripts, and enabled memory content as externally processed data. Raw knowledge-upload bytes and opt-in evaluation fixture blobs remain in the regional StackJack blob store; extracted knowledge text and later live-test results can still enter the Anthropic builder or run paths described above. A regional StackJack storage home does not make Anthropic session or memory operations regional.

What a region move changes

A region move changes the destination for StackJack's regional database, cache, blob, vault, and application hosts. It does not move or erase copies a provider already holds under that provider's terms. Organization deletion has similar boundaries; review Customer Data & Privacy before starting it.