MantisOps
MANTISOPS Managed IT Operations
Home Legal

Data Processing Agreement

Effective: October 11, 2026 · Last updated: October 11, 2026
This Data Processing Agreement forms part of the Terms of Service (or your signed Master Service Agreement) and applies automatically, without signature, where you are subject to the GDPR, UK GDPR or CCPA/CPRA. If you need a countersigned copy for your records, email privacy@mantisops.net.
Contents
  1. 1. Background
  2. 2. Definitions
  3. 3. Roles and Scope
  4. 4. Processor Obligations
  5. 5. Sub-Processors
  6. 6. International Transfers
  7. 7. Audit Rights
  8. 8. Liability
  9. 9. Term, Return, and Deletion
  10. 10. Conflict
  11. 11. Governing Law
  12. Annex I — Details of Processing
  13. Annex II — Technical and Organizational Security Measures
  14. Annex III — List of Sub-Processors

1. Background

This Data Processing Agreement ("DPA") supplements the Master Service Agreement (or, if none, the Terms of Service) between the customer that accepted those terms ("Controller") and MantisOps, LLC, a South Carolina limited liability company ("Processor") (the "Principal Agreement"). It governs how Processor handles Personal Data on behalf of Controller in connection with the MantisRMM, Mantis360, and/or MantisNMS services (the "Services"). In the event of conflict between this DPA and the Principal Agreement on matters of data protection, this DPA controls.

2. Definitions

Capitalized terms not defined here have the meanings in the Principal Agreement. The following apply:

  • "Personal Data" has the meaning in GDPR Article 4(1) (and equivalents in CCPA/CPRA "personal information") — any information relating to an identified or identifiable natural person processed by Processor on behalf of Controller through the Services. In the MantisOps context this typically includes: device hostnames assigned to identifiable users, IP addresses associated with employee endpoints, authentication events, agent-collected user activity (process lists, logged-in user names), and remote-session interaction.
  • "Processing" has the meaning in GDPR Article 4(2).
  • "Sub-Processor" means any third party engaged by Processor to Process Personal Data on Controller's behalf.
  • "Applicable Data Protection Law" means, as applicable to a given processing activity: the EU General Data Protection Regulation (EU 2016/679) ("GDPR"), the UK GDPR and the UK Data Protection Act 2018 ("UK GDPR"), the California Consumer Privacy Act of 2018 as amended by the California Privacy Rights Act ("CCPA/CPRA"), and any other comparable data-protection laws of a jurisdiction whose residents' data is Processed under this DPA.
  • "Standard Contractual Clauses" or "SCCs" means the standard contractual clauses approved by the European Commission in Commission Implementing Decision (EU) 2021/914, and where applicable the UK Information Commissioner's International Data Transfer Addendum.
  • "Data Subject Request" means a request from a data subject exercising rights under Applicable Data Protection Law.
  • "Personal Data Breach" has the meaning in GDPR Article 4(12).

3. Roles and Scope

3.1 Roles

For purposes of this DPA, Controller is the "controller" (or "business" under CCPA/CPRA) and Processor is the "processor" (or "service provider" under CCPA/CPRA) of Personal Data.

3.2 Subject matter and duration

The subject matter is Processor's provision of the Services. The duration is the Subscription Term plus any post-termination retention period required by Section 9.

3.3 Nature and purpose

Processor will Process Personal Data only to provide and improve the Services, perform billing, and comply with law.

3.4 Categories of data subjects and Personal Data

  • Data subjects: Controller's employees, contractors, and end users whose endpoints or activity are captured by the Services.
  • Personal Data: as described in Section 2 above and the Privacy Policy.

3.5 Documented instructions

Controller's documented instructions to Processor consist of: (a) this DPA, (b) the Principal Agreement, (c) Controller's use of the Services (configuration choices, scan targets, policy settings), and (d) any other written instructions Controller provides. Processor will inform Controller if, in Processor's opinion, an instruction violates Applicable Data Protection Law.

4. Processor Obligations

Processor will:

(a) Limit Processing to what is necessary to provide the Services and as instructed by Controller. Processor will not Sell or Share (as defined in CCPA/CPRA) Personal Data and will not Process Personal Data outside the direct business relationship with Controller.

(b) Implement appropriate technical and organizational security measures, as described in Annex II, including:

  • Encryption in transit (TLS 1.2+) and at rest;
  • Per-tenant database isolation (separate D1 database per customer);
  • Access controls and multi-factor authentication on administrative accounts;
  • Rate limiting and account lockout on authentication endpoints;
  • Login audit logging;
  • Annual review of access rights;
  • Documented incident response procedures.

(c) Bind personnel with access to Personal Data to written confidentiality obligations no less protective than those in the Principal Agreement.

(d) Notify Controller of a Personal Data Breach without undue delay, and in any event within seventy-two (72) hours of becoming aware. The notification will include the nature of the breach, categories and approximate number of data subjects and records affected, likely consequences, and the measures taken or proposed.

(e) Assist Controller with Data Subject Requests received directly from data subjects by forwarding them to Controller within five (5) business days. Where the Services include functionality allowing Controller to respond directly (e.g., data export), Processor's assistance is satisfied by maintaining that functionality.

(f) Assist Controller with data protection impact assessments and prior consultations with supervisory authorities required by Applicable Data Protection Law, to the extent Controller does not otherwise have access to the relevant information.

(g) Delete or return all Personal Data within thirty (30) days of termination of the Services, at Controller's option, except where retention is required by law (e.g., financial records retained for seven years for tax purposes). Backups containing Personal Data are purged on the normal retention rotation (90 days).

(h) Make available all information reasonably necessary to demonstrate compliance with this DPA and contribute to audits in accordance with Section 7.

5. Sub-Processors

5.1 General authorization

Controller grants Processor a general authorization to engage Sub-Processors, subject to the conditions below.

5.2 Current Sub-Processors

The current Sub-Processors are listed at https://mantisops.net/legal/sub-processors. As of the date of this DPA:

Sub-ProcessorServiceLocationPrivacy Policy
Cloudflare, Inc.Workers, D1, R2, KV, Durable Objects, Workers Cron, DNS, CDN, DDoS — entire application-hosting and data-storage platformUnited States + global PoPshttps://www.cloudflare.com/privacypolicy/
Stripe, Inc.Subscription billing, payment processingUnited Stateshttps://stripe.com/privacy
ResendTransactional email deliveryUnited Stateshttps://resend.com/legal/privacy-policy
Microsoft (Graph API)Administrative email send-asUnited Stateshttps://privacy.microsoft.com/
Quo (formerly OpenPhone)Business phone / VoIP — sales and support calls, voicemail, SMSUnited Stateshttps://www.quo.com/privacy
Anthropic, PBCAI-assisted support — triage + drafting of replies to support tickets (processes support-ticket content; human-reviewed before any reply is sent; not used to train models under Anthropic's commercial terms)United Stateshttps://www.anthropic.com/legal/privacy

5.3 Notice of new Sub-Processors

Processor will notify Controller by email at least thirty (30) days before engaging a new Sub-Processor that Processes Personal Data of Controller's data subjects. Controller may object on reasonable, documented data-protection grounds within that thirty-day period. If Controller objects, the Parties will work in good faith to resolve the objection; if no resolution is reached, Controller may terminate the affected Subscription Term as its sole remedy and receive a pro-rata refund of prepaid unused fees.

5.4 Sub-Processor obligations

Processor will impose data-protection obligations on each Sub-Processor that are no less protective than those in this DPA. Processor remains liable to Controller for Sub-Processors' acts and omissions.

6. International Transfers

6.1 EEA and UK

Where Personal Data is transferred from the EEA, Switzerland, or the UK to a country not subject to an adequacy decision, the Parties incorporate the Standard Contractual Clauses (Module Two: Controller-to-Processor) into this DPA by reference. The UK International Data Transfer Addendum applies for UK transfers. Annex III to this DPA completes the SCCs.

6.2 Onward transfers

Processor's Sub-Processors located outside the EEA or UK are bound by SCCs or equivalent safeguards as part of Processor's contracts with them.

6.3 California

For Personal Data subject to CCPA/CPRA, Processor will not retain, use, or disclose Personal Data for any purpose other than the specific purpose of providing the Services as set forth in the Principal Agreement.

7. Audit Rights

7.1 Audit reports

Processor will make available to Controller, upon written request, summary results of third-party security audits and certifications (e.g., SOC 2 reports once available, penetration test summaries).

7.2 Direct audit

On at least thirty (30) days' prior written notice, and no more than once per calendar year (except where required by a supervisory authority or following a confirmed Personal Data Breach), Controller may conduct or commission a qualified independent auditor to audit Processor's compliance with this DPA. Audits will be conducted during normal business hours, will not unreasonably interfere with Processor's operations, and will be at Controller's expense unless the audit reveals a material breach by Processor.

7.3 Confidentiality

Audit reports are Confidential Information of Processor.

8. Liability

Each Party's liability under this DPA is subject to the limitations set forth in the Principal Agreement.

9. Term, Return, and Deletion

9.1 Term

This DPA takes effect when Controller accepts the Terms of Service (or signs the Master Service Agreement) and remains in effect until termination of the Principal Agreement plus the post-termination period required for deletion.

9.2 Return and deletion

On termination, Controller may export Personal Data via the Services for thirty (30) days. Thereafter, Processor will delete Personal Data within thirty (30) days, except where retention is required by law. Sections 4(h) (audit assistance), 7 (audit rights), and 11 (governing law) survive termination to the extent necessary to give effect to outstanding obligations.

10. Conflict

If any provision of this DPA conflicts with the Principal Agreement on matters of data protection, this DPA prevails. If any provision of this DPA conflicts with the SCCs as incorporated under Section 6.1, the SCCs prevail.

11. Governing Law

This DPA is governed by the law specified in the Principal Agreement, except that the SCCs incorporated under Section 6.1 are governed by the law specified in those clauses.

Annex I — Details of Processing

A. List of Parties

  • Data exporter (Controller): the customer, as identified by the organization name and address in its MantisOps account. Contact: the account owner, or the privacy contact the customer designates by email to privacy@mantisops.net.
  • Data importer (Processor): MantisOps, LLC, 6650 Rivers Ave., Suite 100, Charleston, SC 29406 (registered office). Contact: privacy@mantisops.net.

B. Description of Transfer

  • Categories of data subjects: Controller's employees, contractors, and end users whose endpoints, networks, or accounts are managed or scanned via the Services.
  • Categories of Personal Data: Device hostnames; IP addresses; usernames and authentication events; agent-collected process / service / network metadata; remote-session activity logs; vulnerability scan results that reference user-associated assets.
  • Special categories: None routinely. The Services are not designed to Process special-category data (GDPR Art. 9) or criminal-conviction data.
  • Frequency of transfer: Continuous for the duration of the Subscription Term.
  • Nature of processing: Storage, retrieval, analysis, display in dashboards, alerting, and (for remote sessions) real-time relay between Controller's operators and managed endpoints.
  • Purposes: Provision of the MantisRMM, Mantis360, and/or MantisNMS services as described in the Principal Agreement and Documentation.
  • Retention period: Per the Privacy Policy §6: scan results, metrics and monitoring history are kept as rolling history for the Subscription Term (older detailed samples are periodically aggregated or purged) and deleted within thirty (30) days after termination; log data 90 days; remote session frames are not retained.

C. Competent Supervisory Authority

For data subjects in the EEA: the supervisory authority of the EU member state where the data exporter is established, or if not established in the EU, the supervisory authority indicated in the SCC as competent (default: Ireland Data Protection Commission, as Processor is established in the United States and SCCs apply).

For data subjects in the UK: the UK Information Commissioner's Office.

Annex II — Technical and Organizational Security Measures

Processor implements the following technical and organizational measures (TOMs):

Pseudonymization and encryption

  • TLS 1.2+ for all data in transit (HTTPS, WSS, agent ↔ server, probe ↔ server, collector ↔ server)
  • Encryption at rest (Cloudflare D1, R2)

Confidentiality, integrity, availability, resilience

  • Per-tenant database isolation — each customer's data is stored in a separate Cloudflare D1 database
  • Multi-factor authentication required on administrative accounts
  • Per-IP rate limiting on authentication endpoints
  • Account lockout after 10 failed login attempts in 15 minutes
  • Password complexity policy (12+ chars, mixed character classes) on all set-password flows
  • Login audit logging with anomalous-activity alerting
  • HTTPS enforced; HSTS preload
  • Cloudflare DDoS protection on all public endpoints

Availability and resilience

  • Cloudflare Workers global edge deployment
  • D1 daily automatic backups (Cloudflare-managed)
  • On-demand database backup to off-platform S3 storage for disaster recovery
  • Status page and incident communication at status.mantisops.net

Restoration of availability

  • Documented internal runbooks for database corruption, regional outage, account compromise, source-code repository loss and software-binary compromise

Regular testing

  • Annual review of access rights
  • Planned: annual third-party penetration test, SOC 2 Type I attestation

User identification and authorization

  • Per-tenant role-based access control
  • Session timeouts; HttpOnly / Secure / SameSite cookies
  • Optional SSO (SAML/OIDC) for enterprise customers

Logging and monitoring

  • Centralized, deduplicated error logging
  • Login attempt log per email + IP
  • Cloudflare usage analytics dashboard

Personnel

  • Confidentiality obligations on all personnel with access to Personal Data
  • Background-check process for new hires with administrative access (planned)
  • Off-boarding access revocation within one business day

Sub-processor management

  • Written contracts with all Sub-Processors imposing equivalent obligations
  • Public Sub-Processor list at https://mantisops.net/legal/sub-processors

Annex III — List of Sub-Processors

See Section 5.2 above and the live list at https://mantisops.net/legal/sub-processors.

← All legal documents