CallRetriever — Privacy Policy

Effective date: May 25, 2026

This Privacy Policy explains how Plains Automation Works LLC ("Plains Automation Works," "PAW," "we," "us," or "our") collects, uses, stores, shares, and protects information in connection with CallRetriever (the "Service").

CallRetriever is a missed-call response platform for tradespeople, home-service businesses, field-service businesses, and similar local service providers. The businesses that use CallRetriever are referred to as "Subscribers." People who call a Subscriber's business number and receive or reply to a text message through CallRetriever are referred to as "Callers."

1. Scope and privacy roles

CallRetriever is used by Subscribers to respond to their own missed, unanswered, busy, or after-hours inbound calls. The Subscriber is generally the business responsible for its relationship with Callers and the sender of messages sent through the Service.

PAW provides CallRetriever as a platform provider and service provider to Subscribers. PAW processes Caller information as reasonably necessary to provide, operate, support, secure, and document the Service. PAW may also process limited Subscriber and Caller information for PAW's own legal, security, fraud-prevention, telecommunications, carrier, A2P 10DLC, service-administration, dispute-resolution, and compliance purposes.

If a Caller contacts PAW with an access, deletion, correction, or privacy request related to a Subscriber's customer relationship, PAW may direct the Caller to the applicable Subscriber where appropriate. PAW may directly honor STOP requests, opt-outs, wrong-number notices, suppression requirements, and legal or compliance obligations.

2. Information we collect

We may collect and process the following categories of information.

Subscriber business information

  • Legal business name;
  • DBA, trade name, or public sender name;
  • entity type;
  • business address;
  • EIN, tax ID, or similar registration information if applicable;
  • business phone number;
  • business email address;
  • website URL or public business profile URL;
  • business category and service description;
  • customer privacy policy URL and terms URL, if provided;
  • onboarding certifications, prohibited-use certifications, and non-marketing-use certifications.

Authorized representative information

  • Representative name;
  • title or role;
  • email address;
  • phone number;
  • authority certification;
  • timestamps, account identifiers, and certification versions.

Phone number and configuration information

  • Assigned CallRetriever numbers;
  • whether a number is PAW-provided or Subscriber-ported;
  • forwarding destination numbers;
  • number validation records;
  • call routing and forwarding configuration;
  • port-in and port-out records;
  • Twilio subaccount, customer profile, Brand, Campaign, Messaging Service, and related provider identifiers.

Call and message information

  • Caller phone numbers;
  • inbound call timestamps;
  • call status, such as missed, busy, unanswered, no-answer, or after-hours context;
  • Twilio Call SIDs or similar provider identifiers;
  • SMS send timestamps;
  • Twilio Message SIDs or similar provider identifiers;
  • delivery status, error codes, filtering indicators, and related metadata;
  • message body text during the applicable retention period;
  • approved template ID and version;
  • template variables needed to send, reconstruct, support, or document messages.

Opt-out, HELP, START, wrong-number, and suppression information

  • STOP, HELP, START, opt-out, revocation, and related message content;
  • Twilio or provider opt-out types where available;
  • natural-language opt-out signals;
  • wrong-number and reassigned-number notices;
  • suppression-list entries;
  • reason codes, timestamps, applicable Subscriber, applicable number, and related message identifiers;
  • confirmation-message records where applicable.

Compliance, evidence, and operational records

  • Customer-specific SMS disclosure page records;
  • template approval records;
  • A2P 10DLC registration records;
  • carrier/provider review records;
  • complaint records;
  • evidence-request records;
  • suspension, pause, reactivation, and termination records;
  • forwarding-failure records;
  • audit logs and administrative review notes.

Support, billing, and communications information

  • Emails, support messages, chat messages, forms, and phone-call notes;
  • billing contact information;
  • payment status and invoice records;
  • account notices and operational communications.

Technical and security information

  • IP addresses;
  • browser, device, operating-system, and log information;
  • authentication and session records;
  • error logs;
  • security, abuse-prevention, and diagnostic records.

3. How we use information

We may use information to:

  • provide, operate, maintain, and improve CallRetriever;
  • detect missed, busy, unanswered, and after-hours inbound calls;
  • send approved non-marketing missed-call SMS responses;
  • forward calls and route communications;
  • relay Caller replies to Subscribers;
  • process STOP, HELP, START, opt-out, wrong-number, reassigned-number, and suppression requests;
  • prevent unwanted messages;
  • verify Subscriber identity, authority, business category, and use case;
  • support A2P 10DLC, carrier, telecommunications, and provider registration;
  • create and maintain customer-specific SMS disclosure pages;
  • approve and version message templates;
  • enforce cooldown, deduplication, suppression, and compliance controls;
  • monitor forwarding destination health and message deliverability;
  • respond to support requests and troubleshoot issues;
  • investigate complaints, filtering, suspicious activity, provider requests, legal demands, or compliance concerns;
  • pause, suspend, disable, reactivate, or terminate messaging when appropriate;
  • maintain records needed for compliance, security, dispute resolution, and enforcement;
  • invoice Subscribers and administer accounts;
  • comply with applicable law, provider requirements, carrier rules, and legal process;
  • protect Callers, Subscribers, PAW, service providers, carriers, and the public.

We do not use Caller phone numbers, Caller SMS consent data, or Caller message content for CallRetriever marketing.

4. SMS privacy and mobile information

CallRetriever sends SMS messages only as part of the Subscriber's non-marketing missed-call follow-up use case. Mobile information collected for SMS purposes is used to provide the Service, honor opt-outs, support compliance, prevent abuse, and maintain records.

We do not sell Caller phone numbers or SMS opt-in/opt-out information. We do not share Caller mobile information with third parties for their own marketing or promotional purposes. No mobile information, SMS opt-in data, or SMS consent data will be shared with third parties, affiliates, or lead generators for marketing or promotional purposes.

We may share mobile information with service providers, telecommunications providers, carriers, compliance providers, cloud providers, and other vendors as needed to provide, secure, support, document, and comply with the Service.

5. Service providers and subprocessors

We may use service providers and subprocessors to provide, host, secure, support, analyze, document, and administer the Service. These may include telecommunications providers, messaging providers, cloud hosting providers, storage providers, email providers, payment processors, compliance providers, analytics providers, security providers, and professional advisers.

Examples may include Twilio for telephony and messaging, cloud infrastructure providers for hosting and storage, Microsoft 365 or similar providers for business communications, GitHub or similar providers for software operations, and professional advisers for legal, tax, accounting, or compliance support.

Service providers may process information only as needed to provide services to us, comply with law, protect their services, or support telecommunications, carrier, or compliance requirements.

6. How Callers receive messages

A Caller may receive an SMS through CallRetriever only after placing a fresh inbound call to a Subscriber's assigned business number and the call is missed, unanswered, busy, or handled through an approved after-hours context.

The message is sent by or on behalf of the Subscriber and is intended to help the Subscriber follow up on the Caller's own inquiry.

The default automated-message cooldown is no more than one automated missed-call response per Subscriber/Caller pair within a rolling twenty-four (24) hour period unless the Caller replies or continues the conversation.

Approved message templates must identify the Subscriber's business name and include STOP, HELP, and message/data-rate disclosures.

7. Opt-out, HELP, START, wrong-number, and suppression handling

Callers may reply STOP to opt out of further SMS messages from the applicable Subscriber through CallRetriever. Callers may reply HELP for help. Callers may reply START or a similar supported phrase to opt back in, where lawful, technically supported, and consistent with provider requirements.

We may also treat STOPALL, UNSUBSCRIBE, CANCEL, END, QUIT, REVOKE, OPT OUT, natural-language opt-out requests, wrong-number replies, reassigned-number notices, and similar statements as opt-out or suppression requests.

Suppression is generally scoped to the applicable Subscriber and Caller phone number. Once suppressed, automated and manual outbound SMS/MMS through CallRetriever will be blocked for that Subscriber/Caller combination unless a valid re-opt-in occurs.

We may retain opt-out, wrong-number, reassigned-number, and suppression information as long as reasonably necessary to honor the request and prevent future unwanted messages.

8. Reassigned numbers and forwarding destination controls

Because CallRetriever's automated messages are triggered only by fresh inbound calls, CallRetriever does not routinely check the FCC Reassigned Numbers Database or similar reassigned-number services for the missed-call response use case unless PAW determines that such checks are required or appropriate for a particular use case, customer, volume, complaint history, or legal requirement.

We may process number-validation records, call-forwarding configuration records, forwarding-failure records, wrong-number notices, reassigned-number notices, suppression records, and related audit logs to operate the Service, prevent unwanted messages, troubleshoot forwarding issues, maintain service reliability, comply with law and carrier requirements, and document compliance.

If a forwarding destination number appears invalid, unsupported, deactivated, unreachable, or repeatedly fails, we may retain related records and may pause or disable messaging for the applicable Subscriber until the configuration is corrected and revalidated.

9. Data minimization and sensitive information

We design CallRetriever to collect and process only the information reasonably needed to provide missed-call follow-up, route communications, support opt-out handling, maintain compliance records, troubleshoot service issues, prevent abuse, and operate the Service.

CallRetriever message templates are intended to ask Callers only for a brief description of the job or service request and preferred contact method.

Callers should not send Social Security numbers, government identification numbers, driver's license numbers, payment card numbers, bank account numbers, passwords, access credentials, medical or health information, insurance claim documents, information about minors, emergency or urgent safety information, firearms or weapons information, regulated goods information, photos, documents, attachments, or other sensitive information through CallRetriever.

Subscribers must not use CallRetriever to request, solicit, or encourage Callers to send unnecessary, sensitive, regulated, prohibited, or high-risk information.

If sensitive information is submitted despite these instructions, we may process it only as needed to provide the Service, maintain security, comply with law, enforce our Terms, investigate abuse, preserve compliance records, or protect legal rights. We may delete, restrict, or decline to process sensitive information where appropriate.

10. MMS and media attachments

CallRetriever currently supports SMS text messaging only unless PAW separately enables MMS or media functionality for a Subscriber.

Unless MMS or media functionality has been expressly enabled, Callers should not send photos, images, videos, documents, attachments, or other media through CallRetriever, and Subscribers should not request them.

Before MMS or media functionality is enabled, PAW may require additional legal, privacy, security, carrier, A2P 10DLC, template, disclosure, retention, access-control, file-type, file-size, malware-scanning, and operational review.

If MMS or media functionality is enabled in the future, this Policy may be updated to explain media collection, storage, access, deletion, security, and retention practices.

11. No emergency use

CallRetriever is not for emergencies, urgent safety issues, 911, emergency dispatch, urgent response, medical emergencies, hazardous conditions, or critical notifications.

Callers should not use CallRetriever SMS to request emergency assistance or send urgent safety information. If a Caller has an emergency or needs immediate assistance, the Caller should call 911 or the appropriate emergency service.

12. Disclosure of information

We may disclose information:

  • to Subscribers, as needed to provide the Service and relay Caller inquiries;
  • to Callers, as part of STOP, HELP, START, or other service messages;
  • to telecommunications providers, carriers, messaging providers, A2P 10DLC registries, compliance vendors, and related service providers;
  • to hosting, storage, security, support, analytics, billing, and business operations providers;
  • to professional advisers, such as attorneys, accountants, auditors, and insurers;
  • to respond to legal process, regulatory inquiries, carrier/provider requests, complaints, investigations, or disputes;
  • to enforce our Terms, protect rights, prevent fraud, protect safety, secure the Service, or respond to suspected abuse;
  • in connection with a business transaction, such as merger, acquisition, financing, reorganization, or sale of assets;
  • with consent or at direction of the applicable Subscriber or individual.

13. Data retention

By default, CallRetriever deletes SMS/MMS message body text after sixty (60) days, unless a longer period is required or reasonably necessary for legal, carrier, telecommunications, platform, compliance, security, dispute-resolution, or business purposes.

We may retain ordinary call and message metadata for up to twenty-four (24) months.

We may retain SMS/MMS compliance records for at least four (4) years after the relevant message, event, account termination, campaign deactivation, number deactivation, or number port-out.

We may retain opt-out, revocation, wrong-number, reassigned-number, and suppression-list records for as long as reasonably necessary to honor those requests and prevent future unwanted messages.

We may retain A2P 10DLC registration records, customer-specific disclosure records, template approval and version records, Subscriber certification records, compliance evidence records, complaint records, suspension records, number-porting records, and related audit logs for as long as reasonably necessary for legal, compliance, security, dispute-resolution, business, or provider purposes.

If message body text has been deleted, Subscriber exports, support responses, legal responses, or Caller requests may be limited to retained metadata and compliance records.

14. Security and access controls

We use administrative, technical, and organizational safeguards designed to protect information from unauthorized access, loss, misuse, alteration, or disclosure.

Internal access to message body content is limited to operational, support, security, compliance, and legal needs. We may log administrative access where feasible.

No system can be guaranteed completely secure. Subscribers are responsible for maintaining secure account credentials, limiting access to their accounts, and promptly notifying PAW of suspected unauthorized access.

15. Children and minors

CallRetriever is not directed to children. Subscribers must not use CallRetriever to request information about minors or to operate services directed to minors without prior review and approval by PAW.

If we learn that information about a minor has been submitted in a way that creates privacy, safety, or compliance risk, we may delete, restrict, suppress, or otherwise handle the information as appropriate.

16. Caller and Subscriber choices

Callers may reply STOP to opt out of further SMS messages from the applicable Subscriber through CallRetriever. Callers may reply HELP for help.

Subscribers may update their business information, forwarding destination number, authorized representative, privacy/terms links, and configuration information through the Service or by contacting PAW.

Subscribers may request access to or export of available Caller conversation data and related records during the ordinary retention period, subject to account status, applicable law, and retained-data limits. Message body text may be unavailable after the 60-day default deletion period.

Privacy requests related to a Subscriber's customer relationship may be directed to the Subscriber. Requests related to PAW's platform handling may be directed to PAW using the contact information below.

17. Changes to this Policy

We may update this Policy from time to time. The current version, with its effective date, will be posted at the applicable CallRetriever or PAW webpage.

Continued use of the Service after an update means the updated Policy applies to information processed after the effective date, subject to applicable law.

18. Contact us

Questions about this Privacy Policy may be directed to:

Plains Automation Works LLC
Email: eric@plainsautomationworks.com
Phone: +1 (605) 610-1922