← mergesafe.ai

Subprocessors

Last updated 7 October 2026.

These are the companies that process data on our behalf to run MergeSafe and this site. For each one: what we use it for, what it receives, and where it operates.

Amazon Web Services

Purpose: hosting — compute, storage, database, DNS, CDN, and outbound email through Amazon SES.

Data categories: everything we store. The repository index is encrypted at rest with a key per customer repository; other stored data (findings, billing records, operational logs) uses AWS-managed or environment-level encryption, varying by service.

Region: United States (us-east-1).

GitHub

Purpose: source of your code; the MergeSafe GitHub App, OAuth sign-in, and where we post review output.

Data categories: GitHub already holds your code; what we send back is the review output we post to your pull requests — findings, comments, and check runs.

Region: United States.

OpenAI

Purpose: AI model inference for reviews.

Data categories: diff hunks, file excerpts, and index context from the pull requests we review. Every review call sets store=false. One short yes/no check that decides whether a review runs the SQL-focused check group (changed-file diff hunks, chunked; it returns only a probability) uses OpenAI’s Decisions endpoint, which has no such setting.

Region: United States.

Anthropic

Purpose: AI model inference for reviews. Anthropic is an approved provider but is not yet configured in production — it receives nothing today.

Data categories: the same as OpenAI, if and when it is enabled.

Region: United States.

Sentry

Purpose: our own application error reporting.

Data categories: scrubbed error events only — no code and no message text.

Region: United States.

Stripe

Purpose: payments and review-credit top-ups.

Data categories: billing contact and payment details, entered directly on Stripe’s own hosted pages. We never receive or store your card details, and no code passes through Stripe.

Region: United States.

Google Workspace

Purpose: our company email, including mail sent to support@mergesafe.ai and privacy@mergesafe.ai, and alarm emails from our own systems.

Data categories: whatever mail you or our systems send us. No code or review content passes through it.

Region: United States.

How we announce changes

If we add, remove, or change what an existing subprocessor receives, we update this page and the date at the top. A change to who processes your code specifically is also reflected on Privacy and Security and data retention, which make the same commitment to keep that list current.

Learn more