Template document. The text below is the standard Data Processing Agreement we offer customers. It is published here for procurement review. Final wording of any executed agreement should be reviewed by your legal counsel and may be tailored (sub-processor scope, audit cadence, liability cap) on Enterprise contracts. Nothing on this page is legal advice.
Required under UK GDPR Article 28 when you share personal data with us. This page is the canonical text — bookmark it, share with your DPO, then request a countersigned PDF when you're ready to sign.
We hold three roles for you under data-protection law:
We will: process only on your documented instructions, encrypt everything in transit and at rest, notify you within 24 hours of any personal-data breach, return or delete your data at the end of the contract, and give you reasonable audit rights. We will not: train AI models on your data, sell or share with third parties for advertising, or use your data after the contract ends.
This Data Processing Agreement (this “DPA”) is entered into between Vygard Ltd, a company registered in England and Wales (“Processor”, “we”, “us”) and the entity executing the underlying Service Agreement for the Vygard service (the “Controller”, “you”). Each a “Party”, together the “Parties”.
We provide the Vygard safety-monitoring service (the “Service”) to you under the terms of a Service Agreement (the “Agreement”). The Service necessarily involves the Processing of Personal Data relating to your workers and administrators. This DPA forms part of the Agreement and governs that Processing under UK GDPR Article 28 and, where applicable, EU GDPR Article 28.
Capitalised terms not defined here have the meaning given in UK GDPR. Specifically:
The subject matter of the Processing is the operation of the Service for the Controller. The nature, purpose, types of Personal Data and categories of Data Subjects are set out in Schedule A. This DPA is co-terminus with the Agreement and continues for the term of the Agreement plus any wind-down period specified in clause 11.
The Processor will:
We will give you at least 30 days' advance notice of any intended addition or replacement of a Sub-processor by publishing the change to this page (Schedule B below) and emailing the notification contact you provide. If you reasonably object on data-protection grounds, you may terminate the affected portion of the Service without penalty within the 30-day notice window.
To subscribe to Sub-processor change notifications, email legal@vygard.com.
Personal Data is hosted in the United Kingdom by default. Where a Sub-processor is located outside the United Kingdom (or, for EU customers, the European Economic Area), transfers are made under the appropriate transfer mechanism listed in Schedule B (UK International Data Transfer Agreement and / or EU Standard Contractual Clauses). Onward transfers by Sub-processors are governed by their own contractual arrangements that mirror this DPA.
You may audit our compliance with this DPA once per year with at least 30 days' written notice, by reviewing our up-to-date third-party security audits (ISO 27001 / SOC 2 when available), penetration test executive summaries, and responses to your supplied security questionnaire (SIG Lite, SIG Core or CAIQ). On-site audits may be substituted where these documents do not adequately answer a specific risk, at your cost and during business hours, subject to reasonable confidentiality terms. We will respond to audit requests within 5 working days.
You are responsible for responding to requests from Data Subjects exercising their rights under UK GDPR Chapter III. We provide tooling within the Service to fulfil access, rectification, restriction, erasure, portability and objection requests for Personal Data we hold on your behalf. If a Data Subject contacts us directly, we will redirect them to you within 2 working days unless prohibited by law.
We will notify your nominated security contact within 24 hours of becoming aware of a Personal Data Breach affecting your Personal Data, providing at minimum: the nature of the breach, categories and approximate number of Data Subjects and records concerned, the likely consequences, and the measures taken or proposed. We will provide further information as it becomes available and cooperate with you on regulator and Data Subject notifications.
On termination or expiry of the Agreement, at your written instruction within 30 days, we will either:
Backups containing Personal Data are overwritten on their normal rotation cycle and fully purged within 35 days of termination. Audit logs retained under regulatory obligation (typically 7 years for safety incidents) are minimised to remove direct identifiers where possible.
The Parties' respective liability under this DPA is subject to the limitations and exclusions of liability set out in the Agreement. Where the Agreement does not contain such terms (e.g. click-through subscriptions), each Party's aggregate liability under this DPA is capped at 12 months' subscription fees paid under the Agreement.
In case of conflict between this DPA and the Agreement, this DPA prevails for matters relating to the Processing of Personal Data.
This DPA is governed by the laws of England and Wales. The courts of England and Wales have exclusive jurisdiction over any dispute arising from or in connection with this DPA.
You accept this DPA either by signing a countersigned PDF (available on request) or by clicking “I agree to the DPA” when prompted during onboarding. Either method binds your organisation.
Signed on behalf of the Processor:
Vygard Ltd · Director · 28 May 2026
| Category | Examples |
|---|---|
| Worker identification | Name, work phone, role, employee ID, site assignment |
| Authentication credentials | Hashed password (scrypt), hashed refresh tokens (SHA-256), device IDs |
| Location data | GPS coordinates, accuracy radius, timestamp; only while clocked on |
| Health-related data (special category) | Heart rate, HRV, motion / fall events, SpO2 (only if the wearable is paired and the worker has consented) |
| Incident records | Triggered alerts, escalation timeline, ack/resolve timestamps, optional voice notes |
| Photographic evidence | PPE check-in selfies, hazard report photos (only if the workflow requires them) |
| Administrator records | Admin user email, name, role, last-seen-at timestamp |
| Audit metadata | Action type, actor, timestamp, IP address, user-agent string |
For the term of the Agreement, plus the wind-down period in clause 11. Indicative retention by data type is published in our Security Overview page and tightened on Enterprise tiers.
Current as of 28 May 2026. Changes notified 30 days in advance per clause 6.
| Sub-processor | Role | Location | Transfer mechanism | DPA |
|---|---|---|---|---|
| Vercel Inc. | Admin web app + marketing site hosting (Next.js) | London (lhr1) primary; US fallback only for static asset CDN | UK IDTA + EU SCCs (Module 2: Controller-to-Processor) | View |
| Fly.io Inc. | API hosting (Fastify) + Postgres database (lwp-api, lwp-db) | London (lhr) only — pinned by deployment config | UK IDTA + EU SCCs (Module 2) | View |
| Upstash Inc. | Redis queue for escalation timing (BullMQ-backed) | Dublin (eu-west-1) | EU SCCs + UK IDTA addendum (Module 2) | View |
| Stripe Payments UK Ltd. | Subscription billing + payment card processing | UK / EU / US — Stripe is the controller for cardholder data | EU SCCs + UK IDTA addendum (Module 1) | View |
| Twilio Ireland Ltd. | SMS OTPs + invite links, WhatsApp Business messaging, voice fallback for SOS escalation | EU (Dublin) + UK; US for delivery telemetry only | EU SCCs + UK IDTA addendum (Module 2) | View |
| Resend Inc. | Transactional email (master admin invites, billing notices, signup confirmations) | US — encrypted in transit + at rest | EU SCCs + UK IDTA addendum (Module 2) | View |
| Anthropic PBC | AI Virtual Watcher anomaly detection + nearest-responder ranking (claude-opus-4-7 via API) | US — standard API endpoint; tenant data is not used for model training (default org setting) | EU SCCs + UK IDTA addendum (Module 2). Per-tenant token cap enforced server-side. | View |
Network operators (mobile carriers carrying SMS / voice) are not treated as Sub-processors as they Process only opaque transit data on their own initiative; this aligns with ICO guidance.
The measures below are reviewed annually and updated as the threat-model evolves. Material additions are noted in the change log at the bottom of this page.
Where Personal Data is transferred outside the United Kingdom (or the EEA for EU customers), the following transfer tools apply, in this order of preference:
| Version | Date | Notes |
|---|---|---|
| 1.0 | 28 May 2026 | First public version. Aligns with UK GDPR Article 28, UK IDTA, and EU SCCs (Decision 2021/914). |
legal@vygard.com — countersigned PDF turnaround within 1 working day. Or book a 30-min call with our DPO if you need bespoke wording for Enterprise.