5. License and permitted use
Subject to the Agreement and payment of applicable fees, Zayloft grants Customer a limited, non-exclusive, non-transferable and non-sublicensable right to access and use the Services during the applicable term for Customer’s internal business purposes and to provide Customer’s own services to its End Users where the product is designed for that use.
Customer may not copy, modify, reverse engineer, decompile, attempt to discover source code or underlying non-public technology, bypass technical restrictions, scrape protected interfaces, resell standalone access except under an authorized reseller arrangement, or use the Services to build a substitute service using Zayloft confidential or proprietary materials, except to the extent a restriction is prohibited by applicable law.
6. Customer responsibilities and lawful communications
Customer is responsible for its use of the Services, its Customer Content, its End Users, its sender identities, and the legal basis for communications it initiates.
Customer must comply with applicable communications, telemarketing, electronic messaging, privacy, consumer-protection, advertising, fraud, data-protection and industry requirements. This includes obtaining legally sufficient consent where required, keeping evidence of consent when appropriate, honoring opt-outs and revocations, maintaining suppression controls, using accurate sender information, and communicating only with recipients Customer is authorized to contact.
Customer must not use Zayloft to evade carrier, network, channel, regulator or platform requirements, falsify traffic origin, obscure identity, circumvent registration or verification controls, or continue contacting recipients after a legally effective opt-out.
7. Acceptable Use Policy
The Acceptable Use Policy forms part of the Agreement and applies to Customer, Customer’s users and End Users. Prohibited conduct includes unlawful, deceptive, fraudulent, abusive, harassing, exploitative or security-threatening activity and other conduct identified in that policy.
Zayloft may investigate suspected misuse and may request information reasonably necessary to verify traffic, consent, identity, sender authorization, destination use, account ownership or compliance.
8. Messaging, email, voice and channel-specific conditions
Communications services depend on third-party networks, carriers, mailbox providers, device platforms, channel operators, number authorities and other delivery participants. Their rules, technical limits, registration requirements and fees may apply in addition to this Agreement.
Acceptance of a message, call, email or verification request for processing does not guarantee final delivery, recipient receipt, inbox placement, call completion, device support or a particular delivery time. Delivery states can be asynchronous and may depend on downstream providers.
Customer is responsible for complying with channel-specific requirements applicable to sender IDs, numbers, templates, short codes, toll-free resources, email authentication, voice origination and other communications resources it uses.
9. Developer interfaces and technical limits
APIs, SMPP connections, webhooks, SDKs, documentation and other developer interfaces must be used according to applicable documentation and account configuration. Customer must respect rate, throughput, concurrency, payload, session and security limits.
Customer should design integrations for retries, idempotency, asynchronous events, partial failures and provider latency. Zayloft may apply technical controls reasonably necessary to protect service integrity, prevent abuse, manage capacity or satisfy downstream requirements.
10. AI and NLP services
AI and NLP functionality may produce probabilistic, incomplete or inaccurate outputs. Customer is responsible for evaluating outputs before using them in decisions, communications or automated workflows where errors could cause material harm.
Customer must have the rights and permissions needed for prompts, documents, training examples, retrieved content and other data submitted to AI functionality. Service-specific AI terms, model-provider restrictions or data-processing terms may also apply.