Texts only with a lawful basis. STOP always works.

Who this covers

Aestar AI Solutions is operated by Profacio, LLC. This page explains how we treat US application-to-person (A2P) SMS when a shop uses Aestar to message that shop's own customers. It restates the SMS, TCPA, and consent rules already in our Privacy Policy (effective July 17, 2026) and Terms of Service (effective July 29, 2026). It does not replace those documents.

What this page covers

This is Aestar's public SMS and A2P 10DLC notice. It sits next to Privacy and Terms on every marketing footer. It is not a carrier registration certificate and it does not claim a shop is already 10DLC-approved.

Consent

We only send automated texts on a shop's behalf after that shop has a lawful basis to reach the person. Recipients can opt out at any time. Consent to receive texts is not a condition of purchase. We do not use purchased or cold lists.

• Reply STOP to opt out. That opt-out applies across every Aestar sender for that number.
• Reply HELP for help. Message frequency varies. Message and data rates may apply.
• Owner authorization is not consumer consent.
• Consent must match the kind of message. A booking confirmation is not permission for a marketing campaign.

STOP, HELP, and opt-out

STOP, unsubscribe, cancel, and end opt a number out across every Aestar sender for that shop. Opt-out is fail-closed: once recorded, later campaigns and follow-ups must honor it. HELP replies with the shop identity and how to get support. Recipients can also email hello@aestarai.com or privacy@aestarai.com.

A2P 10DLC

Carrier 10DLC brand and campaign registration is shop-specific. Until a shop's campaign is approved, outbound SMS can fail closed. The desk must not look like texts are going out when the carrier is blocking them. We do not claim that publishing this notice, connecting a phone number, or completing onboarding registers a shop with The Campaign Registry or any carrier.

What shops must do

If you use Aestar to contact your customers by text, you represent that you have the legal right and any required consent to contact them. You are responsible for TCPA, CAN-SPAM, carrier rules, and applicable law. We provide opt-out handling and consent records; the underlying relationship and permission are yours.

• Collect and keep proof of consumer consent before asking Aestar to text a customer for marketing or follow-up.
• Do not upload purchased, rented, or cold-acquired contact lists.
• CRM imports never trigger automatic outbound campaigns.
• Honor STOP immediately. Do not ask Aestar to override an opt-out or treat an inbound job request as a reset.

What Aestar does on the server

canTextCustomer() and suppression checks are mandatory for marketing or follow-up SMS. Voice and messaging agents may not infer consent. Models draft; they do not authorize a send that the gates reject. Twilio is the messaging provider. Signature verification, status callbacks, and idempotent retries apply on provider webhooks.

What Aestar will not do

We will not infer consent from a call, a website visit, or a photo-drop quote request. We will not bypass quiet hours, frequency caps, or STOP handling. Send stays off until a human approves live messaging for that shop. Provider errors or a failed suppression check mean we do not send.