[L8] / Legal

Subprocessor List

Effective September 25, 2026Last updated September 25, 2026

This page identifies core third-party service providers RELAVANZ currently uses, or has selected for an identified launch function, when those providers may process customer personal data on RELAVANZ's behalf.

Customer-directed connected platforms such as Google Search Console, Google Business Profile, Google Merchant, Shopify, GitHub, and a customer's WordPress/CMS environment are described separately below. They are not automatically classified as RELAVANZ subprocessors merely because a customer connects them.

Core service providers

Provider	Purpose	Data that may be processed	Status / notes
Supabase	Authentication, database, storage, and protected backend data services.	Account/Workspace data, Site records, product state, integration metadata, audit and lifecycle records, and other application data stored by RELAVANZ.	Active core infrastructure.
Google Cloud Platform	Cloud Run compute, jobs, storage, scheduling/queues, and platform infrastructure.	Website crawl/evidence payloads, worker inputs/outputs, operational logs, service telemetry, and other data processed by RELAVANZ platform workloads.	Active core platform infrastructure.
Vercel	Web application hosting and deployment.	Web requests, application delivery metadata, and data processed by server/runtime functions used by the RELAVANZ web application.	Active web-application hosting.
OpenAI	Production AI model execution for Ask RELAVANZ and Article Engine workflows.	Prompts, questions, objectives, selected Site evidence/context, article context, and AI-generation metadata needed for the requested AI feature.	Active production model provider for Agent and Article Engine. Provider/model routing can change and is monitored through Legal Health.
Google Gemini API	AI-assisted audit and SEO/GEO analysis, classification, summarization, and related supported analysis paths.	Site/public-web evidence, analysis inputs, and feature-specific context needed for the requested audit or analysis stage.	Active in selected analysis paths; separate from Google OAuth integrations.
DataForSEO	SEO, backlink, Local, and search/visibility research data used by supported RELAVANZ modules.	Domains, URLs, keywords, geography/query parameters, and provider-research inputs/outputs used for the requested research feature.	Active for bounded provider-backed research where the feature is enabled.
Resend (Plus Five Five, Inc.)	Transactional and product email delivery, including the existing scan/report delivery path and other email flows that use the RELAVANZ sending infrastructure.	Recipient email address, message content, delivery metadata, suppression/opt-out state, and provider message identifiers needed to send and operate the email.	Active email-delivery provider in current RELAVANZ code. Delivery events, notification preferences, and bounce/complaint suppression are reflected in the current Privacy Policy.
Stripe	Payment processing and subscription billing.	Billing/contact information, payment-method information handled by Stripe, subscription/payment status, invoices, and transaction metadata.	Current payment processor for supported RELAVANZ self-service checkout and subscription billing.

Customer-directed connected platforms

When you connect a third-party account, you direct RELAVANZ to exchange data with that provider according to the permissions and feature you select. These relationships are generally different from a provider RELAVANZ hires to run its own infrastructure.

Connected platform	RELAVANZ use
Google Search Console	Read-only Search Console properties and observations using webmasters.readonly.
Google Business Profile	Authorized profile/location discovery and capability-gated management using business.manage.
Google Merchant	Merchant account/data-source/product observations and separately approved write operations using the content scope.
Shopify	Store/catalog/content/navigation/market reads and optional write capabilities requested only where supported.
GitHub	GitHub App repository access and pull-request-based source-change workflows within granted permissions.
WordPress / Custom CMS	Customer-connected Site operations limited to the credential, connector tier, and detected/granted capabilities.

Changes to subprocessors

RELAVANZ may add, replace, or remove service providers as the product evolves. Material provider additions/removals are monitored by the RELAVANZ Legal Health system. Where a governing DPA or applicable law requires advance notice or an objection process, RELAVANZ will provide the applicable notice/process for that customer relationship.

Processing locations and transfers

Providers may process information in the United States and other locations where they operate. Where a legally required international-transfer mechanism applies, RELAVANZ will use an available mechanism appropriate to the provider and RELAVANZ's role. Provider-specific processing locations and transfer mechanisms can vary over time and by service region.

Historical changes

This is RELAVANZ's initial published Subprocessor List. Future material additions or removals will be reflected by updating this page's date and, where required by an applicable agreement or law, through the applicable notice process.

Contact

Questions about this list may be sent to hello@relavanz.com.

← Back home