1. Roles and scope
The customer is the controller of the personal data in its workspace; Zmle Technology, LLC is the processor. Where the customer itself acts for others, it is a processor and we are its sub-processor. This agreement applies to that processing, forms part of the terms of service, and is meant to meet article 28 of the GDPR and UK GDPR, and the service provider contract terms of the California Consumer Privacy Act and similar laws. Annex 1 describes the processing.
This agreement is the same for every customer, wherever it is established. It is built on article 28 of the GDPR and the UK GDPR as the baseline; where the data protection law that applies to you requires more, tell us and we will agree the additional terms that law requires in writing.
2. Instructions
We process customer data only on your documented instructions, unless the law requires otherwise, in which case we tell you first where allowed. Using the service as configured is such an instruction. We tell you if we think an instruction breaks data protection law. We do not sell customer data, do not share it for advertising, do not use it for our own purposes outside this agreement, do not combine it with other data except as the law allows a service provider, and do not use it to train AI models. We comply with the law that applies to us and tell you if we can no longer do so.
3. Confidentiality
Everyone who can access customer data is bound by confidentiality and accesses it only as needed to provide the service or support you asked for. Our support staff can open a workspace only while its owner has granted support access in the workspace: view-only by default or full, for 1 hour, 24 hours or 7 days, revocable at any time, and revoking it ends the session on the next request. The support person also needs a ticket id and a fresh authenticator code, and every session appears in the workspace's own activity log. Without a grant, access is possible only for a declared security incident: the owner is told at once and the access is reviewed within 24 hours.
4. Security measures
We keep the technical and organisational measures in Annex 2. We may change them if the level of protection does not fall.
5. Sub-processors
You give general authorisation to the sub-processors in the list at zmle.com/legal/subprocessors. If you signed this agreement we e-mail you at least 30 days before adding or replacing one, so you can object on reasonable data protection grounds by replying before the change takes effect. If we cannot resolve the objection, you may end the affected service before the change with a pro rata refund of prepaid fees for it. We bind each sub-processor by contract to the same data protection duties and stay liable for its work.
AI providers that you connect to your workspace with your own keys or accounts are engaged by you: they are your own processors, not our sub-processors, and your agreement with that provider governs their processing. The same holds for the payment gateway, SMS, WhatsApp, courier, e-invoicing and other accounts you connect. We send personal data to such a provider only when a user or a rule of your workspace uses that function, and we store the keys encrypted. We do not provide, resell or meter AI for your workspace.
6. Assistance
We help you respond to requests from individuals: the workspace has export, correction, anonymisation and consent tools, and we pass on any request that reaches us without answering it ourselves. We help with security, breach notification, impact assessments and consultation with authorities, taking into account the nature of the processing.
7. Personal data breaches
We notify the workspace owner without undue delay after becoming aware of a personal data breach affecting your data, where feasible within 48 hours, with what we know: its nature, the data and people concerned, likely consequences, measures taken and a contact. We add information as it becomes available. We keep a record of each breach.
8. Return and deletion
While the subscription is active you can export your data from the workspace at any time. When the owner closes the workspace, its data is erased 30 days later; when the subscription ends in another way (cancelled at the end of a billing period, or ended after 60 days of suspension for non-payment), 90 days after it ended. Until then a copy can be handed over on request. The export copy made before an erasure is deleted 90 days after it was made. Backup copies of an erased workspace are kept for 30 days after erasure, only for disaster recovery, and are then deleted. Data we must keep by law, such as our own invoices to you, is kept only as long as that law requires.
9. Audits
We make available the information needed to show compliance with this agreement and allow reasonable audits, including inspections, by you or an auditor you appoint, with reasonable notice and confidentiality. We hold no ISO/IEC 27001 certificate or SOC 2 report at this time; what we do not claim is listed at zmle.com/security.
10. International transfers
Customer data is processed where the listed sub-processors process it and where our staff work (the United States of America (State of Delaware)). Where the GDPR applies to you and data goes to a country without an adequacy decision, the standard contractual clauses of Commission Implementing Decision (EU) 2021/914 are incorporated into this agreement: module 2 where you are a controller, module 3 where you are a processor. For them: clause 7 (docking) applies; under clause 9(a) option 2 applies with the notice period of section 5; the optional wording in clause 11 does not apply; for clauses 17 and 18 the governing law and courts are those of the EU Member State where the customer is established or, if it has none there, the Member State of its representative; annexes I to III are Annex 1, Annex 2 and the sub-processor list. Where the UK GDPR applies, the UK Addendum issued by the Information Commissioner (version B1.0) applies as well, with its tables filled from this agreement, or, where we agree it instead, the UK International Data Transfer Agreement (IDTA). Where the Swiss data protection act applies, the clauses apply with the changes the Swiss authority requires. If the clauses conflict with this agreement, the clauses prevail. We tell you about any binding request from an authority for customer data unless the law forbids it, and we challenge a request we consider unlawful. Where the data protection law of another country restricts transfers of personal data abroad, the standard contractual clauses incorporated above, together with the measures of this agreement, are the safeguard we offer; if that law requires a specific form or registration, tell us and we will cooperate with you in completing it.
11. Health and other sensitive data
Only use apps made for health, children's or other special-category data with the protections your law requires. Tell us before you start if you need a particular data location or additional measures. The clinical apps encrypt notes field by field and log chart access; AI features stay away from clinical notes unless consent is recorded. You remain responsible for the assessments, consents and registrations your law requires.
12. Governing law and contact
Apart from section 10, this agreement follows the governing law and courts of the terms of service (zmle.com/legal/terms), unless the data protection law that applies to you requires otherwise. If this agreement conflicts with the terms, this agreement prevails for personal data. Data protection questions: support@zmle.com. Data protection officer: none named yet; use the privacy contact above. EU representative: none named yet. UK representative: none named yet.
13. Changes to this agreement
We may change this agreement under the rules of section 19 of the terms of service (zmle.com/legal/terms), with these additions. A change never lowers the protection of customer data below what article 28 of the GDPR and UK GDPR, the standard contractual clauses or the other data protection law that applies to you require. A material change, such as a narrower duty of ours or a longer retention, is announced at least 30 days before it takes effect, by e-mail to the workspace owner and to the signatory of this agreement and in the workspace; if you object on reasonable data protection grounds before it takes effect and we cannot resolve the objection, you may end the affected service with a pro rata refund of prepaid fees for it. A change required by data protection law or by an authority, or needed to protect the security of customer data, may take effect sooner, with notice as soon as we reasonably can. Changes of the security measures follow section 4. New or replaced sub-processors follow section 5 only: at least 30 days' notice and your right to object; nothing in this section shortens that notice or that right. Every published version of this document stays available, with its effective date and a summary of what changed, at zmle.com/legal/dpa; each version has its own address (zmle.com/legal/dpa/v/1, /v/2 and so on).
Annex 1. Description of the processing
Exporter: the customer, identified at sign-up and in the signature. Importer: Zmle Technology, LLC, 131 Continental Dr, Suite 305, Newark, DE 19713, United States, contact support@zmle.com. Activities: hosting and operating the business software and websites the customer configures.
People: the customer's customers, leads, suppliers, staff, website visitors and other people the customer records.
Data: whatever the customer enters or collects, typically contact and identity details, transactions, invoices, bookings, messages, staff and payroll data, and usage logs. Only if the customer uses those apps: health data, children's data, location of staff on duty, identity documents. Safeguards for those: section 11.
Frequency: continuous while the subscription runs. Nature and purpose: storage, retrieval and use as needed to provide the service and support. Retention: section 8. Sub-processors: the same subject and duration, for the purposes in the list. Competent authority: the one competent for the customer under clause 13 of the clauses.
Annex 2. Security measures (technical and organisational measures)
Separation: each workspace has its own database schema and its own database role, so the database itself refuses a query that reaches into another workspace; tables shared by several workspaces use row level security; the database is not reachable from the internet.
Access: role-based permissions that can be limited to a branch; two-step sign-in or passkeys, which the customer can require for chosen roles and which every member of our staff must use; a fresh confirmation before sensitive actions such as bulk exports; slowing down and locking after repeated failed sign-ins; support access only while the owner's grant is live (section 3).
Encryption: HTTPS in transit, with browsers told to use nothing else (HSTS); passwords and API, MCP and SCIM tokens stored only as hashes; provider secrets and two-step sign-in seeds encrypted with AES-256-GCM under a separate key for each workspace; clinical notes encrypted field by field; backups and archived database changes encrypted with AES-256 and checked for integrity before a restore. Encryption of the database server's disks is not yet confirmed and is not claimed.
Logging: an activity log per workspace whose entries are chained by hashes, so a changed, reordered or deleted entry is detected; every action of our operators written to the platform audit log; export of the activity log and a stream to the customer's SIEM.
Resilience: encrypted backups every hour, nightly backups that include files, continuous archiving of database changes for point-in-time recovery, an off-site copy with a different provider than the server, a copy before every release, and automatic restore tests.
Software: uploaded files scanned for malware; a content security policy and other security headers; public forms and endpoints validated and rate-limited; signed release images and update bundles; dependencies and code scanned for known vulnerabilities and leaked secrets.
People: staff get only the capabilities their job needs, and every operator accepts a confidentiality acknowledgement.
Incidents: a written procedure for detecting and handling incidents, notice to affected customers as in section 7, a review after every incident, and security reports through zmle.com/security/disclosure.
We hold no ISO/IEC 27001 certificate or SOC 2 report, and no independent penetration test has been published yet.