Messaging and Anti-Spam Policy

This Messaging and Anti-Spam Policy applies when Customer uses Demand Trail to send, schedule, automate, relay, route, or manage email and any future SMS, calling, or similar communication functionality.

This Policy permits legitimate business communications that comply with applicable law, recipient permission requirements, and the rules of the provider used to transmit them. Unsolicited mass email, deceptive sending, and attempts to evade provider restrictions are prohibited.

This Policy applies to platform-managed sending services and customer-connected SMTP services. Where a sending provider imposes stricter requirements than applicable law, Customer must satisfy those requirements when using that provider through Demand Trail.

Customer is responsible for its campaigns and messages and is the sender or initiator to the extent provided by applicable law. YggyTech LLC provides Demand Trail as technology that acts on Customer instructions, subject to applicable restrictions.

Customer is responsible for audience selection, list provenance, sender identity, message content, required disclosures, recipient permission, opt-out handling, suppression, frequency, and compliance with applicable marketing and privacy laws and sending provider requirements.

Customer must not rely on Demand Trail's availability, a successful import, a verified sender identity, or a provider's acceptance of a message as evidence that the recipient has permitted the communication.

Customer may send a message only when the communication is permitted by applicable law and satisfies the permission requirements of the provider used to transmit it.

Where explicit recipient permission is required by applicable law or the sending provider, Customer must obtain and retain demonstrable permission covering the intended sender and communication purpose before sending.

Customer must be able to demonstrate where recipient data came from and why the intended communication is permitted. Where permission is relied upon, supporting evidence must identify how and when it was obtained and what the recipient agreed to receive.

Purchased, rented, scraped, licensed, enriched, third-party, or publicly available contact data does not by itself establish permission to send a message. Customer may store or otherwise lawfully process such data in the CRM, but its presence in Demand Trail does not make it eligible for sending.

A lawful basis under applicable law does not override a provider's stricter permission requirements. Customer must not use unsolicited mass messaging through the Services even where Customer believes that a particular legal regime permits its activity.

Recipient data must not be obtained through unlawful harvesting, credential theft, unauthorized access, or sources whose terms prohibit the intended use.

YggyTech LLC may request evidence of recipient permission, list provenance, or lawful sending practices when investigating activity or reviewing access to sending functionality.

Messages must use accurate and non-deceptive sender information, domains, display names, headers, routing information, and subject lines.

Customer must not impersonate another business or individual, conceal the commercial nature of a message where disclosure is legally required, or use misleading claims designed to obtain engagement through deception.

Customer must include a valid business identity and physical postal address where required by applicable law.

Marketing and outreach emails must include a clear and functional unsubscribe mechanism. Customer must also provide any additional opt-out mechanisms required by applicable law or the sending provider.

Customer must honor valid opt-out requests promptly and stop the affected marketing or outreach messages. Customer must not require payment, account creation, or unnecessary personal information to unsubscribe.

Customer must not re-add an opted-out recipient to the affected marketing audience without fresh, demonstrable permission. An import, enrichment update, campaign change, or change of sender does not override an applicable opt-out.

Addresses subject to an applicable hard-bounce, complaint, abuse, or provider suppression must not receive further messages through the affected sending route unless the restriction is resolved in accordance with the provider's requirements and Demand Trail's policies.

Customer may not bypass suppression by changing accounts, sender identities, domains, campaigns, integrations, or providers. A marketing opt-out must not be used to justify sending promotional content as a transactional message.

Customer must maintain appropriate sender authentication and DNS configuration for domains used through the Services, including SPF, DKIM, DMARC, or other standards required by Demand Trail or the applicable provider.

Customer must follow reasonable sending limits, warm-up requirements, rate limits, bounce controls, complaint controls, and reputation safeguards communicated in Documentation or product notices.

Demand Trail may reject, throttle, or pause sending when bounce rates, complaint rates, blocklisting, authentication failures, provider restrictions, abnormal volume, or other signals create material deliverability or abuse risk.

Transactional and operational messages relate to a recipient's requested action, account, subscription, security, or existing service relationship. Examples include account verification, authorized user invitations, password resets, receipts, billing notices, and necessary service notifications.

Such messages must be relevant to the action or relationship that gives rise to them and must comply with applicable law and the sending provider's requirements. An existing account or service relationship does not automatically establish permission for unrelated marketing.

Customer must not classify a promotional campaign as transactional, add unrelated promotional content to avoid marketing restrictions, or use transactional sending to bypass recipient permission or suppression requirements.

Demand Trail may transmit communications through platform-managed sending services, customer-connected SMTP services, or other Connected Services selected by Customer. The requirements of the provider actually used apply to each message.

Customer must comply with applicable law, this Policy, and the requirements of the email service provider used to transmit each message. Where a provider requires explicit recipient permission or imposes stricter sending restrictions, Customer must satisfy those requirements.

Routing a message through another provider, including a fallback provider, must not be used to bypass applicable recipient permission requirements, unsubscribe requests, suppression, or sending restrictions.

If a message cannot be sent through a Connected Service, it may be routed through another service only if it is independently eligible for that sending route and the routing is permitted by the Agreement and Customer's configuration.

A provider may reject, defer, filter, rate-limit, or suspend messages or sender identities. YggyTech LLC may restrict an affected sending route or Customer account to comply with provider requirements and protect recipients and other customers.

Connecting a customer-owned mailbox or provider account does not exempt Customer from this Policy or authorize abusive sending.

Demand Trail does not guarantee delivery, inbox placement, spam-folder placement, open rates, reply rates, or campaign performance. Deliverability depends on many factors outside Demand Trail's control, including sender reputation, domain history, recipient behavior, content, DNS, provider filtering, and third-party systems.

Unless an Order expressly states otherwise, Demand Trail is not a general-purpose mailbox provider and does not replace a business email hosting service. Any inbound message synchronization, reply capture, unified inbox, or similar functionality is limited to the features described in the applicable Documentation.

YggyTech LLC may investigate recipient complaints, abuse reports, unusual sending patterns, authentication failures, blocklisting, provider notices, or suspected violations of this Policy.

For a minor or correctable violation, we will ordinarily provide a warning describing the issue and a reasonable opportunity to correct it where circumstances permit.

We may require evidence of recipient permission, list provenance, sender authorization, and lawful sending practices. We may reject messages, reduce sending limits, pause campaigns, disable a sending route, or suspend sending where reasonably necessary to protect recipients, infrastructure, provider relationships, or other customers.

Immediate action may be taken without advance notice where a violation involves phishing, fraud, unsolicited mass messaging, evasion of restrictions, a security threat, or another serious risk. Where reasonably practicable, restrictions will apply to the affected sending feature or activity rather than unrelated CRM functionality.

Repeated or serious violations may result in termination of the affected subscription or account under the Terms of Service.

Where legally permitted and reasonably practicable, we will notify Customer of the restriction, its general reason, and any corrective steps required. Customer may request a review through [SUPPORT EMAIL]. A review request does not automatically lift a restriction or restore access.

Customer must cooperate with reasonable investigations and must not evade restrictions by creating additional accounts or changing sender identities, domains, integrations, or providers.

Billing, refunds, and data export following suspension or termination are governed by the Terms of Service, the applicable Order, the DPA, and applicable law.

If you receive an unwanted, deceptive, or abusive message that appears to have been sent through Demand Trail, you may report it to [ABUSE CONTACT EMAIL].

Where possible, include the original message, full email headers, the sender address, and the date received. Do not include passwords or unnecessary sensitive information.

YggyTech LLC may review the report and take action under this Policy. Reporting a message does not require a Demand Trail account.