Trust center
Privacy, in plain language.
Relay needs enough information to build a fixed service brief, contact businesses, compare quotes, and show you the evidence behind a recommendation. This notice explains what that means in the current product.
Last updated July 19, 2026
01
Information Relay handles
Depending on the features you use, Relay handles your account identity from Clerk; optional profile details such as your phone number, location, and time zone; the addresses, dates, inventory, budget, access constraints, and notes in a service brief; and the businesses, quotes, conditions, and decisions connected to a request.
Voice interviews, uploaded estimates, call transcripts, and recordings can contain personal or sensitive details. Relay also records limited technical information such as request IDs, timestamps, provider statuses, and safe error categories so the workflow can be secured and repaired.
02
How the information is used
Relay uses this information to authenticate you, create the exact brief you approve, find candidate businesses, request and negotiate comparable quotes, produce an evidence-backed report, apply your notification and retention choices, and investigate failures or abuse.
Relay can gather and negotiate quotes, but it does not accept a quote, book a provider, sign an agreement, or submit payment.
03
Services involved
A production Relay deployment can send the minimum necessary data to configured service providers: Clerk for authentication, Google Places for business discovery, ElevenLabs and Twilio for voice calling, OpenAI for structured extraction, Supabase for private evidence storage, and the configured Postgres and Redis services for application and job data.
Those providers process information under their own terms and may operate in other regions. A feature that is not configured in a deployment is not used by that deployment.
04
Calls, transcripts, and recordings
Relay requires the applicable customer consent before starting a business-calling run and records the consent against that request. During a call, Sara introduces herself by name and from Relay. If asked, she truthfully explains that Relay uses an automated voice service. Recording and disclosure rules vary by location, so live calling must be configured for the relevant jurisdiction.
05
Retention and deletion
The settings page provides 7, 30, or 90 day retention choices for recordings, transcripts, and uploaded evidence. Quote summaries, request records, consent records, and account data can follow a different retention lifecycle where they are needed to operate or audit the workflow. Relay stops serving evidence after its access deadline; physical cleanup from configured storage can follow a separate operational process.
A verified self-service deletion workflow for all Relay application data is not available yet. Removing a Clerk identity does not by itself guarantee removal of separate Relay request or evidence records. Relay will not present an account deletion control as complete until that lifecycle is implemented and verified.
06
Your controls
You can review and correct your brief before calls begin, pause or cancel active work, change supported privacy preferences in Settings, download the account export currently provided there, and manage sign-in methods and sessions in Account security.
For a privacy or security concern, follow the safe reporting steps on the Support page. Never send passwords, verification codes, API keys, or full recordings to an unverified address.
About this notice
This is a product disclosure written for clarity, not legal advice. Calling, recording, consent, and retention requirements vary by jurisdiction and must be reviewed before live use.