1. Scope
This policy applies to every message sent through Sndiq, however it is sent: campaigns and one-off texts from the dashboard, automations, replies written by the AI agent, and messages sent through the API, webhooks, or connected tools. It covers everyone who uses an account, including owners, team members, contractors, and agencies acting for their clients. The account holder is responsible for compliance by everyone who uses the account.
2. You are the sender
The customer is the sender and initiator of every message it directs Sndiq to transmit. The customer decides who receives messages, where contact data comes from, what the messages say, when and how often they are sent, and how replies are handled.
Customers are responsible for complying with the Telephone Consumer Protection Act (TCPA), FCC rules, the Telemarketing Sales Rule, state mini-TCPA and quiet-hour laws, do-not-call requirements, carrier rules, CTIA guidance, A2P 10DLC and toll-free verification requirements, and other laws or standards applicable to their messages. Agencies are responsible for ensuring that each client account they manage meets this policy.
3. Consent is required
Before sending, customers must obtain the level of consent required for the message and technology used. Marketing or telemarketing texts may require the recipient's prior express written consent. Informational texts may require prior express consent or another valid legal basis. Consent must be specific to the actual sender and program and cannot be treated as permission for unrelated brands or campaigns.
Buying, renting, scraping, appending, or otherwise acquiring a list does not establish consent. A prior business relationship, a published phone number, or a recipient's consent to another company is not by itself permission to text through Sndiq. Customers who use data from lead sellers, affiliates, or other third parties must confirm that the consent behind it covers their brand and their messages; Sndiq does not verify the source of uploaded data. In an agency account, consent given to one client never extends to another client.
4. Opt-in disclosures
An opt-in request must be clear and conspicuous and must not be hidden in unrelated terms. As applicable, the disclosure should:
- identify the brand and program;
- describe the types and purpose of messages;
- state expected or variable frequency;
- state that message and data rates may apply;
- provide HELP and STOP instructions;
- link to the program's Terms and Privacy Policy; and
- state that consent is not a condition of purchase when that rule applies.
Pre-checked boxes and deceptive or bundled consent are prohibited.
Illustrative disclosure:
"By checking this box and submitting, you agree to receive recurring marketing text messages from [Brand] at the number provided, including messages sent using automated technology. Consent is not a condition of purchase. Message frequency varies. Message and data rates may apply. Reply STOP to opt out or HELP for help. View Terms and Privacy Policy."
This example must be adapted to the actual program and reviewed for applicable federal and state requirements.
5. Consent records
Customers must create and retain reliable evidence of consent, including the phone number, date and time, source URL or method, exact disclosure shown, affirmative action taken, program and brand, IP address or other available audit data, and any later revocation. Records must be produced promptly upon our request, a carrier inquiry, a complaint, or a legal demand. Customers must not upload or represent consent they cannot substantiate.
Sndiq keeps a consent record for each contact and can assemble it into a proof packet, but that record is only as good as the consent information the customer provides.
6. Sender identification and message content
Messages must accurately identify the sender and must match the registered campaign and opt-in description. Customers may not impersonate another person or business, use a brand they are not authorized to use, hide who is sending, or use public link shorteners prohibited by carriers. Content may not differ materially from the sample messages submitted for carrier registration.
Messages must be lawful and accurate. Deceptive claims, fraud, phishing, malware, harassment, threats, and unlawful discriminatory content are prohibited, along with anything barred by our Terms of Service. Marketing messages should include clear opt-out instructions at the frequency required by law and carrier standards.
7. Opt-outs, revocation, and suppression
Recipients may revoke consent by any reasonable method. Customers must honor clear requests such as STOP, STOPALL, UNSUBSCRIBE, CANCEL, END, QUIT, or REVOKE, as well as ordinary language that reasonably communicates a desire to stop. An opt-out may not be conditioned on a fee, login, or additional information. A single confirmation message may be sent when legally permitted, but it may not include marketing content.
Sndiq processes recognized inbound opt-out language into account-scoped suppression records and rechecks suppression before delivery. Customers must also promptly record requests received outside the platform, keep suppression lists current, and ensure all systems, vendors, campaigns, and business units honor the revocation to the extent required by law. Customers may not delete, evade, or re-import suppressed recipients without a documented new opt-in. We may keep opt-out and suppression records as compliance records, including after other account data is deleted.
Customers must also answer HELP requests with the program name and a way to reach them for support.
8. Quiet hours and frequency
Customers must send only during hours permitted in the recipient's location and must comply with any stricter state or program-specific limit. Sndiq restricts ordinary campaign delivery to a conservative platform window beginning at 9:00 a.m. and ending before 8:00 p.m. in the recipient's detected local time, with additional conservative handling for unknown time zones. Platform scheduling also applies stricter state day and time rules where they exist. Platform scheduling is a safeguard, not a substitute for the customer's legal review; some jurisdictions, message types, or recipient requests may require narrower hours or lower frequency.
Message frequency must match what the recipient agreed to and what the disclosure stated. Excessive messaging drives complaints and carrier filtering and may lead us to limit an account.
9. Do-not-call and reassigned numbers
Where applicable, customers must scrub against federal, state, company-specific, and internal do-not-call lists and maintain procedures for honoring those lists. Customers must use reasonable processes to detect wrong or reassigned numbers, stop messaging when notified, and avoid repeatedly sending to invalid or unengaged recipients.
10. Registration and number checks are not consent
Sndiq provides the numbers and files the carrier registrations, but an approved brand or campaign, carrier acceptance, or a working number does not establish legal permission to text anyone. Likewise, number lookups that report whether a number is valid, its carrier, or its line type are not evidence of consent.
11. AI agent and automation
Replies written by the Sndiq AI agent and messages sent by automations are the customer's messages and are held to this policy like any other text. They pass through the same compliance checks as every other text, with no shortcut. Customers are responsible for the persona, playbook, knowledge, offers, and claims they give the agent, for the compliance category they select for their account, and for reviewing what it sends. AI drafts wait for a person's approval by default; customers who allow the agent to send on its own remain responsible for those messages. Customers must not instruct the agent to make claims they could not make themselves.
12. API and integrations
Messages sent through the API, webhooks, or connected tools are subject to this policy and to the same platform controls as messages sent from the dashboard. Customers are responsible for the data and instructions their integrations send, and may not use an integration to bypass consent, suppression, quiet hours, or any other control.
13. No evasion
Customers may not evade carrier or platform controls. That includes rotating numbers or senders to avoid blocking, spreading traffic across numbers to avoid filtering (snowshoeing), opening substitute accounts after a restriction, misrepresenting a business or use case, sending another company's traffic through an account, or working around suppression.
14. Platform safeguards
Sndiq provides features designed to support compliant programs, including consent records, suppression lists, inbound STOP processing, quiet-hour scheduling, managed brand and campaign registration, delivery records, and abuse monitoring. These controls apply to messages sent from the dashboard, by automations, by the AI agent, and through the API alike, and they may block, defer, or stop messages. Customers must not attempt to bypass them and remain responsible for legal compliance even when a platform control does not detect a problem.
15. Reviews and enforcement
We may review campaign information, consent records, data sources, complaint and opt-out rates, content, links, and delivery patterns, and we may ask for documentation of how consent was collected. Campaigns in categories carriers treat as higher risk receive heavier review and may be held to tighter limits. We may reject campaigns; pause or terminate messaging; limit throughput; quarantine lists; require remediation or additional verification; and recover costs or penalties caused by a customer's violation. We may act before an investigation is complete when we see a risk to recipients, carriers, or the platform. Serious or repeated violations may result in account termination without prior notice.
16. Complaints and cooperation
When we receive a complaint, carrier inquiry, or legal demand about a customer's messages, the customer must promptly provide what we need to respond, such as the recipient, message content, campaign details, consent and opt-out records, and sender identity. We may preserve records and share necessary information with carriers, registries, messaging providers, regulators, or law enforcement as required by law or to stop fraud and abuse.
17. Recipient help
To stop messages, reply STOP to the sender. For help, reply HELP or contact the business identified in the message. If a sender does not honor your request, contact us at [email protected] with the sending number, your receiving number, the date of the message, and a screenshot if available. We use that information to investigate and enforce our policies.
18. Changes
We may update this policy and our platform controls as laws, carrier rules, and industry standards change. The effective date above shows when this policy last changed. A violation of this policy is a violation of our Terms of Service.
19. Contact
Compliance questions may be sent to [email protected] or mailed to Sndiq, 6312 Fiddlers Green Circle, Suite 300, Greenwood Village, CO 80111, United States.