[[ … ]] must be completed by qualified counsel. To request a signed copy, contact sales@isoxpert.com.This Data Processing Agreement ("DPA") forms part of the agreement under which the customer organisation ("Customer") subscribes to ISOXPERT Compliance360 - the Terms of Service at /terms together with any order form, quote or online subscription ("Agreement").
It sets out the terms required by Article 28 of the GDPR (and the equivalent UK provision) for the personal data ISOXPERT processes on the Customer's behalf, and the safeguards for the international transfers that this involves.
How it takes effect. [[Counsel to choose: (a) this DPA is incorporated into the Agreement automatically when the Customer accepts the Terms of Service; and/or (b) it takes effect when signed by both parties.]] A countersigned copy can be requested from sales@isoxpert.com.
The parties.
Terms such as controller, processor, data subject, personal data, processing, personal data breach, special categories of personal data and supervisory authority have the meaning given in the GDPR. In addition:
| Term | Meaning |
|---|---|
| Applicable Data Protection Law | Regulation (EU) 2016/679 ("GDPR"); the GDPR as retained in UK law ("UK GDPR") and the UK Data Protection Act 2018; [[the Swiss Federal Act on Data Protection, if Swiss data subjects are in scope]]; and [[any other law counsel decides to cover, e.g. an applicable GCC Personal Data Protection Law]] - in each case to the extent it applies to the processing. |
| Customer Personal Data | Personal data that ISOXPERT processes on behalf of the Customer in providing the Services, as described in Annex I.B. It excludes ISOXPERT Controller Data (Section 3.3). |
| Services | The ISOXPERT Compliance360 platform and related support provided under the Agreement. |
| Workspace | The Customer's organisation (tenant) in the Services, including all records, documents and files stored in it. |
| Authorised Users | People the Customer allows to use its Workspace. |
| Sub-processor | A third party engaged by ISOXPERT that processes Customer Personal Data (Section 8 and Annex III). |
| EU SCCs | The standard contractual clauses for the transfer of personal data to third countries annexed to Commission Implementing Decision (EU) 2021/914 of 4 June 2021. |
| UK Addendum | The International Data Transfer Addendum to the EU Commission Standard Contractual Clauses issued by the UK Information Commissioner under s119A Data Protection Act 2018 (version B1.0, in force 21 March 2022), as amended from time to time. |
| Restricted Transfer | A transfer of Customer Personal Data to a country that does not benefit from an adequacy decision (or UK adequacy regulations) applicable to that data. |
3.1 Customer as controller, ISOXPERT as processor. For Customer Personal Data, the Customer is the controller and ISOXPERT is the processor. The subject matter, duration, nature and purpose of the processing, the types of personal data and the categories of data subjects are set out in Annex I.B.
3.2 Customer acting as a processor. Where the Customer processes the personal data in its Workspace on behalf of a third-party controller (for example a consultant operating a client's management system), ISOXPERT acts as the Customer's sub-processor. The Customer warrants that its instructions, including the appointment of ISOXPERT and its Sub-processors, are authorised by that controller, and the Customer remains the single point of contact for ISOXPERT.
3.3 ISOXPERT as an independent controller (outside this DPA). ISOXPERT is a separate, independent controller - and this DPA does not apply - for the personal data it processes for its own purposes, as described in the Privacy Policy at /privacy ("ISOXPERT Controller Data"):
[[Counsel to confirm this controller/processor split, in particular whether Authorised User sign-in identities are Customer Personal Data or ISOXPERT Controller Data.]]
3.4 Customer responsibilities. The Customer is responsible for:
4.1 ISOXPERT processes Customer Personal Data only on the Customer's documented instructions, including with regard to Restricted Transfers, unless Union or Member State law (or, for UK data, UK law) to which ISOXPERT is subject requires otherwise. In that case ISOXPERT informs the Customer of that legal requirement before processing, unless the law prohibits this on important grounds of public interest.
4.2 The Customer's documented instructions are: (a) the Agreement and this DPA; (b) the Customer's and its Authorised Users' configuration and use of the Services, including requests to AI features; and (c) any other written instruction that the parties agree. Instructions outside the scope of the Services may be subject to [[agreement on fees and feasibility]].
4.3 ISOXPERT will immediately inform the Customer if, in its opinion, an instruction infringes Applicable Data Protection Law (GDPR Art. 28(3), final subparagraph). ISOXPERT is not obliged to perform a comprehensive legal review of instructions.
4.4 ISOXPERT will not sell Customer Personal Data, will not use it for its own purposes, and will not use it - or allow its Sub-processors to use it - to train artificial-intelligence models. [[Placeholder to confirm: the Google Gemini API no-training commitment is recorded in docs/legal/sub-processors.md as "paid API data not used for training", but the acceptance of Google's data-processing terms and the no-training clause is still an open item on the DPA tracking checklist. Confirm before signature.]]
ISOXPERT ensures that every person it authorises to process Customer Personal Data (employees and contractors) is bound by a contractual or statutory duty of confidentiality, has access only to the extent needed for their role, and receives [[data-protection and security awareness training at onboarding and at least annually]]. Platform-administrator access - which can reach every tenant - is a separately granted capability and is only effective on a session verified with multi-factor authentication (Annex II, item 2). ISOXPERT personnel access a Workspace only to provide, support, secure or maintain the Services, or as the Customer instructs.
6.1 ISOXPERT implements the technical and organisational measures described in Annex II, taking into account the state of the art, the costs of implementation, and the nature, scope, context and purposes of the processing, as well as the risks to data subjects.
6.2 ISOXPERT may update those measures as the Services evolve, provided the update does not materially decrease the overall level of protection.
6.3 Security of the Workspace is shared. The Customer is responsible for the measures within its control described in Section 3.4 and for the security of data it exports from the Services.
7.1 Self-service tools. Taking into account the nature of the processing, ISOXPERT assists the Customer through the following functions of the Services:
7.2 Erasure is an assisted, manual process. The Services do not yet include an automated per-person erasure function, and the change history (Annex II, item 6) cannot be edited or deleted through the application by design. On the Customer's written request to privacy@isoxpert.com, ISOXPERT will locate the data subject's personal data across the Workspace - including database records, the change history and stored files - and erase or pseudonymise it as the Customer instructs, within [[timeframe, e.g. 10 business days]] of a complete request, so that the Customer can meet the one-month deadline in Article 12(3). Where a record must be kept for audit integrity or by law, ISOXPERT will pseudonymise it if the Customer so instructs.
7.3 Requests received by ISOXPERT. If ISOXPERT receives a request from a data subject about Customer Personal Data, it will not respond on the merits (other than to tell the data subject to contact the Customer) and will forward the request to the Customer within [[timeframe, e.g. 5 business days]].
7.4 Cost. Assistance under this Section is [[provided at no additional charge, except for requests that are manifestly unfounded or excessive]].
8.1 General authorisation. The Customer gives ISOXPERT general written authorisation to engage Sub-processors. The Sub-processors in use on the effective date are listed in Annex III and on the public page at /sub-processors.
8.2 Notice of changes - 30 days. ISOXPERT will notify the Customer of any intended addition or replacement of a Sub-processor at least 30 days in advance, by [[email to the Workspace administrators and the Customer's notified privacy contact]] and by updating /sub-processors. [[Counsel to decide whether a shorter emergency-replacement procedure is needed when a Sub-processor fails or becomes unlawful to use.]]
8.3 Right to object. The Customer may object in writing within the 30-day notice period on reasonable data-protection grounds. The parties will discuss the objection in good faith. If they cannot resolve it, the Customer may terminate the affected Services by written notice before the change takes effect and receive [[a pro-rata refund of prepaid fees for the unused term]].
8.4 Sub-processor terms. ISOXPERT imposes on each Sub-processor, by written contract, data protection obligations that offer at least the same level of protection as this DPA (Art. 28(4)), including appropriate transfer safeguards. ISOXPERT remains fully liable to the Customer for the performance of each Sub-processor's obligations. On request, ISOXPERT will provide a copy of the relevant Sub-processor terms, which may be redacted to remove commercial information.
9.1 ISOXPERT will notify the Customer of a personal data breach affecting Customer Personal Data without undue delay and in any event within [[48 hours]] of becoming aware of it, by [[email to the Customer's notified privacy contact and Workspace administrators]].
9.2 The notification will include, to the extent then known (and in phases where necessary), the information required by Article 33(3):
9.3 ISOXPERT will take reasonable steps to contain, investigate and remediate the breach, cooperate with the Customer, and provide the information the Customer reasonably needs to notify supervisory authorities and data subjects (Arts. 33 and 34). ISOXPERT will not notify a supervisory authority or data subjects on the Customer's behalf unless the Customer instructs it to or the law requires it.
9.4 Notification is not an acknowledgement of fault or liability. ISOXPERT does not operate a 24/7 security operations centre; the notification period runs from the moment ISOXPERT becomes aware of the breach, including when a Sub-processor notifies ISOXPERT.
ISOXPERT will provide reasonable assistance, using information available to it, for any data protection impact assessment or prior consultation with a supervisory authority that the Customer carries out in relation to the Services - including a description of the processing (Annex I), the security measures (Annex II), the Sub-processors (Annex III), and how AI features handle personal data (Annex II, items 8 and 9). [[Cost of assistance beyond providing existing documentation.]]
11.1 Return. During the term, the Customer can export data from the Services using the export functions available in the application. On written request made within [[30 days]] after the Agreement ends, ISOXPERT will also provide an export of the Workspace in [[machine-readable format, e.g. JSON and CSV, plus stored files]].
11.2 Deletion. After that return window, ISOXPERT will delete the Workspace - its records in every organisation-scoped database table, its change history, and its files in storage - within [[timeframe, e.g. 60 days after the Agreement ends]]. Deletion is carried out by ISOXPERT personnel using internal tooling (it is not self-service), and each deletion is logged. ISOXPERT will confirm deletion in writing on request.
11.3 Backups. Copies held in the hosting provider's automated backups are not restored except for disaster recovery and are overwritten in line with the provider's rolling backup retention of [[backup retention period - confirm against the Supabase plan in use]]. Until then they remain protected by this DPA.
11.4 Legal retention. ISOXPERT may retain Customer Personal Data where Union or Member State law (or UK law) requires it, in which case it will keep the data confidential and process it only for the purpose required by that law.
12.1 Information. ISOXPERT will make available to the Customer all information necessary to demonstrate compliance with Article 28 and this DPA, including this DPA and its Annexes, the security overview at /trust, the current Sub-processor list, and written answers to a reasonable security and privacy questionnaire [[no more than once a year]].
12.2 Audits. ISOXPERT will allow for and contribute to audits, including inspections, by the Customer or an independent auditor mandated by the Customer (who must be bound by confidentiality and must not be a competitor of ISOXPERT), on the following terms:
12.3 Sub-processors. For audits of Sub-processors, ISOXPERT will make available the audit reports or certifications that the Sub-processor publishes or provides, and exercise its own audit rights on the Customer's behalf where those are insufficient.
12.4 No overstated assurance. ISOXPERT holds an ISO/IEC 27001 certificate covering the development and operation of Compliance360. It was issued by Company Certification International (CCI), a certification body related to ISOXPERT (see the Trust Center, sections 0 and 15). It is evidence that an information security management system was audited, not assurance from a body unconnected to ISOXPERT, and it may not satisfy a procurement requirement for an unconnected certifier. ISOXPERT does not hold a SOC 2 report. Nothing in this DPA states or implies that ISOXPERT's controls have been audited by an unconnected third party.
13.1 Where the data goes. ISOXPERT is established in Pakistan and its personnel operate and support the Services from there. Application data is hosted in Singapore (AWS ap-southeast-1, through Supabase), and some Sub-processors process data in the United States or globally (Annex III). Neither Pakistan nor Singapore is covered by an EU adequacy decision or UK adequacy regulations, so making Customer Personal Data available to ISOXPERT is itself a Restricted Transfer, in addition to the onward transfers to Sub-processors.
13.2 EU SCCs - Customer to ISOXPERT. To the extent Customer Personal Data subject to the GDPR is transferred to ISOXPERT, the parties enter into the EU SCCs, which are incorporated into this DPA by reference as follows:
| SCC element | Selection |
|---|---|
| Module | Module 2 (controller to processor) where the Customer is a controller; Module 3 (processor to processor) where the Customer is a processor under Section 3.2. |
| Clause 7 (docking clause) | Included. |
| Clause 9(a) (sub-processors) | Option 2 - general written authorisation, with at least 30 days' advance notice of changes (Section 8). |
| Clause 11(a) (redress) | The optional independent dispute-resolution wording is not included. |
| Clause 13 (supervision) | The supervisory authority identified in Annex I.C. |
| Clause 17 (governing law) | Option 1 - the law of [[Ireland/other EU member state]]. |
| Clause 18(b) (forum) | The courts of [[Ireland/other EU member state]] (the same member state as Clause 17). |
| Annex I | Annex I of this DPA (parties, description of transfer, competent supervisory authority). |
| Annex II | Annex II of this DPA (technical and organisational measures). |
| Annex III | Annex III of this DPA (list of sub-processors). |
The Customer is the "data exporter" and ISOXPERT the "data importer". The provisions of this DPA on audits (Section 12), deletion (Section 11), breach notification (Section 9) and sub-processor notice (Section 8) describe how the parties will carry out the corresponding SCC clauses; they do not modify the SCCs.
13.3 Onward transfers - ISOXPERT to Sub-processors (Module 3). Onward transfers by ISOXPERT are made only in accordance with Clause 8.8 and Clause 9 of the EU SCCs. Where a Sub-processor processes Customer Personal Data in a country without an adequacy decision, ISOXPERT relies on EU SCC Module 3 (processor to processor) in its agreement with that Sub-processor, or for a US-based Sub-processor certified under the EU-US Data Privacy Framework, on that certification with SCCs maintained as a fallback (Section 13.6). [[Counsel note: ISOXPERT is itself established outside the EEA. Confirm the legal analysis for the onward-transfer chain - each Sub-processor's own DPA (Annex III) incorporates the SCCs on its own terms, and the Module 3 "data exporter" role normally presumes an exporter subject to the GDPR. See EDPB Guidelines 05/2021 on the interplay between Article 3 and Chapter V.]]
13.4 UK transfers. For Customer Personal Data subject to the UK GDPR, the EU SCCs apply as amended by the UK Addendum set out in Schedule 1.
13.5 Swiss transfers. [[If Swiss data subjects are in scope: the EU SCCs apply with references to the GDPR read as references to the FADP, the FDPIC as the competent supervisory authority for transfers governed by the FADP, and "Member State" read to include Switzerland so that data subjects in Switzerland can sue there.]]
13.6 United States and the Data Privacy Framework. Some Sub-processors may also rely on the EU-US Data Privacy Framework (and its UK extension). Because the Commission's adequacy decision for the Framework is under appeal before the Court of Justice (Case C-703/25 P), Standard Contractual Clauses remain in place as a fallback so that transfers continue lawfully if the Framework is invalidated. [[Confirm each US Sub-processor's current DPF certification at dataprivacyframework.gov.]]
13.7 Transfer impact assessment. ISOXPERT has assessed, as required by Clause 14 of the EU SCCs, the laws and practices of the destination countries - including laws in Pakistan, Singapore and the United States that may allow public-authority access to data - and the supplementary measures in Annex II. [[Transfer impact assessment reference and date; counsel to complete or confirm. A summary will be made available to the Customer on request.]] ISOXPERT will comply with Clause 15 of the EU SCCs (obligations in case of access by public authorities), including notifying the Customer of legally binding requests where permitted, challenging unlawful requests and disclosing the minimum necessary.
13.8 Changes to transfer mechanisms. If a transfer mechanism relied on in this Section is invalidated, amended or replaced (for example, by new SCCs for importers already subject to the GDPR under Article 3(2)), the parties will cooperate in good faith to adopt a valid alternative without undue delay.
Each party's liability under or in connection with this DPA is subject to the limitations and exclusions of liability in the Agreement. [[Counsel to decide whether data-protection liability is subject to the general cap, a separate cap, or uncapped.]] Nothing in this DPA limits either party's liability to data subjects under Clause 12 of the EU SCCs or Article 82 of the GDPR, or any liability that cannot be limited by law.
15.1 Term. This DPA applies for as long as ISOXPERT processes Customer Personal Data, and Sections 9, 11, 12 and 13 survive until all Customer Personal Data has been returned or deleted.
15.2 Order of precedence. In the event of conflict: (1) the EU SCCs and the UK Addendum prevail; then (2) this DPA; then (3) the rest of the Agreement. On any matter concerning the processing of Customer Personal Data, this DPA prevails over the Agreement.
15.3 Governing law. Other than the EU SCCs and the UK Addendum (which are governed as set out in Section 13 and Schedule 1), this DPA is governed by [[the law governing the Agreement]].
15.4 Changes. ISOXPERT may update this DPA to reflect changes in Applicable Data Protection Law or a supervisory authority's guidance. Any change that materially reduces the protection given to Customer Personal Data requires the Customer's agreement. Sub-processor changes follow Section 8.
| Customer | ISOXPERT | |
|---|---|---|
| Name | [[ ]] | [[ ]] |
| Title | [[ ]] | [[ ]] |
| Signature | [[ ]] | [[ ]] |
| Date | [[ ]] | [[ ]] |
Data exporter(s)
| Name | The Customer as identified in the Agreement: [[CUSTOMER LEGAL NAME]] |
| Address | [[CUSTOMER ADDRESS]] |
| Contact person | [[name, position and email of the Customer's privacy contact]] |
| Activities relevant to the transfer | Use of ISOXPERT Compliance360 to operate the Customer's governance, risk, compliance and management-system activities (for example ISO 9001, ISO 45001, ISO/IEC 27001, ISO 22000 and social-compliance programmes). |
| Role | Controller (Module 2) or processor (Module 3) |
| Signature and date | As in the Signatures section, or by acceptance of the Agreement |
Data importer(s)
| Name | [[REGISTERED LEGAL ENTITY NAME]], trading as ISOXPERT |
| Address | [[REGISTERED ADDRESS]], Karachi, Pakistan |
| Contact person | Privacy contact, privacy@isoxpert.com |
| EU / UK representative | [[EU REPRESENTATIVE]] / [[UK REPRESENTATIVE]] |
| Activities relevant to the transfer | Provision, hosting, support and maintenance of the ISOXPERT Compliance360 software-as-a-service platform. |
| Role | Processor |
| Signature and date | As in the Signatures section, or by acceptance of the Agreement |
Categories of data subjects. Determined by the Customer's use, typically:
Categories of personal data.
Profile photographs are not collected.
Sensitive data transferred (if applicable) and safeguards. Depending on the modules the Customer uses, the Workspace may contain special categories of personal data, in particular:
Safeguards applied: tenant isolation and role-based access (Annex II, items 1 and 3); the immutable change history and electronic signatures (item 6); redaction of people from AI requests (item 8); in-form warnings with one-click removal of names from incident and observation free text (item 8); social-audit evidence of payroll, attendance, worker interviews and photographs held by reference only, without upload (item 8); and the Customer's undertaking to record people in structured fields (Section 3.4). The Customer is responsible for the Article 9(2) condition. [[Customer to confirm the special categories it will process and its Article 9(2) condition.]] Criminal-offence data is not intended to be processed.
Frequency of the transfer. Continuous, for the duration of the Agreement.
Nature of the processing. Hosting and storage; recording, organisation, structuring, retrieval and consultation; AI-assisted drafting and analysis at a user's request; transmission of notification emails; export; support and maintenance access; and deletion.
Purpose(s) of the processing. Providing the Services under the Agreement: the platform's management-system modules, AI assistance, notifications, support, and keeping the Services secure and available.
Retention. For the term of the Agreement, subject to deletion by the Customer within the Workspace and to Section 11 (return and deletion). [[Confirm the retention applied by the AI provider to API requests, e.g. abuse-monitoring logs, and state it here.]]
Transfers to Sub-processors. As set out in Annex III, for the subject matter, nature and duration stated there (duration: the term of the Agreement unless stated otherwise).
In accordance with Clause 13 of the EU SCCs:
For transfers governed by the UK GDPR: the Information Commissioner's Office. [[For transfers governed by the Swiss FADP, if applicable: the FDPIC.]]
Measures provided by an underlying platform rather than built by ISOXPERT are identified as such.
get_my_org_ids()), so a query that omits a filter returns nothing rather than
another customer's data. Uploaded files are stored in private storage buckets keyed by
organisation, so a file reference for one organisation cannot address another's. Server-side API
routes run with elevated database credentials, so routes acting for a signed-in user pass through
a single access gate (apiGuard) that checks authentication, email confirmation, organisation
membership, role and request method, and applies rate limits; routes authenticated by other
means (scheduled jobs, payment webhooks, organisation API keys) verify those credentials
themselves.The Customer authorises the following Sub-processors. The current list is maintained at /sub-processors.
| Sub-processor | Purpose | Customer Personal Data processed | Location | Transfer safeguard | Duration |
|---|---|---|---|---|---|
| Supabase [[contracting entity and address]] | Database, authentication, file storage | All Workspace data (account, employee, compliance records, files, change history) | Singapore (AWS ap-southeast-1) | Supabase DPA incorporating SCCs | Term of the Agreement |
| Google (Gemini API) [[contracting entity, e.g. Google LLC or Google Cloud EMEA]] | AI drafting and analysis on user request | Content submitted to AI features, after redaction (Annex II, item 8) | United States / global | Google data-processing terms incorporating SCCs [[confirm acceptance and no-training clause]] | Per request, plus provider retention [[confirm]] |
| Vercel [[contracting entity]] | Application hosting and serverless functions | Request data in transit through the application and API | United States (serverless functions) / global edge | Vercel DPA incorporating SCCs | Term of the Agreement |
| Resend [[contracting entity]] | Transactional email notifications | Recipient names and emails; notification content (record titles, assignees, due dates) | United States / global | Resend DPA incorporating SCCs | Term of the Agreement |
| Stripe [[contracting entity]] | Billing and payments | Primarily ISOXPERT Controller Data (organisation, plan, subscription metadata); listed for transparency. Card data is handled by Stripe. | United States / global | Stripe DPA (within the Stripe Services Agreement) incorporating SCCs | Term of the Agreement |
Not Sub-processors. ERP integrations (SAP, Oracle, Odoo) are enabled and configured by the Customer, which contracts with those providers directly; data exchanged with them is under the Customer's own arrangements (Section 3.4).
For Restricted Transfers of Customer Personal Data subject to the UK GDPR, the parties enter into the UK Addendum, which is incorporated into this DPA by reference and completed as follows:
| UK Addendum table | Completed as |
|---|---|
| Table 1 - Parties | The parties, their details, contacts and roles are as set out in Annex I.A. The start date is the effective date of this DPA. |
| Table 2 - Selected SCCs, Modules and Selected Clauses | The Approved EU SCCs, including the Appendix Information, as incorporated by Section 13.2: Module 2 (and Module 3 where Section 3.2 applies); Clause 7 docking clause included; Clause 9(a) general written authorisation with 30 days' notice; Clause 11 optional wording not included. |
| Table 3 - Appendix Information | Annex I.A (list of parties), Annex I.B (description of transfer), Annex II (technical and organisational measures) and Annex III (list of sub-processors) of this DPA. |
| Table 4 - Ending this Addendum when the Approved Addendum changes | [[Importer / Exporter / neither party]] may end the UK Addendum as set out in its Section 19. |
The Mandatory Clauses of the Approved Addendum (Part 2) apply. Under them, the EU SCCs as they apply to UK transfers are governed by the laws of England and Wales, disputes are resolved by the courts of England and Wales, and the competent supervisory authority is the Information Commissioner. If there is a conflict between the UK Addendum and this DPA for a UK transfer, the UK Addendum prevails.