← Remedy Automation

Privacy Policy

Last updated: July 10, 2026

Remedy Automation LLC (“Remedy Automation,” “we,” “us,” or “our”) provides an AI phone-receptionist service that answers calls for small service businesses, captures the caller’s request, and helps schedule appointments. This Privacy Policy explains what information we collect, how we use it, and the choices you have. We are based in Cape Coral, Florida, USA.

Information we collect

From the businesses that use our service (our subscribers): your name, business name, email address, phone number, business address, and billing details. Payments are processed by our payment provider (Stripe); we do not store full payment-card numbers.

From people who call a business that uses our service: when you call a business that uses Remedy Automation, our AI receptionist may collect your name, your phone number, the service or reason for your call, any appointment details, and a recording and/or transcript of the call so the business can follow up and book the job.

How we use information

• To answer and route calls and capture and deliver leads to the business you called.
• To schedule and manage appointments.
• To send service-related text messages — appointment confirmations, reminders, and related two-way replies — only to people who have opted in, and to send lead and booking alerts to the business owner about their own calls.
• To provide, maintain, secure, and improve the service, and to comply with law.

Mobile information and text messaging

Mobile phone numbers and SMS opt-in consent are used solely to send the text messages you agreed to receive (appointment confirmations, reminders, the related CONFIRM/CANCEL/RESCHEDULE replies, and account or lead alerts to business owners).

We do not sell your information, and we do not share mobile opt-in information or phone numbers with third parties or affiliates for their own marketing or promotional purposes. Information you provide when opting in to text messaging is not shared with any third parties for marketing. You can opt out of text messages at any time by replying STOP; see our SMS Terms & Conditions.

Google Calendar data

If a business connects its Google Calendar, Remedy Automation uses the Google Calendar API (the calendar.events scope) for two features: appointment booking — checking the business’s availability and creating appointment events when our AI books a caller’s job — and the business’s own owner assistant, which can answer the owner’s questions about their own calendar. We request the least-privileged scope needed for these features, we never access a calendar unless the business connects it, and we only read or change calendar events as described in this section.

Booking: when checking availability, each calendar event is reduced on our servers to only its start and end time — event titles, descriptions, attendees, and other contents are discarded and never stored (a ZIP code may be derived from the event location to plan travel time before the location is discarded). During booking, our AI provider receives only the resulting list of open appointment times (for example, “Tuesday at 2:00 PM”) — callers never receive, and the booking AI is never sent, any calendar event content. The only calendar events booking creates are the appointments callers book.

Owner assistant: if the business owner asks their own assistant about their own calendar (for example, “what’s on my calendar Thursday?”), the times and titles of the owner’s events are shared with our AI provider solely to answer that owner’s request. This content is processed transiently, is not stored by us, is shown only to the authenticated business owner, and is never used to train any AI model. At the owner’s explicit request, the assistant can also add, move, or remove an event on the owner’s own calendar; these owner-initiated changes — plus the booking writes above — are the only changes we ever make to a connected calendar.

The Google authorization (refresh token) is encrypted at rest and used only to provide these features. A business can disconnect at any time from its dashboard, which revokes our access and deletes the stored token.

Remedy Automation’s use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. We do not use Google user data for advertising, and we do not sell it.

Google Docs, Sheets, and Slides

Separately and optionally, a business owner can let their assistant work with specific Google Docs, Sheets, and Slides that the owner chooses. The owner registers a file by pasting its link on their dashboard (or in a chat with the assistant); the assistant can then read that file to answer the owner’s own questions about it — for example, “what’s the price on my rate sheet?” We request access to individual files the owner registers, and do not request permission to browse, list, or search the owner’s Google Drive; the assistant can only reach a file the owner has explicitly given it.

File content is shared with our AI provider solely to answer the owner’s request, is processed transiently, is not stored by us, is shown only to the authenticated owner, and is never used to train any AI model. At the owner’s explicit request the assistant can also edit a file the owner registered (for example, add a row to their own rate sheet); every edit is proposed first and applied only after the owner confirms it, and is recorded in the owner’s activity log. We never create or delete files, and the same Google authorization described above — encrypted at rest, revocable by disconnecting — governs this access.

Microsoft 365 data (Outlook calendar, email, and OneDrive files)

A business can also connect a Microsoft 365 / Outlook account. Calendar access (the delegated Calendars.ReadWrite permission) works exactly like the Google Calendar access above: the same booking minimization (events reduced to start and end time; the booking AI never receives event content) and the same owner-assistant behavior (event times and titles shared with our AI provider only to answer the owner’s own request, never to train any AI model).

Separately and optionally, the owner can grant their assistant access to their own Outlook email and OneDrive files. Message and file content is used only when the owner asks their assistant to find, read, or act on something of their own — the relevant content is shared with our AI provider solely to answer that request, processed transiently, not stored by us, shown only to the authenticated owner, and never used to train any AI model.

What the assistant may do depends on what the owner grants. Reading only (Mail.Read, Files.Read) lets it find and summarize. If the owner also grants sending and editing (Mail.Send, Files.ReadWrite, Contacts.Read), the assistant can send an email from the owner’s own mailbox and edit the owner’s own documents — but only when the owner explicitly asks it to, and each such action is recorded in the owner’s activity log. It never emails the owner’s contacts on its own initiative.

The Microsoft authorization (refresh token) is encrypted at rest. A business can disconnect at any time from its dashboard, which deletes the stored token.

How we share information

We share information only with service providers who help us operate the service, and only so they can perform that work for us — for example:

• Twilio — telephone calls and text messaging;
• Anthropic (Claude) — the AI that understands the conversation and decides how to handle the call; if Anthropic is temporarily unavailable, the request is failed over to OpenAI as a backup;
• Deepgram and ElevenLabs — speech‑to‑text and text‑to‑speech for the voice call;
• Google — calendar scheduling, the owner-assistant calendar features, and (optionally) reading and editing specific Docs, Sheets, or Slides the owner registers, only if the business connects its Google account;
• Microsoft — the same, plus optional read-only owner email and file access, only if the business connects a Microsoft 365 / Outlook account;
• Voyage AI (operated by MongoDB) — converts a business’s uploaded documents and the caller’s question into a numerical form (an “embedding”) so the AI can answer from the most relevant passage, only if the business enables the Knowledge Base add-on;
• Nylas — brokers the connection to a business’s Gmail account, and holds the authorization for it, only if the business connects Gmail;
• Postmark (operated by ActiveCampaign) — delivers the email we send to a business and, where applicable, to its customers;
• Render — hosts the service and its database;
• Stripe — payment processing.

These providers are permitted to use the information only to provide their service to us. We do not sell personal information. We may also disclose information if required by law or to protect our rights, users, or the public.

Data retention and security

We keep information for as long as needed to provide the service and for legitimate business or legal purposes, then delete or de-identify it. We use reasonable administrative and technical safeguards to protect information; no method of transmission or storage is 100% secure.

Your choices

• Text messages: reply STOP to any message to opt out, or HELP for help.
• Access or deletion: email us at the address below to request access to, or deletion of, the personal information we hold about you.

Children

Our service is for businesses and their customers and is not directed to children under 13, and we do not knowingly collect their information.

Changes to this policy

We may update this Privacy Policy from time to time. We will post the updated version here with a new “Last updated” date.

Contact us

Remedy Automation LLC
Cape Coral, Florida, USA
Email: bryan@remedyautomation.com

© 2026 Remedy Automation LLC · Cape Coral, Florida