Courier Privacy Policy
Version 2.1 · last updated 27 October 2026
The short version
We are Quiver Solutions Limited. We use information about your account, vehicle, work, payments, communications and location to operate our courier service.
Background location tracking is linked to an active work session, not simply to being signed in. The app may also request a current location when it opens or reconnects, including to process delivery actions saved while offline.
If you work in the warehouse, the app records your location while you are in warehouse mode, and we use it to work out the hours you were at the warehouse so your pay can be checked. Warehouse mode is therefore a second situation in which we collect location in the background, alongside an active delivery work session.
We work out courier tiers automatically each week from your delivery results, using the rules in our payment principles. Your tier decides which day you can start booking planned availability. You can ask a person at Quiver to look at your tier again.
We delete raw location readings 12 months after we receive them. Before we do, we turn them into trip records that don't include your name, account or the date you travelled, and we keep those for up to 36 months. We may use them to improve our services, to train models, and share or sell them. We never sell your raw location readings.
You can contact matt@quiver.co.uk to ask about your information, request a copy or correction, or exercise your applicable privacy rights.1. Who we are
Quiver Solutions Limited is responsible for the personal information described in this notice.
Company number: 16961611
Registered office: 27 Old Gloucester Street, London, WC1N 3AX
Privacy contact: matt@quiver.co.uk
This notice covers applying to become a courier, arranging a trial, undertaking deliveries and using the Quiver Courier app.2. Information we collect
Depending on your relationship with Quiver and the features you use, we collect:
Account and contact information: your name, email address, telephone numbers, addresses and profile photograph.
Application information: information you submit when applying or arranging a trial, and related communications.
Compliance-check information: identity documents and a selfie used to confirm who you are; your application video; right-to-work documents and Home Office check results; driving licence, vehicle registration (V5C), GOV.UK driving-licence check results and CBT certificate where your vehicle needs them; hire-and-reward insurance certificates; and Basic DBS check information, as described in section 9A. We use automated document reading to extract details such as your name, date of birth and expiry dates from these documents, and a member of our team reviews the result.
Vehicle information: vehicle type, capacity, dimensions and your selected vehicle.
Work records: planned availability, agreed and actual start and finish times, collections, deliveries, arrival and completion times, delivery status and proof of delivery.
Location and delivery-event information: coordinates, timestamps, location accuracy and events associated with approaching, arriving at and completing deliveries.
Performance information: courier tiers, feedback, reported problems, reliability information and performance assessments.
Payment information: bank details, payment address, amounts payable and payment history.
Communications: messages, support requests, photographs, voice messages and call-related records such as timing and outcome, English translations of messages and voice messages, and transcripts of calls you agree to have transcribed.
Authentication and technical information: account identifiers, verification status, passkey registration information, device and app details, installation and notification identifiers, app usage events and diagnostic records.3. Where information comes from
We receive information directly from you through application forms, the app and communications with Quiver. We also receive information through your use of the app, from our Live Ops and management teams, and from customers, retailers and delivery partners involved in your work.4. How we use your information
We use information to process applications and trials; maintain and secure accounts; manage planned availability; allocate and coordinate deliveries; plan routes and calculate arrival estimates; support communications; record delivery progress and completion; administer payments; assess performance and manage tiers; investigate problems and disputes; diagnose faults and improve the app; create trip records from location readings before we delete them (see section 12); and meet applicable legal obligations.
Some information is necessary for particular services. For example, we need payment details to pay you. Restricting location access may prevent location-dependent delivery features from working.5. Location and delivery tracking
During an active work session, the app is designed to collect background location information, including while the app is in the background or your screen is locked. An existing work session may resume when you reopen the app. Signing in alone does not start that background work-session tracking.
The app may also request a current location when it opens or reconnects, including to process delivery actions saved while offline. Location access is therefore not limited exclusively to background tracking during a work session.
We use location information to coordinate deliveries, estimate arrival times, understand delivery progress and investigate delivery issues. Update frequency varies with device permissions, the operating system, connectivity and movement. Information may be held temporarily on your device and uploaded when connectivity returns.
Separately, while you are in warehouse mode the app collects location in the background, in the same way it does during a delivery work session. We compare each reading with the location of our warehouses and use it to work out the periods you were at one. Those periods are what your recorded hours are based on, so that what you are paid can be checked against where you actually were. There is no clock-in or clock-out button; the record comes from the location readings.
We work the periods out from the readings rather than storing a fixed decision, so a correction is reflected straight away. Where the readings stop before you leave, we only count up to the last reading at the warehouse and mark the period for a person to check, rather than assuming when you left. Readings taken away from a warehouse are not counted as working time. Because the app records location in the same way during a delivery work session, a period at a warehouse can include time you were there on a delivery rather than working in the warehouse; we mark those periods so that a person checks them before your hours are agreed. If you believe a period is wrong, you can ask a person at Quiver to look at it, and you can ask us for the periods we hold for you.
The app integrates Doorstep AI for tracking delivery events near destinations. The integration supplies courier and delivery identifiers, destination addresses and coordinates, and uses location-based monitoring to support understanding of arrival and completion. The app also requests motion and Bluetooth permissions for delivery-tracking accuracy where supported.
The app is designed to stop background work-session tracking when you successfully go offline or sign out. If that action fails, check your status or contact Live Ops. You can control location access in your device settings. Previously captured information may still be uploaded afterwards.6. Performance assessment and courier tiers
Each week we work out your tier automatically from your delivery results over the previous eight weeks: how many deliveries you completed successfully, customer reviews, parcels that didn't match what you were given, and whether your documents are in date. The rules and thresholds are set out in our payment principles. Only outcomes count. Hours you planned to be available but didn't work never count.
Your tier decides which day you can start booking planned availability each week. Tier 1 can book from Monday, Tier 2 from Wednesday and Tier 3 from Thursday. Bookings are confirmed straight away.
When your tier changes we tell you in the app and explain why. If you think your tier is wrong, or based on information that is wrong, contact matt@quiver.co.uk. A member of our team will review it and can change it.
We also hold feedback, reported problems and work records to support performance management.7. Sign-in and passkeys
We process information needed for the sign-in methods available in the app, including verification codes and passkeys.
Your device or password manager may ask you to use Face ID, Touch ID or your screen lock when using a passkey. Quiver does not receive your facial scan, fingerprint or device passcode through that process. We receive the credential information needed to register and verify the passkey against your account.8. Calls, messages and delivery evidence
Calling services process the information needed to connect participants, including relevant telephone numbers or account identifiers and connection information. We hold call-related records such as timing and outcome. These records are distinct from recordings of the conversation, and we don't record calls unless you agree to a transcript.
Messages, photographs and voice messages you submit may be stored as part of the delivery or support record. A voice message is deliberately recorded content, rather than a live conversation.
Translation: our support team reads English. When you write or send a voice message in another language, we turn the voice message into text and translate the message or text into English so they can read it, and translate their replies into your language. Translations are made automatically (see section 10) and can contain mistakes; your original message is kept alongside.
Call transcripts: during an in-app call, our support team may ask to transcribe it, for example when you speak different languages. Your app asks you first, in your language, and the call is only recorded if you tap Yes. Saying No makes no difference to your work, and your answer is noted in your chat. If you agree, the call is recorded on our side, turned into text, translated into English and summarised for our support team. The recording is deleted as soon as the transcript is made, and within a day in any case.
Please avoid including unnecessary personal information about customers or other people in photographs and messages.9. Our lawful bases
The lawful basis depends on the purpose:
Contract: where processing is necessary to take steps at your request before entering an agreement, or to perform our agreement with you.
Legal obligation: where processing is necessary to meet applicable legal requirements, including relevant accounting and payment-record obligations.
Legitimate interests: where processing is necessary for interests such as coordinating reliable deliveries, investigating disputes, protecting our services, assessing performance, improving the app and creating trip records, and those interests are not overridden by your rights.
Consent: where an activity requires consent, we will explain it separately and provide a way to withdraw it. We record and transcribe a call only with your agreement on that call (section 8).
Device permissions control what the app can access. They do not, by themselves, determine the legal basis for processing information. Acknowledging this notice is not blanket consent to every use of your information.
You can object to processing based on legitimate interests. We will consider your objection and explain whether there are lawful grounds to continue the processing.9A. Criminal-record information
We ask couriers for a Basic DBS check because our delivery partners and retail customers require it for courier work. We use it only to confirm that your certificate shows no unspent convictions or cautions.
We record the certificate number, issue date and whether it shows none recorded. We do not record what a certificate says beyond that. If you upload a photo of a paper certificate, we delete the photo once it has been reviewed. If you share an online result, we keep a screenshot of the result page as evidence of the check, and we clear the share code once it has been used.
Only the Live Ops staff who carry out compliance checks can see this information. Our lawful basis is our legitimate interest in keeping customers, their goods and their homes safe. We process criminal-record information because it is necessary to prevent or detect unlawful acts such as theft and fraud (Data Protection Act 2018, Schedule 1, paragraph 10). We do not rely on your consent, because the check only works if it applies to every courier. Our appropriate policy document explains how we handle this information. Contact matt@quiver.co.uk for a copy.9B. Checking it's you
Each time you go online, if your last check was more than 24 hours ago, we ask for a selfie and, if your vehicle has a number plate, a photo of your vehicle. We do this because the law requires us to make sure the person working is the person whose right to work we checked.
We compare your selfie with the photo from your right to work check (your passport, or the photo on your GOV.UK share code profile) using Amazon Rekognition, run in the UK. This uses biometric data. We do it because the law requires us to check that the person working is the person whose right to work we checked (UK GDPR Article 9(2)(b) and Data Protection Act 2018 Schedule 1 paragraph 1), so it isn't optional. Amazon doesn't keep any face data from the comparison or use your photos to improve its services. If the automatic check finds a clear mismatch, we ask you for another selfie. If it isn't sure, can't run, or doesn't match two selfies in a row, a person in our support team compares your selfie with your right to work photo and decides. We message you in the app while they check. You can't go online until a selfie is approved or matches. If they decide it isn't you, or your face isn't clear, we ask you for a new selfie. If you think a check got it wrong, contact matt@quiver.co.uk and a person will look at it again.
We keep these photos for 30 days, or a year if a check fails, and keep a record of each check's result while you work with us and for 12 months after.10. Who receives your information
Information is available to Quiver staff managing operations, payments, support and technical services. Relevant delivery information, including progress and arrival estimates, is shared with customers, retailers and delivery partners to coordinate and complete deliveries.
Technology services used in connection with the courier app include:
Amazon Web Services: hosting, storage and authentication services, Amazon Rekognition to compare your daily selfie with your right to work photo (section 9B), Amazon Transcribe to turn voice messages and agreed call recordings into text, and Amazon Bedrock, running Anthropic's Claude model, to translate messages, voice messages and call transcripts into English and to summarise calls (section 8).
Doorstep AI: delivery-location and doorstep-event tracking.
Sentry: technical diagnostics. Diagnostic events can include your courier identifier and email address, together with app and error information.
PostHog: app usage analytics associated with your courier identifier. These analytics are not anonymous simply because your name is not included.
Twilio: telephone routing for customer calling, including telephone numbers and call-related information.
Expo's push notification service and the relevant Apple or Google notification services: delivery of notifications using device tokens, notification content and associated links.
In-app calling uses LiveKit technology. Software use alone does not mean that LiveKit's cloud service receives the call content; this depends on how the calling service is hosted.
If you choose to open navigation in Google Maps, routing information is passed to that service. If you subscribe to your availability calendar, the selected calendar service receives the private feed link and the availability information available through it. Those external services also process information under their own applicable privacy terms.
We may share information with professional advisers, authorities or other recipients where necessary to meet legal obligations or establish, exercise or defend legal claims.11. Where information is processed
Processing is not exclusively within the United Kingdom. The current courier app configuration uses AWS's London region for authentication, transcription and translation (Amazon Bedrock may run a translation in another EU region), a German endpoint for Sentry diagnostics and a European endpoint for PostHog analytics.
Those endpoints do not establish where every associated backup, support activity or subprocessor operates. The processing locations and applicable international-transfer arrangements for our providers are being verified. Contact matt@quiver.co.uk for information about these arrangements.12. How long we retain information
Different records serve different purposes. Relevant considerations include whether information is needed to manage your account or work, investigate delivery issues or payment queries, meet legal record-keeping obligations, or deal with a specific dispute or legal claim.
We delete application videos 30 days after you submit them, unless your application is still being reviewed.
We keep compliance-check documents (identity documents and selfie, right-to-work documents, driving licence, V5C, driving-licence check results, CBT and insurance certificates, and DBS result screenshots) while you work with us, and delete them 12 months after your account is permanently closed, or 12 months after you cancel your application if you don't resume it. We keep the 12 months so we can respond to Home Office, insurance or legal queries about work you carried out. Paper DBS certificate photos are deleted once they have been reviewed.
Location: we delete raw location readings 12 months after we receive them. Readings recorded as part of a delivery event, such as arriving at or completing a delivery, are kept with that delivery's record.
Trip records: before deleting raw readings, we turn them into trip records. A trip record does not include your name, account or any other identifier, or the date: only the quarter of the year, the day of the week and the hour in which the trip started. Each trip covers at most 30 minutes of travel in London, with about 2 kilometres or 10 minutes removed from each end, and its ends are also kept away from places where only a few couriers start their day. Locations are rounded to about 100 metres and times to the minute. The only other details kept are the vehicle type, the distance and the duration. We don't keep trips shorter than 1 kilometre, trips with fewer than four others like them, or any trips for a month in which someone made fewer than 20, and we don't make trip records for warehouse staff. We keep trip records for up to 36 months and review every year whether we still need them. We may use them to improve our services, to train models, and share or sell them to other organisations. We never sell or share your raw location readings. Because a trip record could still, with effort, be linked back to the courier who made it, we treat trip records as personal information and protect them in the same way.
Work sessions: records of when you went online and offline, and with which vehicle, are kept for six years, because they are the record of the hours you worked.
Messages and sign-ins: chat messages and their attachments, and records of devices you have signed out of, are deleted 12 months after they were made. English translations of messages and voice messages, and call transcripts with their translation and summary, are deleted 90 days after the message was sent or the call took place. When your account has been permanently closed for 12 months, we remove your personal details from it; delivery and payment records stay, no longer saying who you are.
Accounts not used for a year: if you haven't delivered with us for 12 months, we email you to ask whether you'd like to come back. If you don't tap Go Active, deliver or reply within 30 days, we permanently close your account, and your personal details are removed 12 months after that.
Other records, including delivery and payment records, are kept for as long as they are needed for the purposes in this notice and to meet legal record-keeping obligations.
Signing out or removing the app does not delete information already held by Quiver. You can ask about, or request deletion of, information we hold about you, subject to applicable legal conditions and exceptions.
Where information is genuinely anonymised so that you are no longer identifiable, it is no longer personal information. Combining records into an aggregate does not by itself guarantee that they are anonymous.13. Your rights
Depending on the circumstances, you may have rights to access your information; correct inaccurate or incomplete information; request deletion; restrict or object to processing; receive certain information in a portable format; withdraw consent where processing relies on it; and obtain information about, and exercise applicable rights concerning, automated decisions.
These rights are subject to legal conditions and exceptions. We may, for example, need to retain records to meet a legal obligation.
Contact matt@quiver.co.uk to make a request. We may need information to verify your identity. We will respond within the applicable statutory timeframe and explain any lawful extension, refusal or applicable charge. Requests are normally free of charge.14. Questions and complaints
Contact matt@quiver.co.uk or write to Quiver Solutions Limited, 27 Old Gloucester Street, London, WC1N 3AX.
You can also complain to the UK Information Commissioner's Office: https://ico.org.uk/make-a-complaint/
Telephone: 0303 123 111315. Changes to this notice
We will update this notice when our processing changes and communicate material changes appropriately, including changes to automated performance scoring or decisions affecting couriers.
This is version 2.1, last updated 27 October 2026. Earlier versions are kept and can be requested from matt@quiver.co.uk.
We are Quiver Solutions Limited. We use information about your account, vehicle, work, payments, communications and location to operate our courier service.
Background location tracking is linked to an active work session, not simply to being signed in. The app may also request a current location when it opens or reconnects, including to process delivery actions saved while offline.
If you work in the warehouse, the app records your location while you are in warehouse mode, and we use it to work out the hours you were at the warehouse so your pay can be checked. Warehouse mode is therefore a second situation in which we collect location in the background, alongside an active delivery work session.
We work out courier tiers automatically each week from your delivery results, using the rules in our payment principles. Your tier decides which day you can start booking planned availability. You can ask a person at Quiver to look at your tier again.
We delete raw location readings 12 months after we receive them. Before we do, we turn them into trip records that don't include your name, account or the date you travelled, and we keep those for up to 36 months. We may use them to improve our services, to train models, and share or sell them. We never sell your raw location readings.
You can contact matt@quiver.co.uk to ask about your information, request a copy or correction, or exercise your applicable privacy rights.1. Who we are
Quiver Solutions Limited is responsible for the personal information described in this notice.
Company number: 16961611
Registered office: 27 Old Gloucester Street, London, WC1N 3AX
Privacy contact: matt@quiver.co.uk
This notice covers applying to become a courier, arranging a trial, undertaking deliveries and using the Quiver Courier app.2. Information we collect
Depending on your relationship with Quiver and the features you use, we collect:
Account and contact information: your name, email address, telephone numbers, addresses and profile photograph.
Application information: information you submit when applying or arranging a trial, and related communications.
Compliance-check information: identity documents and a selfie used to confirm who you are; your application video; right-to-work documents and Home Office check results; driving licence, vehicle registration (V5C), GOV.UK driving-licence check results and CBT certificate where your vehicle needs them; hire-and-reward insurance certificates; and Basic DBS check information, as described in section 9A. We use automated document reading to extract details such as your name, date of birth and expiry dates from these documents, and a member of our team reviews the result.
Vehicle information: vehicle type, capacity, dimensions and your selected vehicle.
Work records: planned availability, agreed and actual start and finish times, collections, deliveries, arrival and completion times, delivery status and proof of delivery.
Location and delivery-event information: coordinates, timestamps, location accuracy and events associated with approaching, arriving at and completing deliveries.
Performance information: courier tiers, feedback, reported problems, reliability information and performance assessments.
Payment information: bank details, payment address, amounts payable and payment history.
Communications: messages, support requests, photographs, voice messages and call-related records such as timing and outcome, English translations of messages and voice messages, and transcripts of calls you agree to have transcribed.
Authentication and technical information: account identifiers, verification status, passkey registration information, device and app details, installation and notification identifiers, app usage events and diagnostic records.3. Where information comes from
We receive information directly from you through application forms, the app and communications with Quiver. We also receive information through your use of the app, from our Live Ops and management teams, and from customers, retailers and delivery partners involved in your work.4. How we use your information
We use information to process applications and trials; maintain and secure accounts; manage planned availability; allocate and coordinate deliveries; plan routes and calculate arrival estimates; support communications; record delivery progress and completion; administer payments; assess performance and manage tiers; investigate problems and disputes; diagnose faults and improve the app; create trip records from location readings before we delete them (see section 12); and meet applicable legal obligations.
Some information is necessary for particular services. For example, we need payment details to pay you. Restricting location access may prevent location-dependent delivery features from working.5. Location and delivery tracking
During an active work session, the app is designed to collect background location information, including while the app is in the background or your screen is locked. An existing work session may resume when you reopen the app. Signing in alone does not start that background work-session tracking.
The app may also request a current location when it opens or reconnects, including to process delivery actions saved while offline. Location access is therefore not limited exclusively to background tracking during a work session.
We use location information to coordinate deliveries, estimate arrival times, understand delivery progress and investigate delivery issues. Update frequency varies with device permissions, the operating system, connectivity and movement. Information may be held temporarily on your device and uploaded when connectivity returns.
Separately, while you are in warehouse mode the app collects location in the background, in the same way it does during a delivery work session. We compare each reading with the location of our warehouses and use it to work out the periods you were at one. Those periods are what your recorded hours are based on, so that what you are paid can be checked against where you actually were. There is no clock-in or clock-out button; the record comes from the location readings.
We work the periods out from the readings rather than storing a fixed decision, so a correction is reflected straight away. Where the readings stop before you leave, we only count up to the last reading at the warehouse and mark the period for a person to check, rather than assuming when you left. Readings taken away from a warehouse are not counted as working time. Because the app records location in the same way during a delivery work session, a period at a warehouse can include time you were there on a delivery rather than working in the warehouse; we mark those periods so that a person checks them before your hours are agreed. If you believe a period is wrong, you can ask a person at Quiver to look at it, and you can ask us for the periods we hold for you.
The app integrates Doorstep AI for tracking delivery events near destinations. The integration supplies courier and delivery identifiers, destination addresses and coordinates, and uses location-based monitoring to support understanding of arrival and completion. The app also requests motion and Bluetooth permissions for delivery-tracking accuracy where supported.
The app is designed to stop background work-session tracking when you successfully go offline or sign out. If that action fails, check your status or contact Live Ops. You can control location access in your device settings. Previously captured information may still be uploaded afterwards.6. Performance assessment and courier tiers
Each week we work out your tier automatically from your delivery results over the previous eight weeks: how many deliveries you completed successfully, customer reviews, parcels that didn't match what you were given, and whether your documents are in date. The rules and thresholds are set out in our payment principles. Only outcomes count. Hours you planned to be available but didn't work never count.
Your tier decides which day you can start booking planned availability each week. Tier 1 can book from Monday, Tier 2 from Wednesday and Tier 3 from Thursday. Bookings are confirmed straight away.
When your tier changes we tell you in the app and explain why. If you think your tier is wrong, or based on information that is wrong, contact matt@quiver.co.uk. A member of our team will review it and can change it.
We also hold feedback, reported problems and work records to support performance management.7. Sign-in and passkeys
We process information needed for the sign-in methods available in the app, including verification codes and passkeys.
Your device or password manager may ask you to use Face ID, Touch ID or your screen lock when using a passkey. Quiver does not receive your facial scan, fingerprint or device passcode through that process. We receive the credential information needed to register and verify the passkey against your account.8. Calls, messages and delivery evidence
Calling services process the information needed to connect participants, including relevant telephone numbers or account identifiers and connection information. We hold call-related records such as timing and outcome. These records are distinct from recordings of the conversation, and we don't record calls unless you agree to a transcript.
Messages, photographs and voice messages you submit may be stored as part of the delivery or support record. A voice message is deliberately recorded content, rather than a live conversation.
Translation: our support team reads English. When you write or send a voice message in another language, we turn the voice message into text and translate the message or text into English so they can read it, and translate their replies into your language. Translations are made automatically (see section 10) and can contain mistakes; your original message is kept alongside.
Call transcripts: during an in-app call, our support team may ask to transcribe it, for example when you speak different languages. Your app asks you first, in your language, and the call is only recorded if you tap Yes. Saying No makes no difference to your work, and your answer is noted in your chat. If you agree, the call is recorded on our side, turned into text, translated into English and summarised for our support team. The recording is deleted as soon as the transcript is made, and within a day in any case.
Please avoid including unnecessary personal information about customers or other people in photographs and messages.9. Our lawful bases
The lawful basis depends on the purpose:
Contract: where processing is necessary to take steps at your request before entering an agreement, or to perform our agreement with you.
Legal obligation: where processing is necessary to meet applicable legal requirements, including relevant accounting and payment-record obligations.
Legitimate interests: where processing is necessary for interests such as coordinating reliable deliveries, investigating disputes, protecting our services, assessing performance, improving the app and creating trip records, and those interests are not overridden by your rights.
Consent: where an activity requires consent, we will explain it separately and provide a way to withdraw it. We record and transcribe a call only with your agreement on that call (section 8).
Device permissions control what the app can access. They do not, by themselves, determine the legal basis for processing information. Acknowledging this notice is not blanket consent to every use of your information.
You can object to processing based on legitimate interests. We will consider your objection and explain whether there are lawful grounds to continue the processing.9A. Criminal-record information
We ask couriers for a Basic DBS check because our delivery partners and retail customers require it for courier work. We use it only to confirm that your certificate shows no unspent convictions or cautions.
We record the certificate number, issue date and whether it shows none recorded. We do not record what a certificate says beyond that. If you upload a photo of a paper certificate, we delete the photo once it has been reviewed. If you share an online result, we keep a screenshot of the result page as evidence of the check, and we clear the share code once it has been used.
Only the Live Ops staff who carry out compliance checks can see this information. Our lawful basis is our legitimate interest in keeping customers, their goods and their homes safe. We process criminal-record information because it is necessary to prevent or detect unlawful acts such as theft and fraud (Data Protection Act 2018, Schedule 1, paragraph 10). We do not rely on your consent, because the check only works if it applies to every courier. Our appropriate policy document explains how we handle this information. Contact matt@quiver.co.uk for a copy.9B. Checking it's you
Each time you go online, if your last check was more than 24 hours ago, we ask for a selfie and, if your vehicle has a number plate, a photo of your vehicle. We do this because the law requires us to make sure the person working is the person whose right to work we checked.
We compare your selfie with the photo from your right to work check (your passport, or the photo on your GOV.UK share code profile) using Amazon Rekognition, run in the UK. This uses biometric data. We do it because the law requires us to check that the person working is the person whose right to work we checked (UK GDPR Article 9(2)(b) and Data Protection Act 2018 Schedule 1 paragraph 1), so it isn't optional. Amazon doesn't keep any face data from the comparison or use your photos to improve its services. If the automatic check finds a clear mismatch, we ask you for another selfie. If it isn't sure, can't run, or doesn't match two selfies in a row, a person in our support team compares your selfie with your right to work photo and decides. We message you in the app while they check. You can't go online until a selfie is approved or matches. If they decide it isn't you, or your face isn't clear, we ask you for a new selfie. If you think a check got it wrong, contact matt@quiver.co.uk and a person will look at it again.
We keep these photos for 30 days, or a year if a check fails, and keep a record of each check's result while you work with us and for 12 months after.10. Who receives your information
Information is available to Quiver staff managing operations, payments, support and technical services. Relevant delivery information, including progress and arrival estimates, is shared with customers, retailers and delivery partners to coordinate and complete deliveries.
Technology services used in connection with the courier app include:
Amazon Web Services: hosting, storage and authentication services, Amazon Rekognition to compare your daily selfie with your right to work photo (section 9B), Amazon Transcribe to turn voice messages and agreed call recordings into text, and Amazon Bedrock, running Anthropic's Claude model, to translate messages, voice messages and call transcripts into English and to summarise calls (section 8).
Doorstep AI: delivery-location and doorstep-event tracking.
Sentry: technical diagnostics. Diagnostic events can include your courier identifier and email address, together with app and error information.
PostHog: app usage analytics associated with your courier identifier. These analytics are not anonymous simply because your name is not included.
Twilio: telephone routing for customer calling, including telephone numbers and call-related information.
Expo's push notification service and the relevant Apple or Google notification services: delivery of notifications using device tokens, notification content and associated links.
In-app calling uses LiveKit technology. Software use alone does not mean that LiveKit's cloud service receives the call content; this depends on how the calling service is hosted.
If you choose to open navigation in Google Maps, routing information is passed to that service. If you subscribe to your availability calendar, the selected calendar service receives the private feed link and the availability information available through it. Those external services also process information under their own applicable privacy terms.
We may share information with professional advisers, authorities or other recipients where necessary to meet legal obligations or establish, exercise or defend legal claims.11. Where information is processed
Processing is not exclusively within the United Kingdom. The current courier app configuration uses AWS's London region for authentication, transcription and translation (Amazon Bedrock may run a translation in another EU region), a German endpoint for Sentry diagnostics and a European endpoint for PostHog analytics.
Those endpoints do not establish where every associated backup, support activity or subprocessor operates. The processing locations and applicable international-transfer arrangements for our providers are being verified. Contact matt@quiver.co.uk for information about these arrangements.12. How long we retain information
Different records serve different purposes. Relevant considerations include whether information is needed to manage your account or work, investigate delivery issues or payment queries, meet legal record-keeping obligations, or deal with a specific dispute or legal claim.
We delete application videos 30 days after you submit them, unless your application is still being reviewed.
We keep compliance-check documents (identity documents and selfie, right-to-work documents, driving licence, V5C, driving-licence check results, CBT and insurance certificates, and DBS result screenshots) while you work with us, and delete them 12 months after your account is permanently closed, or 12 months after you cancel your application if you don't resume it. We keep the 12 months so we can respond to Home Office, insurance or legal queries about work you carried out. Paper DBS certificate photos are deleted once they have been reviewed.
Location: we delete raw location readings 12 months after we receive them. Readings recorded as part of a delivery event, such as arriving at or completing a delivery, are kept with that delivery's record.
Trip records: before deleting raw readings, we turn them into trip records. A trip record does not include your name, account or any other identifier, or the date: only the quarter of the year, the day of the week and the hour in which the trip started. Each trip covers at most 30 minutes of travel in London, with about 2 kilometres or 10 minutes removed from each end, and its ends are also kept away from places where only a few couriers start their day. Locations are rounded to about 100 metres and times to the minute. The only other details kept are the vehicle type, the distance and the duration. We don't keep trips shorter than 1 kilometre, trips with fewer than four others like them, or any trips for a month in which someone made fewer than 20, and we don't make trip records for warehouse staff. We keep trip records for up to 36 months and review every year whether we still need them. We may use them to improve our services, to train models, and share or sell them to other organisations. We never sell or share your raw location readings. Because a trip record could still, with effort, be linked back to the courier who made it, we treat trip records as personal information and protect them in the same way.
Work sessions: records of when you went online and offline, and with which vehicle, are kept for six years, because they are the record of the hours you worked.
Messages and sign-ins: chat messages and their attachments, and records of devices you have signed out of, are deleted 12 months after they were made. English translations of messages and voice messages, and call transcripts with their translation and summary, are deleted 90 days after the message was sent or the call took place. When your account has been permanently closed for 12 months, we remove your personal details from it; delivery and payment records stay, no longer saying who you are.
Accounts not used for a year: if you haven't delivered with us for 12 months, we email you to ask whether you'd like to come back. If you don't tap Go Active, deliver or reply within 30 days, we permanently close your account, and your personal details are removed 12 months after that.
Other records, including delivery and payment records, are kept for as long as they are needed for the purposes in this notice and to meet legal record-keeping obligations.
Signing out or removing the app does not delete information already held by Quiver. You can ask about, or request deletion of, information we hold about you, subject to applicable legal conditions and exceptions.
Where information is genuinely anonymised so that you are no longer identifiable, it is no longer personal information. Combining records into an aggregate does not by itself guarantee that they are anonymous.13. Your rights
Depending on the circumstances, you may have rights to access your information; correct inaccurate or incomplete information; request deletion; restrict or object to processing; receive certain information in a portable format; withdraw consent where processing relies on it; and obtain information about, and exercise applicable rights concerning, automated decisions.
These rights are subject to legal conditions and exceptions. We may, for example, need to retain records to meet a legal obligation.
Contact matt@quiver.co.uk to make a request. We may need information to verify your identity. We will respond within the applicable statutory timeframe and explain any lawful extension, refusal or applicable charge. Requests are normally free of charge.14. Questions and complaints
Contact matt@quiver.co.uk or write to Quiver Solutions Limited, 27 Old Gloucester Street, London, WC1N 3AX.
You can also complain to the UK Information Commissioner's Office: https://ico.org.uk/make-a-complaint/
Telephone: 0303 123 111315. Changes to this notice
We will update this notice when our processing changes and communicate material changes appropriately, including changes to automated performance scoring or decisions affecting couriers.
This is version 2.1, last updated 27 October 2026. Earlier versions are kept and can be requested from matt@quiver.co.uk.
