CodeVet Subprocessors
Last updated October 1, 2026
CodeVet uses the following subprocessors to provide the Cloud Service. This page also serves as the Model Providers list referenced by the CodeVet Labs AI Addendum.
| Name | Purpose | Location | Customer data involved |
|---|---|---|---|
| Amazon Web Services | Hosting, storage, and infrastructure | United States | All customer data and derived project context |
| Amazon Bedrock | Model inference for briefing generation | Within CodeVet’s AWS environment, United States regions | Ticket and documentation content submitted for generation, and the content generated in response |
| Amazon SES | Transactional email: sign-in codes, password resets, team invitations | Within CodeVet’s AWS environment, US East (N. Virginia) region | Recipient name and email address; message bodies containing one-time authentication codes, password reset links, and one-time temporary credentials |
Notice of changes
Subprocessors CodeVet appoints. CodeVet gives at least thirty (30) days’ prior notice before adding or replacing a subprocessor that CodeVet appoints directly, by email to the Customer’s notice address and by updating this page.
Model Providers. CodeVet notifies Customers before any change to the model providers listed above takes effect. The thirty-day period applies to a model provider CodeVet appoints directly.
Further subprocessors appointed by a subprocessor. Where a subprocessor, or a subprocessor further down the chain, adds or replaces a further subprocessor, CodeVet gives notice within 24 hours after receiving advance notice of the change and before the change takes effect. Where CodeVet receives no advance notice, it gives notice within 24 hours after becoming aware of the change. A Customer may object on reasonable data-protection grounds within five calendar days after CodeVet’s notice, or for longer where CodeVet’s own objection period with the subprocessor runs longer than that.
Objection handling, termination, and refund rights are set out in the Data Protection Addendum.
Change history
| Date | Change |
|---|---|
| October 1, 2026 | Initial publication. |
Related
CodeVet’s security posture, architecture, retention and deletion practices are described in the CodeVet Security Measures at codevet.dev/legal/security-measures/v1.