Trust Center/Sub-processors
Sub-processorPurposeData processedRegion
Amazon Web Services, Inc.Cloud hosting — compute, database, KMS, secrets, transactional emailAccount data, audit records, hashes, sealed documents in transit; agent run step descriptions, object digests and shared policy documents; alert e-mails with agent and rule identifiersEU (Stockholm, eu-north-1)
Amazon Web Services, Inc. — Amazon BedrockModel inference for Mímir, the in-app assistant (paid plans)The question typed by the user and the evidence metadata Mímir looks up to answer it (labels, tags, hashes, timestamp authority names, expiry and verification state; for AI agents: agent identifiers, run, verification and policy-evaluation counts, and the tool names and policy text shown on the page the question is asked from). Never file content — Sigill does not hold it. Bedrock does not store prompts or responses, does not share them with the model provider, and does not use them to train models.EU only (eu-north-1, EU cross-region inference)
Stripe Payments Europe, Ltd.Subscription billing and invoicingBilling email, plan, payment metadata. Card data is never seen by Sigill.EU
ZITADEL GmbHFederated identity / SSO (Google, Microsoft Entra ID)Email, OIDC claims, IdP metadata for tenants that enable SSOEU (eu1.zitadel.cloud)
Cloudflare, Inc.Turnstile bot protection on the contact form and the sign-up pageIP address and browser fingerprint at form-submit timeGlobal edge
GitHub, Inc. (ghcr.io)Container image registry for the API and frontend buildsNo customer data — application images onlyGlobal

Transfers outside the EEA

Where a sub-processor operates outside the European Economic Area, the transfer relies on the EU Commission's Standard Contractual Clauses and — where the counterparty is established in the United States — the EU-US Data Privacy Framework. sigill.ai is operated by Sigill AS, organisation number 937 798 970, established in Norway (EEA) with registered office at Arne Garborgs veg 21, 7071 Trondheim, Norway. The primary application data plane runs inside the EU.

What is not a sub-processor

Cryptographic counterparties — external Timestamp Authorities and Certificate Authorities — are not sub-processors in the GDPR sense. They never receive customer documents, only hashes (timestamping) or public-key certificate requests (CA issuance). They are documented under standards.

Notification

Customers on a paid plan with an executed data-processing agreement will be notified by email of new sub-processors at least 30 days before they begin processing. The notice period applies to materially new processors; routine regional capacity changes within an existing sub-processor (for example, AWS adding an availability zone inside eu-north-1) do not require a fresh notice.