UK GDPR Article 28
Data Processing Agreement
Version 2026-11-09 · Last updated: 9 November 2026
Parties
(1) Simon Owenson, trading as Beacon, of Longniddry, East Lothian, Scotland, operating the Beacon service at beaconcore.io ("Beacon" or the "Processor"); privacy contact: privacy@beaconcore.io. ICO registration number: to be added on registration.
(2) the Customer (the "Customer" or the "Controller").
Background. This Agreement forms part of, and is incorporated into, the Beacon Terms of Service (the "Main Agreement"). If there is a conflict between this Agreement and the Main Agreement about the protection of personal data, this Agreement prevails. See also the Privacy Policy.
1. Definitions
"Data Protection Legislation" means the UK GDPR, the Data Protection Act 2018, the Privacy and Electronic Communications Regulations 2003 and any other applicable UK data protection law, each as amended (including by the Data (Use and Access) Act 2025).
"Controller", "Processor", "Data Subject", "Personal Data", "Personal Data Breach", "Processing" and "Supervisory Authority" have the meanings given in the UK GDPR. "ICO" means the UK Information Commission (formerly the Information Commissioner's Office).
"Customer Personal Data" means the Personal Data described in Schedule 1 that Beacon processes on the Customer's behalf in providing the Service.
"Service" means the Beacon web application and progressive web app for NDT and asset inspection reporting, including PDF report generation and the QR code verification page.
"Sub-processor" means a third party engaged by Beacon to process Customer Personal Data.
"Authorised Users" means the Customer's employees and contractors given access to the Service under the Customer's account.
2. Roles and scope
2.1 For Customer Personal Data, the Customer is the Controller and Beacon is the Processor. Beacon is a separate Controller only for its own account administration, billing, service-security and (consent-based) product analytics data, which it handles under its own Privacy Policy.
2.2 The subject matter, duration, nature and purpose of processing, types of Personal Data and categories of Data Subjects are set out in Schedule 1.
2.3 The Customer is responsible for having a lawful basis for the processing, for giving any privacy information to Data Subjects (including its own clients, site operators and inspectors), and for the lawfulness and accuracy of the data its Authorised Users upload.
3. Beacon's obligations
3.1 Beacon will process Customer Personal Data only on the Customer's documented instructions, including about international transfers, unless UK law requires otherwise; in that case Beacon will tell the Customer before processing unless the law prohibits it on important public interest grounds. The Main Agreement, this Agreement and the Customer's use and configuration of the Service are the Customer's documented instructions.
3.2 Beacon will tell the Customer promptly if, in its opinion, an instruction infringes Data Protection Legislation.
3.3 Beacon will ensure that anyone it authorises to process Customer Personal Data is bound by confidentiality (contractual or statutory).
3.4 Beacon will implement the technical and organisational measures in Schedule 2 to meet Article 32 UK GDPR, and may update them provided the overall level of security is not reduced.
3.5 Beacon will not sell Customer Personal Data or use it for its own purposes, except to produce anonymised, aggregated service statistics that do not identify any person or Customer.
4. Public verification page (QR code)
4.1 Each PDF report generated by the Service carries a QR code linking to a public verification page that shows a summary of the report together with its photographs and drawings. Anyone who has the link can view that page, without logging in, until the report is deleted (including after it is purged from the recycle bin).
4.2 The Customer acknowledges that issuing or sharing a report with its QR code is a decision of the Customer and an instruction to Beacon to make that summary, photographs and drawings available to anyone holding the link. The Customer is responsible for deciding what is included in reports it shares and for removing or deleting a report if public verification is no longer appropriate.
4.3 Beacon will use long, non-guessable link identifiers, will not operate a public directory of verification pages, and will remove the verification page when the report is deleted.
5. Sub-processors
5.1 The Customer gives general written authorisation for Beacon to engage the Sub-processors listed in Schedule 3.
5.2 Beacon will give the Customer at least 30 days' notice of any intended addition or replacement of a Sub-processor (by email to the Customer's account owner and/or by updating a published list). The Customer may object on reasonable data protection grounds within that period; if the parties cannot resolve the objection, the Customer may terminate the affected Service and receive a pro-rata refund of prepaid fees as its sole remedy.
5.3 Beacon will impose on each Sub-processor data protection obligations that are no less protective than this Agreement in substance and will remain liable to the Customer for each Sub-processor's performance, as required by Article 28(4) UK GDPR.
6. International transfers
6.1 Beacon's primary data store (Cloud Firestore and Cloud Storage for Firebase) is located in the Google Cloud europe-west2 (London) region.
6.2 Some processing takes place outside the UK: (a) Firebase Authentication is run only from US data centres (Google, "Privacy and Security in Firebase"); (b) Google Analytics for Firebase, used only with consent, runs on Google's global infrastructure; and (c) Vercel Inc. (USA) hosts and serves the web application through a global CDN.
6.3 Beacon will make any restricted transfer only where it is covered by a lawful mechanism under Chapter V UK GDPR, namely: (a) the UK adequacy regulations for the US (the "UK Extension to the EU-US Data Privacy Framework", also called the UK-US data bridge) where the US recipient has an active certification covering the relevant data; Vercel Inc. and Google LLC each state they are certified under the UK Extension; and/or (b) the ICO's International Data Transfer Addendum to the EU Standard Contractual Clauses (the "UK Addendum") or the International Data Transfer Agreement (IDTA), which Vercel's and Google's data processing terms incorporate for UK data.
6.4 Beacon will tell the Customer if a transfer mechanism it relies on ceases to be valid and will take reasonable steps to put an alternative in place.
7. Assistance with Data Subject rights
7.1 Taking into account the nature of the processing, Beacon will assist the Customer by appropriate technical and organisational measures in responding to requests from Data Subjects to exercise their rights (access, rectification, erasure, restriction, portability and objection).
7.2 The Service provides self-service tools for this: Authorised Users can edit and delete reports; the Customer can export its company data; deleted items go to a recycle bin and are permanently purged automatically after 90 days (or earlier if emptied); and account deletion is available in the app.
7.3 If Beacon receives a request directly from a Data Subject about Customer Personal Data, it will not respond on the merits (other than to redirect the person) and will forward the request to the Customer within 5 working days.
7.4 Beacon will also provide reasonable assistance with the Customer's obligations under Articles 32 to 36 UK GDPR (security, breach notification, data protection impact assessments and prior consultation), taking into account the information available to Beacon. Assistance beyond the self-service tools may be charged at reasonable cost.
8. Personal Data Breaches
8.1 Beacon will notify the Customer without undue delay after becoming aware of a Personal Data Breach affecting Customer Personal Data, and will aim to do so within 48 hours.
8.2 The notice will, so far as then known, describe: the nature of the breach, the categories and approximate number of Data Subjects and records concerned; the likely consequences; the measures taken or proposed to address it and mitigate its effects; and Beacon's contact point (privacy@beaconcore.io). Information may be provided in phases as it becomes available.
8.3 Beacon will take reasonable steps to contain, investigate and remedy the breach, and will cooperate with the Customer so the Customer can meet its own duty to notify the ICO within 72 hours and, where required, the affected individuals. Beacon will not notify the ICO or Data Subjects about a breach of Customer Personal Data on the Customer's behalf unless the Customer instructs it to or the law requires it.
8.4 Notification by Beacon is not an admission of fault or liability.
9. Deletion or return at the end
9.1 On termination or expiry of the Main Agreement, the Customer may export its data using the company data export during the 30-day period after termination.
9.2 After that period, at the Customer's choice, Beacon will delete or return all Customer Personal Data, and delete existing copies, unless UK law requires storage. Data in the live database will be deleted within 30 days after the export period; residual copies in Sub-processor backups will be overwritten in the ordinary backup cycle and kept protected until then. Public verification pages stop working once the related reports are deleted.
9.3 Beacon will confirm deletion in writing on request.
10. Records, information and audits
10.1 Beacon will keep a record of processing activities as required by Article 30(2) UK GDPR.
10.2 Beacon will make available to the Customer all information reasonably necessary to demonstrate compliance with Article 28, and will allow for and contribute to audits, including inspections, conducted by the Customer or an independent auditor it mandates (bound by confidentiality).
10.3 To keep this proportionate for a small provider, the Customer will first rely on Beacon's written answers, security documentation and Sub-processors' certifications (such as Google's and Vercel's ISO 27001 / SOC 2 reports). An on-site or remote audit may take place no more than once in any 12-month period (unless following a Personal Data Breach or required by the ICO), on at least 30 days' notice, during working hours, at the Customer's cost. Audits of Sub-processors are limited to the reports and rights those Sub-processors make available.
11. Customer obligations
11.1 The Customer will: ensure its instructions comply with Data Protection Legislation; not upload special category or criminal offence data unless necessary and lawful (photographs should avoid identifiable people where possible); manage Authorised Users' access and passwords and remove leavers promptly; and inform its own clients and inspectors that reports may be verified via a public QR link.
12. Liability
12.1 Each party is liable for its own breaches of this Agreement and of Data Protection Legislation. Article 82 UK GDPR applies to claims by Data Subjects.
12.2 Subject to clause 12.3, each party's total aggregate liability under or in connection with this Agreement is limited as set out in the Terms of Service.
12.3 Nothing in this Agreement limits liability for fraud, for death or personal injury caused by negligence, or any other liability that cannot be limited by law.
12.4 Neither party is liable for any loss caused by the other party's breach, or by the Customer's instructions (including the decision to share reports via QR code).
13. Term
This Agreement starts on the date the Customer first uses the Service or accepts it electronically (whichever is earlier) and continues while Beacon processes Customer Personal Data. Clauses 8, 9, 10 and 12 survive termination.
14. Governing law and jurisdiction
This Agreement is governed by the law of Scotland, and the courts of Scotland have exclusive jurisdiction.
Acceptance
For Beacon (Processor): Simon Owenson, sole trader / founder.
For the Customer (Controller): this Agreement is accepted electronically when a company admin ticks the acceptance box at sign-up (or later in the app) on behalf of the Customer. Larger customers who need a signed copy can request one from privacy@beaconcore.io.
Schedule 1 — Details of processing
- Subject matter
- Provision of the Beacon NDT and asset inspection reporting service to the Customer.
- Duration
- For the term of the Main Agreement plus the post-termination export and deletion periods in clause 9; recycle-bin items are purged automatically after 90 days.
- Nature of processing
- Collection via the app, storage, organisation, retrieval, display, PDF generation, QR-code verification page publication, export, backup, transmission and deletion.
- Purpose
- To let the Customer create, store, sign, issue, share, verify and archive inspection reports, and to provide support and keep the Service secure.
- Types of Personal Data
- Names, job titles, company and contact details of Authorised Users and inspectors; inspector qualifications or certification numbers if captured; handwritten or drawn signatures (stored as images; not processed for biometric identification); photographs (which may incidentally show people, vehicle registrations or other identifying details); drawings and annotations; client and site names (for example operator and installation names) and names of client representatives; findings, comments, dates, locations and report metadata; log-in identifiers, IP addresses and device/usage logs relating to Authorised Users.
- Special category data
- Not intended. The Customer should not upload it. Signatures are stored as images and not used to identify people by biometric processing.
- Data Subjects
- The Customer's Authorised Users and inspectors; the Customer's clients' staff and representatives named in reports (for example operators, site personnel, witnesses); people incidentally captured in photographs; anyone who opens a public verification page (technical logs only).
- Retention
- As set by the Customer: data is kept until the Customer deletes it; deleted items are purged from the recycle bin after 90 days; end-of-contract deletion as in clause 9.
Schedule 2 — Technical and organisational security measures
- Encryption in transit: all traffic to the app, API and verification pages uses HTTPS/TLS (Vercel and Firebase).
- Encryption at rest: Firestore and Cloud Storage data is encrypted at rest by Google by default.
- Access control: Firebase Authentication for user log-in; Firestore and Storage Security Rules restrict each company's data to its own Authorised Users; role-based permissions within a company.
- Administrator access: Beacon's admin accounts on Google Cloud/Firebase, Vercel, Namecheap and email use strong unique passwords and multi-factor authentication; least-privilege access; no shared accounts.
- Public verification pages: long random identifiers; only the summary, photos and drawings shown; removed when the report is deleted.
- Data location: primary data in europe-west2 (London).
- Resilience: managed Google Cloud infrastructure; company data export is available in Settings.
- Deletion: in-app deletion, 90-day automatic recycle-bin purge, account deletion and company data export.
- Monitoring and incident response: provider security alerts and logs are reviewed; breaches handled under Beacon's breach response plan.
- Development: secrets kept out of source code (environment variables); dependencies kept up to date; changes tested before deployment.
- People: Beacon is a sole trader; any future staff or contractors will sign confidentiality terms and receive data protection training.
- Analytics: Google Analytics for Firebase only runs after the user gives consent. Beacon acts as a controller for that consent-based analytics, as described in the Privacy Policy.
Schedule 3 — Authorised Sub-processors
| Sub-processor | Service | Data | Location | Transfer safeguard |
|---|---|---|---|---|
| Google LLC / Google Cloud (Firebase) | Cloud Firestore database and Cloud Storage for Firebase | All report data, photos, drawings, signatures | europe-west2 (London, UK) | Not a restricted transfer for stored data; Google support access may be from outside the UK — covered by Firebase Data Processing and Security Terms (SCCs + UK Addendum) and UK Extension to the DPF |
| Google LLC (Firebase Authentication) | User sign-in | Authorised User names, emails, log-in identifiers, IP addresses | United States (Firebase Authentication runs only from US data centres) | UK Extension to the EU-US DPF (Google certified) and/or SCCs + UK Addendum in Google's terms |
| Google LLC (Google Analytics for Firebase) | Product analytics, only with user consent | Pseudonymous device/app identifiers, usage events | Global Google infrastructure, including the US | As above. Beacon acts as controller for analytics, as described in the Privacy Policy. |
| Vercel Inc. | Web hosting, serverless functions and global CDN | Data passing through the app and verification pages; request logs (IP addresses) | United States, plus global edge network | UK Extension to the EU-US DPF (Vercel shows an active certification) and the UK IDTA/Addendum with SCCs in Vercel's DPA (vercel.com/legal/dpa) |
Related: Terms of Service · Privacy Policy