Data Processing Agreement
Version 1.0 · Effective from the date this version was published on parksphere.co.uk
This Data Processing Agreement (DPA) forms part of the ParkSphere Terms of Service (the Terms) between:
- Smart Path IT Limited, company number 16935628, registered in England and Wales, trading as ParkSphere, registered office address: available on request, ICO registration number: available on request (we, us, the Processor); and
- the business or organisation that has accepted the Terms (you, the Controller).
It sets out the terms required by Article 28 of the UK GDPR for the personal data we process for you when we provide the Service.
1. Definitions
1.1 In this DPA, controller, processor, data subject, personal data, personal data breach, processing, special categories of personal data and supervisory authority have the meanings given in the UK GDPR.
1.2 Data Protection Law means the UK GDPR, the Data Protection Act 2018, and the Privacy and Electronic Communications Regulations 2003, each as amended or replaced from time to time. UK GDPR has the meaning in section 3(10) of the Data Protection Act 2018.
1.3 Customer Personal Data means the personal data in Customer Data that we process on your behalf as your processor. Customer Data and other capitalised terms not defined here have the meanings given in the Terms.
1.4 Sub-processor means a third party we engage to process Customer Personal Data on your behalf.
1.5 Restricted Transfer means a transfer of Customer Personal Data to a country or organisation outside the UK that Data Protection Law treats as a restricted transfer.
1.6 IDTA means the International Data Transfer Agreement, and UK Addendum means the International Data Transfer Addendum to the EU Commission Standard Contractual Clauses, in each case issued by the Information Commissioner under section 119A of the Data Protection Act 2018. UK Extension means the UK Extension to the EU-US Data Privacy Framework (the UK-US data bridge).
2. Roles and scope
2.1 You are the controller of Customer Personal Data, and we are your processor. Customer Personal Data is the personal data of your guests, owners, staff and other people that you or your Authorised Users put into the Service, or that the Service collects on your behalf. Annex 1 describes it.
2.2 We process Customer Personal Data only to provide the Service to you under the Terms, and as set out in Annex 1.
2.3 Our own controller activities. We are an independent controller of personal data we collect for our own purposes, such as your account contact and billing details, sign-up and security records for your account, and enquiries from people who contact us or use our website. This DPA does not apply to them. Our privacy policy at https://parksphere.co.uk/privacy applies.
2.4 Services you connect in your own name. If you connect a service in your own name, such as your own Stripe, GoCardless or Xero account, that provider acts under its contract with you. It is not our Sub-processor, and we pass personal data to it on your instruction. Annex 3, Part D lists them for information.
3. Our obligations as processor
3.1 Instructions. We will process Customer Personal Data only on your documented instructions, which are the Terms, this DPA, your use and configuration of the Service, and any further written instruction you give that is consistent with these. We will tell you if we think an instruction breaches Data Protection Law (but we are not required to check legal compliance of your instructions). If the law requires us to process it otherwise, we will tell you before processing, unless the law prohibits that.
3.2 Confidentiality. We will make sure everyone we authorise to process Customer Personal Data is under a duty of confidentiality, and that access is limited to those who need it to provide the Service.
3.3 Security. We will implement the technical and organisational measures in Annex 2, taking into account the matters listed in Article 32 of the UK GDPR. We may update them if the level of security is not reduced.
3.4 Sub-processors. Clause 6 applies.
3.5 Assistance with data subject requests. Taking into account the nature of the processing, we will help you respond to requests from data subjects who exercise their rights (access, rectification, erasure, restriction, portability, objection, and not being subject to automated decisions), by technical and organisational measures. The Service lets your administrators view, correct and export guest, owner and staff records and run a full export of your data (Terms, clause 13.3). If a data subject contacts us directly about Customer Personal Data, we will not respond other than to tell them to contact you, unless you tell us to or the law requires us to, and we will forward the request to you promptly and, in any event, within 5 business days. Until there is a single-click erasure function for an individual guest, we handle erasure and anonymisation requests for individual records manually when you ask us. We may charge reasonable costs for help that goes beyond what is reasonable in the circumstances, and we will tell you the cost before we incur it.
3.6 Personal data breaches. We will notify you without undue delay, and in any event within 72 hours of becoming aware of a personal data breach affecting Customer Personal Data. The notice will include, as far as we know: the nature of the breach, categories and approximate numbers of data subjects and records, likely consequences, and measures taken or proposed. We will give more information as we get it, take reasonable steps to contain and fix it, and help you meet your duties to notify the ICO and data subjects. Our notice is not an admission of fault. Our incident contact is hello@parksphere.co.uk. Please send yours to the account administrator's email address registered in the Service, unless you give us another contact in writing.
3.7 Assistance with security, impact assessments and consultation. We will give you reasonable help, taking into account the nature of processing and the information we have, with your obligations under Articles 32 to 36 of the UK GDPR (security, breach notification, data protection impact assessments, and prior consultation with the ICO).
3.8 Records. We will keep a record of the processing we carry out for you as Article 30(2) of the UK GDPR requires.
3.9 Information and audits. We will give you the information necessary to show we comply with this DPA and Article 28, and allow and contribute to audits, including inspections, by you or an auditor you appoint. Clause 8 sets out how.
4. Your obligations as controller
4.1 You will comply with Data Protection Law. You are responsible for: (a) having a lawful basis for processing Customer Personal Data, and for any special category data you choose to put in the Service (including a condition under Article 9 of the UK GDPR); (b) giving data subjects the information required by Articles 13 and 14 (privacy notices), including about us and our Sub-processors where required; (c) the accuracy and quality of Customer Personal Data; (d) any direct marketing you send, and the consent, soft opt-in or other basis and opt-outs it needs under PECR; (e) responding to data subjects; (f) deciding retention periods for data in the Service and deleting or anonymising data you no longer need (using the tools in the Service); and (g) your instructions being lawful.
4.2 You must not put in the Service special category data or criminal offence data unless you need to and have a lawful basis and condition. Free-text fields (guest notes, special requests, dietary and accessibility information) can contain health information, and you decide whether to use them.
4.3 You will make sure your Authorised Users are properly authorised and keep their credentials secure.
5. Data subjects' rights and complaints
You remain responsible for responding to data subjects' requests. We will help as set out in clause 3.5.
6. Sub-processors
6.1 General authorisation. You give us general written authorisation to use the Sub-processors listed in Annex 3, Part A and Part B when the DPA takes effect.
6.2 New or replaced Sub-processors. We will tell you at least 30 days before adding or replacing a Sub-processor. We will notify you by email to your account administrator (and may also publish the list). You may object on reasonable data-protection grounds within 14 days of the notice. If you object, we will work with you to find a solution (for example, not using that Sub-processor for your data). If we cannot, you may end the affected part of the Service, or the Agreement, on written notice and we will refund prepaid fees for the period after termination.
6.3 Flow-down. We will have a written contract with each Sub-processor that puts data protection obligations on it that are no less protective than this DPA, as far as they apply to its service. Where a Sub-processor's standard terms are used, we will check that they give materially equivalent protection.
6.4 Responsibility. We remain responsible to you for the performance of our Sub-processors.
6.5 Emergency. We may replace a Sub-processor without notice if urgently needed to keep the Service secure or running, and will tell you as soon as possible after; your objection right in 6.2 then applies.
7. International transfers
7.1 We store and process Customer Personal Data on servers operated by or for Smart Path IT. Production: confirmed in your order form or on request. Disaster recovery and backup: confirmed in your order form or on request. Annex 3, Part C gives more detail. Sub-processors are in Annex 3.
7.2 We will not make a Restricted Transfer unless a transfer mechanism that Data Protection Law allows is in place, such as: (a) the destination is covered by UK adequacy regulations (including the UK Extension for certified US recipients); or (b) the IDTA or UK Addendum, together with a transfer risk assessment where needed; or (c) another safeguard under Article 46 of the UK GDPR.
7.3 Annex 3 states, for each Sub-processor, where it processes data and the mechanism we rely on.
7.4 You agree that we may carry out the transfers listed in Annex 3.
8. Audit
8.1 We will, on request and not more than once a year (unless a personal data breach or a regulator requires more), give you information reasonably needed to show our compliance, such as our security documentation and relevant independent reports or certifications (we do not hold ISO 27001 or Cyber Essentials certification at the date of this DPA).
8.2 If that is not enough to show compliance, or a regulator requires it, you (or an independent auditor bound by confidentiality, not a competitor of ours) may audit us. You must give at least 30 days' written notice, agree the scope and timing with us, carry out the audit during business hours without unreasonably disrupting our business or other customers, and keep what you learn confidential. You pay the cost of the audit (and our reasonable costs of helping beyond one day), unless it finds a material breach by us.
8.3 Audits must not give access to other customers' data or our systems that would put other customers' data at risk.
9. Return and deletion
9.1 During the Term you can export Customer Personal Data using the export tools described in the Terms (clause 13.3).
9.2 When the Agreement ends, at your choice made by written notice before the end of the read and export period in the Terms (clause 17.5), we will return Customer Personal Data by export, and delete it. We do not run an automatic deletion process: our team deletes or anonymises Customer Personal Data within 30 days of your written request or, if you make no choice, within 90 days after the end of the read and export period. Customer Personal Data is removed from backups as they expire in the normal backup cycle, within 90 days after it is deleted from our live systems. On request, we will confirm in writing that we have done so.
9.3 We may keep Customer Personal Data to the extent the law requires us to and for as long as it requires, and in that case we will only process it for that purpose and protect it under this DPA. If you use ParkSphere Accounts, accounting ledger, VAT records and filing receipts are kept for at least six years after the end of the last VAT period. If you ask us to delete this data after you have exported it, we will do so unless the law requires us to keep it.
9.4 During the read and export period, and until deletion, this DPA continues to apply.
10. Liability
Each party's liability under or in connection with this DPA is subject to the limits and exclusions in the Terms (clause 20, including the data protection cap in clause 20.3). Nothing in this DPA limits a data subject's rights against either party, or liability that cannot be limited by law, including either party's liability to data subjects under Article 82 of the UK GDPR.
11. Term and order of precedence
11.1 This DPA starts when the Terms take effect and continues as long as we process Customer Personal Data, even after the Terms end.
11.2 If there is a conflict between this DPA and the Terms about personal data, this DPA prevails. If there is a conflict between this DPA and any IDTA or UK Addendum, that transfer document prevails for the transfer it covers.
12. Changes
We may update this DPA if needed to keep it compliant with Data Protection Law (for example, if the law, regulatory guidance or standard clauses change), on 30 days written notice. Other changes need both parties' agreement, or the process for changes to the Terms (clause 22) where they are not materially adverse to you.
13. Governing law and jurisdiction
This DPA is governed by the law of England and Wales, and the courts of England and Wales have exclusive jurisdiction, subject to any transfer document that says otherwise.
14. Contacts
- Our data protection contact: hello@parksphere.co.uk.
- Your data protection contact: the account administrator's email address registered in the Service, unless you give us another contact in writing.
Annex 1: Details of the processing
(This describes the processing under Article 28(3) of the UK GDPR.)
1. Subject matter
Providing the ParkSphere platform to you, a holiday park, camping site, hotel or similar operator, so that you can run your Sites: bookings and pitch or room management, guest, owner and staff applications, food and drink ordering, events, maintenance and housekeeping, owner accounts and statements, loyalty and reviews, accounting add-on, AI add-ons, notifications, reporting, and the related support.
2. Duration
For the Term of the Agreement, and afterwards for the read and export period (Terms clause 17.5) and until deletion under clause 9 of the DPA. After that, only as the law requires.
3. Nature of the processing
Collecting (where you or your users or your guests enter data, or integrations bring it in), recording, organising, structuring, storing, hosting, adapting, retrieving, consulting, using, transmitting by email, text message and push notification, displaying, backing up, restoring, exporting, combining with other data in your account, generating reports and AI-assisted answers at your request, restricting, erasing and destroying.
4. Purposes
- To provide, secure, support, maintain and improve the Service for you as set out in the Terms.
- To take bookings and payments (via your own payment provider), manage stays and ground-rent accounts, run orders, run maintenance and housekeeping, and send you and your guests, owners and staff service messages (for example booking confirmations and pre-arrival messages) and, where you configure and have the basis for it, marketing messages.
- To produce reports, exports and accounts.
- To provide AI features if you subscribe to them: answering your questions about your parks, proposing actions that you confirm, and producing daily plans and insights.
- To keep the Service secure and prevent fraud and abuse (for example rate limiting, sign-in security, audit logs).
- To back up and recover data.
- To follow your documented instructions.
5. Types of personal data
The Service lets you store the following. You decide what you enter; this list describes the fields and categories the Service holds.
Guests and prospective guests (including people who book, dine, or use the guest app or web pages):
- Identity and contact: first and last name, email address, telephone number, postal address and country, date of birth, emergency contact name and telephone number, vehicle registration, an account login.
- Booking and stay data: dates, pitch or room, party size including the number of children, special requests (free text), prices, payments, invoices and receipts, check-in and check-out, preferences (pitch type, zone), loyalty points and rewards, wallet balances and top-ups.
- Orders: food and drink orders and the items.
- Preferences and opt-ins: dietary requirements and accessibility needs (these can reveal health information), newsletter, text and marketing opt-ins.
- Notes, fault reports, reviews, photos and messages that guests or staff enter.
- Records of notifications sent (to whom, when, which channel).
- Technical data: IP address, device and browser details, push notification tokens, session records.
- Payment data: card payments are made through your Stripe account on Stripe's pages. We hold payment references, amounts and status from Stripe, but not full card numbers or card security codes.
Holiday home owners and their contacts (if you use the owner portal):
- Name, contacts, address, plot or pitch, ground-rent and fee accounts and statements, meter readings and charges, gas orders, Direct Debit mandate references where you use GoCardless, portal login.
Your staff, contractors and other users:
- Name, work email, role, the parks they can access, password (stored only as a hash), last sign-in, activity logs, shift and clock-in records, job and housekeeping records, photos attached to jobs, notification device tokens.
Other data subjects:
- People mentioned in free text, photos or documents that you or others upload.
Special categories and criminal offence data: not intended. We do not require it. Dietary requirements, accessibility needs and free-text notes may reveal health information if you choose to record it (see DPA clause 4.2).
6. Categories of data subjects
- Guests, visitors, enquirers and diners.
- Holiday home owners and their nominated contacts.
- Your employees, contractors and agents who use the Service.
- Children (the Service records the number of children in a booking; it does not require their names).
- Other individuals about whom you put data in the Service.
7. Frequency and storage
Continuous during the Term. Customer Personal Data is stored in our production database and file storage. The backup schedule is nightly (see Annex 2).
8. Retention
Until you delete it or the Agreement ends, then as set out in clause 9 of this DPA. Data export files you request are available to you for 7 days and then deleted. Backups and logs are kept only as long as needed to run and secure the Service and expire in the normal cycle (backups within 90 days after deletion from live systems, clause 9.2). We do not offer configurable retention per data type or automatic purging of guest data.
Annex 2: Technical and organisational security measures
This describes the measures in place at the date of this DPA.
1. Governance
- Certifications: none at the date of this DPA.
- Security incidents and questions: see the contact in clause 3.6.
2. Access control and authentication
- Role-based access: every user has a role (such as account administrator, park manager, receptionist, staff, maintenance, external cleaner, owner, guest), and staff can be limited to specific parks.
- Passwords are stored only as bcrypt hashes. Access tokens are short-lived (15 minutes), with refresh tokens limited to 30 days.
- Sign-in attempts are rate limited per account and per IP address (5 attempts per 15 minutes per account, with a separate per-IP limit) to resist guessing.
- Self-serve sign-up is protected by rate limits and a CAPTCHA (Cloudflare Turnstile).
- Our own administrators sign in to the internal platform console only through Microsoft Entra ID with an allow-list of named people. Their access to a customer's account is through a read-only "view as" session which is short-lived, audited and cannot make changes. Every platform administrator write is recorded in an audit log with the person and reason.
- Production server access is limited to named administrators over a private network (Tailscale). Production services are not exposed on public web ports: traffic reaches them through a Cloudflare Tunnel.
3. Customer data separation
- Every record in the Service belongs to one customer account (tenant) and every request is checked against the signed-in user's tenant, in the gateway and in each service.
- Our automated tests and release checks include cross-tenant access probes.
- The AI service only sees the signed-in user's own parks, treats guest-entered text as untrusted data and cannot make a change without a person confirming, and it does not return bulk lists of guest contact details.
4. Encryption
- In transit: public traffic is encrypted with TLS at Cloudflare, and the Service sends HSTS and other security headers.
- At rest: connection credentials for integrations that you connect (such as GoCardless tokens) are encrypted in the database (AES with an integrity check).
- Operational secrets (keys, passwords) are held in a secrets manager (Infisical).
5. Hosting and physical security
- The Service runs on servers operated by or for Smart Path IT: a primary production server and a separate disaster-recovery and backup server, with a monitoring server. Locations: production confirmed in your order form or on request; disaster recovery and backup confirmed in your order form or on request; monitoring confirmed in your order form or on request.
- Production uses a private network between our servers. The database is not exposed to the public internet.
6. Resilience, backup and recovery
- Nightly backup of every production database and file store to a separate backup server (Kopia).
- We do not publish backup retention, recovery time or recovery point targets.
- The production database streams to a standby on the separate disaster-recovery server.
7. Monitoring, logging and audit
- Central monitoring and alerting of servers, containers and databases, with notifications to our on-call team. Real-user performance and error monitoring on our applications, and crash reporting on the mobile app, through self-hosted tools.
- Platform administrator actions are audit-logged. Logs are redacted for secrets and sensitive fields as far as we are able to.
8. Application and network security
- Public traffic passes through Cloudflare, which provides DDoS protection and web application firewall filtering at the level of our current Cloudflare plan.
- The gateway applies security response headers and strips server identification headers, and rate-limits sensitive routes.
- Input validation, parameterised database queries and automated tests are part of our development process. Dependency vulnerability scanning (pip-audit) and container image scanning run in our build process, and dependency updates are tested on a separate staging environment before release to production.
- Changes are developed and tested on a staging environment and released to production only after automated tests pass.
9. Data minimisation, retention and deletion
- Exports exclude credentials and password hashes, and export links expire after 7 days (and the files are deleted automatically).
- Idle demo accounts are flagged for purging by our platform team. Demo requests that were never opened are deleted after 365 days.
- Customer data deletion at the end of the Agreement is described in clause 9 of the DPA and is carried out by our team on request.
10. Third parties
- Sub-processors are listed in Annex 3.
11. Review
We review these measures at least once a year and after any significant incident.
Annex 3: Sub-processors
Authorised sub-processors at the date of this DPA. We will update this list under clause 6 of the DPA.
Part A: Sub-processors used for all customers
| Sub-processor | What it does for us | Customer Personal Data involved | Location | Transfer mechanism |
|---|---|---|---|---|
| Cloudflare, Inc. (and affiliates) | Content delivery, secure tunnel and proxy for our applications and API (traffic to and from the Service passes through it); Turnstile CAPTCHA on sign-up and request forms | Website, app and API traffic including IP addresses, and request content passing through the proxy | Global network; the provider operates internationally, including outside the UK | a transfer mechanism permitted by Data Protection Law, as described in clause 7.2 (details on request) |
| Microsoft Corporation (Microsoft 365 / Exchange Online) | Receives and stores inbound email: mail sent to support@ and hello@parksphere.co.uk, and replies from your guests, owners and staff to emails sent through the Service | Email addresses, names and the content of correspondence | Location of our Microsoft 365 tenant: available on request | a transfer mechanism permitted by Data Protection Law, as described in clause 7.2 (details on request) |
Part B: Sub-processors used only if you use the feature
| Sub-processor | Feature | Customer Personal Data involved | Location | Transfer mechanism |
|---|---|---|---|---|
| Twilio Inc. (and its affiliates) | Text messages (SMS) to guests and staff, if you switch on text messaging | Recipient telephone number, message content, sender ID | Provider operates internationally, including outside the UK | a transfer mechanism permitted by Data Protection Law, as described in clause 7.2 (details on request) |
| Expo (650 Industries, Inc.) and the push services of Apple and Google that it uses | Push notifications to the ParkSphere mobile app | Device push token, notification title and text | Provider operates internationally, including outside the UK | a transfer mechanism permitted by Data Protection Law, as described in clause 7.2 (details on request) |
| Anthropic, PBC | Language models behind AI Assistant and AI Operations, if you subscribe to an AI add-on | Your questions and the park, booking and operational data the AI looks up to answer them. The AI is designed not to return bulk guest contact details, and untrusted guest text is handled as data | United States | a transfer mechanism permitted by Data Protection Law, as described in clause 7.2 (details on request) |
| OpenRouter, Inc. | Fallback route to the same type of language models if the first provider is unavailable | As for Anthropic | Provider operates internationally, including outside the UK | a transfer mechanism permitted by Data Protection Law, as described in clause 7.2 (details on request) |
Part C: Our own infrastructure (not third parties)
These are run by or for Smart Path IT and are not Sub-processors, but they are listed so you can see where data goes:
| Item | Use | Location |
|---|---|---|
| Production server (ps-prod-02) | Runs the Service and holds the live database and files | confirmed in your order form or on request |
| Disaster-recovery and backup server (sphost1) | Standby database and nightly backup repository | confirmed in your order form or on request |
| Monitoring server (vps1) | Metrics, logs and alerts, uptime checks | confirmed in your order form or on request |
| Outbound email server (mail.smartpathit.co.uk) | Sends booking and service emails to your guests, owners and staff | confirmed in your order form or on request |
| Error tracking and real-user monitoring (self-hosted) | Crash and error reports and page performance | Our own infrastructure (location available on request) |
If any of this infrastructure is provided by a hosting company, we will list that company as a Sub-processor in Part A, with its location.
Part D: Services you connect in your own name (not our Sub-processors)
You contract directly with these providers when you connect them. We transmit data to them only on your instruction.
| Provider | Purpose |
|---|---|
| Stripe Payments Europe Ltd / Stripe, Inc. (Stripe Connect) | Card payments from your guests to you, taken on your own Stripe account. Stripe is a separate controller or processor under your contract with Stripe |
| GoCardless Ltd | Direct Debit collection of ground rent and fees from owners, on your own GoCardless account |
| Xero Ltd | Accounting sync with your own Xero organisation |
| Calendar and channel feeds (iCal, Pitchup and similar) | Exchanging availability and bookings with channels you choose |
Part E: Providers that do not receive Customer Personal Data
For transparency: Smart Path IT's own billing (Stripe, for your subscription), our CRM and our website analytics are controller activities (DPA clause 2.3). The Service gets weather forecasts from Open-Meteo or the Met Office using a park's map coordinates only, not personal data. Our staff sign in to our internal console using Microsoft Entra ID.