Legal
Sashbook Data Processing Agreement
Version 1.2 · In force from 14 November 2026
1. Introduction and how this fits together
1.1 This Data Processing Agreement ("DPA") forms part of the Sashbook Terms of Service between Sashbook LLP (a limited liability partnership, registered number OC461971, registered office 82A James Carter Road, Mildenhall, IP28 7DE) ("Processor", "we", "us") and the business subscribing to the Services ("Controller", "you").
1.2 This DPA takes effect automatically when you accept the Terms of Service. No signature is required. Article 28(9) UK GDPR permits a processing contract to be in electronic form, and we keep a record of your acceptance: which User accepted, the date and time, and the version.
1.3 If you need a signed copy for your own records, email privacy@sashbook.com and we will provide one.
1.4 Where this DPA and the Terms of Service conflict on a data protection matter, this DPA prevails.
2. Definitions
"Data Protection Law" means the UK GDPR, the Data Protection Act 2018, the Privacy and Electronic Communications Regulations 2003, and any legislation amending or replacing them, including the Data (Use and Access) Act 2025.
"Customer Personal Data" means personal data within the Customer Data which we process on your behalf under the Terms of Service.
"Data Subject", "personal data", "processing", "controller", "processor", "special category data" and "personal data breach" have the meanings given in the UK GDPR.
"Sub-processor" means any processor engaged by us to process Customer Personal Data.
"Restricted Transfer" means a transfer of Customer Personal Data to a person outside the United Kingdom to whom Chapter V UK GDPR applies.
Terms defined in the Terms of Service have the same meaning here.
3. Roles of the parties
3.1 In respect of Customer Personal Data, you are the controller and we are the processor.
3.2 You are responsible for: the lawfulness of the personal data you place in the Services; having a lawful basis for it; providing privacy information to your Data Subjects; responding to their requests; and complying with your own obligations under Data Protection Law.
3.3 We will process Customer Personal Data only as set out in this DPA.
3.4 Where we act as controller. We are a controller, not a processor, in respect of:
(a) your account and billing data, as described in our Privacy Policy;
(b) security and access logs, and records generated in detecting and preventing abuse of the Services;
(c) aggregated and anonymised data created under clause 10.3 of the Terms of Service;
(d) Usage Data, as defined in the Terms of Service; and
(e) support correspondence with you.
This is a deliberate and limited list. We do not act as controller in respect of your End Customers' personal data for any purpose, and we do not determine the purposes or means of processing it.
3.5 Certain third parties act as independent controllers in their own right and are not our Sub-processors. These are listed in Annex 3, Part B. Your relationship with them is direct and is governed by their own terms.
4. Processing on documented instructions
Article 28(3)(a)
4.1 We will process Customer Personal Data only on your documented instructions, including in relation to transfers outside the United Kingdom, unless required to do otherwise by law. Where the law requires it, we will inform you before processing unless the law prohibits us from doing so.
4.2 Your documented instructions are:
(a) this DPA and the Terms of Service;
(b) your use of, and configuration of, the features of the Services;
(c) any support access permission you give under clause 12 of the Terms of Service, for one request or standing; and
(d) any other written instruction you give us which we accept.
4.3 Annex 1 sets out the subject matter, duration, nature and purpose of the processing, the types of personal data, and the categories of Data Subject, as required by Article 28(3).
4.4 If you instruct us to do something outside the scope of the Services, we may charge for it or decline it.
4.5 Unlawful instructions. (Article 28(3), final paragraph) We will immediately inform you if, in our opinion, an instruction you give infringes Data Protection Law. We may suspend performance of that instruction until it is resolved.
5. Confidentiality of personnel
Article 28(3)(b)
5.1 We ensure that every person authorised to process Customer Personal Data is bound by a written duty of confidentiality which survives the end of their engagement.
5.2 This applies to our employees, contractors and any individual acting under our authority.
5.3 We limit access to Customer Personal Data to those who need it to perform their role, and only for as long as they need it.
6. Security
Article 28(3)(c) and Article 32
6.1 We implement and maintain appropriate technical and organisational measures to ensure a level of security appropriate to the risk, taking into account the state of the art, the costs of implementation, and the nature, scope, context and purposes of processing.
6.2 The measures in place are described in Annex 2. That annex describes what we actually do. We do not claim certifications we do not hold.
6.3 We may update the measures in Annex 2 from time to time, provided that the overall level of security is not reduced.
6.4 As required by Article 32(1)(d), we regularly test, assess and evaluate the effectiveness of these measures. In particular, every change to the database's access rules is reviewed before it is applied.
7. Sub-processors
Articles 28(2), 28(3)(d) and 28(4)
7.1 General authorisation. You give us general written authorisation to engage Sub-processors. The Sub-processors engaged as at the effective date of this DPA are listed in Annex 3, Part A.
7.2 Contractual protection. Before engaging a Sub-processor we will put in place a written contract imposing data protection obligations equivalent to those in this DPA, in particular obligations to implement appropriate technical and organisational measures.
7.3 Our responsibility. Where a Sub-processor fails to fulfil its data protection obligations, we remain fully liable to you for the performance of those obligations, as if they were our own acts or omissions, subject to clause 16.
7.4 Notice of change. We will give you at least 14 days' notice by email before adding or replacing a Sub-processor, and will update Annex 3.
7.5 Your right to object. You may object on reasonable data protection grounds within 10 days of our notice. If you do, we will discuss it with you and will use reasonable efforts to make an alternative arrangement available. If we cannot, you may terminate the Terms of Service without penalty before the new Sub-processor begins processing, and we will refund any Charges paid in advance on a pro-rata basis.
7.6 We have set a 10-day objection window deliberately, so that it sits inside the notice periods our own providers give us. A longer window would be a promise we could not always keep.
8. Assisting you with Data Subject requests
Article 28(3)(e)
8.1 The Services allow you to access, correct, export and delete individual records directly. This is the primary way we assist you, and in most cases it will be sufficient.
8.2 Where a request cannot be handled through the Services, we will provide reasonable additional assistance, taking into account the nature of the processing and the information available to us.
8.3 Requests that come to us. If a Data Subject contacts us directly about Customer Personal Data, we will not respond substantively. We will:
(a) forward the request to you within 3 business days;
(b) tell the Data Subject that you are the controller and that we have passed it on; and
(c) assist you technically in responding.
8.4 Complaints. Since 19 June 2026, section 164A of the Data Protection Act 2018 requires you, as controller, to provide a means for Data Subjects to complain to you, to acknowledge a complaint within 30 days, to investigate it and to communicate the outcome. Where such a complaint reaches us, we will route it to you under clause 8.3 and assist you in investigating it.
8.5 We do not charge for assistance under this clause unless requests are manifestly excessive.
9. Assisting you with security, breaches and impact assessments
Article 28(3)(f)
9.1 Taking into account the nature of processing and the information available to us, we will assist you in complying with your obligations under Articles 32 to 36 UK GDPR.
9.2 This assistance includes:
(a) providing the information in Annex 2 for your own security assessment;
(b) notifying and supporting you in relation to personal data breaches, under clause 10;
(c) providing information reasonably required for a Data Protection Impact Assessment; and
(d) providing information reasonably required for prior consultation with the ICO.
9.3 DPIA support. Some processing carried out through the Services is likely to require a DPIA. In particular, the ICO identifies as high risk processing where "a personal data breach could jeopardise the physical health or safety of individuals" — which may apply to property access information — and processing which involves tracking an individual's geolocation.
The obligation to carry out a DPIA is yours, as controller. To help you, we make available a product-level DPIA template covering the standard processing performed by the Services, which you may adopt and adapt. It is available on request from privacy@sashbook.com.
10. Personal data breaches
Article 33(2)
10.1 We will notify you of a personal data breach affecting Customer Personal Data without undue delay and in any event within 48 hours of confirming that such a breach has occurred.
10.2 The 48-hour period runs from our confirmation of a breach, not from the detection of a suspected incident. An unverified alert is not a breach.
10.3 Our notification will contain, so far as known at the time:
(a) a description of the nature of the breach, including where possible the categories and approximate number of Data Subjects and records concerned;
(b) the name and contact details of the point of contact for further information;
(c) the likely consequences of the breach; and
(d) the measures taken or proposed to address it, including to mitigate its effects.
10.4 Notification in phases. Where we do not have all of this information at the time of first notification, we will provide it in phases without undue further delay, as permitted by Article 33(4). We will not delay the first notification in order to complete an investigation.
10.5 We do not assess whether a breach is notifiable to the ICO, and we do not filter which breaches we tell you about. That assessment is yours to make as controller. We notify you of every confirmed breach affecting your data.
10.6 We do not notify the ICO or Data Subjects on your behalf unless you instruct us to in writing.
10.7 We maintain an internal record of all personal data breaches, including those which are not notifiable.
10.8 We will not make any public statement identifying you in connection with a breach without your prior written consent, unless legally required to.
11. Deletion and return of data
Article 28(3)(g)
11.1 At your choice, we will delete or return all Customer Personal Data at the end of the provision of the Services, and delete existing copies, unless we are required by law to retain it.
11.2 In practice this operates as follows:
| Stage | Timing |
|---|---|
| Export available | At any time, and throughout the periods below. On request we provide a complete export within 10 working days, in a structured, commonly used, machine-readable format |
| Grace period | 30 days after termination — account suspended, data retained, export still available |
| Deletion from production systems | 90 days after termination or, where you ask us to delete your Account under clause 20.9 of the Terms of Service, 30 days after the request, or one calendar month if that is sooner |
| Backups | Encrypted backups are overwritten in the normal course of the backup cycle following deletion |
| Copies on Users' devices | Page copies expire after 24 hours; the calendar and customer copies are not shown after 7 days; actions taken without signal are kept until sent and removed 7 days after being sent. All are deleted on sign-out; at the next sign-in the copies and other Users' actions are deleted, as described in Annex 2. We cannot delete them remotely |
11.3 Where you have not requested a return of data, deletion under clause 11.2 is deemed to be your instruction.
11.4 Prospect Records. The Services have an automatic deletion setting for Prospect Records, described in clause 20.6 of the Terms of Service. It is switched off when your account is created. While you have it switched on, we apply the periods below. While it is off, we keep Prospect Records until you delete them or the Terms of Service end, and keeping them is your documented instruction for the purposes of Article 28(3)(a):
- records indicating an occupier has declined, or displays a "no junk mail" notice, are retained for as long as you operate in that area, so that the household is not approached again;
- records indicating a property is empty or recently sold are deleted after 6 months;
- all other prospect records are deleted 18 months after the last recorded visit.
11.5 Data we retain as controller under clause 3.4 — in particular billing records retained for six years to meet HMRC requirements — is not Customer Personal Data and is not affected by this clause.
11.6 On written request we will confirm that deletion has taken place.
12. Information and audit
Article 28(3)(h)
12.1 We will make available to you all information necessary to demonstrate compliance with our obligations under Article 28, and will allow for and contribute to audits.
12.2 In the first instance, we satisfy this by:
(a) this DPA and Annex 2;
(b) responding to a reasonable written security questionnaire; and
(c) providing, on request, our record of processing activities as it relates to your data, and the transfer risk assessments referred to in clause 14.
12.3 On-site audits. Where the information in clause 12.2 is not sufficient, you may conduct an audit or inspection, subject to the following, which regulate how the right is exercised and do not remove it:
(a) no more than once in any twelve-month period, except following a personal data breach affecting your data, where you have reasonable grounds to believe that we are not complying with this DPA, or where a regulator requires it;
(b) on at least 30 days' written notice, or 10 business days' where the audit follows a personal data breach affecting your data;
(c) during normal business hours and in a manner that does not unreasonably disrupt the Services;
(d) subject to confidentiality undertakings, and not extending to information about our other customers; and
(e) at your cost, except where the audit reveals a material breach by us, in which case we bear the reasonable cost.
12.4 Where you appoint a third-party auditor, they must not be a competitor of ours and must be subject to equivalent confidentiality obligations.
12.5 How audits work in practice. We have no premises where your data is held: it is held by the Sub-processors listed in Annex 3, and we cannot give you a right to inspect their facilities. For them, we will provide the independent audit reports or certifications they make available to us, such as SOC 2 reports or ISO/IEC 27001 certificates. An audit of us is carried out remotely, by reviewing documents, configuration and access records, unless you show that an on-site inspection is needed.
13. Restrictions on the data you place in the Services
13.1 The Services are designed for scheduling, delivering and invoicing exterior cleaning work. They are not designed to hold payment card numbers, banking credentials, detailed medical records, or criminal offence data, and you must not enter them.
13.2 Access notes and special category data. We recognise that operational notes about access to a property may inadvertently reveal information about a person's health or disability, and that under ICO guidance an intention to treat someone differently on the basis of such information brings it within Article 9 UK GDPR.
Accordingly:
(a) the Services provide structured service-preference fields so that operational needs can be recorded without free-text description of a person's condition, and you must use them in preference to free text;
(b) where you nonetheless record information which reveals a person's health or disability, you must have that person's explicit consent under Article 9(2)(a) and keep a record of it;
(c) we apply the security measures in Annex 2 to all such data whether or not it should have been entered, because our obligations under Article 32 do not depend on your compliance with this clause.
13.3 Prospect Records. You must not enter any name, telephone number, email address or health information into a Prospect Record. This restriction exists because it keeps the processing proportionate, and because it is what makes the canvassing feature defensible.
13.4 You will indemnify us against claims, fines and reasonable costs arising from your breach of this clause 13, subject to clause 18.9 of the Terms of Service, which applies the same cap to your liability.
14. International transfers
14.1 We will not make a Restricted Transfer of Customer Personal Data except in accordance with this clause.
14.2 Where a Sub-processor is established outside the United Kingdom, we rely on the UK adequacy regulations where they cover that Sub-processor, and otherwise on the International Data Transfer Agreement or the UK Addendum to the EU Standard Contractual Clauses issued by the Information Commissioner, as set out in Annex 4.
14.3 For each transfer that relies on the Agreement or the Addendum, we carry out and document an assessment under Article 46(1A) UK GDPR — the "data protection test" — and we will make it available to you on request.
14.4 You acknowledge that under ICO guidance a Restricted Transfer arises where the contracting entity of a provider is established outside the United Kingdom, even where the data itself is stored in the United Kingdom. Our database is configured to store data in the London (eu-west-2) region; this reduces practical risk but does not remove the need for a transfer mechanism.
14.5 Your acceptance of this DPA constitutes your authorisation of the transfers described in Annex 4.
15. Our access to your data
15.1 We do not access Customer Personal Data by default.
15.2 Access occurs only in the two circumstances set out in clause 12 of the Terms of Service: with your permission, either for one request (given by email, limited to 72 hours and confirmed to you by email when it begins and when it ends) or standing (switched on and off by the owner of your Account in Settings > Support access), and in either case only to deal with a question or problem you have raised with us; or in exceptional circumstances relating to security, imminent data loss, service restoration or legal obligation, of which we notify you within 48 hours.
15.3 Each permission you give is a documented instruction for the purposes of clause 4.
15.4 Every access under this clause is recorded, and you can see the record in Settings > Support access.
16. Liability
16.1 Our liability under this DPA is subject to the limitations in clause 18 of the Terms of Service, including the aggregate cap.
16.2 Nothing in this DPA limits or excludes any liability which cannot lawfully be limited, including a Data Subject's rights under Article 82 UK GDPR or the powers of the Information Commissioner under Article 83.
17. Term and general
17.1 This DPA takes effect when you accept the Terms of Service and continues until we have deleted or returned all Customer Personal Data in accordance with clause 11.
17.2 We may update this DPA where required to reflect a change in law, a change in Sub-processors, or a change to the Services. Material changes are notified in accordance with clause 22 of the Terms of Service.
17.3 This DPA is governed by the law of England and Wales, and the courts of England and Wales have exclusive jurisdiction.
ANNEX 1 — Description of the processing
Required by Article 28(3) UK GDPR
Subject matter
The provision of the Sashbook field service management software-as-a-service application to the Controller.
Duration
For the term of the Controller's subscription, plus the retention periods set out in clause 11.
Nature of the processing
Collection, recording, organisation, structuring, storage, retrieval, consultation, use, transmission, erasure and destruction of personal data, by automated means, for the purposes below.
Purpose of the processing
To enable the Controller to operate an exterior cleaning business, including:
- maintaining customer and property records
- scheduling and routing work
- recording completed work, including photographs and signatures of acceptance
- producing quotations, invoices and payment records, and tracking debt
- communicating with the Controller's own customers about their services and payments
- providing a self-service portal to the Controller's own customers
- where enabled by the Controller, recording properties canvassed for prospective business
Types of personal data
| Category | Detail |
|---|---|
| Identity and contact | Name, postal address, telephone number, email address |
| Location | Geographic coordinates of the property, unique property reference number (UPRN) |
| Service and financial | Service history, appointment dates, prices, quotations, invoices, payments, outstanding balances |
| Property access information | Free-text and structured notes recorded to enable access and safe working — for example the location of a key, the presence of an animal, or a service preference. May inadvertently reveal information about a person's health or disability, in which case it constitutes special category data under Article 9 UK GDPR |
| Images | Photographs of work carried out at a property. May inadvertently capture individuals, vehicle registration marks or property interiors |
| Signatures | Digital signatures acknowledging completion of work |
| Payment mandates | References to Direct Debit mandates held by the payment provider. Bank account details are held by the payment provider, not by us |
| Prospect Records | Map coordinates of a canvassed property, a canvassing outcome status, and an optional free-text note. No name, telephone number or email address. Some records created before 2 August 2026 also contain a postal address |
| Communications | Records of messages sent to the Controller's customers, and delivery status |
| Portal access | Authentication tokens issued to the Controller's customers for the self-service portal |
Categories of Data Subject
- Customers of the Controller — individuals, predominantly householders in the United Kingdom
- Users authorised by the Controller — the Controller's staff and operatives
- Occupiers of canvassed properties — individuals who are not customers of the Controller and who have not provided their data, where the Controller uses the canvassing features
Obligations and rights of the Controller
As set out in clause 3 of this DPA and in Data Protection Law.
ANNEX 2 — Technical and organisational measures
Required by Article 32 UK GDPR. These describe what is actually in place. We do not list controls we do not have.
Tenant separation
- All Customer Personal Data is partitioned by tenant identifier (org_id).
- Row-level security is enforced at the database level, not only in application code.
- Every query is filtered by tenant identifier derived from the server-side session. Tenant identifiers are never accepted from client input.
- Every change to row-level security or to the database schema is reviewed line by line before it is applied.
- Deleting a tenant deletes its records, in the periods set out in clause 11.
Travel times and routes
- The Services do not store travel times or routes obtained from any third party.
- Travel times used to plan work are estimated by our own code and are not kept beyond the request that needs them.
Encryption
- All traffic between users and the Services is encrypted in transit using TLS.
- Data at rest is encrypted at the storage layer by our database and storage provider.
- Passwords are stored only as salted hashes. We never hold them in readable form.
Access control
- Access to the Services requires authentication. Passkeys are supported.
- Role-based permissions restrict what each User of the Controller can see and do.
- We do not access Customer Personal Data by default. We do so only as set out in clause 15, and we record each access in a log you can see in Settings > Support access.
- Administrative credentials are held in a password manager. Secrets are never committed to source control.
Data on Users' devices
So that Users can keep working without a mobile signal, the application keeps a limited copy of Customer Personal Data in the browser storage of the User's own device.
- What is kept: the calendar for the months the User has opened, at most three; copies of pages the User has opened; and a copy of the Controller's customers that are not inactive, with their names, telephone numbers, email addresses, property addresses, property access notes, and the jobs and planned visits from three months before to three months after the day of the copy, with their prices and whether they are paid. The copies also say which customers can be charged by Direct Debit, but never hold the mandate itself.
- Actions taken without signal: when the User marks a job as done or skipped, records a payment (cash, contactless or Direct Debit), or writes, changes or deletes a property's access notes without signal, the device keeps that action (the job or property, the invoice when known, the payment method or the note, and the time) until it is sent. It is sent automatically when signal returns and applied once only: each action carries its own identifier, and an action that conflicts with a change made in the meantime is not applied but shown to the User. For access notes, the User's text is shown with a button to copy it. Actions already sent are removed from the device after 7 days.
- What is never kept: any field identified as secret. It is removed before the copy is written.
- Who can see it: the copy is tied to one User and one tenant. It is shown only to that User, in that tenant, while that User is signed in on the device.
- How long it lasts: page copies expire after 24 hours. The calendar and customer copies are not shown once they are more than 7 days old, and are deleted the next time they load with a connection. The customer copy is refreshed every 30 minutes while there is signal; a refresh that fails keeps the previous copy.
- When it is deleted: everything is deleted when the User signs out, from the account menu or the welcome page; if actions are still waiting to be sent, the User is warned first. When anyone signs in on the device with a password, a passkey or an invitation, the calendar copy, the customer copy and the page copies are deleted, and so are any queued actions that belong to another User; the signed-in User's own queued actions are kept so that they can still be sent. Completing a password reset deletes the page copies. Signing in through an email link does not trigger this deletion; the 7-day limits still apply.
- Other changes offline: apart from marking jobs as done or skipped, recording payments and changing property access notes, nothing can be saved while the device has no connection.
- Limits: we cannot delete a copy held on a device remotely, including after termination. The copy relies on the device's own encryption and screen lock. Keeping Users' devices locked is your responsibility under clause 4.2 of the Terms of Service.
Stored files and images
- Photographs of work and documents are held in private storage and are not publicly accessible.
- The only publicly accessible storage holds the business logos that customers choose to show on their documents and portal.
Logging
- Sign-in events are recorded by our authentication provider.
- We keep a record of every access we make to a tenant's data under clause 15.
Availability and resilience
- Our database provider takes daily backups.
Data location
- The primary database and file storage are configured to the London (eu-west-2) region.
- Provider support personnel may access systems from other jurisdictions under the transfer mechanisms in Annex 4.
Change management
- All changes are made through reviewed pull requests against a protected main branch.
- Automated tests and type checks must pass before a change can be merged.
- Database schema changes are applied through a controlled migration process.
Organisational measures
- Everyone with access to Customer Personal Data is bound by written confidentiality obligations.
- A record of processing activities is maintained under Article 30 UK GDPR, as controller and as processor.
- A record of all personal data breaches is maintained, whether or not notifiable.
- Sub-processors are engaged only under written contracts containing equivalent obligations.
What we do not have
We would rather tell you than let you assume:
- We do not hold ISO 27001 or SOC 2 certification.
- We do not offer a guaranteed uptime percentage or service credits.
- We do not operate a 24/7 on-call rota.
- We do not carry out third-party penetration testing at present.
- We do not run automated security alerting of our own beyond our providers' standard monitoring.
- We do not hold a backup outside our database provider.
- We do not encrypt individual fields, such as access notes, beyond the encryption at rest provided by our database provider.
ANNEX 3 — Sub-processors and other recipients
Part A — Sub-processors
These process Customer Personal Data on our behalf.
| Sub-processor | Contracting entity and country | Purpose | Data location | Restricted Transfer? |
|---|---|---|---|---|
| Supabase | Supabase Pte. Ltd., Singapore | Database, authentication and file storage | London (eu-west-2) | Yes |
| Vercel | Vercel Inc., United States | Application hosting and serverless execution | United States and edge locations | Yes |
| Resend | Plus Five Five, Inc., United States | Delivery of email to the Controller, its Users and its customers | European Union (Ireland) | Yes |
| The SMS Works | The SMS Works Ltd, United Kingdom (company 10663067) | Delivery of automatic text messages to the Controller's customers, only if the Controller switches them on | United Kingdom (Amazon Web Services, UK data centres) | No |
| Ideal Postcodes | IDDQD Limited, United Kingdom | UK address lookup and verification, including its postcodes.io service, used when a record is created or converted to a customer record | United Kingdom | No |
| Anthropic | Anthropic, PBC, United States | AI assistance to our support staff when we look into a request with your permission under clause 15 | United States | Yes |
Messages sent from a User's own phone. Where a User taps a link in the Services to send a WhatsApp message or a text message, the message is sent by the User's own device and phone provider, not by us. Those providers are not our Sub-processors.
Push notifications. Where a User turns on notifications, they are delivered through the push service of the User's browser (for example Google, Apple or Mozilla). The content of each notification is encrypted under the Web Push standard, so the push service cannot read it.
Part B — Independent controllers
These are not our Sub-processors. They determine their own purposes and means, and have a direct relationship with you and, in some cases, with your customers. They have their own privacy notices, which you should read.
| Party | Role |
|---|---|
| GoCardless Ltd (United Kingdom) | Independent controller in respect of Direct Debit mandates and payers. GoCardless requires that its privacy information is made accessible on payment pages — you must comply with this |
| PayPal UK Ltd (United Kingdom) | Independent controller in respect of payments made through PayPal |
| Starling Bank Limited (United Kingdom) | Your bank, if you connect it for bank reconciliation. It sends us your account's transaction data on your instruction |
| Google Cloud EMEA Ltd (Republic of Ireland) | Independent controller in respect of maps and routes drawn in the browser. See the note below |
▸ Google Maps Platform — location data disclosed to an independent controller
Google Maps Platform is used to display maps and, when a User draws a route on the map, to calculate that route. Doing the second means location data leaves the Services and reaches Google. Because Google acts as an independent controller of that data rather than as our processor, we want you to see exactly what is involved.
What is sent.
| When | What Google receives |
|---|---|
| A map is shown | The area of the map being viewed, with the device's IP address, browser information and any Google cookies already present on that device. The positions of the pins on the map are drawn by the device and are not sent |
| A route is drawn on the map | The coordinates of the properties on the route, together with the device's IP address, browser information and any Google cookies already present on that device. This allows Google to associate a set of residential coordinates with a device and potentially with a Google account |
What is never sent. Names, telephone numbers, email addresses, service history, prices, invoices, photographs, access notes or any other record content. Our servers send Google nothing. Google receives locations, not people.
Why Google is not listed as a sub-processor. It cannot be. Google contracts for Maps Platform on controller-to-controller terms under which each party is an independent controller. It publishes no sub-processor list for Maps and offers no UK or EEA data residency for it. This is Google's contractual position, not a gap in ours. The practical consequence is that, unlike our sub-processors in Part A, we cannot tell you that Google processes this data only on documented instructions, because that would not be true.
What this means for you.
- Location data about your customers' properties is disclosed to a third party acting as an independent controller. You should reflect this in the privacy information you give your own customers. We can provide suggested wording on request.
- Drawing a route also discloses information about the User whose device it is. If you provide a privacy notice to your staff, it should mention this.
- Google's use of the data is governed by its own terms, not by this DPA, and we do not warrant its compliance. We cannot pass on rights we do not have.
What we have done, and what remains. Since 30 September 2026 our servers no longer send any data to Google: travel times are estimated by our own code. Only the map and the route drawn in the browser still use Google. We have not committed to a date to change this and you should not rely on one.
Stored content. We do not store any content that we obtain from Google Maps. Some older records may contain address text originally obtained from Google; these are retained as historical records and are subject to the retention periods in clause 11.
Part C — Not applicable
Stripe processes payments from you to us for your subscription. That involves your account data, in respect of which we are controller, not your customers' data. It is therefore covered by our Privacy Policy and not by this DPA.
Changes
This Annex is the current list, published at app.sashbook.com/legal/dpa. We give at least 14 days' notice before adding or replacing a Sub-processor. See clause 7.
ANNEX 4 — International transfer mechanisms
| Sub-processor | Country of establishment | UK adequacy? | Mechanism relied on |
|---|---|---|---|
| Supabase | Singapore | No | UK Addendum to the EU Standard Contractual Clauses, incorporated in the Supabase Data Processing Addendum, together with a documented data protection test |
| Vercel | United States | Yes, while Vercel Inc. is certified to the UK Extension | UK adequacy regulations for the US (UK Extension to the EU–US Data Privacy Framework), while Vercel Inc. is certified; if not, the transfer clauses in the Vercel Data Processing Addendum, together with a documented data protection test |
| Resend | United States | Yes, while Plus Five Five, Inc. is certified to the UK Extension | UK adequacy regulations for the US (UK Extension to the EU–US Data Privacy Framework), while Plus Five Five, Inc. is certified; if not, the transfer clauses in the Resend Data Processing Addendum, together with a documented data protection test |
| Anthropic | United States | No | UK Addendum to the EU Standard Contractual Clauses, incorporated in the Anthropic Data Processing Addendum, together with a documented data protection test |
| The SMS Works | United Kingdom | Not applicable | No Restricted Transfer |
| Ideal Postcodes | United Kingdom | Not applicable | No Restricted Transfer |
A copy of the data protection test carried out for each transfer that relies on a safeguard is available on request to privacy@sashbook.com.
Sashbook LLP. A limited liability partnership registered in England and Wales, number OC461971. Registered office: 82A James Carter Road, Mildenhall, IP28 7DE. ICO registration C2080975.