How does RelayLaunch protect my business data?

Cloud providers encrypt data in transit and at rest. Database policies and service-side checks scope supported queries to the configured tenant, while audit logs record defined administrative activity.

Does RelayLaunch train AI models on my data?

RelayLaunch does not use customer content to train its own models. Third-party provider handling follows the configured service terms and is documented during onboarding.

Is RelayLaunch SOC 2 compliant?

RelayLaunch is not SOC 2 certified today. We are scoping a lightweight control set around audit logging, encryption, access control, backups, and owner-approved AI operations before pursuing formal certification.

Can I export or delete my data from RelayLaunch?

Yes. You can request export or deletion of your business data. We support privacy requests and document the retention/deletion path before onboarding regulated or enterprise customers.

How RelayLaunch protects your data

Infrastructure

RelayLaunch is built with hardened cloud infrastructure patterns:

Cloudflare Workers: Edge compute with DDoS protection, WAF, and automatic TLS. Requests run in isolated per-request sandboxes on Cloudflare's edge network.
Supabase (Pro): PostgreSQL database with tenant-scoped access policies on application tables and provider-managed backup controls.
Railway: Relay Deck console deployed from versioned container images with automatic HTTPS and release rollback support.

Encryption

All data is encrypted in transit and at rest:

In transit: Public website and console connections use provider-managed TLS. HSTS is configured on supported public domains.
At rest: Provider-managed database encryption via Supabase/AWS infrastructure.
API keys: Service role keys are environment-scoped and are not embedded in client bundles.

AI Safety & Deterministic Enforcement

Our safety design separates model output from execution. Generation-layer filters can supplement the workflow, while code-enforced checks remain the execution boundary:

Layer 1: NVIDIA NeMo Guardrails (Generation Layer): A standby gateway can advise on brief drafts and filter selected generation risks without controlling dispatch. It is not represented as active for every tenant.
Layer 2: Deterministic Execution Checks: Supported outbound workflows cross code-enforced checks for authorization, consent, content, and deliverability outside the model output. End-to-end dispatch is not represented as verified until scheduler, tenant resolution, approval, provider acceptance, and delivery evidence are observed.
Auditable reasoning: Where a workflow exposes decision traces, RelayLaunch records the available source and reasoning context. Multi-model dissent is an enterprise proof-layer capability, not a promise on every SMB action.
AI data handling: RelayLaunch does not use customer content to train its own models. Third-party provider handling follows the configured service terms and client requirements documented during onboarding.
Tenant scoping: Application checks and database policies scope supported workflows to the configured tenant. Retention and memory behavior follow the documented workflow and data policy.

Generation guardrails: standby

Architecture snapshot

Deployment state Not tenant-wired

Scope Generation layer only

Execution boundaries

Application input validation CODE

Customer dispatch checks REQUIRED

Tenant query scoping POLICY

Generation gateway STANDBY

Glass Box vs. Black Box Security

Traditional AI assistants can rely heavily on model instructions. RelayLaunch uses a "Glass Box" approach that places operational checks outside model output, so a generated instruction alone does not authorize a send or a cross-tenant query.

Security Threat	Traditional "Black Box" AI	RelayLaunch "Glass Box"
Prompt Injection	Relies on instructing the AI model to "ignore malicious commands" in system prompts. Easily bypassed by jailbreaks.	Deterministic Filters: Version-pinned schemas and code-based sanitizers validate supported payloads at defined boundaries before downstream processing.
Tenant Data Isolation	Injects all tenant data into a single shared model context, risking cross-tenant data leaks and boundary violations.	Query-Level Isolation: Database Row Level Security (RLS) and server-enforced tenant context are designed to keep supported queries within the configured tenant.
Unapproved Actions	Grants the AI model autonomous write permissions to dispatch emails or update external booking databases directly.	Owner-in-the-Loop: Supported dispatch paths require the configured authorization and owner-review checks; delivery is verified separately.
Resource Exhaustion	Trusts LLM routing loops to manage budget constraints, leading to runaway costs and platform key drain.	Budget Controls: Rate and budget controls at the model gateway reduce runaway request and cost risk.

Access Control

Authentication: Supabase Auth with email/password and magic link support. Session tokens are short-lived with automatic refresh.
Tenant-scoped access: Application tables use tenant filters and service-side checks so customer data is only returned in the right tenant context.
Role-based access: Team plans support member, admin, and owner roles with scoped permissions.
Audit logging: Admin actions (data exports, deletions, configuration changes) are logged with timestamp, actor, and IP address.

Data Handling

Data residency: Primary database hosted in US-East (AWS). Cloudflare edge caching is read-only and contains no PII.
Retention: Active accounts retain all data. Deleted accounts are purged within 30 days. You can request immediate deletion at any time.
Backups: Provider-managed backups are part of the hosted database posture; enterprise retention and recovery windows are confirmed during onboarding.
No selling: We never sell, rent, or share your data with third parties for marketing or advertising purposes.

Compliance

SOC 2: Not certified today. Control scoping is in progress before a formal audit.
CCPA: Privacy request workflows are supported for access, deletion, and opt-out requests.
GDPR: Data processing and erasure requests are handled during onboarding and support.
HIPAA: Not yet certified. Healthcare clients should contact us to discuss requirements.

Vulnerability Reporting

Found a security issue? We take reports seriously. Email security@relaylaunch.com with details. We aim to acknowledge within 24 hours and will work with you on responsible disclosure.

Status & Uptime

Internal monitoring covers the website, Relay Deck console, Relay Pulse Workers, and the LiteLLM model gateway. Public incidents and recent platform changes are tracked on the status page and changelog as the public status process matures.

Our Commitment

RelayLaunch is founder-led. We build systems we trust with our own operations — because we do. Victor Medina uses Relay Deck to run RelayLaunch every day.

Questions about our security practices? Contact us at hello@relaylaunch.com.

Security & Trust