Sub-processors
The companies we use to run Jenz that may process personal data, and what each one does.
A sub-processor is a company we use to help run Jenz that may process personal data in the course of doing so. This page lists the sub-processors Jenz AS ("Jenz," "we," "our," or "us") currently uses, and what each one does for us.
This page supports Section 7.1 of our Privacy Policy, which remains the full statement of how we handle personal data. Where this page is shorter, the Privacy Policy governs.
1. Current Sub-processors
| Sub-processor | What it does for Jenz | Location |
|---|---|---|
| Slack | The Slack workspace where Jenz runs, when Jenz creates and operates it for you. Members message Jenz in Slack, and Jenz replies there. | United States |
| Microsoft Azure Bot Service | From the Microsoft Teams launch: relays messages between Microsoft Teams and Jenz when a workspace uses Jenz in Teams. | EU |
| Railway | Hosts the Jenz application and runs our primary database and cache, where account and workspace data is stored. | Netherlands (Amsterdam) |
| OpenRouter | Routes our requests to AI model providers. It does not store the content. See "How AI processing works" below. | United States or EU |
| Google Cloud (Vertex AI), Microsoft Azure, Amazon Web Services (Bedrock) | Run the AI models that read your instructions and connected data and generate Jenz’s responses and actions. By default, in their EU regions. | EU (default) |
| Anthropic, OpenAI | Provide AI models when a workspace chooses US processing, and serve as a fallback if our primary routing is unavailable. | United States |
| Composio | Connects Jenz to the services you link, such as Shopify, Gmail, and Meta, and holds those connections on our behalf. | United States |
| Modal | Runs code that Jenz writes for you inside an isolated virtual machine, and stores files you upload or Jenz creates. | United States |
| Browserbase | Provides the hosted browser Jenz uses when a task requires it to visit a website on your behalf. | United States |
| context.dev | Performs web searches and fetches web pages when a task requires it. It receives the search text and page addresses. | United States |
| Sentry | Records errors and diagnostic data so we can find and fix faults. Diagnostic data can include the content of the request that failed. | EU (Germany) |
| PostHog | Measures how our website (meetjenz.com) and the Jenz web app are used. Its event analytics runs without cookies. Session recording on meetjenz.com is switched on only for visitors who accept the cookie banner. | EU |
| Resend | Sends transactional email, including sign-in links and service notices. | United States |
| Vercel | Hosts the web apps Jenz builds and deploys for you. | United States |
| Convex | Provides the database behind the web apps Jenz builds and deploys for you. | United States |
| Stripe | Processes subscription payments and stores payment method details. Jenz never stores card numbers. For billing, Jenz is the data controller. | EU and United States |
2. How AI Processing Works
Jenz is an AI coworker, so AI models are central to how it works. When you ask Jenz to do something, your instructions and the data needed to carry them out, including data from services you have connected, are sent to large language models. Those models read that data and produce the analysis, answers, and actions you asked for.
That traffic is sent through OpenRouter, which passes each request only to model hosting from a restricted set we configure, and asks providers not to store or train on it. By default a workspace is set to EEA processing, and the models run in the EU regions of Google Cloud, Microsoft Azure and Amazon Web Services. A workspace can choose US processing, for example to use models not offered in the EU; the set then also includes US endpoints of Anthropic, OpenAI, Google and xAI.
Model training: We do not use Customer Data or Workspace Member data to train AI models unless you have explicitly opted in. Prompts sent to Jenz are forwarded to our AI model providers solely to generate responses. This is the same commitment made in Section 5 of the Privacy Policy.
3. Services You Connect Are Not Sub-processors
Services you choose to connect to Jenz, such as Shopify, Meta for Facebook and Instagram ads, Gmail, or Google Calendar, are not sub-processors. They are your own accounts, and Jenz accesses them only as you instruct. Data that stays inside those services is governed by their own privacy policies, which you should review separately.
Composio appears on the list above because it is the provider we use to establish and hold those connections. Slack appears because it is the surface Jenz runs on when we operate the workspace for you. If you use Jenz in your own Slack workspace or Microsoft Teams tenant, that service is your own provider.
Signing in with Google or Microsoft works the same way: you sign in with your own account, and the provider shares your name and email address with us. They are not sub-processors. How we handle that account data is described in the Privacy Policy.
4. Where Processing Takes Place
Some of the sub-processors above are located outside the EEA, including in the United States. Transfers to them are made under the safeguards described in Section 8 of our Privacy Policy, including Standard Contractual Clauses adopted by the European Commission.
The Location column above shows where each sub-processor stores or processes data. Companies established in the United States may be subject to US disclosure laws even when processing takes place in the EU.
5. Changes to This List
We update this page when our sub-processors change. Subscribers are emailed at least 14 days before a new sub-processor is added or replaced, and customers with a Data Processing Agreement may object as set out in it. Other material changes to how we handle personal data are notified as described in Section 15 of the Privacy Policy. The "Last updated" date at the top of this page reflects the most recent revision.
6. Questions
For the full picture of what we collect, why we process it, who we share it with, and every right you have, read the Privacy Policy.
Privacy Policy: Read the Jenz Privacy Policy
Contact: contact@jenz.ai