Skip to content

Providers and Services

The services supporting Relsor and how their involvement depends on your workflow.

Last updated · 2026-10-30

Relsor uses external services to operate the platform and deliver selected features. The entries below explain the purpose and scope of the implementations in our service. They are not a statement that every provider receives every customer's content. A customer-specific subprocessor schedule, provider entity and processing location should be confirmed in the applicable data-processing documentation.

Google Cloud and Firebase

Application infrastructure, authentication, database and file storage

Information involved
Account and workspace records, uploaded files, generated artifacts and operational records relevant to those services
When it applies
Core platform services; exact resources and locations depend on the deployed configuration

Vercel

Website and web-application hosting; website analytics and performance measurement

Information involved
Web requests and technical information; application data handled by web routes; page-usage and performance information for enabled measurement
When it applies
Production web hosting and the analytics components enabled for the website

Resend

Transactional email delivery

Information involved
Recipient address, subject, message content and delivery metadata
When it applies
Verification, account recovery, approvals and other service emails sent through the configured email service

Stripe

Payment and subscription processing

Information involved
Payment information entered in Stripe's flow, customer and subscription identifiers, transaction and invoice information
When it applies
Paid purchases and subscription operations. Stripe also determines certain processing for its own payment, fraud and legal obligations

OpenAI

Configured AI model processing

Information involved
Messages, task instructions and relevant text, images or other context included in a model request
When it applies
When the selected feature or model routes a request to OpenAI

Anthropic or Google Gemini

Additional configurable AI model processing

Information involved
The content included in the applicable model request
When it applies
Only when enabled, configured and selected for the feature or model route. Their implementation does not mean they process every workspace

Higgsfield or Google Veo

Configurable Nova video generation

Information involved
Generation instructions and any source media included in the selected video request
When it applies
Only when the corresponding Nova video provider is configured, enabled and selected. Availability in code is not confirmation that it is used for your workspace

PostHog

Configured product and website measurement

Information involved
Page and feature events, browser or device information, and fixed identifiers for dedicated marketing actions
When it applies
When configured and enabled for collection. Dedicated marketing action events do not contain form or brief text

Sentry

Configured error and performance monitoring

Information involved
Diagnostic events, technical context and performance information captured by the configured SDKs
When it applies
When a Sentry DSN is configured. Collection depends on the enabled SDK features and configuration

Services you connect or select

A connected email, calendar, document, collaboration or business service is involved only when the connection and workflow use it. Other feature-specific providers may be involved when you choose that feature. Review connection permissions, the applicable feature information and any agreed provider restrictions before use.

A connector appearing in the product or code does not mean it has been connected, authorised or used by your organisation. Customer-controlled integrations and recipients are not automatically part of the same contractual subprocessor category as our platform vendors.

Need a contractual subprocessor schedule?

Contact hello@relsor.ai with your workspace and intended features to request the applicable provider entities, locations and data-processing documentation. A signed or otherwise validly accepted DPA governs any contractual authorisation, change notice or objection procedure. This page does not replace that agreement.

Relsor · DBM LLC

8 The Green, Ste B, Dover, Delaware 19901, United States

hello@relsor.ai