Privacy Policy
Last updated: 5 October 2026
This Privacy Policy explains how the service operator (“ParoWorks”, “we”, “us”, “our”) handles personal data when you use the ParoWorks platform (the “Service”), under the UK General Data Protection Regulation (“UK GDPR”) and the Data Protection Act 2018. If you are a ParoWorks customer, read clause 2 first — it decides which of the rest applies to you.
1.Who we are
ParoWorks is a system-design and estimating platform for UK security and fire installers, operated by the service operator.
Our privacy contact details are being finalised ahead of launch; this section will be completed shortly.
2.Controller or processor?
This is the most important clause in the policy, because ParoWorks is both, for different data, and which one we are changes who is answerable for what.
For your own account, billing and usage data, we are the controller. We decide what to collect and why: who your users are, what they are entitled to, what you have paid, what the system logged. This policy describes that processing and we answer for it.
For the customer and project data you put into the Service, you are the controller and we are your processor. The names, site addresses, contact details, job details and pricing of your own customers are yours. You decided to collect them and why; we hold and process them on your instructions, as set out in our Data Processing Agreement, which UK GDPR Art. 28 requires and which forms part of your contract with us.
The practical consequences are worth spelling out:
- If one of your customers asks what data is held about them, that request is for you to answer. We will help you answer it, and if they contact us directly we will point them back to you rather than answer for you.
- You are responsible for having a lawful basis for the details you enter, and for telling those individuals that you use a third-party system to do it. Naming ParoWorks in your own privacy notice is the usual way.
- We do not decide what happens to that data. We do not use it for our own purposes, do not sell it, and do not use it to train AI models.
- If you want to know what we hold about you — a named user of the Service — that is a request to us under clause 11, because for that data we are the controller.
Where an individual is both (your named contact at a customer company who also has a ParoWorks login), both roles apply to different records about the same person.
3.Data we collect
As controller
- Account data: name, work email address, company name, password (stored hashed by our authentication provider), role, and seat assignment within your workspace.
- Billing data: billing name and address, subscription tier and transaction history. Card details are collected and processed by Stripe directly — we receive limited billing metadata such as the last four digits of a card, and never store a full card number.
- Usage and diagnostic data: sign-in activity, feature usage, browser and device information, IP address, and error diagnostics, used to operate, secure and improve the Service.
As processor, on your instructions
- Project and customer data you enter: your customers and their site contacts, site addresses, system designs, price book entries, quotes, purchase orders and invoices.
- Files you upload: drawings, specifications, surveys and correspondence attached to a customer or site, which may contain personal data we have no way to anticipate.
- AI assistant queries, where the optional assistant is enabled: the question asked and the quote context needed to answer it. See clause 7 — the assistant is off unless an AI provider key is configured for the deployment.
4.Lawful bases
These are the bases we rely on for the data we control (clause 2). For data we merely process on your behalf, the lawful basis is yours to establish, not ours.
- Performance of a contract (Art. 6(1)(b)) — to create and administer your account, provide the Service you subscribed to, take payment, and support you.
- Legitimate interests (Art. 6(1)(f)) — to secure the Service against fraud and abuse, to diagnose faults, to understand which features are used, and to tell existing customers about the Service. You can object at any time; for marketing, we will always stop.
- Consent (Art. 6(1)(a)) — for marketing to people who are not already customers, and for anything else we specifically ask for.
- Legal obligation (Art. 6(1)(c)) — for accounting and tax records we are required to keep.
5.We do not sell your data
We do not sell, rent or trade your personal data, your company's data, or your end customers' data. We share data only with the sub-processors in clause 7, only to run the Service, and otherwise only where the law requires it. We do not use your project or customer data to train AI models, and we do not expose it to other ParoWorks customers.
6.How we use your data
- To run the Service — producing designs, bills of materials, quotes and documents from what you enter.
- To take subscription payments and manage billing.
- To send the emails you ask us to send, and the account emails you need.
- To answer support requests and tell you about material service changes.
- To detect, investigate and prevent fraud, abuse and security incidents.
- To analyse aggregated, non-identifying usage patterns to improve the product.
- To meet our legal and regulatory obligations.
7.Sub-processors
These are the third parties that process personal data on our behalf. Each entry was derived from the code that integrates it, so the list reflects what the software actually does. Each provider's own data processing agreement is linked from its name.
| Sub-processor | Purpose | 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. | 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. | 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. | 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. | 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. | United States. | Only when the feature is switched on |
| Voyage AI | 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. | 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. | 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 |
AI processing depends on the configured feature and provider. OpenAI supplies assistant and extraction responses when its API key is configured. Microsoft Azure Document Intelligence performs managed OCR and extraction for supported uploads that require that path when its endpoint and key are configured; selectable PDF text can be extracted locally. Voyage AI separately supplies document-search embeddings when its key and indexing feature are configured. Without the relevant provider key, no data reaches that provider; production AI requests are unavailable rather than simulated.
If we add or replace a sub-processor we will update this list and give notice as set out in clause 8 of the Data Processing Agreement, where you also have a right to object.
8.International transfers
Some sub-processors process personal data outside the UK, including in the United States — see the Location column above. Where that happens we rely on a transfer mechanism recognised under Chapter V of the UK GDPR: 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.
We will tell you which mechanism applies to a particular provider on request. We would rather answer that specifically than claim a blanket safeguard here that turns out not to be the one in force.
9.Retention
We keep personal data only as long as we need it. The periods below are what we apply. Where a period is marked proposed it is a policy we have set but not yet finally confirmed, and we have said so rather than presented it as settled.
| Data | Kept for | Why |
|---|---|---|
| Your account data (name, work email, role, workspace membership) | For as long as the account exists, then deleted | Deleting your account in Settings removes your membership. A sole owner deleting their workspace removes its stored uploads and derived page images before deleting workspace records by database cascade. If file enumeration or removal fails, workspace deletion is refused and can be retried. Some files may already have been removed if a later step fails. Removing your membership does not erase the organisation's files; stored locations outside the workspace are left untouched and reported. See DPA clauses 12.3.1–12.3.2. |
| Your project and end-customer data (quotes, customers, sites, price book, uploaded files) | For as long as your subscription runs, plus 30 days | You control this data — you can delete any of it at any time. The 30-day window after a subscription ends exists so you can export it (Terms clause 11.3). |
| Billing and accounting records (invoices, payment history) | 6 years from the end of the accounting period | UK tax and VAT record-keeping requirements. These are kept even after account deletion, because we are required to keep them. |
| Application and security logs (sign-in events, request diagnostics, rate-limit counters) | 90 daysproposed | Long enough to investigate a security incident or a support problem after the fact, short enough that it is not a standing store of activity data. |
| AI assistant safety log (a redacted excerpt of a query that was refused or flagged) | For the lifetime of the account | Deliberately not rotated: detecting an account being used to abuse the assistant needs its whole history, not a rolling window. Deleted with the account. Only refused or flagged queries are recorded — ordinary assistant use is not. |
| Marketing contact details, where you have opted in | Until you unsubscribe, then 3 yearsproposed | The short tail after unsubscribing is a suppression record — we keep enough to remember not to contact you again. |
Backups held by our infrastructure providers expire on those providers' own cycles. Data in an expiring backup is not restored to live systems and is overwritten in the ordinary course.
10.Security
We apply technical and organisational measures appropriate to the risk. The full list is Annex 3 of the Data Processing Agreement, including a plain statement of what we do not have. In summary:
- Tenant isolation enforced in the database, by PostgreSQL row-level security policies rather than by application code — a query for another workspace's rows returns nothing whatever the application asks for.
- Server-side re-authorisation of every privileged request. The browser's copy of your role controls only what the interface offers, never what the API allows.
- Encryption in transit (HTTPS/TLS) for everything, and encryption at rest from our database and storage providers.
- Rate limiting on authentication and other sensitive endpoints.
- Internal access to production data limited to what support and operations require.
No system is completely secure and we do not claim otherwise. We hold no security certification at present, and say so in Annex 3 rather than leaving you to find out.
11.Your rights
Under UK GDPR you have the right to access the personal data we hold about you, to have it rectified if it is wrong, to have it erased subject to records we must keep, to receive it in a portable machine-readable format, to object to processing based on legitimate interests (always, for direct marketing), to have processing restricted in certain circumstances, and to withdraw consent where we rely on it, without affecting what was done before.
You can do much of this yourself: Settings lets you change your details, export your data, and delete your account.
Otherwise contact us using the details in clause 1 above once they are published. We will respond within one month. Where we need more information from you to identify you or to find what you are asking for, that month runs from when you give it (UK GDPR Art. 12A, as inserted by the Data (Use and Access) Act 2025).
If your data was entered by an installer using ParoWorks — you are their customer, not ours — we are only their processor for it. Send your request to them; we will pass it on and help them answer it, but the answer is theirs to give. See clause 2.
13.Breach notification
If we become aware of a personal data breach affecting data we control, we will notify the ICO within 72 hours where UK GDPR Art. 33 requires it, and tell affected individuals without undue delay where Art. 34 requires it.
For data we process on your behalf, the decision to notify is yours. We commit to telling you within 48 hoursproposed of becoming aware, so your own 72-hour clock is not already half spent when you hear from us. See clause 9 of the Data Processing Agreement.
14.Children and B2B use
ParoWorks is a business-to-business product for professionals in the security and fire industry. It is not directed at children and we do not knowingly collect personal data from anyone under 18. If you believe a child's data has reached us, tell us and we will remove it.
15.Changes to this policy
We may update this policy — for example when a sub-processor changes or the law does. We will update the “Last updated” date above and, for material changes, give reasonable notice by email or in-product notice before they take effect.
16.How to complain
If you are unhappy with how we handle personal data, tell us first using the details in clause 1 above once they are published. We will acknowledge your complaint within 30 days and tell you the outcome, as section 164A of the Data Protection Act 2018 (in force from 19 June 2026) requires.
You can also complain to the UK supervisory authority at any time, and you do not have to come to us first:
Information Commissioner's Office (ICO)
Wycliffe House, Water Lane, Wilmslow, Cheshire, SK9 5AF
Helpline: 0303 123 1113
Website: ico.org.uk