Remiah

Privacy Policy

Last updated: October 23, 2026

Remiah is operated by RevSonar LLC, an Arizona limited liability company ("RevSonar," "we," "us," or "our"). This Privacy Policy explains what information we collect through the Remiah website, dashboard, and mobile app (together, the "Service"), how we use it, and the choices you have.

"You" refers to the service business that signs up for Remiah (the "Customer") and its authorized team members. Remiah also processes information about your callers on your behalf, as described below.

1. Information We Collect

Account and business information. When you sign up, we collect your name, email address, phone number, business name, business type, business address, and business hours.

Call recordings, transcripts, and lead data. Remiah answers calls on your behalf using an AI voice agent. We record and transcribe these calls and extract details such as the caller's name, phone number, reason for calling, and urgency, so the call can be turned into a lead in your dashboard. Remiah plays an automatic disclosure at the start of every call letting the caller know the call may be recorded — see "Call Recording & Consent" below.

Payment information. Subscription payments are processed by Stripe. We do not store your full card number — Stripe handles that directly, and we only retain the subscription and billing status needed to run your account.

Calendar and scheduling data. If you connect your device calendar in the iOS app, appointment details you create in Remiah are synced to that calendar through Apple's EventKit framework. We only store the appointment information needed to keep your dashboard and calendar in sync.

Push notification data. If you enable notifications in the iOS app, we store a device token issued by Apple so we can deliver new-lead alerts to your device.

Support communications. If you contact us or submit a support ticket, we collect what you send us so we can respond.

Usage and log data. We collect basic technical data — such as request logs and error reports — to operate, secure, and troubleshoot the Service.

2. How We Use Information

  • To provide, maintain, and improve the Service
  • To answer calls, capture leads, and schedule appointments on your behalf
  • To process payments and manage your subscription
  • To send you service notifications, such as new-lead alerts and billing receipts
  • To provide customer support
  • To detect, investigate, and prevent fraud, abuse, and security incidents
  • To comply with legal obligations

We do not sell your information or your callers' information, and we do not use it for third-party advertising.

3. How We Share Information

We share information with the service providers who help us run Remiah, each of whom is only permitted to use it to provide their service to us:

  • Supabase — authentication and database hosting
  • Retell AI — the voice platform that answers, records, and transcribes calls, and stores the recordings
  • Anthropic — reads each call transcript to produce the structured lead, and powers the in-app assistant
  • MiniMax — speech synthesis for the receptionist's voice and greeting previews
  • Google — Calendar availability and sync where you connect it, and push notification delivery to Android devices
  • Apple — push notification delivery to iPhones and iPads, and, if enabled, device calendar sync
  • Housecall Pro — only if you connect it, to sync customers and jobs with your account there
  • Stripe — payment processing and subscription billing
  • Resend — transactional email delivery (receipts, notifications, password resets)
  • Twilio — text messages to your customers: their booking confirmation and, if you turn it on, the review request. Twilio receives the customer's phone number and the message text
  • Sentry — error reporting, if enabled. Configured not to send request bodies, headers or user identifiers
  • Render and Vercel — application and website hosting
  • Plausible — cookie-less, anonymous page analytics on the public website only, if enabled. It never runs inside your dashboard and holds no personal data

We may also disclose information if required by law, to protect the rights and safety of Remiah, our customers, or the public, or in connection with a merger, acquisition, or sale of assets.

Text messages. When a customer books with a business that uses Remiah and gives their phone number on the call, Remiah may send that customer a text confirming the booking and, if the business has turned it on, one request for a review. Each text names the business it is sent for and says how to stop. We do not sell or share your SMS opt-in data or personal information with third parties for marketing purposes. No mobile information, phone numbers, or SMS opt-in consent will be shared with third parties or affiliates for marketing or promotional purposes. The messages are sent by Remiah, a service of RevSonar LLC, through Twilio, named above, solely to deliver them.

4. Call Recording & Consent

U.S. law on recording phone calls varies by state. Under the federal Wiretap Act, only one participant in a call needs to consent for a recording to be lawful, and courts have long recognized that the party operating the recording system — here, Remiah, acting on your behalf — can be that one participant. Most states follow this "one-party consent" rule.

A smaller group of states require that every participant in a call be notified, with an opportunity to decline, before it is recorded — often called "all-party" or "two-party consent" states. States commonly identified this way include California, Connecticut, Delaware, Florida, Illinois, Maryland, Massachusetts, Michigan, Montana, Nevada, New Hampshire, Pennsylvania, and Washington. (State law changes over time and how it applies can depend on the specific facts of a call; this list is provided for general awareness, not as a legal conclusion about any particular state or call.)

To help meet notice requirements in all-party consent states, Remiah automatically speaks a disclosure — "This call may be recorded for quality and training purposes." — at the very start of every call it answers, before any conversation about the caller's request begins. This disclosure is built directly into the system: it cannot be turned off, shortened, or overridden by a Customer's custom greeting. A caller who continues the call after hearing the disclosure is treated as having received notice and had the opportunity to decline.

This mechanism is designed to support compliance across the states where Remiah is commonly used, but it does not eliminate the need for you, as the Customer, to understand how call-recording law applies to your specific business — for example, if you operate in, advertise in, or route calls involving multiple states. See "Call Recording & Your Compliance Responsibilities" in our Terms of Service for more detail. We encourage you to consult an attorney licensed in your state if you have questions about how these laws apply to your business.

5. Data Retention

We retain account, call, and lead data for as long as your account is active, and for a reasonable period afterward to comply with legal, accounting, or dispute-resolution needs. You can request deletion of your account data at any time by contacting us at privacy@remiah.ai.

6. Health-Related Information

Remiah answers calls for medical, dental, veterinary and other offices. When a caller describes why they are booking, that description is recorded, transcribed, summarised and stored in the same way as any other call, and is handled by the service providers listed in section 3 — including Retell AI, which records and transcribes the call, and Anthropic, which reads the transcript to produce the structured appointment record.

Remiah is not a HIPAA-covered entity and we do not currently offer a Business Associate Agreement. If your practice is a covered entity, that is a decision for you to make before using Remiah to answer patient calls, and we would rather you make it with this on the page than discover it afterwards.

Remiah's receptionist never assesses how serious or how urgent a medical, dental or veterinary problem is, and never gives advice of any kind. A caller describing something that could be an emergency is told to hang up and call 911, and no appointment is booked. This is enforced in the product rather than requested of it: an office account cannot record a call as high-urgency or as an emergency at all.

7. Data Security

We use industry-standard safeguards — including encryption in transit, access controls, and audited third-party infrastructure — to protect information. No method of transmission or storage is completely secure, and we cannot guarantee absolute security.

8. Your Choices & Rights

You can access, correct, or request deletion of your account information at any time from your Remiah dashboard settings, or by emailing privacy@remiah.ai. Depending on where you live, you may have additional rights under laws such as the California Consumer Privacy Act. We'll honor verified requests consistent with applicable law.

Stopping texts. If you receive a text from Remiah on a business's behalf, reply STOP to that number and you will not be texted again; reply HELP for assistance. Message and data rates may apply. A business can switch customer texts off for its whole account in Settings.

9. Children's Privacy

Remiah is a business tool and is not directed to, or knowingly used to collect information from, children under 16.

10. Changes to This Policy

We may update this Privacy Policy from time to time. If we make material changes, we'll update the "Last updated" date above and, where appropriate, notify you directly.

11. Contact Us

RevSonar LLC (d/b/a Remiah)
Phoenix, Arizona, United States
privacy@remiah.ai