Data Processing Addendum
Data Processing Addendum (DPA)
Effective date: 2026-05-29
This page describes our approach to data processing agreements for business customers who need a signed DPA for GDPR, UK GDPR, or similar data protection regulation compliance.
For most users: our Privacy Policy describes everything Kalmantic does with your data. You don't need a separate DPA. The Privacy Policy covers lawful basis, retention, subprocessors, your rights, international transfers, and security measures.
For business customers processing personal data of EU/UK/Swiss data subjects: contact legal@jusinfer.com for a Kalmantic-issued DPA. We can sign yours if it doesn't materially conflict with our Terms of Service and Privacy Policy, or you can countersign ours.
What our DPA covers
When signed, our DPA includes:
- Standard Contractual Clauses (EU 2021/914) for transfers from the EEA to non-adequate countries
- The UK Addendum to the SCCs (for UK GDPR)
- A list of subprocessors (Cloudflare, Stripe, Firebase, Resend, upstream LLM providers) with contact information
- Security measures we apply, mapped to ISO 27001 control areas (TLS in transit, AES at rest, key hashing, principle of least privilege, breach notification within 72 hours)
- Customer audit rights — you can request an audit summary annually; physical site audits are by appointment and subject to our reasonable security policies
- Subprocessor notification — 30 days' advance notice before we add or change a material subprocessor
- Data subject request handling — we will assist your fulfillment of GDPR Articles 15-22 requests within reasonable time
Subprocessors we use
Current as of 2026-05-29. Notification of additions or changes will go to your account contact email at least 30 days in advance.
Active platform subprocessors
These run on every request — authentication, payment, edge compute, email delivery.
| Subprocessor | Service | Data processed | Region |
|---|---|---|---|
| Cloudflare | DNS, CDN, Workers compute, D1, KV, Analytics, AI Gateway | All request metadata, API content (transit + storage) | Global edge |
| Firebase (Google Cloud) | Authentication | Email, display name, UID | US (us-central1) |
| Stripe | Payment processing | Billing data, last-4 of card | US, EU, India (presentment) |
| Resend | Transactional email | Recipient email + message body | US, EU |
LLM inference providers we may route to
jusInfer is a routing layer. We do not commit to any specific upstream model or provider. We continuously optimize routing on a dollar-per-token basis, subject to capability for the task, capacity / availability at the upstream, and your selected pricing tier. The provider serving any specific request can change between requests as upstream prices, latency, and availability shift — we move traffic to keep your bill low and the platform available.
The table below lists every commercial LLM inference provider we have an integration path for and may route requests to. Inclusion here is a disclosure of potential routing scope, not a commitment that any specific request will be served by any specific provider. Adding a brand-new provider that does not appear in this list triggers the 30-day notification described in the platform subprocessors section above; routing among the providers listed here happens at our discretion.
Customers needing data residency or sector-specific compliance (HIPAA, FedRAMP, SOC 2 Type II, residency-locked, EU-only, US-only) can pin routing to a subset of these providers via a signed DPA. Email legal@jusinfer.com to scope.
| Provider | Primary region |
|---|---|
| Anthropic | US |
| Anyscale | US |
| AWS Bedrock | US, EU, multi-region |
| Cerebras | US |
| Cloudflare Workers AI | Global edge |
| Cohere | US, Canada |
| DeepInfra | US |
| DeepSeek | China |
| Fireworks AI | US |
| Google (Gemini, Vertex AI) | US, EU, multi-region |
| Groq | US |
| Lepton AI | US |
| Microsoft Azure (Azure OpenAI, model catalog) | US, EU, multi-region |
| Mistral AI | EU (France) |
| Modal Labs | US |
| OpenAI | US |
| OpenRouter (multi-provider aggregator) | US |
| Perplexity | US |
| Replicate | US |
| SiliconFlow | China / Singapore |
| Together AI | US |
| xAI (Grok) | US |
Data flow for any inference provider above is identical: jusInfer forwards your prompt (including any system message, tool definitions, and message history you sent) to the provider, receives the response, returns it to you, and logs request metadata (tenant id, user id, chosen model, token counts, latency, cost). We do not store the prompt or response content in our own database. The chosen provider's own privacy policy and data-retention terms apply once the request reaches them.
Why this framing. Locking our routing to a specific provider would either raise your bill (when that provider's rate goes up) or break your workload (when that provider has an outage). Dynamic routing across the disclosed set is what lets us deliver the price + reliability posture we offer. Customers who need certainty over flexibility can buy that certainty via the pin-routing DPA above.
Enterprise plan: scope-pending options for custom contracts
For customers with stricter data-residency, regulatory, or sovereignty requirements than the standard pin-routing DPA can meet, jusInfer offers an Enterprise plan with custom-contract terms.
Enterprise terms are negotiated individually. The options listed below describe what may be in scope for a given engagement, subject to (a) scoping discussion, (b) technical feasibility assessment, (c) commercial agreement on pricing, and (d) a signed enterprise contract. Not every option is available on every engagement, and inclusion in this list is not a commitment to deliver any specific option to any specific customer.
Options that may be available in an enterprise engagement:
- Regional pinning — routing constrained to a single geographic region (e.g. EU-only, US-only, India-only, GCC-only) with audit-logged enforcement at the gateway layer
- Provider pinning — routing constrained to a customer-approved subset of the providers listed above
- Sovereign cloud routing — routing exclusively to providers operating under your jurisdiction's sovereign-cloud framework (e.g. Microsoft Azure for Sovereign Cloud, AWS GovCloud, Google Sovereign Controls)
- On-premise / private-cloud deployment — a dedicated jusInfer gateway instance deployed inside your VPC, sovereign cloud tenancy, or on-premise data center, talking only to upstream models you authorize. Customer retains custody of all data and infrastructure; we supply deployment artifacts, configuration, and operational runbook.
- Custom subprocessor list — a contractually frozen subprocessor list with stricter notification windows (e.g. 60 or 90 days) and a customer veto on additions
- Custom retention — usage logs deleted on a schedule shorter than this DPA's 13-month default, or never written to durable storage
- Dedicated support channel with named contacts and committed response times
Enterprise options are not available on the standard self-serve plans and require a signed enterprise agreement. Pricing reflects the engineering and operational overhead of the chosen configuration.
A note on encryption keys. jusInfer acts as the upstream-API-key custodian for our customers — your jusInfer token is what unlocks routing, and we manage the upstream provider keys on your behalf as part of the service. We do not currently operate a customer-managed-key (BYOK) system for at-rest storage of jusInfer-side metadata. Metadata is encrypted at rest using the standard managed-key infrastructure of our storage providers (Cloudflare D1, KV, R2). If your enterprise engagement requires customer-managed at-rest encryption for jusInfer metadata, raise it during scoping — it would require a new build and is not available today.
To scope an enterprise contract, email legal@jusinfer.com with: your legal entity, the specific residency or sovereignty requirements you need to meet (citing the regulation if applicable), your expected request volume, and any provider-pinning preferences. We will return a scoping call invite within 3 business days.
How to request a DPA
Email legal@jusinfer.com with:
- Your legal entity name and registered address
- The jurisdiction(s) of the data subjects whose personal data you'll process via jusInfer
- Whether you need our standard DPA, the UK Addendum, the Swiss adaptation, or all three
- Whether you need any custom terms (we'll review; common asks include enhanced breach notification or specific subprocessor restrictions)
We aim to return a signed DPA within 5 business days for standard requests.
Contact
legal@jusinfer.com — for DPA requests, subprocessor notifications, audit requests, and any other data-processing question.
privacy@jusinfer.com — for data subject requests (access, deletion, portability).
security@jusinfer.com — for security incident reports.
Kalmantic operates jusInfer. This page was last updated on 2026-05-29.