DRAFT — pending attorney review. Not in effect.
eTop Discovery Data Processing Addendum (DPA)
Version: 2026-11-02-draft
This addendum is part of the [Terms of Service](terms.md) between eTop Technology [attorney: confirm legal entity] ("eTop") and the Customer (an MSP). It applies to personal information in Customer Data that eTop processes to provide eTop Discovery (the "Service").
1. Roles
- Customer is the controller of Customer Data it collects about its own prospects, clients, and their people, or, where it acts for a prospect or client that is the controller, a processor for that prospect or client. Customer is responsible for telling eTop which applies.
- eTop is a processor (a "service provider" under the CCPA) and processes Customer Data only for the Customer, as in this DPA and the Terms.
- If Customer is a processor for its client, eTop is a subprocessor. Customer will make sure its own agreements with its clients allow eTop's processing under this DPA.
2. Details of processing
- Subject matter and purpose: hosting, storing, and analyzing information gathered during IT discovery, and producing reports for the Customer.
- Duration: the subscription term plus the 30-day export period, and until deletion under section 9.
- Data subjects: employees, contractors, and other users at the Customer's prospects and clients; the Customer's own users.
- Types of data: directory and device records (names, work emails, account and device details), network information, Microsoft 365 and Azure configuration and cost information, survey photos, uploaded bills, audio notes and transcripts. The Customer must not submit health information (PHI) or controlled unclassified information (CUI).
3. Customer instructions and responsibilities
eTop will process Customer Data only on the Customer's documented instructions, which are the Terms, this DPA, and the Customer's use of the Service's features. If eTop thinks an instruction breaks the law, it will tell the Customer. The Customer remains responsible for having the authority and consent required by section 6 of the Terms before it uses the Service on any environment.
4. Confidentiality
eTop will make sure people who handle Customer Data are bound by confidentiality. The operator tools eTop staff use to run the Service are built to reach registry and lifecycle information only, not tenant content (see section 6).
5. Subprocessors
The Customer agrees to eTop using these subprocessors for Customer Data:
| Subprocessor | Role | Location | | ---------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------- | | Cloudflare, Inc. | Hosts the Service and each Customer's isolated tenant; stores Customer Data; provides AI Gateway and hosted AI models | [placeholder: confirm; U.S.-only storage is not yet confirmed] | | Microsoft Corporation | Sign-in (Microsoft Entra) and the source of read-only Microsoft 365 and Azure data collected with administrator consent | United States and other Microsoft regions [placeholder: confirm] | | Stripe, Inc. | Payment processing; receives Customer account and billing data only, not scanned-environment data | United States [placeholder: confirm] | | AI model provider(s) reached through Cloudflare AI Gateway | Reads photos and bills, transcribes audio | [placeholder: provider names and locations to be finalized] |
[attorney: confirm whether Microsoft and Stripe belong in this table, since neither receives scanned-environment data from eTop.]
Notice of changes. eTop will give the Customer at least [placeholder: 30] days' notice before adding or replacing a subprocessor, by email to the account owner and on [placeholder: subprocessor page URL]. The Customer may object on reasonable data-protection grounds within that time. If the parties cannot resolve it, the Customer may cancel the affected Service and receive a refund of prepaid fees for the unused period. eTop is responsible for its subprocessors' performance of these obligations.
6. Security measures
eTop keeps appropriate technical and organizational measures. In summary, based on how the platform is built:
- Isolated tenants. Each Customer has its own tenant on Cloudflare. The platform's control plane holds only registry information (which tenants exist, their status, hostnames, and plan). It does not hold tenant data and cannot reach a tenant's data.
- Operator limits, enforced by tests. What eTop operators can do through the control plane is a fixed, published list. It cannot write a tenant's users, roles, grants, or credentials, cannot read tenant data, cannot get a tenant's tool token or call into a tenant, and cannot set a tenant's sign-in directories. Automated tests fail if the code stops matching that list.
- Audit trail. Every operator action on a tenant is recorded against that tenant in the same D1 batch as the action, so it can be shown to the tenant.
- Controlled releases. Tenant software is built from a single hash-pinned release; operators cannot apply their own SQL, scripts, or settings to a tenant.
- Read-only collection. The scanner and the Microsoft 365 and Azure connections only read. [BJ/attorney: add a statement about secret screening only after confirming it in the scanner code.] Access to a Microsoft environment starts only after that environment's administrator approves it.
- Hostname protection. A tenant's hostnames cannot be moved to another tenant while in use, which prevents traffic being redirected to a different tenant.
- Access control. Operators sign in through Cloudflare Access with dedicated operator accounts, separate from any account eTop staff use as an MSP tenant.
- Operator trust until the key service is live. Until the per-tenant key service is live, the keys that protect credentials a Customer stores in the Service are held by the platform, so eTop personnel able to deploy software to the platform could, in principle, gain access to those credentials; eTop limits that ability to its reviewed release process.
- Planned, not yet in effect: per-tenant encryption keys (including customer-held keys), customer-approved support access, and independent audits are in design. We are building to SOC 2. We do not hold a SOC 2 report or certification. [BJ/attorney: update this list to match what is built on launch day; do not list anything not built.]
eTop will review these measures as the Service changes and will not materially reduce the protection they give.
7. Personal data breach
eTop will tell the Customer without undue delay, and in any case within [placeholder: 72] hours, after becoming aware of a breach of security that leads to accidental or unlawful destruction, loss, alteration, or unauthorized disclosure of, or access to, Customer Data. The notice will say what we know about the nature of the breach, the data affected, likely consequences, and what we are doing, and eTop will update it as we learn more. The Customer is responsible for any notice to its own clients and regulators unless the law requires eTop to give it.
8. Help with requests and assessments
Taking into account the nature of the processing, eTop will reasonably help the Customer to (a) respond to requests from individuals to exercise their privacy rights, (b) meet breach-notice duties, and (c) carry out data protection assessments. If an individual contacts eTop directly about Customer Data, eTop will refer them to the Customer unless law says otherwise.
9. Return and deletion
When the subscription ends, the Customer has 30 days to export its Customer Data. After that, eTop will delete the Customer's tenant and Customer Data. Backups age out on the normal schedule of the underlying stores [placeholder: confirm window]. eTop may keep data that law requires it to keep, and will keep protecting it. On request, eTop will confirm deletion in writing [attorney/BJ: decide whether to offer a certificate of destruction; it is in the platform design but not confirmed as built].
10. Audits and information
eTop will give the Customer the information reasonably needed to show compliance with this DPA, including its published operator-boundary description and its subprocessor list. If that is not enough, the Customer may, no more than once a year and on [placeholder: 30] days' notice, audit eTop's relevant controls, in a way that does not disrupt eTop's business or expose other customers' data, at the Customer's cost. eTop may meet this duty by providing an independent audit report when one exists. [attorney: eTop has no SOC 2 report today; confirm the audit mechanism for launch.]
11. CCPA terms
eTop will not (a) sell or share Customer Data, (b) retain, use, or disclose it outside the direct business relationship or for any purpose other than providing the Service, or (c) combine it with other data, except as the CCPA allows. eTop certifies that it understands these limits. The Customer may take reasonable steps to confirm eTop is using Customer Data consistently with its CCPA duties, and to stop and fix unauthorized use.
12. International transfers
[attorney: the Service is U.S.-based. Decide whether any transfer terms (such as Standard Contractual Clauses) are needed at launch, or whether to limit launch to U.S. customers.]
13. Liability and order of precedence
Liability under this DPA is subject to the limits in the Terms [attorney: confirm]. If this DPA and the Terms conflict about personal information, this DPA controls.
Version 04317c36280b