Client Data Protection Policy
We keep client data in the client's control, use the least of it needed to do the work, and delete our copies when the work is done.
Purpose and scope
This policy applies to every client engagement with The Wired Connection, LLC ("TWC", "we"), including AI tools, automation, IT support, and consulting.
It covers any data a client shares with us or lets us access: in their systems, in files they send, or in conversations about their environment. Each Statement of Work (SOW) may add project-specific commitments. Where an SOW is more protective than this policy, the SOW controls.
What client data we handle
We only access the data a project needs, and we agree on it with the client before work starts. Typical categories:
| Category | Examples |
|---|---|
| Operational records | Help desk tickets, dispatch records, work orders, invoices |
| Communications | Emails, chat messages, call notes shared for a project |
| Documents | Process documentation, policies, spreadsheets, databases |
| Personal information | Employee and customer names, emails, phone numbers in those records |
| Credentials | API keys, service accounts, and admin access granted for the project |
We do not ask for and do not want payment card numbers, Social Security numbers, health records, or banking credentials. If a project would expose us to them, we name it in the SOW and agree on extra safeguards first.
Where client data lives
We build in the client's own environment by default, such as their Azure, Microsoft 365, AWS, or Google Workspace account. The data, the tools we build, and any search indexes stay there and belong to the client.
When we need a working copy (for example, sample records to test with), it stays on TWC-controlled, encrypted devices or accounts with multi-factor authentication. We never put client data on personal devices, public file-sharing links, or shared accounts. Working copies are limited to what the task needs and deleted under the retention rules below.
AI models and third-party services
Client data is never used to train AI models. We only use AI services under business or API terms that exclude customer data from model training, and we confirm the provider's terms for each project.
- Client's account first. Where possible, AI models run through the client's own cloud or AI account, so the data stays under the client's agreements with that provider.
- Least data out. Only the text a task needs is sent to a model. Web searches carry a generalized description of the problem, never names, email addresses, or other identifying details.
- No consumer tools. We do not paste client data into free or consumer AI chat apps.
- Named in the SOW. Every third-party service that will process client data (AI provider, hosting, search) is listed in the SOW or approved by the client before use.
- Labeled AI output. AI suggestions can be added to a client's systems automatically, such as an internal note on a ticket, and are always labeled as AI-generated. TWC does not review individual suggestions; the client's own staff decide what to act on. The SOW sets which records, if any, need a client staff member's sign-off before AI writes to them.
Access and credentials
We ask for the narrowest access that gets the job done, and we never share it.
- Dedicated accounts. We use a project-specific service account or API user, not a staff member's login.
- Least privilege. Permissions are limited to what the SOW describes, such as read tickets and add notes, not full admin rights.
- Stored securely. Credentials live in a password manager or the client's secret store (such as Azure Key Vault), never in code, email, or chat.
- Multi-factor authentication on every TWC account that can reach client systems.
- Removed at the end. We ask the client to disable our access at handoff and confirm when it's done.
Retention and deletion
We delete our working copies of client data within 30 days of project handoff, and sooner on request.
- During a project: working copies are kept only as long as a task needs them.
- At handoff: working copies, exports, and test data on TWC systems are deleted. Anything built for the client stays in the client's environment.
- On request: a client can ask us to delete their data at any time, and we confirm in writing once it's done.
- What we keep: the SOW, invoices, time records, and project emails, as required for business and tax records. These contain no bulk client data.
- Ongoing support: if a client keeps us on for support after handoff, access and data follow the support agreement instead.
Security incidents
If we learn that client data in our care was accessed, lost, or exposed without authorization, we notify the client within 72 hours.
The notice says what happened, what data was involved, what we've already done to contain it, and what we recommend next. We revoke or rotate any affected credentials right away and work with the client's team until the issue is closed. Where the client has legal notification duties, we provide the details they need to meet them.
Subcontractors
No one outside TWC touches client data without the client's approval. When a subcontractor joins a project, we name them to the client first, they agree in writing to follow this policy, and their access ends when their part of the work does. TWC stays responsible to the client for their handling of the data.
Requests, changes, and contact
Clients can ask at any time what data we hold, where it is, and who can reach it, and can ask us to delete it. We answer within 5 business days.
We review this policy at least once a year. If a change makes it less protective, it applies only to new engagements; current projects keep the terms they started with. Every change is listed below.
Questions or requests: The Wired Connection, LLC · privacy@thewiredconnection.com · 720.339.6013
Version history
1.1 · October 11, 2026 · Clarified that AI suggestions can post automatically and are not individually reviewed by TWC.
1.0 · October 11, 2026 · First published.