SendlyConnect is built so that client data stays in client-owned systems and within the client's own cloud. This policy explains how we process information across the engagements we deliver and is intended to align with the Texas Data Privacy and Security Act.
SendlyConnect (a DBA of Peacock Consulting LLC, a Texas limited liability company) is engineered around a single principle: client data should never accumulate where it doesn't belong. The applications, products, and automations we deliver are built to run inside standalone, client-owned environments. We do not operate a centralized SaaS that ingests your data, and we do not sell client data or share it with third parties for their own purposes.
This policy covers (a) information processed by the systems we build and operate on a client's behalf, and (b) information submitted directly to SendlyConnect through this website. The specific technical stack for each engagement — cloud provider, runtime, and any tools selected at the client's direction — is defined in the applicable Statement of Work.
Automation and application logic executes within infrastructure owned or controlled by the client, under credentials managed by the client and scoped to the narrowest access required. Administrative access is restricted to named operators, and secrets are stored in client-managed secret stores rather than copied into SendlyConnect-owned infrastructure.
We design systems to process only the data needed for the task and to retain it no longer than necessary. Where a workflow allows, raw payloads — documents, message templates, evaluation contexts — are processed transiently and cleared once the operation completes. Retention periods for any persisted data are configured by the client to meet their own legal and operational requirements.
We are not tied to any single vendor. Where a client chooses to incorporate third-party platforms (for example, a cloud provider, an orchestration tool, or a messaging service), those tools are selected and configured according to the client's needs and documented in the Statement of Work. We do not introduce additional sub-processors that handle client data without the client's prior agreement.
Operational logging is written to the client's own logging facilities. Logs are scoped to structural metadata — timestamps, status codes, and record counts — rather than to the contents of personal-data payloads. Log retention and access are governed by the client's configuration.
The contact form on this site collects only the fields required to respond: name, business email, project details, and your message. Submissions are sent to an internal inbox and are not synced to a third-party CRM, marketing platform, or analytics processor.
We serve clients nationwide. If you are a Texas resident, the Texas Data Privacy and Security Act (TDPSA) gives you rights to confirm whether we process your personal data, to access and correct it, to request its deletion, to obtain a portable copy, and to opt out of targeted advertising, the sale of personal data, or certain profiling. Residents of other U.S. states may have similar rights under their own applicable privacy laws — contact us and we will honor any request the law entitles you to. We do not sell personal data or use it for targeted advertising. For data held within client-owned systems, requests are exercised through the relevant client as the controller.
To make a request or appeal a decision, email admin@sendlyconnect.com. We will respond within the timeframe required by applicable law. We may need to verify your identity before acting on a request.
We follow reasonable administrative, technical, and physical safeguards appropriate to the nature of the data we handle. No method of transmission or storage is completely secure, but we work with clients to apply least-privilege access, encryption in transit, and client-controlled credentials.
We may revise this policy as our services evolve. Material changes will be reflected in the "Last updated" date above.