Legal

Privacy Policy

This policy describes what information Tradesphone collects, how we use it, who we share it with, and the choices you have. We've tried to write it in plain English. Where lawyers required us to use exact phrasing, we did, but the bulk of this is meant to be read by humans.

Effective May 11, 2026.

01Summary in plain English

Tradesphone is an AI receptionist for trades businesses (plumbers, HVAC technicians, electricians, and similar). When a contractor signs up, we provide a phone line and an AI agent that answers their calls, books appointments, and sends text confirmations.

For contractors who use the service: we collect the information you give us at signup (your name, email, business details, payment method) and the operational data the service produces on your behalf (calls, texts, bookings, leads, calendar entries).

For people who call or text a contractor: we process the audio, transcript, and text content of those interactions on the contractor’s behalf so they can return the call, fulfill the appointment, or follow up. The contractor — not Tradesphone — decides what happens with that data, including whether calls are recorded.

We don’t sell personal information. We don’t use customer call recordings to train AI models. We use a small number of named subprocessors (listed below) to actually run the service.

02Who this policy is from

Tradesphone is a product of Ridgetech LLC (“Ridgetech,” “Tradesphone,” “we,” “us”), a Delaware limited liability company. Our contact details are at the bottom of this page.

This policy covers tradesphone.com, the Tradesphone web dashboard, the Tradesphone API, and the inbound call and SMS service we operate on behalf of contractor customers.

03Information we collect

From contractors who sign up

  • Account information — name, email, password (hashed and managed by our authentication provider).
  • Business profile — business name, trade type, timezone, service area zip codes, working hours, services offered, voice preferences, language settings.
  • Payment information — billing address and partial card details (last four digits, expiration). Full card numbers are never sent to or stored by Tradesphone; they are handled directly by Stripe.
  • Compliance information — for SMS registration (10DLC), we collect your legal business name, EIN/tax ID, business type, intended use case, and your stated opt-in process. This is required by U.S. wireless carriers before any business text can be sent.
  • Calendar OAuth tokens — if you connect Google or Microsoft calendar, we receive an access token that lets us read free/busy information and create the events the AI books. Tokens are encrypted at rest.

From people who call or text a contractor

  • Caller phone number and inbound metadata (time, duration, geographic area code).
  • Call audio and transcripts — when the contractor has enabled call recording in their settings, the call audio is captured and an automatic transcript is generated. Before recording starts, an audible disclosure is played to the caller. When recording is disabled, no audio is stored and only the transcript that the AI uses in real time is retained.
  • SMS content — text messages exchanged with the contractor’s Tradesphone number.
  • Information the caller volunteers — name, service address, problem description, scheduling preferences. We process this on the contractor’s behalf so they can deliver the service.

Automatically

  • Service logs — request/response metadata, errors, IP addresses of dashboard logins. Used for security, debugging, and abuse detection.
  • Cookies — essential session cookies for keeping you signed in. We do not use third-party advertising cookies.

04How we use information

We use the information above only for the following purposes:

  • To provide the Tradesphone service to the contractor who hired us.
  • To process payments, send invoices, and manage the contractor’s subscription.
  • To deliver inbound calls and texts to the AI and route results back to you.
  • To generate the dashboard reporting (lead counts, conversion rates, busiest times) the contractor sees in their own account.
  • To detect and prevent fraud, spam, abuse, and violations of our Terms of Service.
  • To comply with legal obligations (tax, audit, lawful requests from authorities).
  • To improve the product. We do not use the audio of any customer call, the content of any SMS, or the contents of any transcript to train AI models — ours or any third party’s. Aggregate, non-identifying metrics (e.g. “average call duration across all accounts is X seconds”) may be used internally to size capacity and improve the product.

05How we share information

We share information only in the following circumstances:

  • With our subprocessors — the named vendors in the list below, only as needed to deliver the service.
  • With the contractor whose number was called — every caller’s number, transcript, and any details shared during the call are visible to that contractor in their dashboard. That is the whole point of the service.
  • When required by law — valid subpoenas, court orders, or law-enforcement requests, where we have a good-faith basis to comply. We’ll push back on overbroad requests where we can.
  • During a business transfer — if Ridgetech is acquired or merges, customer data may transfer to the new owner subject to this policy.

We do not sell personal information. We do not share it with advertisers. We do not rent it. We do not trade it.

06Subprocessors

To deliver the service we rely on the following named subprocessors. Each handles a specific function and is bound by its own data-protection terms.

VendorPurposeData
TwilioTelephony and SMS deliveryPhone numbers, call audio, SMS content
Retell AIReal-time AI voice agentCall audio, transcripts, agent context
AnthropicLLM used inside the agentTranscript turns at inference time
DeepgramSpeech-to-textCall audio
CartesiaText-to-speechAI response text
SupabaseDatabase and file storageAccount data, transcripts, recordings
StripePayments and subscription billingBilling details, payment method (card data never touches us)
ClerkUser authenticationEmail, hashed password, session tokens
InngestBackground jobs (reminders, summaries)Job payload metadata
ResendTransactional emailRecipient email, message content
Google Cloud (Calendar API)Calendar sync — optionalOAuth access token, free/busy windows, events we create
Microsoft (Graph API)Calendar sync — optionalOAuth access token, free/busy windows, events we create
Sentry / AxiomError and request loggingStack traces, request metadata (no message content)

If we add or replace a subprocessor, we’ll update this list before the change takes effect. Customers on a written agreement that requires advance notice will get email notification.

07How long we keep information

  • Call recordings: retention is controlled by the contractor in their settings, between 7 and 365 days. Default 90 days. Deleted automatically once retention expires.
  • Call transcripts and summaries: retained for the life of the contractor’s account.
  • SMS message content: retained for the life of the contractor’s account.
  • Account, booking, lead, and reporting data: retained for the life of the account and for 30 days after cancellation to allow for re-subscription. After 30 days post-cancellation, all customer data is permanently deleted, except where retention is required by law (e.g. tax records for invoiced periods).
  • Opt-out records: when a person texts STOP (or any standard opt-out keyword), we retain their phone number on a do-not-text list indefinitely. This is required to honor the opt-out.

08How we protect information

  • All data in transit is encrypted with TLS 1.2 or higher.
  • All data at rest in our database is encrypted at the storage layer. Calendar OAuth tokens are additionally encrypted at the application layer using AES-256-GCM.
  • Access to production systems is restricted to authorized personnel.
  • We use row-level security in our database so a contractor’s data cannot be read by code running on behalf of another contractor.
  • We’re a small company. No security program eliminates risk. If you suspect a security issue, email security@tradesphone.com.

09Your rights and choices

If you are a contractor with a Tradesphone account, you can do the following at any time from your dashboard or by emailing us:

  • Access — see the information we hold by visiting the dashboard or by exporting a full ZIP archive from Settings → Billing → Data export.
  • Correct — update any information from Settings.
  • Delete — cancel your subscription and we will delete all account data 30 days later. You may also email us for immediate deletion.
  • Port — the export is a portable archive of leads, bookings, calls, transcripts, and a recording manifest in CSV and JSON.
  • Complain — if you believe we’ve mishandled your information, contact us first; you also have the right to complain to your state attorney general.

If you are a caller or customer of a contractor (not a Tradesphone account holder) and want a copy of, or deletion of, information held on your behalf, contact the contractor whose number you called. They control that data. We will help where we can; we cannot delete a record without the contractor’s consent.

10California residents (CCPA / CPRA)

If you live in California, the California Consumer Privacy Act gives you specific rights. Below are the disclosures the law requires:

  • Categories of personal information collected in the last 12 months: identifiers (name, email, phone number), commercial information (subscription transactions), audio/electronic information (call recordings, transcripts, SMS), internet activity (service logs).
  • Sources: directly from the contractor customer, from callers/texters interacting with the service, and automatically from logs.
  • Business purposes: to deliver the service, process payments, prevent fraud, comply with law (see Section 4).
  • Sale of personal information: we do not sell personal information and have not in the past 12 months.
  • Sharing for cross-context behavioral advertising: we do not share personal information for behavioral advertising.

California residents can exercise their access, deletion, correction, and opt-out rights by emailing privacy@tradesphone.com. We’ll respond within 45 days.

11Children

Tradesphone is a B2B service for trades businesses. It is not directed at children under 16 and we do not knowingly collect personal information from anyone under 16. If you believe we have, contact us and we’ll delete it.

12Changes to this policy

We’ll update this policy when we make material changes to how we handle information — for example, when we add or replace a subprocessor, when we change retention periods, or when laws require new disclosures. For material changes, we will email contractor customers and post a notice in the dashboard at least 14 days before the change takes effect. For minor edits we’ll update the “effective date” at the top of this page.

13Contact us

Ridgetech LLC, attn: Privacy.
Email: privacy@tradesphone.com (privacy questions), support@tradesphone.com (everything else).

Questions? Email support@tradesphone.com and a real person will get back to you.