Skip to main content
Back to Security

Subprocessors

These are the companies that handle data for us. We keep this list current. We will tell you before we add one.

Last updated

Most of them only see metadata

Package names, versions, findings, scores. That is all that leaves your machine when you scan. So that is all any of these companies can hold.

Three of them can see your code

AWS and OpenAI, when you ask the agent to write a fix. Your Git host, when you connect a repository. None of it happens unless you ask.

The register

CompanyWhat they do for usWhat they receiveWhere
CloudflareCompute, database, object storage, and cookieless edge web analyticsMetadata

Scan metadata, account identity, workspace membership

Global edge
ClerkSign-in, organizations, SSOIdentity

Name, email, workspace membership

United States
TinybirdAnalytics over scan and audit eventsMetadata

Scan metadata, workspace identifiers

EU (GCP europe-west2)
ResendTransactional email — invitations and notificationsIdentity

Name, email

United States
Amazon Web ServicesVirtual machines for the remediation agentSource code

Your source code, when you ask the agent to write a fix

Per workspace residency
OpenAIThe model behind the remediation agent and scan analysisSource code

Source-derived input, when you ask the agent to write a fix

United States
GitHub, GitLab, BitbucketRepository access, when you connect oneSource code

Repository contents you grant access to

US / EU

Our own marketing

These hold Vibgrate's marketing data, not your platform data. We list them so the picture is complete.

CompanyWhat they do for usWhat they receiveWhere
Google AnalyticsWebsite traffic analytics for vibgrate.com (GA4)Metadata

Page views, referrers, approximate location, device/browser signals; first-party cookies (_ga, _ga_*)

Global (Google)
HubSpotMarketing CRMIdentity

Name, email — if you give them to us

United States

Worth knowing

Marketing-site analytics. vibgrate.com uses Google Analytics 4 (first-party cookies such as _ga) and Cloudflare Web Analytics (cookieless edge metrics). Theme preference is stored in local storage. See the privacy policy for detail.

You can bring your own model key. Would you rather your code never reached our model provider? Add your own key and it goes to yours instead.

We are not claiming EU data residency. The routing is built. The storage is not switched on yet. Your data is in our primary region today, and we will change this page the day that changes.

Questions about a specific processor?

Write to privacy@vibgrate.com. Need a filled-in questionnaire? Ask. We will not make you book a call first.