Adjuro Beta
The AttestationA signed JWS, built for FRE 901 evidence Evidence PacketsWin the TCPA motion Pricing & pilot$500, 30 days, 10K calls Trust NetworkFederated signing roots
adjuro · verifier SDKOpen-source · Apache 2.0 · npm Protocol DocsThe attestation format, specified Verify in your browserNo account · runs client-side
SecurityHSM-backed signing keys Privacy & TermsHow we handle data Request early accessJoin the early-access list
Verifier SDK Start the pilot — $500
← Back to Privacy Policy

Subprocessors

The third parties that process data on Adjuro's behalf, what each one handles, and where it runs.

LAST UPDATED August 5, 2026

This page is the current subprocessor list referenced by Section 4.1 of our Privacy Policy. Each provider below is bound by a data processing agreement requiring it to process data only on Adjuro's instructions. We will notify customers of material changes to this list.

Infrastructure

ProviderPurposeData processedLocation
Fly.ioApplication server hostingAPI request data in transit and in memoryLondon, UK
SupabaseManaged Postgres databaseTenant accounts, agents, attestations, signing key metadataLondon, UK
Amazon Web ServicesAWS KMS — cryptographic signingAttestation payloads submitted for signature and the returned signatures. Private keys are generated inside KMS hardware security modules and cannot be exportedUnited States
UpstashRedis-backed API rate limitingIP addresses and tenant identifiers onlyGlobal edge
VercelWebsite and documentation hostingWebsite request logsGlobal edge
CloudflareDNS, content delivery, DDoS protectionNetwork-level request metadataGlobal edge

Business operations

ProviderPurposeData processedLocation
ResendTransactional emailAccount email addresses, sign-in links, service notificationsUnited States
StripePayment processingBilling contact and payment details. Adjuro does not store card numbersUnited States
Loom and similar toolsCustomer support and demosContent you choose to share in a support interactionUnited States

Not subprocessors

Voice-agent platforms — Vapi, Retell, Bland and similar — are not Adjuro subprocessors.

They are your vendors. At your direction they send Adjuro call-event metadata: a call identifier, a status, an ended-reason code, and the fields you injected at call creation. Data flows one way. Adjuro does not send them your data, does not retrieve call recordings or transcripts from them, and holds no contractual relationship with them on your behalf.

What no subprocessor receives

None of the providers above receives call audio, call transcripts, or recipient phone numbers — because Adjuro does not collect them. Recipient numbers reach us only as HMAC-SHA256 hashes, salted per tenant. Where a customer binds a call recording to an attestation, the customer computes the SHA-256 digest themselves and sends only that digest; the recording never leaves their control.

Changes to this list

We update this page whenever a subprocessor is added or removed, and notify customers of material changes as described in Section 10 of the Privacy Policy.

Questions about this list privacy@adjuro.ai
Adjuro

Cryptographic evidence for AI agent actions. The trust layer for AI voice agents.

From the Latin adjurō, “I attest under oath.”

Product

The Attestation Evidence Packets Pricing & pilot Trust Network

Developers

npm · adjuro Protocol Docs Verify an attestation

Company

Security Request early access status.adjuro.ai

Legal

Privacy Terms Contact

© 2026 ADJURO · CRYPTOGRAPHIC EVIDENCE FOR AI AGENT ACTIONS

status.adjuro.ai log.adjuro.ai hi@adjuro.ai

The open-source verifier SDK is live on npm (adjuro, Apache 2.0); the public transparency log (log.adjuro.ai) and status page (status.adjuro.ai) are live. The metrics strip above reflects current shipping state. Attestations are designed for FRE 901 admissibility; full court-admissibility evaluation is pending qualified-counsel review.