This Data Processing Addendum (the "DPA") forms part of the IdentityMesh End User License Agreement or other agreement under which SteadyDeveloper LLC ("SteadyDeveloper") licenses IdentityMesh to the customer named in the Order ("Customer") (the "Agreement"). It applies only to the limited personal data that SteadyDeveloper processes as described below. If there is a conflict between this DPA and the Agreement about the processing of personal data, this DPA controls.
1. Purpose and Narrow Scope
1.1 Self-hosted product. IdentityMesh is self-hosted software that Customer installs and runs on its own infrastructure, with its own SQL Server database. In normal operation, the identity, directory, and HR data that IdentityMesh processes ("Customer Data") stays on Customer's infrastructure, and SteadyDeveloper does not receive, host, or have access to it.
1.2 What this DPA covers. SteadyDeveloper processes personal data relating to Customer only through the following channels (together, the "Processing Channels"):
(a) Support sessions: remote screen-sharing or similar sessions that Customer initiates and controls, during which SteadyDeveloper personnel may view personal data displayed on Customer's systems;
(b) Logs and diagnostics: log files, configuration exports, screenshots, or diagnostic files that Customer chooses to upload or send to SteadyDeveloper for support; and
(c) Licensing and billing contacts: names, business email addresses, phone numbers, and similar business contact details of Customer personnel used for licensing, invoicing, account management, and support communications.
1.3 Out of scope. This DPA does not apply to: (i) Customer Data processed by IdentityMesh on Customer's infrastructure without SteadyDeveloper's access; (ii) data that Customer sends to a third-party AI provider using Customer's own API key, which is governed by Customer's agreement with that provider; (iii) data in third-party systems that Customer connects to IdentityMesh; or (iv) services provided by a reseller or other third party under its own agreement with Customer.
2. Definitions
2.1 "Personal Data," "Controller," "Processor," "Data Subject," "Processing," and "Supervisory Authority" have the meanings given in Data Protection Law. "Data Protection Law" means all data protection and privacy laws applicable to a party's Processing of Personal Data under the Agreement. "Support Data" means Personal Data that SteadyDeveloper receives through support sessions or logs and diagnostics. "Contact Data" means licensing and billing contact data. "Security Incident" means a breach of security leading to the accidental or unlawful destruction, loss, alteration, unauthorized disclosure of, or access to, Support Data in SteadyDeveloper's possession or control.
3. Roles of the Parties
3.1 Support Data. For Support Data, Customer is the Controller (or a Processor acting on behalf of its own Controller) and SteadyDeveloper is a Processor acting on Customer's behalf.
3.2 Contact Data. For Contact Data, each party is an independent Controller, and SteadyDeveloper processes Contact Data to manage the commercial relationship, issue licenses, invoice, provide support communications, and comply with law, as described in its privacy notice at https://identitymesh.com/legal/privacy-policy. Sections 4 through 10 apply only to Support Data.
3.3 Customer responsibilities. Customer is responsible for the lawfulness of the Personal Data it makes available to SteadyDeveloper, for providing any required notices to Data Subjects, and for minimizing Personal Data in uploads and support sessions where practical (for example, by redacting logs or using test data).
4. Processing Instructions and Details
4.1 Instructions. SteadyDeveloper will process Support Data only on Customer's documented instructions, which consist of the Agreement, this DPA, and Customer's support requests, unless required otherwise by law (in which case SteadyDeveloper will inform Customer unless the law prohibits it). SteadyDeveloper will not sell Support Data or use it for advertising, profiling, or training AI models.
4.2 Details of processing.
| Item | Description |
|---|---|
| Subject matter and purpose | Diagnosing and resolving support requests and maintaining the Software |
| Duration | For the duration of the support request, plus the retention period in Section 8 |
| Data Subjects | Customer's employees, contractors, and other individuals whose identity records appear in support sessions or uploaded files |
| Categories of Personal Data | Identity and directory attributes such as names, usernames, email addresses, group memberships, job and organizational data, account identifiers, and system log entries |
| Special categories | None intended. Customer will not knowingly send special-category data, and will redact it where practical |
| Location of processing | the United States |
4.3 Confidentiality of personnel. SteadyDeveloper will ensure that personnel authorized to process Support Data are bound by confidentiality obligations and access it only as needed for the support request.
4.4 Assistance. Taking into account the limited nature of the processing, SteadyDeveloper will provide reasonable assistance to Customer with Data Subject requests, data protection impact assessments, and consultations with Supervisory Authorities relating to Support Data. If SteadyDeveloper receives a Data Subject request about Support Data, it will refer the Data Subject to Customer.
5. Security Measures
5.1 SteadyDeveloper will implement and maintain appropriate technical and organizational measures to protect Support Data, including at least:
(a) encryption of Support Data in transit and at rest in SteadyDeveloper's support and file-transfer systems;
(b) access limited to authorized support personnel, with unique accounts and multi-factor authentication;
(c) support sessions conducted only when initiated or approved by Customer, with Customer able to end the session at any time, and no persistent or unattended remote access without Customer's written approval;
(d) storage of uploaded logs and diagnostics only in designated support systems, not on removable media or personal devices;
(e) security awareness training for personnel with access to Support Data;
(f) logging of access to Support Data where the support systems support it; and
(g) multi-factor authentication for all SteadyDeveloper staff access to support systems, and encryption of Support Data at rest and in transit.
5.2 Customer security. Customer is responsible for the security of its own infrastructure, the Software installation, credentials, and Customer Data.
6. Subprocessors
6.1 Authorization. Customer authorizes SteadyDeveloper to use subprocessors to process Support Data. Current subprocessors are: Microsoft Azure (hosting of the customer portal, support tickets and uploads; United States) and Mailgun (transactional email; United States).
6.2 Obligations. SteadyDeveloper will enter into written agreements with subprocessors imposing data protection obligations no less protective than this DPA and remains responsible for their performance.
6.3 Notice of changes. SteadyDeveloper will give Customer at least 30 days' notice before adding or replacing a subprocessor, by updating the subprocessor list published at https://identitymesh.com/legal and notifying Customer by email. Customer may object on reasonable data protection grounds within that period. If the parties cannot resolve the objection, Customer may stop using the affected support channel or terminate the affected Order and receive a refund of prepaid fees for the unused portion of the Subscription Term.
7. Security Incident Notification
7.1 Notice. SteadyDeveloper will notify Customer without undue delay, and in any event within 72 hours, after becoming aware of a Security Incident.
7.2 Content and cooperation. The notice will describe, to the extent known, the nature of the Security Incident, the Support Data affected, the likely consequences, and the measures taken or proposed. SteadyDeveloper will take reasonable steps to contain and remediate the Security Incident and will cooperate reasonably with Customer's notification obligations.
7.3 No admission. Notification is not an acknowledgment of fault or liability.
8. Deletion and Return
8.1 Retention. SteadyDeveloper will delete uploaded logs and diagnostics within 90 days after the related support request is closed, unless Customer asks for earlier deletion or law requires longer retention.
8.2 End of the Agreement. When the Agreement ends, SteadyDeveloper will delete or, at Customer's written request made within 30 days, return Support Data in its possession, except copies retained as required by law or in routine backups, which remain protected under this DPA until deleted in the ordinary course.
8.3 Support sessions. SteadyDeveloper does not record support sessions unless Customer agrees in advance and deletes any recording within thirty (30) days after the related support request is closed.
9. International Transfers
9.1 Transfers. Support Data may be processed in the locations stated in Section 4. Where Data Protection Law restricts the transfer of Support Data from Customer's jurisdiction to SteadyDeveloper or a subprocessor, the parties will rely on the Standard Contractual Clauses adopted by the European Commission, and any equivalent transfer mechanism required under the laws of the United Kingdom, Switzerland, or another relevant jurisdiction, which are incorporated by reference with SteadyDeveloper as data importer and Customer as data exporter, using Module Two (controller to processor), with the docking clause in Clause 7 included, Option 2 (general written authorization) in Clause 9, and the law and courts of Ireland in Clauses 17 and 18. Where available, the parties may instead rely on another lawful transfer mechanism.
9.2 Conflict. If there is a conflict between this DPA and applicable transfer clauses, the transfer clauses control.
10. Audit
10.1 Information. On Customer's written request, not more than once in any twelve (12) month period (unless required by a Supervisory Authority or following a Security Incident), SteadyDeveloper will provide written responses to reasonable security questionnaires and information necessary to demonstrate compliance with this DPA.
10.2 Audits. If that information is not sufficient to demonstrate compliance, Customer may conduct an audit of SteadyDeveloper's processing of Support Data, at Customer's expense, on at least 30 days' notice, during business hours, by Customer or an independent auditor bound by confidentiality, in a manner that does not unreasonably disrupt SteadyDeveloper's business or compromise other customers' data.
11. General
11.1 Liability. Each party's liability under this DPA is subject to the limitations and exclusions of liability in the Agreement.
11.2 Term. This DPA remains in effect for as long as SteadyDeveloper processes Support Data under the Agreement.
11.3 Changes in law. SteadyDeveloper may update this DPA to reflect changes in Data Protection Law or its subprocessors as described above; other changes require Customer's agreement.
11.4 Contact. Privacy questions and notices under this DPA go to privacy@identitymesh.com.
11.5 Governing law. This DPA is governed by the law that governs the Agreement, except where Data Protection Law or applicable transfer clauses require otherwise.