Data Processing Agreement
How we process personal data for your MSP. Last updated 18 November 2026.
Enlist is made and run by WolfByte.Works, a sole proprietorship owned by Dennis Wallace in Texas, USA (“WolfByte.Works”, “we”, “us”). This Data Processing Agreement (“DPA”) is part of the Terms of Service between us and your MSP (“you”), and you accept it when you accept the terms. It applies when we process personal data for you in providing Enlist. It is meant to meet Article 28 of the EU and UK GDPR, the Swiss FADP, and the service-provider terms of the CCPA/CPRA and other US state privacy laws. If this DPA and the terms disagree about personal data, this DPA wins.
1. Roles
For personal data about your clients and their users (“Client Personal Data”), you are the controller (or a processor for your client) and we are your processor (or sub-processor). For the accounts of your own team and your billing contacts, we are a controller, as the Privacy Policy describes. Paddle, our reseller, processes payment data as its own controller and is not a subprocessor of Client Personal Data.
2. What we process
Annex 1 below describes the processing. Enlist isn't meant for special categories of data (such as health records), payment card data or government ID numbers. Don't put them into scripts, settings or notes. We don't sign Business Associate Agreements under HIPAA yet: don't put protected health information into Enlist until we have signed one with you.
3. Your instructions
We process Client Personal Data only on your documented instructions: these terms, and what you set in the console and the API. If we think an instruction breaks data protection law, we tell you. If the law makes us process it otherwise, we tell you first unless the law forbids it.
As a service provider under US state privacy laws, we don't sell or share Client Personal Data, keep, use or disclose it for any purpose other than providing Enlist, use it outside our direct business relationship with you, or combine it with other data, except as those laws allow. We comply with those laws and tell you if we can no longer meet them. You may take reasonable steps to stop and fix any use you didn't authorise.
4. Confidentiality and staff access
Everyone who can reach Client Personal Data is bound to confidentiality and gets only the access their job needs. EnlistIt support can open your MSP only with a stated reason, for at most an hour, with your owners emailed and every action in your Activity log.
5. Security
We keep the technical and organisational measures in Annex 2 and on the security page. We may improve them but won't make them weaker overall.
6. Subprocessors
You give general authorisation for the subprocessors on the Subprocessors page. We tell you at least 30 days before adding or replacing one, by updating that page and emailing your owners. You may object for a reasonable data-protection reason within that time; if we can't address it, you may end the affected service and get a pro-rata refund of prepaid fees. Each subprocessor is bound by data-protection terms at least as protective as these, and we remain responsible for them.
7. Helping you
The console lets you find, export, correct and delete data to answer people's requests. If a person asks us directly, we pass the request to you without answering it ourselves, unless you ask us to. We help, at reasonable cost if it is a lot of work, with security, impact assessments, prior consultations and questions from regulators.
8. Breaches
If we become aware of a breach of Client Personal Data, we tell your owners without undue delay and within 72 hours, with what we know (what happened, the data and people likely affected, the likely consequences, what we are doing, and who to contact), and we keep you updated as we learn more. Telling you isn't an admission of fault.
9. Deletion and return
You can export your data at any time. When you close your MSP, everything is erased after a 7-day grace period (in which you can cancel), and you can download a signed erasure certificate. Encrypted backups age out within 6 months. If the Service ends any other way, we erase your data within 30 days unless the law requires us to keep part of it, which we then protect under this DPA for as long as we keep it.
10. Where data is, and transfers
Enlist's servers and data are in the United States. Where Client Personal Data from the EU, EEA, UK or Switzerland comes to us, the EU Standard Contractual Clauses (Commission Decision 2021/914) apply and are made part of this DPA as follows:
- Module two (controller to processor) where you are a controller; module three (processor to processor) where you are a processor for your client.
- Clause 7 (docking) applies. Clause 9: option 2, general authorisation, with the 30 days' notice in section 6. Clause 11: the optional wording doesn't apply.
- Clause 13: the supervisory authority of the EU member state where you are established, or where your representative is. Clauses 17 and 18: the law and courts of Ireland.
- Annexes I and II of the Clauses are Annex 1 and Annex 2 below; Annex III is the Subprocessors page.
- For the UK, the ICO's International Data Transfer Addendum applies, with Tables 1 to 3 filled in from this DPA and either party able to end it as its Table 4 allows. For Switzerland, the Clauses apply with the FDPIC as the authority and the Swiss FADP in place of the GDPR where it governs.
We tell you before we move your data to another country.
11. Audits
We make available the information you need to show we meet this DPA, such as our security documentation, answers to your security questionnaire, and any audit reports we have. Once a year, or after a breach, or when a regulator requires it, you may audit us with 30 days' notice, at your cost, under confidentiality, during business hours, and in a way that doesn't risk other customers' data.
12. Liability and order of documents
The limits in the Terms of Service apply to this DPA, as far as the law allows. If the Standard Contractual Clauses and this DPA disagree, the Clauses win.
Annex 1: Description of the processing
| Data exporter | The MSP that accepted the Terms of Service, contactable through its owners' email addresses in Enlist. Role: controller or processor. |
|---|---|
| Data importer | WolfByte.Works (Dennis Wallace), 10160 Highway 242, Ste 800 PMB 1028, Conroe, TX 77385-4307, United States, [email protected]. Role: processor or sub-processor. |
| People whose data is processed | Your clients' computer users and staff; your own team. |
| Personal data | Computer names, serial numbers and hardware and software inventory; user names and accounts on those computers; the output of scripts and updates you run; recovery keys and local admin passwords you choose to escrow (encrypted); user details you put in blueprints, moves or migrations; sign-in records and IP addresses; anything else you put into scripts, settings or notes. |
| Sensitive data | None intended. See section 2. |
| How often | Continuously, while you use Enlist. |
| What we do with it | Store, organise, display, send to and from your managed computers, back up, secure and delete, so that you can onboard, configure, patch, move and look after those computers. |
| Purpose | Only to provide, secure and support Enlist for you. |
| How long | While you use Enlist, then deleted as in section 9. |
| Subprocessors | As listed on the Subprocessors page, for the purposes listed there. |
Annex 2: Technical and organisational measures
- Encryption: TLS 1.2 or later for everything in transit; agents talk to the server over mutual TLS. Data at rest is encrypted; escrowed keys and passwords are encrypted again with a key per MSP, which is itself locked by a master key kept outside the database.
- Separation: a separate database per MSP, with row-level security as a second check.
- Access: passkey sign-in for everyone, role-based access, step-up checks for sensitive actions, least-privilege staff access with an authenticator code, and time-limited, logged support access.
- Integrity: signed agent updates and packages, malware scanning of uploaded files, and approval steps for risky actions such as moves.
- Logging: an append-only, hash-chained Activity log of every sign-in, change and sensitive view, and alerts to owners for security events.
- Availability: nightly encrypted backups to separate storage (deleted after 35 days in Oracle Cloud, and after at most 6 months in our own backup storage), written restore steps (target: at most 24 hours of data lost, service back within 4 hours), health monitoring and an incident process.
- Development: code review, automated tests, dependency and security scanning on every change.
- People: confidentiality duties for everyone with access, and access removed when it is no longer needed.