Data Processing Agreement
Version 2026-10-01 · Effective 1 October 2026
This Data Processing Agreement ("DPA") forms part of the Terms of Service between Telos-IQ ("Provider") and the customer that accepted them ("Customer"). It applies whenever the Provider processes personal data on the Customer's behalf in the course of providing Telos-IQ ("the Service"). It is accepted together with the Terms; no separate signature is needed. If the Customer requires a countersigned copy, email support@telos-iq.com.
1. Definitions
"Personal data", "processing", "controller", "processor", "data subject" and "supervisory authority" have the meanings given in applicable data-protection law, including the EU and UK General Data Protection Regulation ("GDPR") and US state privacy laws such as the California Consumer Privacy Act ("CCPA"), where those laws apply. "Customer Data" means the data the Customer and its connected tools supply to the Service, as described in the Terms.
2. Roles
- The Customer is the controller (or, where the Customer acts for its own clients, a processor) of personal data within Customer Data, and instructs the Provider to process it.
- The Provider is the Customer's processor (or sub-processor) and processes that personal data only on the Customer's documented instructions.
- Where the Customer processes data on behalf of its own clients, the Customer confirms that it is authorized to appoint the Provider as a sub-processor and to agree to this DPA on those clients' behalf.
3. Details of processing
- Subject matter: providing the Service, namely reading data from the Customer's connected tools, producing coverage and configuration reports, and carrying out actions the Customer explicitly triggers.
- Duration: while the Customer has a workspace, plus the deletion period in Section 9.
- Nature and purpose: collection, storage, structuring, comparison, display and deletion of operational IT data, for the purpose of identifying security-coverage gaps.
- Types of personal data: names and work email addresses of the Customer's users and of its clients' users; device host names; last signed-in user names; IP addresses in logs; license, role and multi-factor status; and similar operational identifiers. The Service is not designed to process special categories of data and the Customer must not use it to do so.
- Data subjects: the Customer's staff, the staff of the Customer's clients, and other users of devices managed by the Customer.
4. Provider obligations
- Instructions. The Provider processes personal data only on the Customer's documented instructions, which are the Terms, this DPA and the Customer's use of the Service's controls. Where the law requires other processing, the Provider will inform the Customer beforehand where legally permitted.
- Confidentiality. Anyone the Provider authorizes to process personal data is bound by confidentiality.
- Security. The Provider implements the technical and organizational measures in Annex 1 and keeps them under review.
- Assistance. Taking into account the nature of the processing, the Provider assists the Customer in responding to data-subject requests and in meeting its obligations on security, breach notification, impact assessments and consultation with supervisory authorities.
- Breach notification. The Provider notifies the Customer without undue delay, and in any case within 72 hours, after becoming aware of a personal-data breach affecting Customer Data, and provides the information reasonably needed for the Customer to meet its own notification duties.
- Deletion. The Provider deletes or returns personal data at the end of the Service as set out in Section 9.
- Compliance. The Provider makes available the information reasonably necessary to demonstrate compliance with this DPA and allows for audits as set out in Section 8.
- Unlawful instructions. The Provider informs the Customer promptly if, in its opinion, an instruction infringes data-protection law.
5. Customer obligations
- Lawful basis. The Customer ensures it has a lawful basis, and any notices or consents required, for the personal data it and its connected tools provide to the Service, including data about its clients' users.
- Authorized access. The Customer connects only tools and accounts it is authorized to connect, grants only the access the Service needs, and revokes that access when it stops using the Service.
- Controls. The Customer uses the Service's controls (user roles, tool connections, exceptions, data export and workspace closure) to give processing instructions and to meet its own obligations to data subjects.
- Lawful instructions. The Customer does not instruct the Provider to process personal data in a way that would breach applicable law.
6. Sub-processors
The Customer gives general authorization for the Provider to use the sub-processors listed in Annex 2. The Provider will impose data-protection obligations on each sub-processor no less protective than this DPA and remains responsible for their performance.
The Provider will give at least 30 days' notice, by email to the workspace owner and by updating https://app.telos-iq.com/dpa, before adding or replacing a sub-processor. The Customer may object on reasonable data-protection grounds within that period. If the parties cannot resolve the objection, the Customer may close its workspace and receive a pro-rata refund of prepaid fees.
7. International transfers
The Service is hosted in the United States. Where the Customer transfers personal data subject to GDPR or UK data-protection law to the Provider, the parties rely on the European Commission's Standard Contractual Clauses (Module Two, controller to processor, or Module Three, processor to processor, as applicable), together with the UK International Data Transfer Addendum, which are incorporated into this DPA by reference. Annex 1 and Annex 2 of this DPA serve as the annexes to those clauses. The Provider will apply supplementary measures where required and will inform the Customer if it can no longer comply with the clauses.
8. Audits
On written request, no more than once in any 12-month period unless required by a supervisory authority or following a breach, the Provider will make available documentation describing its security measures and, where reasonably required, answer a written security questionnaire. If that is insufficient to demonstrate compliance, the Customer or an independent auditor bound by confidentiality may audit the Provider's relevant processing on 30 days' notice, during business hours, at the Customer's expense, and in a way that does not compromise the security of other customers.
9. Return and deletion
The Customer may export reports from the Service at any time and may request a copy of its Customer Data before, or within 14 days after, closing its workspace. When the Customer closes its workspace, or on written request, the Provider will delete the workspace's data, credentials and storage within 30 days, and encrypted backups will age out within a further 35 days, unless retention is required by law. On request the Provider will confirm deletion in writing.
10. US state privacy laws
Where CCPA or a similar US state law applies, the Provider acts as a "service provider" or "processor". The Provider will not sell or share personal information, will not retain, use or disclose it for any purpose other than providing the Service or as permitted by law, will not combine it with personal information from other sources except as permitted, and will notify the Customer if it can no longer meet these obligations. The Customer may take reasonable steps to stop and remediate unauthorized use.
11. Liability and precedence
The liability limits in the Terms apply to this DPA. Where this DPA conflicts with the Terms on the processing of personal data, this DPA prevails; where the Standard Contractual Clauses conflict with this DPA, the clauses prevail.
Annex 1: Technical and organizational measures
- Isolation. Each customer's workspace runs in its own compute environment with its own storage. Workspaces cannot reach one another; outbound network access is restricted to approved destinations.
- Encryption. TLS for all data in transit. Encryption at rest for storage, databases and backups using provider-managed keys. Tool credentials are held in an encrypted secrets store with a key path readable only by the owning workspace.
- Access control. Multi-factor authentication is required for every workspace user and every operator. Role-based permissions within workspaces. Operators cannot read workspace credentials; operator access into a workspace is via a time-limited, single-use, audited support session that appears in the workspace's audit log.
- Least privilege. Connected-tool access is requested at the minimum scope the Service needs and is documented on each connection screen.
- Logging and monitoring. Audit logs of administrative actions in workspaces and the operator console. Infrastructure change logging and alerting on privilege changes.
- Change management. Code changes are reviewed and built by an automated pipeline; releases are rolled out in stages with automatic stop on failure.
- Resilience. Automated backups of workspace storage with versioning; infrastructure defined as code and rebuildable.
- Incident response. Documented emergency procedures; breach notification per Section 4.
- Personnel. Access to production is limited to named operators bound by confidentiality.
Annex 2: Sub-processors
| Sub-processor | Service | Location |
|---|---|---|
| Amazon Web Services, Inc. | Cloud hosting, storage, secrets and key management, email delivery (SES) | United States |
| Stripe, Inc. | Payment processing and subscription billing (account data only; no workspace data) | United States |
| Microsoft Corporation | Transactional email delivery via Microsoft 365, where enabled | United States |
Contact
Telos-IQ · support@telos-iq.com · https://app.telos-iq.com