Subprocessors
Effective November 8, 2026
What a subprocessor is here
A subprocessor is a third party that can hold or handle data on our behalf while we deliver the service to you. Everything that can touch tenant data is on this page.
A software library that runs inside our own systems is not a subprocessor and is not listed — nothing leaves our infrastructure for it. The distinction is the point of the page: this is the list of places your data actually goes.
Two services are left out for that reason. Single sign-on uses your own identity provider, which is your service and not ours. When someone sets a password, we check it against Have I Been Pwned’s Pwned Passwords service, which receives only the first five characters of the password’s hash and no tenant data.
Always used
These are part of running the platform, for every tenant.
| Subprocessor | What it does | What it can see | Region |
|---|---|---|---|
| Vercel | Application hosting, scheduled jobs, content delivery, and the bot check on the discovery form | Request metadata, any data in transit through the application, and function logs, which can include logged error text | United States for application compute. Requests enter through Vercel's global edge network |
| Supabase | Managed Postgres database and file storage | All tenant records, user accounts and hashed passwords, and stored files such as contract originals, attachments and imports | United States |
| Amazon Web Services (S3) | Separate backup copy of stored files, in an AWS account Vered controls | A copy of the files stored in Supabase, with their names. Raw line telemetry files are not copied. Database records are not copied here | United States |
| Anthropic | Large language model inference for Bromel and in-module AI, including contract text extraction and reading images | Prompt content, which may include tenant business records, contract documents and images and, where the mail agent is used, the text of email messages | Stored in the United States. Inference can run outside the United States unless the account restricts it |
| Microsoft 365 (outbound email) | Delivery of the business email the platform sends, such as invitations and notices, through a single Microsoft 365 mailbox | Recipient address, subject, message body, and attachments | Set by the Microsoft 365 tenant that holds the mailbox |
| Resend | Delivery of Vered's own product email, such as password resets, and fallback delivery for business email | Recipient address, subject, message body, and attachments | United States |
| Sentry | Error monitoring | Stack traces, request context with credential headers removed, and error messages, which can contain record values | United States |
| GitHub | Source code hosting, automated builds and tests | Source code, configuration and test files. It is not where the running platform stores data, but the repository's history and some current test files contain data derived from customer records | Not yet confirmed |
Only if you turn them on
These are integrations a tenant chooses to connect. If you never connect one, no data reaches it.
| Subprocessor | What it does | What it can see | Region |
|---|---|---|---|
| Microsoft Graph | Mailbox and calendar sync into CRM and SharePoint import into Legal, where a tenant connects them, and the mail agent, where a person connects their own mailbox | CRM sync: email and meeting details, previews of up to 500 characters, and participant addresses. SharePoint: files in the location the tenant grants. Mail agent: message headers, subjects and text, and attachment names; an attachment's contents only when the person files it; reply drafts saved to their own Drafts folder (never sent) | Set by your Microsoft 365 tenant |
| DocuSign | Electronic signature, where a tenant enables it | Documents sent for signature, signed copies, and signer names and addresses | Set by the DocuSign account |
| Slack | Notification delivery, where a tenant connects a workspace | Notification content sent to the channels the tenant selects | Set by your Slack workspace |
AI processing, specifically
Anthropic appears in the first table because Bromel and the in-module AI features send prompt content to a model, and that content can include your business records. That is the honest description, and it is the one an auditor should get.
What reaches a model, what never does, and what is not used for training are set out in AI Data Handling.
Where your data is hosted
Vered runs in the United States. The application runs on Vercel in its US West region (Oregon), and the database is a managed Postgres instance on Supabase in AWS us-west-2 (Oregon), the same region. The backup copy of stored files is in a separate AWS account in that region too. The region for each other subprocessor is shown in the tables above, including where a provider’s processing can leave the United States.
If there is a breach
If we confirm that your data, or personal data we hold for you, was accessed or disclosed by someone not authorised to see it, we will tell your named security or account contact within 72 hours of confirming it. The notice says what happened and when, what data and which users were involved, what we have done, what you should do, and who to contact. Anything not yet known is stated as unknown rather than guessed. Where your agreement with us sets a shorter period, the agreement applies.
Changes to this list
We keep this page current. Customers with a data processing agreement receive notice of a new subprocessor on the terms set in that agreement. To ask a question about any entry, or about a vendor you expected to see and do not, write to legal@vered.io.
Used for Vered's own business only
These services handle personal data for Vered’s own sales work. They never receive tenant data.
| Service | What it does | What it can see | Region |
|---|---|---|---|
| Origami | Vered's own outbound prospecting email. Vered reads the prospect a reply belongs to and adds addresses to its do-not-contact list | Prospect names, work email addresses, companies and titles, outreach messages and replies, and do-not-contact entries. No tenant data | Not yet confirmed |
Questions about this document go to legal@vered.io.
← All legal notices