Data Processing Agreement
Last updated: 30 July 2026
This Data Processing Agreement (the “DPA”) sets out the terms on which the service operator (“ParoWorks”, “we”, the “Processor”) processes personal data on behalf of a customer of the ParoWorks platform (“you”, the “Customer”, the “Controller”). It gives effect to Article 28 of the UK GDPR and forms part of the Terms of Service. “UK GDPR” and “Data Protection Law” mean the UK General Data Protection Regulation and the Data Protection Act 2018, and any legislation replacing or amending them. Terms such as controller, processor, personal data, processing, data subject and personal data breach carry the meanings given to them there.
1.Scope and how this fits
1.1. This DPA applies to ParoWorks's processing of Customer Personal Data — personal data contained in the project and business data you put into the Service, most obviously the names, site addresses, contact details and pricing of your own customers.
1.2. It does not apply to personal data for which ParoWorks is itself the controller — your account, billing and usage data. That processing is governed by our Privacy Policy, not by this DPA. Clause 2 explains the boundary.
1.3. This DPA takes effect when you first use the Service and continues for as long as we process Customer Personal Data for you. No signature is required for it to apply — it is incorporated into the Terms of Service. If your organisation needs a countersigned copy for its own records, ask us and we will provide one.
1.4. If this DPA and the Terms of Service conflict on a question of data protection, this DPA prevails.
2.Roles of the parties
2.1. For Customer Personal Data you are the controller and ParoWorks is the processor. You decide whose details go into the Service, why, and for how long; we act on your instructions.
2.2. For your account, billing and usage data — the identity and contact details of your own staff who use the Service, your subscription and payment records, sign-in and diagnostic logs — ParoWorks is the controller in its own right.
2.3. The line between the two is who decided the purpose. A site contact's phone number is in the Service because you put it there to price a job: yours. A log line recording that someone signed in from a given address exists because we need it to secure and operate the platform: ours.
2.4. You confirm that you have a lawful basis for the Customer Personal Data you enter, that you have given the required information to the individuals concerned, and that your instructions to us comply with Data Protection Law. We do not check this and are not in a position to.
3.Processing instructions
3.1. ParoWorks processes Customer Personal Data only on your documented instructions, including as to transfers outside the UK, unless required to do otherwise by law — in which case we will tell you before processing, unless the law forbids it (UK GDPR Art. 28(3)(a)).
3.2. Your instructions are: the Terms of Service, this DPA, and the actions you and your users take in the Service. Together those are the complete instruction set. Anything outside them needs to be agreed in writing, and may attract a charge if it requires work we do not otherwise do.
3.3. If we consider an instruction to infringe Data Protection Law, we will tell you (UK GDPR Art. 28(3), final paragraph). We may suspend the instruction until it is resolved.
3.4. We do not use Customer Personal Data for our own purposes, do not sell or share it, and do not use it to train third-party AI models. Where we derive statistics to improve the Service, they are aggregated and do not identify you, your customers or any individual.
4.Confidentiality
4.1. Everyone ParoWorks authorises to process Customer Personal Data is bound by a duty of confidence, whether contractually or by statute (UK GDPR Art. 28(3)(b)), and is given access only to what their role requires.
4.2. The duty survives the end of their engagement and the end of this DPA.
5.Security
5.1. ParoWorks implements technical and organisational measures appropriate to the risk, as required by UK GDPR Art. 32. The measures in force are set out in Annex 3.
5.2. We may change those measures as the Service develops, provided the level of protection is not reduced.
6.Information and audit
6.1. ParoWorks will make available the information reasonably necessary to demonstrate compliance with this DPA and with Art. 28 (UK GDPR Art. 28(3)(h)).
6.2. In the first instance this means documentation: this DPA, the measures in Annex 3, the sub-processor list in Annex 2, and the sub-processors' own security documentation where we are permitted to pass it on.
6.3. You may audit our compliance, or appoint an independent auditor to do so, on 30 days'proposed written notice, no more than once in any twelve-month period unless a personal data breach or a supervisory authority requires otherwise. Audits take place during business hours, must not unreasonably disrupt the Service or affect other customers' data, and are at your cost.
6.4. We are a small provider and hold no third-party security certification at present. We would rather tell you that than have an audit discover it.
7.Assistance with data subject rights
7.1. The Service gives you direct access to the Customer Personal Data you hold in it, and the ability to view, correct, export and delete it yourself. For most access, rectification, erasure and portability requests you will not need us at all — that is the intended route.
7.2. Where you do need us, we will provide reasonable assistance by appropriate technical and organisational measures, insofar as possible, so you can respond to requests from data subjects exercising their rights (UK GDPR Art. 28(3)(e)).
7.3. If a data subject contacts ParoWorks directly about Customer Personal Data, we will not respond to the substance ourselves. We will tell them to contact you, and tell you promptly.
8.Sub-processors
8.1. You give ParoWorks general written authorisation to engage sub-processors (UK GDPR Art. 28(2)). The sub-processors engaged as at the date of this DPA are listed in Annex 2.
8.2. We will give you at least 30 days'proposed notice before adding or replacing a sub-processor, by updating Annex 2 and notifying you by email or in-product notice.
8.3. You may object to a new sub-processor on reasonable data protection grounds within that notice period. If we cannot resolve your objection, you may terminate your subscription without penalty and receive a pro-rata refund of fees paid for the unused remainder of the term. We would rather lose the subscription than move your data somewhere you have said no to.
8.4. Every sub-processor is engaged under a written contract imposing data protection obligations equivalent to those in this DPA, and ParoWorks remains fully liable to you for their performance (UK GDPR Art. 28(4)).
9.Breaches, DPIAs and consultation
9.1. ParoWorks will notify you without undue delay, and in any event within 48 hoursproposed of becoming aware, of a personal data breach affecting Customer Personal Data. The notification will describe the nature of the breach, the categories and approximate number of data subjects and records affected, the likely consequences, and the measures taken or proposed — to the extent we know them at the time, with further detail following as it becomes available.
9.2. It is your decision, as controller, whether to notify the ICO under Art. 33 and affected individuals under Art. 34. Our 48-hour commitment exists so your own 72-hour clock is not already half spent by the time you hear from us.
9.3. We will provide reasonable assistance with data protection impact assessments and any prior consultation with the ICO, taking into account the nature of the processing and the information available to us (UK GDPR Art. 28(3)(f), Arts. 35–36).
10.International transfers
10.1. Some sub-processors process personal data outside the UK — see the Location column in Annex 2. Where Customer Personal Data is transferred outside the UK, ParoWorks will ensure an appropriate transfer mechanism under UK GDPR Chapter V is in place, being one of: UK adequacy regulations for the destination; the UK International Data Transfer Agreement (IDTA); the EU Standard Contractual Clauses with the ICO's UK Addendum; or, for a provider certified under it, the UK Extension to the EU–US Data Privacy Framework.
10.2. We will tell you which mechanism applies to a given sub-processor on request, and provide a copy of the relevant terms where the provider permits it.
10.3. You instruct us to make these transfers by using the Service.
11.Liability
11.1. Each party is responsible for its own compliance with Data Protection Law in the role clause 2 gives it.
11.2. The limitations and exclusions of liability in clause 9 of the Terms of Service apply to claims under this DPA, and the cap is a single aggregate cap across both documents rather than a separate one for each.
11.3. Nothing in this DPA limits a data subject's rights, or either party's liability to a data subject or to a supervisory authority, under UK GDPR Art. 82.
12.Return and deletion of data
12.1. At the end of the provision of services, ParoWorks will delete or return all Customer Personal Data at your choice, and delete existing copies, unless UK law requires us to keep it (UK GDPR Art. 28(3)(g)).
12.2. In practice: for 30 days after your subscription ends your data remains available so you can export it from the Service (Terms clause 11.3), and you may ask us for an export instead. After that period we may delete it.
12.3. Deleting your account in Settings deletes the workspace and every record it owns immediately — customers, sites, quotes, invoices and price book — by database cascade, and removes the sign-in credential. It is not reversible. Deleting an individual uploaded file removes the stored file itself as well as its record.
12.3.1. That includes the stored file objects, not only the records that index them. Deleting a workspace enumerates every file it owns — uploaded drawings and site documents, and the page images derived from them — removes those objects from storage, and only then deletes the database rows, because the rows are what identify the files. If any part of that enumeration cannot be read, we remove nothing and the deletion fails with your account intact so it can be retried: a partial erasure is worse than none, because you would be told it had completed.
12.3.2. Two deliberate limits. A file whose stored location does not belong to your workspace is reported and never removed — acting on it would make your deletion someone else's data loss. And a team member removing their own account does not erase the workspace's files, which belong to the organisation rather than to them.
12.4. Backups held by our infrastructure providers expire on those providers' own cycles and are not individually editable. Data in an expiring backup is not restored to live systems and is overwritten in the ordinary course. The exact backup retention window is a property of the production hosting plan; we will confirm it on request rather than state a figure here that we have not verified.
13.Term, termination and governing law
13.1. This DPA runs for as long as ParoWorks processes Customer Personal Data for you. Clauses 4, 6, 11 and 12 survive its end.
13.2. This DPA is governed by the laws of England and Wales, and the courts of England and Wales have exclusive jurisdiction, matching clause 13 of the Terms of Service.
13.3. Contact for anything in this DPA: our data protection contact address, which is being finalised ahead of launch.
Annex 1.Details of processing
Required by UK GDPR Art. 28(3) opening paragraph.
- Subject matter
- Provision of the ParoWorks system-design, estimating and quoting platform to the Customer.
- Duration
- For the term of the Customer's subscription, plus the 30-day post-termination export window in clause 12.2.
- Nature and purpose
- Storage, organisation, retrieval, calculation and document generation, so that the Customer can design security and fire systems, price them, and produce quotes, purchase orders and invoices for its own customers. Transmission of those documents by email where the Customer sends them.
- Types of personal data
- Names, business and site addresses, telephone numbers, email addresses, job titles and correspondence of the Customer's own customers and site contacts; the commercial detail of the jobs quoted to them; and the content of drawings, specifications and other documents the Customer uploads, which may contain any of the above.
- Categories of data subject
- The Customer's own customers, their staff and site contacts, and the Customer's suppliers' contacts.
- Special category data
- None is required by the Service, and the Terms ask customers not to enter it. Because free-text fields and uploaded files cannot be policed, we cannot warrant that none is present — but no feature depends on it and none is deliberately collected.
Annex 2.Sub-processors
Authorised under clause 8. Every entry below was derived from the code that integrates it, not from a list kept separately, and each provider's own data processing agreement is linked from its name.
| Sub-processor | Purpose | Data | Location | Engaged |
|---|---|---|---|---|
| Supabase | Managed PostgreSQL database, authentication, and file storage. All Customer Data — customers, sites, quotes, price book, invoices, uploaded drawings and specifications — is held here. | Account data; all project and end-customer data entered into the Service; uploaded files. | The hosting region is a per-project setting on the Supabase side, so it is a deployment fact rather than a code fact — see the note under this table. | Always |
| Vercel | Application hosting, serverless function execution, edge network and request logging. Personal data passes through Vercel in transit on every request. | Any data submitted to or returned by the Service in transit; request metadata including IP address and user agent. | Global edge network, with function execution in the deployment's configured region. | Always |
| Stripe | Subscription billing for your ParoWorks plan, and — only if you switch on ParoWorks Payments — collecting card payments from your own customers through a Stripe connected account. | Billing contact details and payment card data (collected by Stripe directly; ParoWorks never stores full card numbers). Where ParoWorks Payments is enabled, your end customer's payment details also. | United Kingdom, European Economic Area and United States. | Always |
| Resend | Transactional email delivery — account and password emails, team invitations, quotes and invoices sent to your customers, purchase orders sent to your suppliers. | Recipient name and email address, and the content of the message including any quote or invoice detail in it. | European Economic Area and United States. | Always |
| OpenAI | Supplies the models behind the in-product AI assistant and document extraction. Engaged when an OpenAI API key is configured. Without a key, production AI requests are unavailable; local development can use a deterministic offline path. | Assistant questions, permitted quote and site memory context, retrieved document excerpts, and submitted images or PDFs. These may contain site and end-customer details entered or uploaded by users. | United States. | Only when the feature is switched on |
| Voyage AIVoyage AI's Terms of Service and public DPA body were checked on 5 October 2026. The terms provide a training opt-out that only covers later submissions, with immediate deletion after processing. This account's applicable agreement, opt-out state and effective date, retention controls, funding and limits remain unverified; no account-specific no-training or zero-retention guarantee is made. | Generates the numeric text embeddings used to search uploaded project documents. Engaged only when a Voyage API key is configured; with no key the adapter computes a deterministic offline stand-in and makes no network call. | Extracted text from uploaded documents and document-search questions, which may include site addresses and end-customer details. | United States. | Only when the feature is switched on |
| Microsoft Azure Document Intelligence | Managed OCR and document extraction for supported uploads requiring that path, including scanned pages and Office files. Engaged when the Document Intelligence endpoint and key are configured and managed extraction is selected; selectable PDF text can be extracted locally. | Uploaded document or image bytes and the text extracted from them. These may contain site, employee and end-customer details supplied by users. | The configured Azure resource region. ParoWorks's current production resource is in UK South, verified on 5 October 2026; this is a deployment fact rather than a region guaranteed by code. | Only when the feature is switched on |
The last two are engaged only when the optional AI features are switched on for the deployment. Those features are off by default: with no provider key configured, the adapters run a deterministic offline path and make no network call, so no data reaches those providers at all.
Supabase's hosting region is a setting on the Supabase project rather than something the application code controls, so it is not stated as a fact above. We will confirm the region of the live project in writing on request.
Annex 3.Security measures
The technical and organisational measures in force under clause 5 and UK GDPR Art. 32. This is a description of what the Service actually does, not an aspiration.
- Tenant isolation enforced in the database. Every tenant-owned table carries PostgreSQL row-level security policies, so a query for another workspace's rows returns nothing regardless of what the application asks for. The boundary is in the database, not in application code.
- Server-side re-authorisation. Role and permission decisions are made again on the server for every privileged request; the browser's copy of a role controls only what the interface offers, never what the API allows.
- Encryption in transit (HTTPS/TLS) for all traffic to and from the Service, and encryption at rest as provided by the database and storage providers.
- Secrets are server-only. Modules that read a provider key are marked so that importing them into browser code fails the build rather than shipping the key path to the client, and a test derives the set of secret-reading modules from source so a new one cannot arrive unnoticed.
- Rate limiting on authentication and other sensitive endpoints, to bound credential-stuffing and abuse.
- Least-privilege internal access. Access to production data is limited to what support and operations genuinely require.
- Deletion on request by database cascade, as described in clause 12.3.
What we do not have, stated plainly so you can weigh it: no ISO 27001 or SOC 2 certification, no independent penetration test to date, and no formally documented and rehearsed backup-restore procedure. A restore drill is a known outstanding item rather than something we have quietly skipped.