AI-Companies LLC d/b/a AI Remote Hire
Website: https://ai-remotehire.com/
Privacy Policy URL: https://ai-remotehire.com/privacy-policy/
Last Updated: February 4, 2026
This Privacy Policy and SMS/MMS Messaging Program Terms (this “Policy”) is issued by AI-Companies LLC, doing business as AI Remote Hire (“AI Remote Hire,” “Company,” “we,” “us,” “our”), and governs the collection, use, disclosure, retention, protection, and administration of information processed in connection with (i) our website located at https://ai-remotehire.com/ and any pages thereunder that we control (the “Site”), (ii) inbound and outbound communications through email, telephone, webforms, and other channels made available by us (collectively, “Communications”), and (iii) SMS/MMS text messaging activities conducted by or on behalf of the Company using application-to-person long-code messaging pathways and associated telephony and messaging infrastructure (including, where applicable, Zoom Phone or comparable providers), it being the intent of this Policy to define, with precision and operational detail, the consent pathways, disclosures, recordkeeping practices, opt-out mechanics, dispute handling, complaint handling, message-content governance, reassigned-number mitigation, and strict data-sharing restrictions applicable to SMS/MMS, such that an independent reviewer can verify compliance without reliance upon implication, custom, unwritten practice, or informal assurances.
1. Company Identification; Contact Information; Communications Channels
AI-Companies LLC d/b/a AI Remote Hire maintains a principal business address at 300 Spectrum Center Dr, Irvine, CA 92618, United States. The Company may be contacted via email at [email protected] and via telephone at (714) 650-1976 or (888) 668-3304. Communications may occur through channels including email, telephone voice calls, web-based forms, and SMS/MMS, and insofar as certain messaging compliance functions require prompt automated processing (including the processing of opt-out keywords and, where permitted, the sending of a single administrative confirmation), the Company may transmit or process limited administrative messages outside standard business hours, provided that such activity remains consistent with the consent scope and the requirements of Section 11 of this Policy.
2. Scope; Applicability; Covered Individuals; Covered Data
This Policy applies to (a) Site visitors, (b) persons communicating with the Company through Communications, (c) representatives of client organizations, prospective clients, and vendors interacting with the Company, and (d) any person whose mobile number receives or transmits SMS/MMS messages with the Company (a “Messaging Participant”), including circumstances in which a mobile number may have changed hands or been reassigned, in which case the Company’s opt-out mechanism remains available and the Company will take reasonable steps to prevent continued messaging once an opt-out is received or the Company becomes aware of an error. This Policy applies to Personal Information (as defined herein), Mobile Information (as defined herein), and Text Messaging Originator Opt-In Data and Consent (as defined herein), and shall govern both data elements actively provided by a user and data elements generated through operational logging and compliance administration, including delivery receipts, routing metadata, consent timestamps, and opt-out suppression state.
3. Third-Party Sites and Platforms; Service Providers Distinguished
This Policy does not apply to third-party websites, platforms, or services not controlled by the Company, even if linked from the Site. However, where third parties process information on behalf of the Company as Service Providers, such processing is authorized solely to provide services to the Company, and is subject to restrictions described in this Policy, including the strict limitations on Mobile Information sharing described in Section 10 and Section 19.
4. Business Description; Explicit Exclusions; Prohibited SMS/MMS Use Cases
The Company provides remote staffing, talent matching, and related business-to-business services. The Company does not operate a public job board, does not send mass consumer job alerts via SMS/MMS, does not purchase, rent, scrape, append, or otherwise obtain third-party lead lists for texting, and does not use SMS/MMS for disallowed or high-risk categories including illegal products, adult sexual content, hate or harassment, gambling, or high-risk financial products such as payday loans, and the Company does not authorize third parties to use the Company’s SMS/MMS capabilities for unrelated lead generation or affiliate marketing.
5. Definitions; Precision Terms Used for Compliance Verification
For purposes of this Policy, the following definitions apply, and shall be interpreted in a manner that favors transparency, user control, and compliance.
5.1 Personal Information
“Personal Information” means information that identifies, relates to, describes, is reasonably capable of being associated with, or could reasonably be linked, directly or indirectly, with a particular individual, household, device, or account, including where such information is defined as personal information or personal data under applicable law.
5.2 Mobile Information
“Mobile Information” means any information processed in connection with SMS/MMS messaging, including without limitation: a mobile telephone number; message content; timestamps; delivery receipts; routing data; opt-in and opt-out status; and records evidencing consent provenance and revocation.
5.3 Text Messaging Originator Opt-In Data and Consent
“Text Messaging Originator Opt-In Data and Consent” means the subset of Mobile Information that evidences whether, when, how, and under what disclosure context a mobile number opted in to receive SMS/MMS messages from the Company, including any data element which, alone or in combination, identifies a number as eligible or ineligible for messaging based on consent status, including opt-out suppression state.
5.4 Opt-In and Opt-Out
“Opt-In” means an affirmative action by which a person authorizes the Company to send SMS/MMS messages to a specified number under the disclosures and rules in Section 11 of this Policy, and “Opt-Out” means a request to stop receiving SMS/MMS messages, including through the opt-out keyword mechanism specified in Section 11.6.
5.5 Consent Capture Surface
“Consent Capture Surface” means the page, form, interface, script, recording, paper instrument, keyword prompt, or other medium by which Opt-In is obtained, and which medium must, for Opt-In to be treated as valid for the Company’s SMS/MMS purposes, be accompanied by the disclosures referenced in Section 11 and implemented through one of the specific paths described in Section 12.
5.6 Consent Record and Opt-Out Record
“Consent Record” means the record maintained by the Company evidencing Opt-In, including at minimum the mobile number, timestamp, opt-in path, and sufficient detail regarding the disclosure context to allow verification, and “Opt-Out Record” means the record maintained by the Company evidencing Opt-Out and subsequent suppression actions.
5.7 Service Provider
“Service Provider” means an entity that processes information on behalf of the Company to provide services such as hosting, telephony and messaging delivery, routing, compliance logging, security monitoring, analytics, and professional services, subject to restrictions described herein.
6. Categories of Information Collected
6.1 Information Provided Directly
The Company may collect information provided by you through Communications and forms, including name, business email address, company name, job title, phone number(s), inquiry content, scheduling preferences, and attachments or text you choose to provide.
6.2 Information Collected Automatically
When you use the Site, the Company may collect IP address, browser type, operating system, referring URLs, pages viewed, timestamps, and similar device and usage data; the Company may use cookies and similar technologies to operate the Site and measure aggregated usage.
6.3 Messaging-Related Information
When you participate in SMS/MMS, the Company processes Mobile Information, including the content of inbound and outbound messages, delivery and routing status, and Consent Records and Opt-Out Records necessary to administer the program and demonstrate compliance.
6.4 Information from Service Providers
Service Providers may provide operational data such as message delivery confirmation, error reports, spam or abuse signals, and system logs, and such data is used for administration, security, troubleshooting, and compliance recordkeeping.
7. Purposes of Processing; Use Limitation Principles
The Company processes Personal Information to operate the Site, respond to inquiries, schedule and manage consultations, provide services, maintain business records, prevent fraud and abuse, comply with legal obligations, and improve operations. The Company processes Mobile Information to send messages consistent with Opt-In, receive and respond to inbound messages, administer help requests and opt-out mechanics as defined in Section 11, maintain suppression state, and maintain Consent Records and Opt-Out Records sufficient to demonstrate compliance. The Company does not process Mobile Information for independent third-party marketing purposes, does not monetize Mobile Information, and does not treat Text Messaging Originator Opt-In Data and Consent as a transferable marketing asset.
8. Cookies and Similar Technologies
The Company may use cookies, pixels, local storage, and similar technologies to support essential Site functionality, maintain session continuity, analyze aggregate traffic patterns, and improve Site performance. You may control cookie behavior through browser settings, acknowledging that disabling certain cookies may impair Site functionality.
9. General Disclosure of Information; Permitted Sharing Categories
The Company may disclose Personal Information to Service Providers to the extent necessary for them to provide services to the Company (including hosting, communications delivery, analytics, security, and professional services), provided that such Service Providers are restricted from using the information for independent purposes. The Company may disclose information if required by law, legal process, or governmental request, or to protect rights, property, and safety, or in connection with a merger, acquisition, or asset sale, subject to lawful safeguards.
10. Absolute Prohibition on Mobile Information Sharing for Marketing or Promotional Purposes
Notwithstanding any other provision of this Policy, the Company does not sell, rent, license, disclose, transfer, or otherwise share Mobile Information, including Text Messaging Originator Opt-In Data and Consent, with any third party or affiliate for that party’s marketing, promotional, advertising, lead generation, or similar outreach purposes, and all other categories of sharing described in this Policy expressly exclude Text Messaging Originator Opt-In Data and Consent except to the limited extent strictly necessary for a Service Provider to deliver messages on the Company’s behalf under contractual and operational limitations that prohibit the Service Provider from using such data for its own marketing or promotional purposes. For avoidance of doubt and to satisfy carrier vetting expectations, the Company adopts the following exclusion statement exactly as written: No mobile information will be shared with third parties/affiliates for marketing/promotional purposes. All other categories exclude text messaging originator opt-in data and consent; this information will not be shared with any third parties
11. Authoritative SMS/MMS Program Disclosures and Mandatory Instructions
This Section 11 is the single authoritative location in this Policy containing the disclosures and instructions governing SMS/MMS participation; all other sections incorporate this Section 11 by reference and do not restate its required disclosure text.
11.1 Sender Identity
SMS/MMS messages are sent by AI-Companies LLC d/b/a AI Remote Hire.
11.2 Program Purpose
Messages may include responses to your inquiries, scheduling and appointment confirmations and reminders, rescheduling coordination, and service-related notifications consistent with the context of your request and the consent you provided.
11.3 Message Frequency
Message frequency may vary depending on your interactions with the Company and the nature of your inquiry or scheduling thread.
11.4 Rates
Message and data rates may apply depending on your carrier plan.
11.5 HELP
For assistance, reply HELP to any message, or contact [email protected], or call (888) 668-3304.
11.6 STOP
To opt out of further messaging, reply STOP to any message; after STOP is processed, the Company will cease sending SMS/MMS messages to that number except for a permitted confirmation of opt-out or any message required to comply with law or carrier obligations.
11.7 Privacy Policy Reference
Consent Capture Surfaces must refer to this Policy as the privacy policy governing messaging and must present “Privacy Policy” as a hyperlink to https://ai-remotehire.com/privacy-policy/ where technologically feasible, and where the Company uses a Contact Us form or similar form to collect phone numbers, the Company intends that the Privacy Policy hyperlink be presented on that form in a manner reasonably calculated to be noticed prior to submission.
12. Specific Paths for Mobile Opt-In; Deep Consent Mechanics; Exhaustive Scenario Handling
Opt-In is obtained through specific, documentable paths, and the Company’s compliance posture is that each path must be implemented so that (i) the Consent Capture Surface is identifiable and stable, (ii) the disclosures in Section 11 are presented in connection with the opt-in act in a manner reasonably calculated to be noticed and understood, and (iii) a Consent Record can be produced that ties the number to the opt-in act and disclosure context, such that an external reviewer can verify the consent pathway without requiring the reviewer to infer missing steps.
12.1 Website Form Submission Path (Web-Based CTA Path)
Where Opt-In is captured via webform, the Company’s required implementation is that the user enters a mobile number into the form, is presented on the same Consent Capture Surface with the disclosure text set forth in Section 13, and submits the form; ergo, the affirmative act constituting Opt-In is the submission action taken after the disclosure is presented, and the Company treats that submission as authorizing SMS/MMS only insofar as the disclosure was displayed in reasonable proximity to the submission action and the user had a meaningful opportunity to read it prior to submission.
12.1.1 Proximity and Presentation Requirements
The disclosure in Section 13 is intended to be presented near the phone field and or near the submit control in a manner that avoids being obscured by UI elements, overlays, footers, or collapsed content, and the Company’s compliance posture is that a disclosure hidden behind an additional click or placed materially distant from the consent action undermines verifiability and therefore should not be used as the sole disclosure at the moment consent is captured.
12.1.2 Multiple Forms; Separate Provenance
If the Company operates multiple forms and those forms accept phone numbers that may be used for SMS/MMS, each such form is treated as a distinct Consent Capture Surface for Consent Record purposes, whereby the Company endeavors to record which form, page path, and disclosure instance applied, because consent provenance is not satisfied by a generic claim that a number was obtained from the website where the user experience and disclosure placement may vary across forms.
12.1.3 Mandatory Versus Optional Phone Fields
If the phone field is mandatory for a particular workflow, the Company still treats Opt-In as conditioned upon the disclosure being present and the user submitting under that disclosure; if the phone field is optional, the Company does not treat the mere presence of the field as consent unless the user both provides the number and submits under the disclosure, and where a user leaves the phone field blank, the Company does not send SMS/MMS to that user solely because the user submitted the form.
12.1.4 Normalization and Validation
Because compliance is undermined by messages sent to incorrect recipients, the Company’s compliance posture is to implement reasonable formatting validation, normalize storage into a consistent format, and reject patently invalid inputs where feasible, and to store the normalized number as part of the Consent Record, recognizing that normalization is not a substitute for consent but is an operational control to minimize wrong-party texting risk.
12.1.5 Autofill and Stale Session Scenarios
Where browser autofill, cached values, or stale sessions could result in a number being submitted that the user did not intend to provide, the Company’s compliance posture is to implement reasonable mitigations where feasible and to treat wrong-party complaints arising from such scenarios as compliance signals warranting suppression and process review.
12.1.6 Numbers Belonging to Third Persons
If a user provides a number belonging to another person, the Company’s compliance posture is that the user should only provide numbers over which the user has authority to consent, and where the Company becomes aware that the number belongs to a third person who did not consent, the Company will treat the number conservatively, including suppression, because the compliance objective is to avoid messaging non-consenting recipients.
12.1.7 Free-Text Numbers and Attachments
If a user includes a number only in free-text fields or attachments without completing the specific opt-in act described in this Section 12.1, the Company’s compliance posture is to refrain from treating that number as opted in for SMS/MMS unless the user separately completes an Opt-In path consistent with this Policy, because a number appearing incidentally in content does not, without additional evidence, establish that the disclosures in Section 11 were presented and accepted.
12.1.8 Consent Checkbox Variants
Where a checkbox is used to strengthen affirmative express consent, the checkbox is intended to be unchecked by default and to clearly describe SMS authorization consistent with Section 11, and the Consent Record may include the checkbox state at submission; however, the Company does not treat a checkbox as a replacement for displaying the disclosure in Section 13 on the Consent Capture Surface.
12.2 Keyword Enrollment Path (Where Enabled)
Where the Company enables keyword enrollment, the Company’s compliance posture is that keyword enrollment is valid only when the user performs an affirmative act (sending the enrollment keyword) after being presented with the disclosures required by Section 11, and the Company maintains a Consent Record reflecting the inbound keyword, timestamp, receiving number, and the context in which the keyword enrollment was offered.
12.2.1 Solicitation Context Requirements
A keyword enrollment flow is treated as compliant only when the user has been informed of the program terms before enrolling, meaning that a keyword presented on a page, in print, or verbally must be accompanied by disclosures consistent with Section 11.
12.2.2 Ambiguous Inputs
If a user sends a message that is ambiguous, misspelled, or not clearly an enrollment command, the Company may respond with clarifying instructions that do not exceed the user’s apparent intent, and the Company may refrain from enrolling the number until a clear enrollment act is received.
12.2.3 Accidental Enrollment Claims
If a user claims accidental enrollment or indicates non-consent, the Company treats that communication as a request to stop messaging and applies suppression consistent with Section 15.
12.3 Inbound-First Path
Where the user initiates an inbound SMS/MMS message to the Company, the Company may respond to that inquiry because the user has chosen the channel; however, the Company construes such inbound initiation as authorizing a response within the scope of the user’s inquiry and does not construe it as perpetual authorization for unrelated messaging, and where ongoing outbound messaging is anticipated beyond fulfilling the immediate request, the Company will require a defined opt-in path yielding a Consent Record or a defined confirmation mechanism prior to continued outbound messaging.
12.3.1 Wrong Number Claims
If the recipient indicates they are not the intended party or that the number is incorrect, the Company treats that as a stop request in substance and suppresses the number in its systems.
12.3.2 Reassigned Number Scenario
If a number appears to have been reassigned, or if the recipient indicates that they did not opt in and have newly obtained the number, the Company will treat the number conservatively, including suppression.
12.3.3 Shared Corporate Phones
If inbound messages are received from shared corporate phones or switchboards, the Company may request a responsible party to confirm that the number is an appropriate channel for receiving Company messages.
12.4 Written Authorization Path
Where written authorization is obtained, such as through a service agreement, intake document, or electronic signature workflow, the Company’s compliance posture is that the written instrument shall include or incorporate the disclosures in Section 11, and the user’s signature or equivalent electronic assent shall constitute the Opt-In act, and the Consent Record shall connect the mobile number, the assent event, and the disclosure context in a manner that can be produced for review.
12.4.1 Authority to Consent for a Number
If a representative provides a number belonging to another person, the Company’s compliance posture is that the representative should only do so where the representative has authority to provide that consent, and where a dispute arises, the Company will suppress the number pending verification.
12.4.2 Document Retention and Minimization
If the written instrument contains information beyond what is necessary for consent proof, the Company may retain a redacted or minimized record sufficient to demonstrate consent while reducing unnecessary retention of unrelated personal data, provided that such minimization does not impair the Company’s ability to demonstrate compliance.
12.5 Verbal Authorization Path
Where verbal authorization is obtained, the Company’s compliance posture is that the disclosures in Section 11 must be conveyed to the consenting party during the call, that the consenting party must provide a clear affirmative response authorizing SMS/MMS contact, and that the Company must create a Consent Record sufficient to evidence what was disclosed and what the consenting party agreed to.
12.5.1 Recorded Calls
If the call is recorded, the Consent Record may include a recording identifier, date, time, and markers sufficient to locate the disclosure and the affirmative response; if the call is not recorded, the Company’s compliance posture is to document the consent contemporaneously, identifying the agent, the script used (or script identifier), the date and time, and the consenting party’s response.
12.5.2 Voicemail
The Company does not treat voicemail as a substitute for delivering disclosures and obtaining affirmative consent unless the voicemail itself contains an affirmative consent statement that is sufficiently clear and is accompanied by evidence that the user had the Section 11 disclosure context.
12.5.3 Language and Comprehension
If the Company has reason to believe the consenting party did not understand the disclosure due to language barriers or confusion, the Company will require a clearer written opt-in path.
12.6 Database Presence Is Not Consent
The Company recognizes that internal tools, CRM records, or contact syncing can associate numbers with profiles in ways that do not themselves establish messaging consent; accordingly, the Company’s compliance posture is that a number’s presence in a database is not treated as Opt-In absent a Consent Record.
13. Canonical Webform CTA Disclosure Text
Where a website form is used to capture SMS/MMS consent through submission, the following disclosure text must be displayed on the Consent Capture Surface in reasonable proximity to the phone number field or the submit action, and “Privacy Policy” must link to https://ai-remotehire.com/privacy-policy/ where technologically feasible:
“By providing a telephone number and submitting the form, you are consenting to be contacted by SMS text message and agreeing to our Privacy Policy. Message frequency may vary. Message and data rates may apply. Reply STOP to opt out of further messaging. Reply HELP for more information.”
14. Consent Records; Evidence Architecture; What Is Stored; How It Is Stored; Why It Is Stored
The Company maintains Consent Records for the purpose of demonstrating that Opt-In was obtained through a defined path and accompanied by the required disclosures in Section 11, and the Company’s design objective is that a Consent Record be sufficiently complete to allow verification while avoiding unnecessary collection of unrelated personal data.
14.1 Minimum Elements
The minimum elements the Company endeavors to retain, subject to technical feasibility and lawful limitations, include: the mobile number as normalized; the timestamp of the affirmative Opt-In act; the opt-in path identifier; the Consent Capture Surface identifier; and a disclosure version identifier linking the opt-in to the Section 11 disclosure framework.
14.2 Sequencing Evidence
The Company endeavors to retain evidence sufficient to show that messages were not sent prior to Opt-In and were ceased after Opt-Out, meaning that Consent Records, first-message logs, and Opt-Out Records may be logically linkable by time and number.
14.3 Change Control
The Company’s compliance posture is that Consent Records should be maintained in systems with access controls and change logging sufficient to detect unauthorized modifications, meaning that if a record is corrected, the system should preserve an audit trail showing what changed, when, and by whom.
14.4 Evidence of Disclosures
Where practical, the Company may preserve archived versions of the relevant form or script libraries to evidence the disclosure context at the moment of consent.
14.5 Access Controls
Consent Records are accessed only by personnel with legitimate operational, compliance, security, or dispute-resolution needs, and vendor access is scoped to what is necessary for service delivery.
15. Opt-Out Processing; Suppression State; Timing; Confirmation; Failure Modes; Edge Cases
Upon receipt of an Opt-Out request pursuant to Section 11.6, the Company will create an Opt-Out Record and apply a suppression state intended to prevent further messaging to that number, and the Company treats opt-out as a user-control mechanism that must be effective without burdensome steps.
15.1 Operational Sequence
Opt-out inputs are detected by the messaging system, converted into an Opt-Out Record, and applied to suppression logic that blocks further outbound messages to the number within the Company’s messaging workflows.
15.2 Processing Timing Standard
The Company processes Opt-Out as promptly as reasonably practicable given system constraints and endeavors to apply suppression quickly where platform controls support near real-time suppression, and otherwise within the period required by applicable law or mandatory platform rules, and where a transient outage delays propagation, the Company’s compliance posture is to treat the number as suppressed at the earliest possible point and to avoid discretionary sends during the delay.
15.3 Confirmation Messages
Where supported and permitted, the Company may send a single administrative confirmation acknowledging opt-out.
15.4 Opt-Out via Support Channels
If a user seeks opt-out via email or telephone, the Company will request the number to be suppressed and sufficient information to ensure the correct number is identified, because suppression operates on numbers; once identified, the Company applies suppression consistent with this Section 15.
15.5 Stop-Like Statements
If the user transmits a message that reasonably indicates a desire to stop messaging but does not use the opt-out keyword, the Company will treat that as Opt-Out in substance and apply suppression.
15.6 Multiple Systems
If the Company uses multiple sending numbers or system partitions, the Company’s compliance posture is to implement suppression across the Company’s messaging operations to the extent technically feasible.
15.7 Message-in-Flight
If a message is queued or in flight at the moment an Opt-Out is received, Opt-Out will prevent subsequent messages and the Company will not treat an occasional in-flight delivery as authorization to resume messaging.
16. Re-Enrollment After Opt-Out; Confirmation Mechanics; Conditions; Timing
If a user who previously opted out later requests renewed messaging, the Company treats re-enrollment as a new Opt-In requiring a new Consent Record captured through a defined opt-in path in Section 12, and the Company will require a confirmation act designed to ensure the person controlling the number is knowingly requesting renewed messaging.
16.1 Forms of Confirmation
Confirmation may be implemented through re-submission of a webform under Section 13, through completion of a keyword enrollment act where enabled, through an affirmative reply in response to a single enrollment confirmation prompt, or through documented written or verbal authorization that references the Section 11 disclosure framework.
16.2 When Confirmation Is Used
Confirmation is used where the Company deems it compliance-serving, including when the prior Opt-Out occurred via the keyword mechanism, when the Opt-Out is recent, when the request to re-enroll is ambiguous, when the request appears to come from a third party rather than the number owner, when the number appears to have changed hands, or when platform controls require explicit re-authorization after Opt-Out.
16.3 Activation Timing
Re-enrollment is effective only after the confirmation act is completed and recorded; until such confirmation is completed, the Company maintains suppression and refrains from sending further messages other than those strictly necessary to facilitate the confirmation step.
16.4 Expiration of Incomplete Re-Enrollment
If a re-enrollment request is initiated but not completed within a reasonable period set by the Company based on operational context, the Company will treat the request as stale and continue suppression until a new Opt-In act is completed.
17. Purpose Limitation; Scope Control; Content Consistency With Consent Context
Consent is treated as purpose-limited, meaning that messages are limited to the general purpose categories disclosed in Section 11 and reasonably expected based on the context in which the user provided consent, and the Company does not treat consent as authorization for unrelated promotional outreach.
18. Prohibited Sources of Numbers; No Purchased or Rented Lists; No Third-Party Lead Campaigning
The Company does not obtain mobile numbers for SMS/MMS from purchased, rented, scraped, appended, or brokered lists, does not buy SMS opt-ins, does not use shared opt-in lists, and does not authorize third parties to send messages using Company consent data for their own purposes. If the Company receives a number from a business client or representative, the Company’s compliance posture is that such number will not be messaged unless a valid Opt-In path exists for that number consistent with this Policy.
19. Service Providers for Messaging; Permitted Processing; Prohibited Uses; Subprocessors; Contractual Controls; Compliance Controls
The Company may use Service Providers to deliver and administer SMS/MMS messages, including telephony and messaging platforms, routing providers, compliance tools, and customer support systems, and such providers may process Mobile Information only to provide services to the Company, with processing scope limited to what is necessary to deliver messages, maintain delivery and Opt-Out status, prevent abuse, and maintain compliance logs.
19.1 Permitted Processing
Permitted processing includes message transmission, routing, delivery receipts, error handling, Opt-Out keyword recognition, help-response routing, number formatting and validation as necessary to deliver messages, and logging necessary to evidence compliance sequencing.
19.2 Prohibited Uses
Service Providers are not authorized to use Mobile Information or Text Messaging Originator Opt-In Data and Consent for their own marketing, promotional outreach, list building, audience creation, cross-client enrichment, or profiling unrelated to service delivery.
19.3 Subprocessor Governance
Where a Service Provider uses subprocessors, such subprocessors operate solely to deliver messages and maintain network integrity, and the primary Service Provider remains responsible for ensuring that subprocessor access to Mobile Information is limited to what is necessary and is not repurposed for marketing.
19.4 Contractual and Operational Controls
The Company’s compliance posture is to impose contractual controls requiring confidentiality, purpose limitation, security safeguards, and restrictions against independent marketing use, and to adopt operational controls such as least-privilege access and logging.
19.5 Incident Handling
If a Service Provider experiences a security incident involving Mobile Information, the Company expects notification consistent with contractual terms and applicable law, and the Company will investigate, remediate, and take steps to prevent recurrence.
20. Retention; Deletion; Compliance-Driven Preservation
The Company retains Personal Information for as long as reasonably necessary to fulfill the purposes described in this Policy, including service delivery, legal compliance, dispute resolution, and security.
20.1 Consent and Opt-Out Records
Consent Records and Opt-Out Records are retained for a period reasonably necessary to demonstrate compliance, maintain suppression state, and respond to disputes; after such period, the Company deletes or de-identifies information where feasible, unless retention is required by law or legitimate business necessity.
20.2 Message Logs
Message logs may be retained to support operational continuity, investigation of abuse, dispute resolution, and compliance verification, subject to reasonable minimization.
21. Security Measures; No Absolute Guarantee
The Company implements reasonable administrative, technical, and organizational safeguards designed to protect Personal Information, including Mobile Information, from unauthorized access, use, disclosure, alteration, or destruction; however, no system is guaranteed perfectly secure.
22. International Transfers
If you access the Site or communicate with us from outside the United States, your information may be processed in the United States or other jurisdictions where Service Providers operate, and such jurisdictions may have different data protection laws; where required, the Company will implement appropriate safeguards.
23. Individual Rights; Requests; Verification
Depending on your jurisdiction, you may have rights to request access, correction, deletion, restriction, objection, or portability of certain Personal Information, subject to verification and legal exceptions. Requests may be made by emailing [email protected]. For SMS/MMS, Opt-Out is effectuated via the mechanism described in Section 11.6.
24. Children
The Site and services are not directed to children under 13 (or higher minimum age where applicable), and the Company does not knowingly collect Personal Information from children.
25. Consent Dispute Resolution Procedure; Objections; “I Did Not Consent” Claims; Proof Requests
When the Company receives a complaint, objection, or dispute asserting that a recipient did not consent to receive SMS/MMS messages, or asserting that consent was withdrawn, or asserting that the recipient is not the person who provided Opt-In, the Company’s compliance posture is to prioritize cessation and verification rather than continued engagement, and therefore, upon receipt of such a dispute through any channel, the Company will take risk-reducing steps and preserve an audit trail.
25.1 Immediate Risk-Reducing Action
The Company will place the recipient number into suppression pending review even if the dispute is not phrased as an Opt-Out keyword.
25.2 Dispute Record
The Company will create a dispute record linking the recipient number, the date and time the dispute was received, the channel of receipt, and the content of the complaint.
25.3 Consent Record Retrieval
The Company will retrieve the Consent Record associated with the number and review it for completeness, including the Opt-In path, the Consent Capture Surface identifier, the timestamp, and the disclosure version identifier, and will review message logs for sequence integrity.
25.4 Authority Review
If the Consent Record indicates a number was provided by a representative or third party, the Company will assess authority and will maintain suppression where authority is unclear or disputed.
25.5 Outcomes
The Company will either maintain suppression permanently absent a new Opt-In, or maintain suppression upon objection even if consent appears valid, or maintain suppression and remediate operational causes if wrong-party messaging is detected.
25.6 Proof Requests
If a carrier, platform, or other authorized party requests proof of Opt-In, the Company may produce the Consent Record and related evidence, subject to confidentiality and lawful limits and with redaction of unrelated data.
26. Reassigned Number and Wrong-Party Mitigation; Wrong Recipient Handling; Compliance-First Fail-Safes
The Company acknowledges that mobile numbers may be reassigned or recycled and that wrong-party messaging can arise from transcription errors, typos, or contact synchronization mistakes; accordingly, the Company adopts mitigation controls designed to reduce the likelihood of wrong-party messaging and to provide rapid cessation paths.
26.1 STOP as Universal Safety Valve
The STOP mechanism in Section 11.6 is treated as universally available to any recipient regardless of whether that recipient was the original consenting party.
26.2 Conservative Interpretation of Wrong-Party Signals
Wrong-number assertions and plain-language stop requests are treated as requests to cease and trigger suppression.
26.3 Operational Indicators
The Company may pause or suppress messaging to affected numbers upon patterns indicating elevated wrong-party risk.
26.4 High-Risk Re-Validation
Where circumstances indicate elevated reassignment risk, the Company may require a new Opt-In through a defined path prior to continued outbound messaging.
27. Message Content Governance; Template Control; Human Access Controls; Preventing Unapproved Content
The Company limits the ability to send SMS/MMS messages through its messaging tools to authorized personnel or system roles, grants authorization on a need-to-send basis, and restricts message content to the purposes described in Section 11.2 and the context of Opt-In.
27.1 Template Controls
Where templates are used, the Company may maintain a library of approved templates and restrict editing privileges, and templates used for initial contact are intended to include clear brand identification and user-control instructions consistent with Section 11 without expanding beyond the disclosed purposes.
27.2 Prohibited Content Controls
The Company prohibits message content that would violate Section 4 and will treat violations as compliance incidents subject to corrective action.
27.3 Logging and Supervision
The Company may maintain logs of outbound messages and administrative actions for compliance auditing, abuse prevention, and dispute resolution.
28. Proof of Consent Production; Preservation for Verification
Because carriers and platforms may request proof of Opt-In, the Company preserves Consent Records and Opt-Out Records consistent with Section 20 and in a manner designed to support later verification, and, when producing proof to an authorized requester, the Company may provide the timestamp of consent acquisition, the consent pathway, the Consent Capture Surface identifier, the relevant disclosure version identifier, and the phone number for which consent was granted, with redaction of unrelated data where appropriate.
29. Complaints; Escalations; Corrective Actions; Non-Retaliation
If the Company receives complaints about messaging behavior, including complaints routed through carriers, platforms, clients, or recipients, the Company treats complaints as compliance signals that trigger immediate risk reduction and process correction.
29.1 Intake and Categorization
Complaints may be logged and categorized by type, including non-consent, wrong-party delivery, content objection, frequency objection, or operational error.
29.2 Corrective Action
Corrective actions may include suppression of affected numbers, review of Consent Records, review of message logs, suspension of sending privileges pending investigation, modification of templates, modification of Consent Capture Surfaces, and vendor escalation where delivery or keyword processing is implicated.
29.3 Non-Retaliation
The Company does not retaliate against recipients for Opt-Out or complaints, does not condition service on continued SMS/MMS participation where SMS/MMS is optional, and treats recipient control as primary, meaning that a recipient who opts out remains opted out unless and until the recipient affirmatively re-enrolls through a defined Opt-In path.
30. Changes to This Policy
The Company may update this Policy from time to time and will update the “Last Updated” date. Continued use of the Site or continued Communications after an update constitutes acknowledgment of the updated Policy to the extent permitted by law.
31. Contact
Email: [email protected]
Phone: (714) 650-1976 | (888) 668-3304
Mail: AI-Companies LLC d/b/a AI Remote Hire, 300 Spectrum Center Dr, Irvine, CA 92618, USA