Skip to content

Cookies.

Necessary cookies keep this site working. The rest only run if you say so: , or read the Cookie Policy.

Operator Privacy Notice.

Last updated 29 October 2026

Jump to a section

Version 2026-10-30. It takes effect on the day we publish it. This notice explains what we do with information about you when you work through Recovru as an independent operator, or when you are sent to jobs booked through Recovru by an operator. It is written for you, not for lawyers, and it is deliberately specific about the things operators most often ask about: where you are, how requests reach you, how quotes are ranked, what your performance record is used for, and what happens to your identity documents. A separate notice covers customers. If you also use Recovru as a customer, both apply to you in those separate roles.

Changes in this version

section 4.3 says that we now delete your last position when you go offline, or when your app has sent none for 30 minutes, unless you are on a job, and section 12 matches it; section 2 says that we note which area of a map grid your position falls in, kept and deleted with the position, and section 12 that we count operators by area only where there are 3 or more, with no names; sections 4.4, 5 and 11 say that driving times for matching requests now come from our own routing server, on our server in Manchester, England, instead of the public Project OSRM server, and that, once we switch it on, Google works them out with live traffic for the operators about to be sent a request; and section 5 says that, once our updated matching is in use, we record a score with each request we send you, which does not decide whether or when you are sent it. What changed in version 2026-10-29: we may now ask you to confirm it is you, and sections 2, 3, 7, 9.2 and 12 say when, what we record about your phone and connection to decide when to ask, what allows us to, and how long we keep it; until we switch on the face check, each check is a video call with a member of our staff; section 9 says how we compare the name on your account with the name on your identity document; sections 3, 8, 11 and 12 say that when your identity or right to work is checked through TrustID, TrustID and its partner LexisNexis Risk Solutions screen you against sanctions and politically exposed person lists, and otherwise Didit does, and what allows us to; and sections 9, 12 and 13.1 say that the images of your identity document are kept while you work through Recovru and for 2 years after you stop or delete your account, the same as right to work evidence, instead of 24 months from the check, what counts as stopping, and that you can also ask to delete your account at support@recovru.com. What changed in version 2026-10-28: section 9.4 explains the Operator Agreement you sign electronically, what our signing service records about the signing and how long we keep it; sections 8, 10 and 11 say that the web app and WM HQ, our operations system, are now served from a server in Manchester, England, that Hostinger provides, that Cloudflare now only relays a call, and that Webmasters LDN, which builds and runs WM HQ, is a trading name of Dapper Trading Ltd, the company behind Recovru, not a separate supplier. What changed in version 2026-10-22: section 9.1 names TrustID, a registered right to work digital verification service provider, as the way a British or Irish passport can be checked once we switch it on, and sections 2, 3, 8, 11, 12 and 13 say what it receives, the police database it checks, where it holds your information, how long each copy is kept and how to withdraw consent; section 9.1 also says how we check original documents in person or on a live video call, and section 7 says what happens if a provider changes its result after we approved it. Section 4.1 says what location permission the iPhone and Android apps each ask for. Sections 2, 3, 12 and 13 add reports about messages, blocks and the word filter. Sections 9 and 9.2 say you can withdraw face check consent, and ask for an identity check without face matching, in the app, including on the consent screen itself. Section 13.1 adds www.recovru.com/delete-account, and says that if you signed in with Apple we tell Apple to end Recovru's access to your Apple ID when you delete your account, which is the only reason we keep Apple's token (section 2). Sections 9 and 12 say which deletions are automatic and which are not yet, as the customer Privacy Policy does: the invoices and other tax records we keep, and the removal of files from our storage provider, are not yet automatic. Section 9 says to ask us whether the removal of your face images is complete, and sections 7 and 9 say that a possible match in Didit's sanctions and politically exposed person screening stops you going online until a member of our staff has reviewed it.

1. Who is responsible for your information.

Dapper Trading Ltd, trading as Recovru ("we", "us"), is the data controller for the information described here. That means we decide why and how it is used, and we are accountable for it.

  • Company: Dapper Trading Ltd (company number 08800299), registered in England and Wales, trading as Recovru.
  • Registered office: Oak House, Reeds Crescent, Watford WD24 4QP.
  • Data protection contact: privacy@recovru.com, live chat with our staff in the app, or post to that address marked "Data protection". We have not appointed a data protection officer; privacy@recovru.com reaches the person at Recovru responsible for data protection.

If you are sent to jobs booked through Recovru by an operator who employs or engages you, that operator is also a controller of your information for their own purposes, and some of what we know about you came from them.

2. What we collect about you.

  • Who you are. What it includes: your name, date of birth, phone number, email address and profile photograph. Where it comes from: you, when you sign up.
  • Your business. What it includes: whether you are a sole trader, a partnership or a company, your legal name and any trading name, your business address, your company number and registered office if you are a company, whether you are VAT registered, with your VAT number and the result of its check with HMRC if you are, or your confirmation that you are not, a business email if you give us one, and your website. Where it comes from: you, the register at Companies House, and the check of your VAT number with HMRC, which our payment provider, Stripe, makes for us, or which we make with HMRC directly (section 11).
  • Your authority to act for your company. What it includes: if you are a company, we look up your company number at Companies House and keep the company's name, status, type and registered office, and the name, role and appointment date of each of its current directors, members and persons with significant control, with the month and year of birth Companies House shows for the person we match to you; the result of matching your verified name and date of birth to that list; any signed letter of authority from a director that you or the director send us, with the signer's name and role and the date; and the decision our staff make, with their reasons. Where it comes from: Companies House, which is a public register, you, and our staff.
  • Your VAT checks. What it includes: each time you give or change a VAT number, and then every month, we check it. We keep the number, the date and result of each check, the name and address HMRC holds for that number, HMRC's reference for the check where it gives one, whether HMRC's name matches your legal name, your trading name or your own name and whether the postcode matches, and the history of what you told us about your VAT status, including your written confirmation that you are not registered. Where it comes from: you, HMRC (through Stripe, which makes the check for us, or directly through HMRC's own online service where HMRC has approved our software), and our staff if they check by hand.
  • Your identity check. What it includes: the legal name, date of birth, nationality, document type, document number and expiry read from your identity document; the result of the chip read where your passport has one; images of your document; the photograph and short video of your face taken for the liveness test; the score of the match between that face and the photograph on your document; whether sanctions and politically exposed person screening raised anything; the result of comparing the name on your account with the name on your document; your internet address during the check, what Didit's check says about it, and the phone number you give Didit; the country that issued your document, any warnings Didit raised about it, and the full result Didit sends us. Where it comes from: Didit (section 9), and we receive and keep all of it.
  • Right to work. What it includes: which of the routes in section 9.1 was used, and the evidence for it: the result of the Home Office online check and the share code and date of birth used for it; or a note and copy of the original documents a member of our staff checked with you; or the Home Office's Positive Verification Notice, with its reference and date; or, for a check by TrustID, its report, its reference, the date of the check, its confirmations, the image of your passport or card, the image of your face and the photograph on the document that it compared, and its result. Also the date of the check, who carried it out, and the date by which it must be checked again if your permission has an end date. Where it comes from: you, and the Home Office.
  • Insurance, licences and other documents. What it includes: the certificates, schedules, licences, inspection reports and other documents section 8.3 of the Operator Terms asks for, and the details you and our staff record from them, such as the insurer, policy number, limits, dates and the class of use printed on a certificate. For every service it includes both sides of your photocard driving licence, which show your name, address, date of birth, photograph, licence number, and the categories you may drive and until when; a photocard does not show penalty points or endorsements, and we do not ask for them or check them. We do not ask for a D4 medical merely to prove a licence category already on that licence. The app accepts supported images and PDF documents directly into your private operator file for staff review. Our staff can also add a document received through an authorised alternative route. We do not send these insurance, licence or service documents to our identity provider or an AI reader. A medical report or DBS certificate already supplied is handled under its recorded explicit consent or other lawful condition, and the restrictions in section 3 and section 9.3. Where it comes from: you, and our staff.
  • How you work. What it includes: the services you say you offer and what you tell us about them, your answers to our licensing questions (the heaviest vehicle you carry, whether you move vehicles that are not broken down, whether you cross borders, and any note you add), and whether you are British or Irish and whether you employ others, which decide which checks we ask for. Where it comes from: you, and our staff if they record it for you.
  • Work for an organisation or a police force. What it includes: where an organisation that books through Recovru asks that its requests go only to operators who meet its requirements, what you gave us to meet them, for example your insurance cover or a PAS 43 certificate; that the organisation approves you, with its reference, the dates the approval runs and the kinds of work it covers; for a police force that requires it, your vetting level, its reference and its expiry date, recorded from what the force confirms to us and never from a record you obtained about yourself; on a police booking, the handover record you make (who received the vehicle, when, its condition on arrival and photographs of the vehicle only); and a log of each time you, our staff or the force's staff open, change or are given the force's booking details. Where it comes from: the organisation, you, and our staff.
  • A DBS certificate already supplied, or an organisation's vetting confirmation where required for its work. Section 9.3 explains the limits. Where it comes from: the relevant organisation, or you where a certificate was previously supplied.
  • Checks that it is you (section 9.2). What it includes: for each check we ask for, what prompted it, the signals used and the chance it was asked, whether and when it was taken, and its result; for a face check, two scores as well. Where it comes from: the app, our staff, and Didit.
  • Your phone and connection, for the checks in section 9.2. What it includes: a one-way hash of an identifier the app makes at random when it is installed (not your phone's own identifiers), the platform and app version, when each phone was first and last used with your account, and the country your connection comes from. Where it comes from: your device and its connection.
  • Where you are. What it includes: your position while you are online, and your route while you are on a job; and, with your position, which area of a map grid it falls in, at four sizes from about 250 square kilometres down to under 1 (the open-source H3 grid, worked out on our own servers). See section 4: this is the most detailed thing we hold about you. Where it comes from: your device.
  • Your quotes and jobs. What it includes: the requests you were sent, the quotes you sent and when, the arrival band set for each quote, which quotes customers accepted, the jobs you completed or cancelled, anything you recorded about a job changing, your photographs, and your payouts for each. Where it comes from: the app, automatically.
  • How you perform. What it includes: the performance information described in section 7.1. Where it comes from: the app, customers and our staff.
  • What customers say. What it includes: your star rating, the number of ratings, any compliments awarded, and the number of jobs you have completed. Where it comes from: customers, after a job.
  • Money. What it includes: the payout account you hold with Stripe, your payouts, your membership payments, your payout statements, your monthly statements and, if you are VAT registered, your quarterly VAT summaries, the record of who accounts for the VAT on each job and why, the invoices, receipts and credit notes we issue in your name as your agent, and our own VAT invoices to you. Every invoice and receipt is emailed to you or the customer from billing@recovru.com. Where it comes from: you and Stripe.
  • Your standing with us. What it includes: the messages we send you about your account and why (for example that a document is running out or a VAT number was rejected), the notices of changes to our terms and whether the email reached you, which terms and fees you accepted and when, your founding place number if you have one, and the record of any override our staff made to let you work. Where it comes from: the app, our staff and Brevo.
  • Agreements you sign with us. What it includes: the agreement, the version you signed, when, the name you typed, and your device's internet address and browser details at the time. Where it comes from: you (section 9.4).
  • Communications. What it includes: messages you send in the app, live chat and emails with our staff, photographs and video you attach, and the fact, time, length, outcome and the device used for each in-app call. Where it comes from: you.
  • Reports and blocks. What it includes: a report you make about a message, photo or video, with your reason and any note, a copy of what was sent, who sent it and when, and the support case it opens; a report a customer makes about one of your messages, with a copy of it; and the people you block, and whether a customer has blocked you. In a quote chat, the case your report opens does not show the customer's identity. Where it comes from: you, the customer and the app.
  • The people you send. What it includes: the name and Recovru email address you give us for a person you are sending to a job, the undertaking they sign, and, if we ask, the information Operator Terms section 5.1 describes about anyone you employ or engage: who they are, who engaged them, the type of business, registered addresses and company numbers, and what right to work checks were made. Where it comes from: you, and the person you send. They have their own account, and this notice applies to them as an operator.
  • Hazards you report. What it includes: the kind of hazard, where it is, any note you add, when, and each time you confirm or clear one. Other operators see the hazard, where it is and how many people have confirmed it, never who reported it. Where it comes from: you.
  • Your vehicle. What it includes: the registration, make, model and photograph of the vehicle you work from, and the results of its MOT, tax and stolen vehicle checks. Where it comes from: you, and our vehicle data provider.
  • Device and app data. What it includes: your device type, app version, notification and call-ringing tokens, which screens you open and which steps you take, a record of where the app fails, and a scrambled copy of your email address and internet address for each sign-in attempt, to stop guessing of passwords. If you sign in with Apple on an iPhone, we keep, encrypted, the token Apple gives us for your sign-in, only so that when you delete your account we can tell Apple to end Recovru's access to your Apple ID. Where it comes from: your device, and Apple.

What we do not hold. We never see or store the contents of your in-app calls. They connect directly between you and the customer and are not recorded. We never store your full card or bank details, which are held by Stripe. We do not obtain any immigration decision, visa history or Home Office file about you: from the Home Office check we see only the result the Home Office's own service shows. If the identity document you choose is a residence permit, we hold an image of it, and a residence permit is an immigration document.

3. Why we use it, and what allows us to.

  • Setting up and running your operator account. Our legal basis: performance of our contract with you.
  • Verifying who you are and that your business is real. Our legal basis: our legitimate interest in a network customers can trust, and, for the biometric part, your explicit consent (section 9).
  • Asking you to confirm it is you, at the times section 9.2 describes, and using your phone and connection signals to decide when to ask. Our legal basis: our legitimate interest, and our customers', in the person who arrives being the person we verified. The face check itself is biometric, and for it we rely on your explicit consent (section 9.2); without it, the check is a video call with a member of our staff.
  • Screening against sanctions and politically exposed person lists. Our legal basis: our legal obligation not to make funds available to a person under the UK's financial sanctions (the Sanctions and Anti-Money Laundering Act 2018 and the regulations made under it), since we pay you, and our legitimate interest in preventing fraud and the misuse of Recovru. Where a result could be information about an offence, the condition we rely on is preventing or detecting unlawful acts (paragraph 10 of Schedule 1 to the Data Protection Act 2018), and we are adopting the appropriate policy document that paragraph requires.
  • Comparing the name on your account with the name on your identity document. Our legal basis: performance of our contract with you, and our legitimate interest in keeping each account to the person verified for it.
  • Checking your right to work, and that of anyone you send. Our legal basis: legal obligation, from 1 October 2026, under sections 14A and 15A of the Immigration, Asylum and Nationality Act 2006, inserted by section 48 of the Border Security, Asylum and Immigration Act 2025. Where the check reveals special category information, such as your nationality or ethnic origin shown on a document, the condition we rely on is paragraph 1 of Schedule 1 to the Data Protection Act 2018, and we are adopting the appropriate policy document that paragraph requires. Where TrustID compares your face with the photograph on your document, which is biometric, the condition we rely on is your explicit consent, which we ask for on its own screen first (section 9.1).
  • Checking that you are allowed to act for your company. Our legal basis: our legitimate interest in knowing that the person who signs up, quotes and is paid for a company has its authority.
  • Checking your insurance, licences and documents are valid and current. Our legal basis: performance of our contract, and our legitimate interest in customer safety.
  • Checking your driving licence. Our legal basis: performance of our contract and our legitimate interest in customer safety. We check the categories you may drive and their expiry, never penalty points or endorsements. We do not require a D4 medical upload merely to prove an entitlement on your licence. A medical report previously supplied is health information. Where we hold it on explicit consent, we retain the consent record, limit access to permitted staff and use it only for the stated purpose. You can withdraw that consent at privacy@recovru.com and ask us to delete the report. Withdrawing an unnecessary medical report does not itself remove ordinary service clearance; a separate lawful requirement for a particular activity must be identified and explained before we collect any further health information.
  • Checking your VAT number, and deciding who accounts for the VAT on each job. Our legal basis: legal obligation for tax and accounting records, and our legitimate interest in issuing correct invoices in your name. The check is automatic. If HMRC does not know the number, or it belongs to a different business from the one on your account, it is rejected and you cannot quote until you correct it or tell us in the app that you are not VAT registered. If a monthly check fails, VAT is switched off for you at once and you cannot quote until it is put right, and we tell you why. Our staff can override a rejection only by recording a written reason under their own name.
  • Sending an organisation's requests only to operators who meet its requirements, and keeping the records a police force's work needs. Our legal basis: performance of our contract with you and our legitimate interest in the organisation's requirements being met. A vetting level records only the standard a force has cleared you to, never the reasons.
  • Sharing your latest position with our staff while the app is open, only if you switch on Share live location (section 4.3). Our legal basis: your consent, which you give by switching it on and withdraw by switching it off.
  • Understanding how the app is used and where it fails, so we can fix and improve it. Our legal basis: our legitimate interest in a service that works. You can object by switching off Usage analytics, and the reports of where the app fails by switching off Share trip data, in the Privacy screen.
  • Showing other operators a hazard on the road. Our legal basis: our legitimate interest in operators and customers being safe.
  • Checking a DBS certificate. Our legal basis: section 9.3.
  • Sending you nearby requests. Our legal basis: performance of our contract with you; without it we cannot send you work.
  • Showing customers your quote, and ordering the quotes they see. Our legal basis: performance of our contract, and our legitimate interest in customers being able to choose reliable help quickly.
  • Showing the customer where you are while you are on their job. Our legal basis: performance of our contract, and our legitimate interest in the customer knowing help is coming.
  • Paying you, issuing invoices, receipts and credit notes in your name as your agent, issuing our own VAT invoices to you, and taking your membership payment. Our legal basis: performance of our contract, and legal obligation for tax and accounting records.
  • Reporting to HMRC. Our legal basis: legal obligation, where the rules for digital platforms in the Platform Operators (Due Diligence and Reporting Requirements) Regulations 2023 apply to us. If they do, we must collect details such as your address, date of birth, tax reference and bank account, and report what you earned through Recovru to HMRC each year. We will tell you before we first ask.
  • Keeping and reviewing your performance record. Our legal basis: our legitimate interests in giving customers reliable help and in treating operators fairly and consistently, and performance of our contract (section 7 of the Operator Terms describes the review). Section 7.1 sets it out in full.
  • Handling disputes about a job, a charge, a cancellation or a payment. Our legal basis: legitimate interest in resolving disputes fairly with evidence, and legal obligation where a claim follows.
  • Answering you in live chat. Our legal basis: performance of our contract, and legitimate interest in resolving problems with a record of what was said.
  • Reviewing reports about messages, photos and videos, keeping blocks in place, and the automatic word filter, which replaces listed offensive words with **** before a message is delivered and makes no decision about you. Our legal basis: legitimate interests in keeping customers and operators safe and dealing with complaints, and performance of our contract (Operator Terms, section 14A). If you ask for the information we hold about you, we do not tell you who reported you. A photo or video our staff remove after a report is kept for their review, but neither of you can open it in the app again.
  • Keeping the platform safe and preventing fraud. Our legal basis: legitimate interest in protecting customers, operators and the business.
  • Meeting our other legal and regulatory duties. Our legal basis: legal obligation.

Where we rely on legitimate interests, we have considered whether our reasons are outweighed by your interests and rights. You can ask us for that assessment, and you can object: see section 13.

4. Your location: exactly what we do.

Read this section even if you read nothing else. This is the most detailed information we hold about you, and we would rather you understood it than discovered it.

4.1 When we collect it.

We collect your location whenever you are online in the operator app, whether or not you are on a job. We do this because requests are sent by distance and driving time: when a customer asks for help, we look for the operators who can reach them. If we did not know where you were while you were available, we could not send you requests. On an iPhone the app asks for permission to use your location in the background (Always), meaning while the app is not open on your screen, and the phone shows its blue location indicator while it does; we ask for this and not the lesser permission because a request can arrive while your phone is in your pocket and you are driving. On Android the app asks only for permission while it is in use, and keeps sharing your location while you are online or on a job, even with the screen off, with a notification that says "Recovru is sharing your location" for as long as it does. Going offline stops it.

4.2 How precise it is, and what we keep.

It is precise. Your position updates as you move, roughly every ten to twenty metres of travel, at the highest accuracy your device provides.

  • While you are online and not on a job, we keep only your latest position. Each update replaces the one before, and we do not keep a history of where you have been.
  • While you are on a job, we also keep the route you actually drove, a point roughly every ten seconds with its time, direction and speed, because that record is what proves you attended, what shows whether you arrived within your band, and what calculates a cancellation fee fairly if a customer cancels while you are on your way. While you are on a job the customer also sees the route you are following, and it is deleted from the live tracking record when the job ends.

4.3 When we stop.

We stop when you go offline. Going offline in the app stops us collecting your position for requests. You can also switch the permission off entirely in your phone settings at any time, but you will not receive requests while it is off, because we will not know whether you can reach a customer. When you go offline, we delete your last position, and the map grid areas noted with it, straight away. If your app sends us no position for 30 minutes, we delete the last one within the next 5 minutes, even if you are still online. The one exception is while you are on a job: then your position stays until the job ends, because the customer is following you, and it goes within 5 minutes after that if you are offline. Your route is kept as section 4.2 says.

Separately, only if you switch on Share live location in the Privacy screen, which is off unless you do, then whether you are online or not, while the app is open on your screen, the app sends us your position about every 45 seconds, and our staff can see it beside your name and email address, so they can see who is using Recovru and where. Your consent, given by switching it on, is what allows us to do this. We keep only the latest, each one replacing the last, and a daily clear-out deletes it once it is more than 24 hours old. Switching Share live location off stops it and deletes it straight away.

4.4 Who sees it.

  • Our system for matching requests to operators. What it sees: your position, to work out which requests are near you and how long you would take to get there. When: while you are online.
  • Customers who receive your quote. What they see: your distance from them and your arrival band. When: while your quote is live.
  • The customer on your job. What they see: your position on a map, and your estimated arrival time. When: from the moment they accept your quote until the job ends. They are told when you are about a mile away.
  • Other customers. What they see: nothing of where you are. Customers who have not received your quote do not see your position on a map.
  • Our staff. What they see: your position while you are on a job, on our live operations board; your route on a specific job, when investigating a dispute, a complaint, a performance review or a safety issue; and, only if you switch on Share live location, the latest position it shares (section 4.3). When: the board while the job is under way; the job record only when there is a reason; the shared position while you share it.
  • Other operators. What they see: nothing at all. When: never.
  • Outside services. What they receive: to work out driving times, our servers use our own routing server and, once we switch it on, send map points, with no name or account attached, to Google for driving times with live traffic; to show you speed limits during navigation, they send a point rounded to about 55 metres to a speed limit service; and your maps and routes come from Google Maps. While you navigate, Google's navigation software on your phone also receives your location, destination and route, as a controller in its own right under Google's terms for that service. Section 11 names each one.

5. How requests reach you, and how quotes are ranked.

We are required to explain how we decide which operators are sent which requests, and we would want to anyway. When a customer asks for help, we send the request first to qualifying operators within 5 miles and 15 minutes' drive. If nobody has quoted within 45 seconds, we widen to 10 miles and 25 minutes, then 15 miles and 35 minutes, then 20 miles and 45 minutes, then 25 miles and 45 minutes, each 45 seconds after the last. Within each ring the request goes to every operator who qualifies, not just the closest one.

What decides whether you qualify: whether you are online at that moment, with a position from the last 15 minutes; whether your driving time to the customer, from our own routing server (or, if it cannot answer, an estimate from the distance in a straight line) or, once we switch it on, from Google with live traffic, is within that ring's limit, and never more than 45 minutes; whether your vehicle and verified capabilities suit the job; whether your verification, right to work check, insurance and membership are current; whether you are suspended; and whether you are already on another job. Your rating does not decide whether you are sent a request. For a booking by an organisation, such as a company, a council, an emergency service or a police force, the request also goes only to operators who meet that organisation's own requirements, for example a level of insurance, a PAS 43 certificate, vetting, or being on its approved list. And you cannot send a quote until your VAT position has been checked or you have told us in the app that you are not registered. Once our updated matching is in use, we also record, with each request we send you, a score made from your driving time, your distance, how recent your position is and whether you offer the service asked for, with the reasons. It is a record for our staff, so that they can see how a request was matched: it does not decide whether you are sent the request, or when. Declining, not quoting and your rating are never part of it.

How quotes are shown. A customer sees up to five live quotes at a time, ordered by a score made up of your arrival band, your price compared with the lowest quote, your rating, your completion record, your distance and whether you are verified for the work, less any ranking reduction our staff have applied with written reasons. That ordering is automatic, it uses the same factors for every operator, and it does not decide anything about you: the customer chooses. The Operator Terms, section 7, give the exact weight of each factor.

Declining a request carries no penalty. You can decline any request, or let it pass, for any reason. We record that you did, because we need to know whether requests are being answered, but it does not reduce the requests you are sent, does not affect your ranking and does not affect your rating. The customer whose job you take does see the share of the requests sent to you that you accepted rather than declined or let pass (section 8).

6. Your rating, and what it is used for.

After a job, a customer may rate you from one to five stars and award compliments. Your rating is the average of those, alongside the number of ratings you have received and the number of jobs you have completed. Until you have your first rating, customers see that you are a verified operator rather than a score, and your profile carries a "New operator" label. We do not invent a starting rating to show customers. A "Well rated" label is shown beside your quotes when your average is 4.7 or more across at least 5 ratings. Your rating is one of the factors in the order customers see quotes in (section 5), and our staff may look at it in a performance review (section 7). Ratings are visible to customers, to you, and to our staff. Individual ratings are not shown to you attached to a named customer. A customer may also write a short review (up to 500 characters). Written reviews are seen by the customer who wrote them and by our staff, who may hide one with a written reason, and are not shown to other customers or to you.

7. Decisions about you are made by people.

No automated suspension, removal or penalty. A person, not software, decides whether to warn you, reduce your ranking, suspend you or remove you. Our staff review cancellations after a customer has accepted your quote, arriving after your band without a recorded reason, not turning up, complaints, disputes and conduct, by hand. After looking at the facts and hearing from you, a reviewer may take no action, warn you, reduce your ranking, suspend you or remove you. If they do anything other than take no action, you will be given the reasons in writing, as section 15 of the Operator Terms requires, and you can challenge it through our operator complaints process.

When we ask you to confirm it is you is chosen partly at random and partly from the signals in section 9.2: a new phone, another country, a recent change of details, a recent check that did not match, your number of jobs, time away and the number of phones used. That is profiling. It only decides when we ask; it never refuses you or suspends you, and never takes you offline during a job. A check that does not match twice, a name that differs from your document, and a possible screening match are each decided by a person, and you can tell them your side.

Some things do happen automatically: matching you to nearby requests, ordering the quotes a customer sees using the same factors for everyone, calculating a cancellation fee from the distance you actually travelled and the time since you set off, an organisation's requests reaching only the operators who meet its requirements, and flagging unusual activity for a person to look at. Some of them stop you working for a while, and those are automated decisions about you: no longer sending you requests for a service while a document it needs is missing, declined, expired or withdrawn, or shows cover below a statutory minimum or the relevant organisation's required limit or cover that has not started, while a declaration or approval it needs is not in place, while your permission to work or your membership has lapsed, or while a right to work result that a registered provider changed after our approval waits for a person to read it (section 9.1); rejecting a VAT number HMRC does not confirm as yours, and no longer letting you quote while your VAT number is being checked or has failed its check (section 3); stopping you going online while a company plan that pays for your membership has lapsed; stopping you going online while a possible match in the sanctions and politically exposed person screening waits for a member of our staff to review it (sections 8 and 9); and, once the face check is switched on, not taking you online until you take a check you were asked for when you signed in, came back to the app or went online, and taking you offline when you did not take one asked for between jobs within 15 minutes and are not on a job (section 9.2). None of those ends your account, and each lasts only until the document, declaration, approval, number, plan or requirement is put right, the match is reviewed, or the check is taken. For each one, we tell you why it happened; you can tell us what you think; and you can ask a person to review it and change it if it was wrong, at any time, at support@recovru.com or privacy@recovru.com. If any calculation affecting your money looks wrong to you, ask us and a person will review it.

7.1 Your performance information: what we keep, why, and for how long.

What we keep. How long you take to respond to requests and to quote; requests you were sent and did not answer; how often you quote and how often your quotes are accepted; cancellations after a customer accepted your quote; jobs you recorded you could not complete; how your actual arrival compares with the band on your quote; completed jobs, ratings, complaints and disputes; and every decision our staff make about your performance, with their reasons and the evidence they relied on.

Why we keep it. To show you your own figures in the app. To order the quotes customers see, which uses your rating and completion record (section 5). To let our staff review cancellations and poor service fairly and consistently, with evidence rather than impressions. To understand whether requests are reaching enough operators, and to improve how requests are matched to operators.

What allows us to. Our legitimate interests in giving customers reliable help and in treating operators fairly and consistently, and performance of our contract with you, because the Operator Terms describe the review. We have weighed those interests against yours: requests you did not answer never affect your ranking or the requests you are sent, no decision to suspend, remove or penalise you is taken by software, apart from the automatic stops in section 7, which a person reviews if you ask, you can see your own figures, and you are told the reasons for any action and can challenge it. You can ask us for that assessment, and you can object (section 13).

How long we keep it. The figures themselves: each record of a request, an answer, a quote or an arrival for 6 years from the event, or for 12 months after our staff remove you from Recovru if that is sooner, and then they are deleted. A staff decision about your performance, with its reasons and the evidence it relied on: 6 years from the decision, because it may have to be shown if it is challenged or a claim is made.

Who sees it. You, and our staff. Customers see your rating, your number of ratings and completed jobs, and any "Well rated" or "New" label. The customer whose job you take also sees your compliments and the share of the requests sent to you that you accepted (section 8).

8. Who we share your information with.

  • Customers who receive your quote. What they get: your business name, photograph or logo, that you are verified, your rating and number of ratings, your capabilities, your distance, your arrival band, your price and anything you said your quote does not cover, and, before they accept it, whether you are a sole trader, a partnership or a company, your legal name, your trading name, your business address, your registered office if you are a company, your business email if you give us one, your company number if you are a company, and your VAT number if you are VAT registered. Why: so they can choose, and because the law requires a customer to know who the trader is, and where to find them, before the contract is made.
  • The customer on your job. What they get: in addition, your name, your vehicle, its number plate and your live position, the number of jobs you have completed, the compliments customers have given you, the share of the requests sent to you that you accepted, for a garage or workshop its address and opening hours, and the invoice, receipt and any credit note we issue to them in your name. Why: so they know who is coming, can see you approaching, and have a valid invoice.
  • People a customer chooses to share the trip with. What they get: your first name, your vehicle's make, model, colour and number plate, and, only while you are on your way to the customer, where you are and when you should arrive. Never your full name, your business details or anything about money. Why: so that someone the customer trusts can see that help is coming. The link stops working when the customer stops it, soon after the job ends, or 12 hours after it was made. Members of the customer's Family plan see the same about a rescue of a vehicle shared with them.
  • An operator company whose membership you join (Operator Terms, section 6). What it gets: your name and email, whether you joined or said no, that you are on its membership and whether it is active, and, for each job you do as the company, the invoice issued in its name, the price, our fee and the VAT on it, the payout and how the job ended. It never sees your live location or route, your messages or calls, the jobs you do as yourself or your earnings from them, your own membership or payments, or your identity and verification documents. Why: the company is the supplier on the jobs you do as it, and pays for your membership.
  • Apple or Google, if you take out your membership in the app. What they get from us: only a random number that stands for your Recovru account, never your name or email address. They sell the membership to you and take the payment, as controllers in their own right under their own privacy policies, and tell us which membership you have and whether it is paid. Why: so the membership works wherever you sign in.
  • Didit, our identity verification provider. What they get: section 9. Why: to verify you.
  • TrustID, our right to work checking service, only if you choose its check once we switch it on. What they get: section 9.1. Why: to check your right to work.
  • TrustID and its partner LexisNexis Risk Solutions, for screening, only when your identity or right to work is checked through TrustID. What they get: your name, date of birth, nationality and address. Why: to screen you against sanctions and politically exposed person lists (section 3). Otherwise Didit screens names against sanctions and politically exposed person lists, using your name, date of birth and nationality, as part of your identity check (section 9); we do not ask it for adverse media checks or ongoing monitoring.
  • The Home Office's Employer Checking Service, only if an application of yours is still with the Home Office. What they get: the details it asks for, such as your name, date of birth, nationality and the reference of your application. Why: to confirm your right to work.
  • An organisation whose booking you take (a company, a council, an emergency service, a police force). What it gets: the invoice and any credit note we issue in your name, with your business details; the member who booked sees what any customer on your job sees; and on a police booking, the handover record you make. It never sees your live location after the job, your messages or calls, or your identity and verification documents. Why: it is the customer and it pays for the job.
  • Stripe. What they get: the details needed to pay you, to take your membership payment and to check your VAT number with HMRC, and the VAT number itself, which we save on your Stripe customer record. Stripe also checks your identity and business for your payout account as a controller in its own right, under its own privacy policy. Why: to pay you, and so that VAT is charged on your quotes only once your number is checked.
  • The companies that host and run Recovru for us. What they get: only what is needed to run the service, on our instructions. Section 11 names each one.
  • HMRC. What they get: your VAT number, so that it can be checked, with our own VAT number as the requester so that HMRC gives us proof that the check was made, where HMRC has approved our software; and what the law requires, including any report under the digital platform rules in section 3. Why: legal obligation.
  • Our VAT return. What it involves: we email our quarterly VAT report through Brevo to our own finance inbox, which we run under our Webmasters LDN name (another trading name of Dapper Trading Ltd): the figures for our VAT return and a list of our own sales, which names who each one was sold to (for our fee and your membership, that is you or your business), with the job, the amounts and the tax rule that applied. Why: legal obligation for our tax returns.
  • The Home Office. What they get: information about your right to work, and that of anyone you send, and the information about the chain of engagement described in section 5.1 of the Operator Terms, where the law requires it or in an investigation. We will tell you when we have passed something on, unless the law stops us. Why: legal obligation.
  • Insurers, auditors and our professional advisers. What they get: information relevant to a specific claim, dispute, audit or advice. Why: only where there is a claim, dispute, audit or legal need.
  • The police, the courts, or a regulator. What they get: information they are entitled to require. Why: where we are legally obliged, or where someone's safety is at risk.
  • A buyer of our business. What they get: your account and records, if Recovru is sold or merged, on the same terms as this notice. We will tell you first.

We never sell your personal information, and we never share it with other operators.

Verifying who you are involves your identity document and a photograph and short video of your face. Comparing your face to your document creates biometric information, which the law treats as a special category needing your explicit consent. We ask for that consent before the check begins, and you can refuse. If you would rather your face was not compared by software, tell us before you start: on the consent screen, choose Ask for a check without face matching; later, in the app under Account, Privacy, Ask for an identity check without face matching; or email support@recovru.com. A member of our staff will check your original identity document with you in person or on a live video call instead. We are required to know who is being sent to a customer, often alone, often at night, and we will not send someone we have not verified, but we will not make software face matching the only way through.

  • Who performs it: Didit Identity Spain, S.L., Calle Nápoles 227, 08013 Barcelona, Spain, as our processor and on our instructions.
  • What they receive: your identity document, a photograph and short video of your face, and the details you enter. The new verification flow uses Didit only for identity, liveness and name screening. Insurance certificates and right to work evidence, including a share code, go directly to our staff, and Didit is not asked to read them. Until our identity-only set-up at Didit is in place, Didit's older check may still ask for the share code or employers' liability certificate and pass them to us. Didit also screens your name, date of birth and nationality against sanctions and politically exposed person lists, unless TrustID does (section 8), and a possible match stops your verification counting until a member of our staff has reviewed it (section 7). Your other insurance certificates, licences and documents come straight to us, and a member of our staff reads every document, wherever it came from.
  • What we receive and keep: all of it. The images and the video are copied into our own private storage when the check finishes, because the links Didit gives us stop working after sixty minutes, and a reviewer opening your file the next day would otherwise see nothing. A file with no evidence in it is a rubber stamp, and we are not willing to approve people that way.
  • Who looks at it: a named member of Recovru staff, and only through an internal console that logs who opened your file and when. The images are never on a permanent link: each time a page is opened it requests links that stop working five minutes later, so nothing can be forwarded or pasted somewhere it outlives the review.
  • What no machine decides: whether you can work. Didit returning "approved" is its opinion. A person reads the evidence and clears you service by service, and if they refuse something they have to write why, in words meant for you, and you can send that one document again without repeating the rest.
  • Your name: we compare the name on your account with the name on your identity document. Forms of the same name count as the same, for example initials, a familiar form of your first name, your middle names, a title, or the machine-readable line of a passport. Any other difference is checked by a person before your identity check counts; it is never refused automatically. If you change the name on your account later, we compare it again, and a difference goes to a person.
  • How long we keep it: the photograph and video of your face, and the images of the face on your document, 12 months after the check; your document images while you work through Recovru and for 2 years after you stop or delete your account, the same as right to work evidence, so that we can show who we checked if a question about a job you did comes up. When those periods end the links to them are removed automatically. Removing the files themselves from our storage provider is not yet automatic: until it is, ask us at privacy@recovru.com and we will delete them by hand. If you want them deleted sooner, withdraw your consent (below) or ask us. We keep the record that a check happened, and who decided what, for 6 years after you stop working through Recovru.
  • Where it is processed: by Didit in the European Economic Area, and stored by us with Supabase in Frankfurt, Germany (section 11).
  • No other use: Didit acts only as our processor, on our instructions, and we do not allow it to use your images, your biometric data or anything else from your check for any purpose of its own, such as improving or training its systems.
  • Withdrawing consent: in the app, choose Account, Privacy, Withdraw face check consent, or tell us at privacy@recovru.com. We arrange removal of the face and liveness captures we hold and ask Didit to delete its copy, normally within one month. The removal process queues and retries both requests. A queued request is not confirmation of deletion: ask us, in live chat or at privacy@recovru.com, and we will tell you whether removal has been confirmed. We keep the record that a check was completed and who approved it, because we have to be able to show why we let somebody onto the road. You can then be verified in person instead.
  • Assessment: because this involves biometric data we have written a data protection impact assessment for this processing, as Article 35 UK GDPR requires, and it has not yet been signed off. You can ask for a summary of it at privacy@recovru.com.

9.1 Your right to work check: the routes.

From 1 October 2026 the law treats a service like Recovru as employing the person who personally does the work it matches, for the purposes of the illegal working rules, so we must check the right to work of every person who works through Recovru before they do any work, whether they are an operator or someone an operator sends. It is done in one of these ways, which are the ways the Home Office recognises, and a member of our staff, named on the record, carries it out.

If you have a share code. You generate the nine-character code free at gov.uk/prove-right-to-work and give it to us with your date of birth. A member of our staff enters it in the Home Office's online right to work service and reads the result, which shows your photograph and what you are permitted to do. We keep a copy of that result and the date it was checked. We do not receive your immigration history, your visa or any Home Office file: only that result.

With your original documents. A member of our staff checks your original documents from the Home Office's lists, which we must have in our hands, while you are with us in person or on a live video call, confirms the photographs are you, takes a copy and records the date. You may post the documents to us by tracked delivery, and we return them the same way. If you do not have documents on those lists, you use a share code.

If an application of yours is still with the Home Office. A person with an outstanding application, appeal or administrative review, an Application Registration Card or a non-digital Certificate of Application cannot show their right to work online. A member of our staff asks the Home Office's Employer Checking Service, giving it the details it asks for, such as your name, date of birth and the reference of your application. If it confirms, it sends a Positive Verification Notice, which gives us a statutory excuse for six months from its date. We keep the notice, its reference and its date, and we check again before the six months end.

A registered right to work digital verification service provider. The law also allows a registered right to work digital verification service provider (a provider registered on the government's digital verification services register to carry out right to work checks) to check a British or Irish passport or an Irish passport card. Ours is TrustID Limited, which is on that register (trust mark 020101) and makes the check on our instructions, as our processor. This route is switched off at the moment: we will tell you in the app when it opens, and until then those documents are checked as original documents, as above. When it is on and you choose it, you photograph your passport or card on your phone and take a short video and photograph of your face, and TrustID receives them with your name and email address. TrustID checks that the document is genuine, checks your details against a police database of known false identities, compares your face with the photograph on the document, and sends us its report. A member of our staff reads the report, confirms that the person TrustID checked is the person whose identity we verified, and decides: TrustID does not decide whether you can work. Comparing your face with the photograph creates biometric information, so we ask for your explicit consent first, on its own screen. You can say no without any disadvantage, and have your original documents checked by a member of our staff instead. If your document turns out to be forged or stolen, TrustID's terms let it keep that and share it with the police and regulators, and its terms also let it use checks to train its own staff. TrustID keeps its copy for no more than 31 days. We keep its report, the image of your document and both facial images, of your face and of the photograph on the document, as the law requires (below). If TrustID changes its result after we have approved your check, the approval stops counting, and you cannot receive requests, until a member of our staff has read the new result (Operator Terms, section 5.1).

If your permission has an end date, we check again before it runs out. If it lapses you stop receiving requests until it is checked again, and we will tell you before that happens rather than after.

What allows us to. Legal obligation. Where the check reveals special category information, such as your nationality or ethnic origin shown on a document, the condition we rely on is paragraph 1 of Schedule 1 to the Data Protection Act 2018, and we are adopting the appropriate policy document that paragraph requires. For TrustID's comparison of your face with the photograph on your document, the condition we rely on is your explicit consent, which you can withdraw at privacy@recovru.com; withdrawing does not undo a check already made, and we still keep what the law requires.

How long we keep the evidence. While you work through Recovru and for 2 years after you stop, as the Home Office expects, and then it is deleted. That includes TrustID's report and the images it compared. We keep the record that a check was done, when and by whom, for 6 years after you stop.

What we do not do with it. Your nationality and your route through this check play no part in which requests you are sent, how your quotes are ranked, what you are paid, or your rating. Section 5 sets out what matching requests to operators actually uses, and this is not in it.

9.2 Confirming it is you, and the face check.

Section 5.2 of the Operator Terms says when the app may ask you to confirm it is you: once the face check is on, on some days, chosen at random for you, before you first go online that day (your first day always asks, and never more than 3 days apart); when you sign in, come back to the app or go online, and between jobs, never during a job; always when something has changed; and otherwise at random, at most 3 times a day and 4 hours apart. Which days ask is drawn for you from your account and the date by our own system, not by a person.

The face check is switched off at the moment. Until it is on, each check we ask for is a short video call with a member of our staff, who compares you with your identity evidence and records the result; it never stops you working. We will give you at least 15 days' notice before we switch the face check on.

When it is on: Didit takes a short video of your face, checks it is a live person and compares it with the identity already held: your identity document, or, if your identity or right to work was checked through TrustID, TrustID's live photograph of you from that check. Because that is biometric, it needs your explicit consent, which we ask for once, separately, before your first face check, and you can withdraw it at any time, in the app under Account, Privacy, Withdraw face check consent, or at privacy@recovru.com. If you do not consent, choose Ask for a check without face matching on the consent screen, or ask us: a member of our staff calls you on video instead, and that call never stops you working and has no deadline.

No image from a face check is copied into our storage. For each check we ask for we keep what prompted it, the signals used and the chance it was asked, whether and when it was taken and passed, a one-way hash of the phone and the country of the connection, and we delete that record after 12 months. For a face check we also keep the liveness score and the match score, and we delete them after 90 days. Either is kept longer only while an investigation about you is still open. If a face check does not match twice, a person reviews it; it does not lock you out on its own.

9.3 DBS certificates and organisation vetting.

We do not require a basic DBS certificate merely because you provide locksmith or another ordinary service. We do not ask for an unrelated criminal record. For work under a named organisation's agreement, that organisation may require lawful vetting appropriate to the role. For police vetting we record the level, reference, scope and dates the force confirms, rather than asking you to upload the force's underlying criminal information. Expressing interest in police, ambulance or council work is not a vetting result or approval.

A DBS certificate previously supplied is criminal offence data. Where we hold one on the basis of consent, we record that consent and the applicable condition under paragraph 29 of Schedule 1 to the Data Protection Act 2018. You may withdraw it at privacy@recovru.com and ask us to remove the certificate. Withdrawing an optional certificate does not itself remove your ordinary service clearance. If a named organisation requires lawful evidence for its own work, we explain that separate requirement before collecting it and identify the legal basis and condition that permits us to use it; we do not treat agreeing to these terms as blanket consent.

Only staff whose role permits reviewing this evidence can open it, and the access is recorded. We keep an existing certificate no longer than 12 months after our decision, or until a replacement supersedes it sooner. We keep the decision, reference and date for 6 years after you stop working through Recovru where needed to evidence that decision. A conviction does not by itself end your account: any relevant decision is made by a person with reasons and a route to challenge it.

9.4 The agreements you sign with us.

The Operator Agreement. We may ask you to sign the Operator Agreement, which records that your business has agreed to the Operator Terms and who signed for it (Operator Terms, section 5.3). You can read the form at recovru.com/legal/operator-agreement. When you ask for it in the app, we email a signing link to the address on your account from documents@recovru.com, through Brevo (section 8), and it is signed in WM HQ, our operations system (section 10). When you, or the person signing for your business, signs, we record: the signature drawn or typed; the name, capacity and details entered in the agreement's Schedule (the business's legal form, legal name, trading name, company or LLP number and address, and the signer's contact email address, telephone number and postal address); the date and time; a one-way hash of the internet address used, which cannot be turned back into the address; the type of device and browser; whether a code we emailed was entered; and a SHA-256 fingerprint of the exact document signed. Together that is the signing certificate. We use it to make and prove the agreement and to check the signer's authority: that is necessary for the contract between us, and in our legitimate interest in being able to prove it (UK GDPR, articles 6(1)(b) and 6(1)(f)). We keep the signed agreement and its certificate for 6 years after the agreement ends, in WM HQ and in our database (section 11). If someone else signs for your business, such as a director, the email with the link points them to this notice, and it applies to their information in the same way.

Other agreements. Some services need a separate written agreement, for example an undertaking for prestige or heavy recovery work, or an agreement you ask for. When you sign one in the app we keep the agreement, the version, the time, the name you typed and your device's internet address and browser details, as the evidence that you signed it. We keep that for 6 years after the agreement ends.

Our staff may use Google's Gemini model to produce a first draft of a new agreement from their own instructions, which may include your name or business name and the service. Nothing else about you is sent, and a person reads, edits and decides on every draft before it reaches you.

10. Who inside Recovru can see your information.

Our staff use two internal consoles to run the service: our own console and WM HQ, our operations system, which is built and run by Webmasters LDN, another trading name of Dapper Trading Ltd, the company behind Recovru (section 11). Every member of staff can use them, and every member of staff is bound by confidentiality. Opening one person's account, documents or evidence needs a case or an investigation (which senior staff open automatically) and is logged against the member of staff who did it. Lists and dashboards, such as who is online, show names, the position of operators on a job and, for anyone who has switched on Share live location, the latest position it shares, and opening them leaves no log entry.

  • They can see your account, business details and verification status, to approve you, support you and answer your questions, including in live chat.
  • They can see the evidence behind your verification, meaning the images of your identity document, the photograph and video of your face, your right to work evidence, your DBS certificate if you gave one, and your insurance and other documents, in order to decide whether to clear you. That is the whole point of the check being made by a person: nobody can approve you without looking. The images are reached only through links that stop working after five minutes, every file that is opened is recorded against the member of staff who opened it, and looking at a record you have no business reason to see is a disciplinary matter.
  • They can see your quotes, jobs and performance information, and your position and route on a specific job, to review your performance, investigate a dispute, a complaint or a safety concern, or answer a question you have asked.
  • They can see your ratings and job history, to handle a complaint about a job.
  • They can see your payouts, statements and membership payments, to resolve a payment query.
  • They can see messages sent on a job, only when investigating a specific dispute or safety issue.

A named operator's route on a job is opened in connection with a specific job or problem, and that opening is recorded. Opening the dashboards in this section is not recorded, so we cannot show you a record of who looked at them, which is one reason Share live location is off unless you switch it on.

11. Where your information is held.

Some of the companies that help us run Recovru are outside the United Kingdom. Where information leaves the UK, we rely on a UK adequacy decision for that country, the UK Extension to the EU-US Data Privacy Framework for a certified US company, or the Standard Contractual Clauses with the UK Addendum approved by the Information Commissioner, as named below.

  • Database, sign-in, file storage and servers, including your documents and verification evidence. Who: Supabase, Inc. Where: stored in Frankfurt, Germany; Supabase is established in the United States and can reach it from there. Safeguard: the Standard Contractual Clauses with the UK Addendum, in Supabase's data processing agreement.
  • Identity and business verification, liveness and face matching, and sanctions screening. Who: Didit Identity Spain, S.L., Barcelona. Where: the European Economic Area. Safeguard: UK adequacy regulations for the EEA.
  • Right to work checks of a British or Irish passport or an Irish passport card, and the sanctions and politically exposed person screening that comes with a TrustID check, only once we switch that route on and you choose it. Who: TrustID Limited, a registered right to work digital verification service provider, as our processor. What: section 9.1. Where: stored in the United Kingdom, with some processing in European Economic Area countries; TrustID's own supplier, LexisNexis Risk Solutions, keeps screening data for 6 years and may transfer data to the United States in exceptional cases. Safeguard: UK adequacy regulations for the EEA, and the UK Extension to the EU-US Data Privacy Framework for a transfer to the United States.
  • Payouts, membership payments, your payout account, and the check of your VAT number with HMRC. Who: Stripe, which makes that check with HMRC for us, and, where HMRC has approved our software, HMRC directly. Where: the UK, Europe and the United States; HMRC's service is in the United Kingdom. Safeguard: Stripe relies on the UK Extension to the EU-US Data Privacy Framework, with the UK International Data Transfer Addendum behind it.
  • Push notifications. Who: Google (Firebase Cloud Messaging). What: your notification token and the text of each notification, such as a request, a customer's name or the start of a message. On an iPhone, Google passes each notification to Apple's push service to deliver, and in a web browser to that browser's push service. Where: Google's infrastructure, including the United States. Safeguard: Google's Firebase data processing terms, and Google LLC's certification under the UK Extension to the EU-US Data Privacy Framework.
  • Ringing an iPhone for an in-app call. Who: Apple, directly from our servers, where we have switched this on. What: your call-ringing token and, for each call, the caller's name and role and the label of the job. Where: Apple's infrastructure, including the United States. Safeguard: Apple is a controller in its own right for its push service, under its own privacy policy.
  • Crash reporting and marketing analytics, only if you switch them on. Who: Google (Firebase Crashlytics and Google Analytics for Firebase). Where and safeguard: as for push notifications.
  • Maps, navigation, address search, routes and arrival times. Who: Google (Google Maps Platform). What: your device's internet address and the map area on screen; while you navigate on your phone, Google's navigation software on your phone uses your location, your destination and your route, and exchanges them with Google, including while the app is in the background; and from our servers, every few seconds while you are on a job, your position to snap it to the road, and the map points and addresses needed for routes. Where: Google's infrastructure, including the United States. Safeguard: Google acts as a controller in its own right under the Google Maps Platform controller data protection terms, and Google LLC is certified under the UK Extension to the EU-US Data Privacy Framework.
  • Driving times for matching requests. Who: our own routing server, which runs the open-source OSRM software on the server in Manchester, England, that Hostinger provides (hosting, below); and, once we switch it on, Google (the Routes API), for driving times with live traffic. What: map points only, the positions of the operators being considered and the customer's, with no name, account or job reference. Where: the United Kingdom; for Google, Google's infrastructure, including the United States. Safeguard: for our own server, as for hosting; for Google, as for maps, above.
  • Speed limits during navigation. Who: public OpenStreetMap Overpass servers, run by independent organisations in Germany and elsewhere, some outside the UK and Europe. What: a point on the road rounded to about 55 metres, sent by our servers with no name, account or job reference. Safeguard: there is no contract with these services, so we limit what they receive to a rounded map point.
  • Email. Who: Sendinblue SAS, trading as Brevo (France). What: your name, email address and the content of each email, including invoices, statements and receipts. Where: servers in the European Union. Safeguard: UK adequacy regulations for the EU; we are obtaining written confirmation of the safeguard Brevo relies on where its own suppliers can reach data from outside the UK and Europe.
  • Telling our staff when you report a problem, make a complaint or raise a dispute. Who: Slack Technologies, LLC (part of Salesforce). What: the kind of report, its subject and what you wrote, your email address, and short references to the report and the job. Where: Slack's infrastructure, including the United States. Safeguard: Slack's data processing terms; we are obtaining written confirmation of the transfer safeguard it relies on.
  • Hosting app.recovru.com and WM HQ. Who: Hostinger International Ltd, on a server it provides to us in Manchester, England. What: internet addresses and browser details for the web app, and what our staff look at in WM HQ. Where: the United Kingdom. Safeguard: the server is in the UK, Hostinger is established in the European Union (Cyprus), which UK adequacy regulations cover, and its data processing terms bind it to act only on our instructions.
  • Relaying an in-app call when a direct connection will not work. Who: Cloudflare, Inc. What: both parties' internet addresses and the call's timing; it cannot decrypt the audio. Where: Cloudflare's global network. Safeguard: Cloudflare's certification under the UK Extension to the EU-US Data Privacy Framework, with the Standard Contractual Clauses in its data processing terms.
  • Hosting recovru.com and our own staff console. Who: Vercel Inc. Where: the website runs on Vercel's global network, and our own console in Frankfurt, Germany. Safeguard: Vercel's certification under the UK Extension to the EU-US Data Privacy Framework.
  • Vehicle details, MOT, tax and stolen vehicle checks. Who: OneAutoAPI, a UK vehicle data provider. What: the number plate only. Where: the United Kingdom. Safeguard: no transfer.
  • Drafting agreements, only when our staff choose to. Who: Google (Gemini). What: section 9.4. Where and safeguard: Google's infrastructure, under Google's terms for that service, and Google LLC's certification under the UK Extension to the EU-US Data Privacy Framework.
  • Selling the membership in the app, only if you take it out there. Who: Apple (the App Store) on an iPhone, or Google (Google Play) on Android. What: only a random number that stands for your Recovru account. Safeguard: they are controllers in their own right for the purchase, under their own privacy policies.
  • Signing in with Apple or Google, only if you choose to. Who: Apple or Google, as controllers in their own right.

You can ask us for a current copy of this list at any time, including the transfer safeguard we rely on for each provider.

12. How long we keep it.

  • Your account and business details: for as long as you keep your account. When you delete it, section 13 explains what goes and what stays.
  • Verification outcomes, your verified name, and the record of who approved you and why: for at least 6 years after you stop working through Recovru. The clear-out that removes the document number, date of birth, nationality, phone number, internet address and share code at that point runs automatically; we do not use a temporary suspension as the date you stopped. Why that long: a claim about a job can be brought for six years, and for that long we may have to show what we checked before sending you to a customer.
  • The photograph and video of your face, and the face images taken from your document: 12 months from the check. Why only that long: these are biometric data, and once the review is done and any challenge to it has passed there is no reason to hold them. When that period ends the links to them are removed automatically; removing the files from our storage provider is not yet automatic (section 9).
  • Images of your identity document: while you work through Recovru, and for 2 years after you stop or delete your account. Why that long: it matches how long the Home Office expects right to work evidence to be kept, and lets us show who we checked if a question about a job you did comes up. After that the record that a check was done, which we keep for 6 years, is enough, so the images go. When that period ends the links to them are removed automatically; removing the files from our storage provider is not yet automatic (section 9).
  • Insurance and other documents: 6 years after the document expires. Why that long: a claim can be brought years after the work was done.
  • Right to work evidence, including a TrustID report and the images it compared: while you work through Recovru and 2 years after you stop. Why that long, and no longer: that is what the Home Office expects, and after that keeping copies of your documents has no purpose. The record that a check was done: 6 years after you stop. TrustID's own copy of a check: no more than 31 days.
  • A DBS certificate: section 9.3.
  • Checks that it is you (section 9.2): the record of each check we ask for, and a face check's result, 12 months after it; a face check's two scores, 90 days; longer only while an investigation about you is still open.
  • Your phones' records (section 2): 12 months after a phone was last used with your account, longer only while an investigation about you is still open, and no longer than your account (section 13.1).
  • Screening results: with your verification outcomes, above. LexisNexis keeps its own copy of a TrustID screening for 6 years.
  • Your position while online and not on a job, and the map grid areas noted with it: only the latest one, replaced by each update. It is deleted when you go offline, or when your app has sent no position for 30 minutes (section 4.3).
  • Counts of operators by map area, taken every 15 minutes: they hold no names or account details, an area is counted only where there are 3 or more operators, and they are kept 400 days, to see how the need for operators changes through the year.
  • The latest position the app shares while it is open (section 4.3): replaced by each update, and deleted once it is more than 24 hours old.
  • Your route on a completed job: 90 days after the job closes. Why that long: long enough to answer a dispute about attendance, arrival time or a cancellation fee.
  • Your route on a job in dispute: until the dispute, claim or investigation ends, and then it is deleted at the next nightly clear-out. Why: it is the evidence while the matter is open.
  • Your quotes and job records: 6 years after the job. Why that long: the limitation period for a claim, and tax and accounting law. They are deleted automatically when that period ends, unless a legal hold applies. The score recorded with a request you were sent (section 5) is part of that request's record.
  • The invoices, receipts and credit notes we issue in your name, our VAT invoices to you, your statements and payout records. These are tax records. How long: until the end of the sixth year after the accounting year they fall in. Deleting them then is not yet automatic; none falls due before 2032.
  • The record of each time a member of our staff opens one of your documents: 6 years from when it was opened. Why that long: it is how we can show who looked at your documents, and why, for as long as a claim can be brought.
  • Your performance figures: each record for 6 years from the event, or 12 months after our staff remove you from Recovru if that is sooner. A staff decision about your performance, with its reasons and evidence: 6 years from the decision. Section 7.1 explains why.
  • The company authority check and any letter of authority: 6 years after the check and 6 years after you stop working through Recovru, except that a check which no decision rests on goes 12 months after a newer check replaces it, and a letter nobody relied on goes after 90 days. Why that long: the same six-year claim period.
  • Your VAT checks and the history of your VAT status: 6 years after the job or check they relate to. Why that long: tax records. We intend to delete them then, but the clear-out that will do that is not built yet.
  • A police booking's details: 90 days after the handover. The log of who opened them: 12 months after that.
  • An organisation's approval of you, with any vetting level, reference and expiry: until the approval ends or you ask us to remove it, and then 12 months.
  • Which screens you open, which steps you take and the notes the app makes when it hits an error: 12 months. The record of sign-in attempts: 30 days.
  • Hazards you report or vote on: 12 months after the hazard expires.
  • Messages about your account and notices of changes to terms: read messages 12 months, everything 6 years. Reminders that a document is running out: 13 months after the date they were about. The record of the terms and fees you accepted is further down this list.
  • The record of each time our staff open your account, documents or evidence, and of what they change: we do not delete it at the moment, because it is how we can show who looked at your information and why; we are setting a period, and will put it here.
  • Agreements you sign with us: 6 years after the agreement ends, and deleted automatically then. A recorded end date is needed; where it is missing we keep the record until it is established.
  • Your membership's record: which membership, who billed it, its dates, payments and refunds: 6 years after it ends. Why that long: they are purchase records, and settle any question about a payment.
  • Messages and in-app call records on a job: 90 days after the job closes, or until a dispute about it ends if that is later. Why that long: support and disputes. A photo or video our staff removed after a report is deleted with the rest of the chat.
  • Reports about messages, with the copy of what was reported: until the case they opened is closed and any complaint or claim that could rest on them has ended, and never more than 6 years after the case closes.
  • Blocks: until the block is lifted, or either of you deletes your account.
  • Live chat with our staff: 12 months from your last message, or 6 years where it concerns a payment, a dispute, a complaint or a decision about you. Why that long: to help you if you come back to us, and because a conversation about money or a decision is evidence for as long as a claim can be brought.
  • Your ratings and any written review: while you are an operator, and they are deleted when your account is deleted.
  • Records of what you accepted, the terms and fees among them: 6 years after your account closes, and deleted automatically then. The settings you chose on the Privacy screen are deleted with your account.
  • Information we need for an open dispute, chargeback, investigation, legal claim, or request from the Home Office, HMRC, the police or a regulator: until it is resolved, even if a period above has passed.

Where a period above ends for a document, a photograph or another file, the current clear-out removes it from our records and every link to it. Removing the file itself from our storage provider's private store is not yet automatic: until it is, ask us at privacy@recovru.com and we will delete it by hand. An open legal hold prevents removal. Where something is held in a backup, it is kept beyond use until that backup expires in the normal cycle, and it is not restored back into the live service except to recover from a failure, in which case we delete again anything that had already been deleted.

13. Your rights, and deleting your account.

  • Ask what we hold: we will give you a copy, normally within one month. Your quotes, jobs, payouts and performance figures are also in the app, and Access your data gives you a copy straight away, including the people you blocked and the reports you made. Reports customers made about you are held back, as complaints made by others are, and our staff send you what can be shared.
  • Ask us to correct it: if something is wrong, including something in your performance record, tell us and we will fix it.
  • Ask us to delete it: section 13.1 below.
  • Object to how we use it: particularly where we rely on legitimate interests, including your performance record. Tell us why and we will stop unless we have compelling grounds not to.
  • Ask us to restrict use: while a dispute about accuracy or our reasons is resolved.
  • Ask for it in portable form: for information you gave us, in a machine-readable file.
  • Withdraw your consent: for the biometric part of your identity check, for the face check, for TrustID's face comparison, for a DBS certificate you chose to give us, and for anything else we asked your consent for. It is free, and it takes effect immediately going forward. It does not undo a check already completed: see section 9.
  • Complain: to us, and to the Information Commissioner (section 14).

To use any of these, contact us at privacy@recovru.com. We will not charge you and we will not treat you differently for asking. We may need to check it is really you before we act.

13.1 Deleting your account. You can delete your account in the app, by asking at www.recovru.com/delete-account, or by emailing support@recovru.com or privacy@recovru.com. You can delete it now, or ask us to hold it closed for six months first, in case of a dispute or investigation, after which it is deleted automatically. Neither is available while you have a job in progress. We also wait, and keep trying, while a job of yours is evidence in an open dispute, chargeback, complaint or investigation, while money on your jobs has not settled, or while a payout is owed to you, and we tell you the reason on screen. What goes: your sign-in, your profile, your vehicles and settings, your devices, your current position, your job routes, your face check scores, and a membership we bill through Stripe, or Google bills, is cancelled. A membership Apple bills cannot be cancelled by us: cancel it in your App Store account settings, or Apple will keep charging you. The app tells you this before you delete. If you signed in with Apple, we also tell Apple to end Recovru's access to your Apple ID. Your Stripe payout account is Stripe's own record, held under Stripe's terms. We do not close it when you delete your account, and Stripe keeps what the law requires it to keep. You can close it with Stripe once nothing is owed to you. What stays, with your name taken off where the law allows it: job, payment, invoice, receipt, credit note and statement records for 6 years, because tax and accounting law and the time limit for claims require them. What stays as it is, for a stated time and reason: your right to work evidence until 2 years after you stopped working through Recovru, and the record that it was checked for 6 years, because the law requires us to be able to show it; the verification decisions about you and any staff decision about your performance for 6 years; agreements you signed for 6 years after they end; the images of your identity document for 2 years after deletion, the same as right to work evidence; your insurance and other documents until 6 years after they expired, and no longer than 6 years after deletion; and anything needed for an open dispute, chargeback, investigation, legal claim or official request until it is resolved. If you never finished joining and do not sign in for 2 years, we treat you as having stopped, and the same periods run from your last sign-in. Backups are kept beyond use until they expire. When your account is deleted we tell you on screen if you are in the app, and you can ask us at privacy@recovru.com what we have kept and why.

If something goes wrong with your data: where a breach of security is likely to put your rights or freedoms at high risk we will tell you without undue delay, in plain words, and say what we are doing about it. Where the law requires it we also report it to the Information Commissioner within 72 hours of becoming aware. A breach involving your identity documents, your right to work evidence, a DBS certificate or the images of your face we would treat as high risk by default, and tell you, rather than assessing our way out of telling you.

14. Complaining.

Please tell us first, so we can put it right: privacy@recovru.com, live chat, or post, and say it is a data protection complaint. You can use any of these and we will treat it the same way. We acknowledge it within 30 days, and in practice within 2 working days; we look into it without undue delay, and keep you told how it is going; and we tell you what we found and what we are doing about it. If you are not satisfied you can complain to the Information Commissioner's Office at ico.org.uk/make-a-complaint, or by phone on 0303 123 1113. The Commissioner will usually expect you to have given us the chance to put it right first, but you can go to them at any time.

15. Changes.

If we change this notice we will tell you in the app and by email before the change takes effect. Before the first operators go live, a new version applies to new operators at once, and to an operator who accepted an earlier version when they accept the new one in the app. Once operators are live, we give you at least 15 days' notice of any change that materially affects you, unless a shorter period is required by law, and the version you accepted keeps applying to you until the notice has run. The version and date at the top always tell you which version applies.

Recovru is a trading name of Dapper Trading LTD, registered in England and Wales, Company No. 08800299, VAT No. 190396586. Registered office: Oak House, Reeds Crescent, Watford WD24 4QP. General enquiries: hello@recovru.com. Help with a job, a payment or your account: support@recovru.com. Our policies, or to delete your data: privacy@recovru.com.