Appearance
Privacy
This notice applies from 16 November 2026.
WOODCOMMERCE LTD (company number 17495526, 5 Brayford Square, London E1 0SG) is responsible for the personal data described here. Questions and requests: support@benchfleet.com.
The app
- Your phones' data stays on your computer. Screens, recordings, logs, files and everything the Hub learns about your phones are stored in your user folder. We never receive them.
- Local mode by default. A new installation sends nothing to the internet. Cloud AI providers, notification channels and integrations send data only after you turn them on, and the Privacy page in the app lists every destination with what it would receive and logs what was sent.
- No telemetry, no analytics, no crash uploads. Crash reports stay on your computer.
- Paid plans. When you allow account checks and sign in, the app sends your email address to sign in, then once a day this computer's installation ID with its sign-in token to fetch its licence. Nothing about your phones. You can use a licence file instead and leave account checks off.
- AI providers you choose. If you add a cloud AI provider, the data the Privacy page lists (screenshots, screen structure, your instructions) goes to that provider under your own agreement with them.
Phone Mirror (Chrome extension)
- Nothing leaves your computer. Phone Mirror shows your phone's screen and lets you control it from a Chrome tab over USB. The picture, your input, screenshots, recordings, logs, files and bug reports go only between the phone and your browser, and are saved only when you choose to save them. The extension makes no network requests: we never receive any of it.
- No accounts, no analytics, no tracking. The extension asks for no browser permissions and reads no websites.
- Stored in your browser. The key your phone trusts for USB debugging (created by the extension) is kept in the extension's own browser storage; removing the extension deletes it. Chrome remembers which USB phone you allowed, and you can remove that in Chrome's site settings.
- Bug reports. A bug report is built on your computer and copied or saved only when you click. It can contain the phone's log, so look through it before you share it; email and IP addresses are replaced unless you untick that option.
Your account
When you create an account we store your email address, the computers that use it (their installation IDs, when they were added and last checked a licence), the licences issued, and your subscription's status, with a log of what happens on the account (sign-ins, plan changes, licence files and similar steps, with their times) and when each signed-in browser was last used. Sign-in codes are stored only as one-way hashes and expire after 10 minutes. If you set a password, we store only a slow one-way hash of it (scrypt), never the password itself. If you switch on two-step sign-in, we keep the key your authenticator app shares with us, encrypted, and your recovery codes only as one-way hashes; while you type the second code, a cookie keeps that sign-in for at most 10 minutes.
Changing your email address. On your account page you can move the account to another address. We send a code to the new address, and once you type it we tell the old address, with a link that puts it back for 30 days. For those 30 days we keep both addresses and the time of the change with the account, so the link works; then that record is deleted. Stripe is given the new address for your receipts and invoices. A newsletter subscription stays with the address it was made for.
A copy of your data. "Download my data" on your account page gives you one file with everything listed in this notice that our account service keeps about your account, in a format other programs can read. It leaves out secrets (password hashes, codes and tokens) and anything about other people. Card details and invoices are with Stripe, on the page "Payment details and invoices".
Sign in with Google. Only if you click "Continue with Google", your browser goes to Google, and Google tells us your email address, whether Google has verified it, your Google Workspace domain if you have one, and a number that identifies your Google account. We keep that number with your account to recognise you next time, and nothing else from Google: no name, no picture, no contacts, and no Google tokens. Google's own privacy policy covers what Google does when you sign in there.
Emails about your account. After you create an account we send one welcome email about what the account is for. If a cloud phone of yours is running and your minutes are nearly used up, we tell you, at most once a week. If a payment for your plan does not go through, we tell you, remind you shortly before the plan would pause, and tell you if it pauses or ends, each at most once per billing period; we keep which of these we sent. We also tell you when two-step sign-in is switched on or off, or a recovery code is used. Short getting-started tips, a note about what the Free plan covers and one note if a paid plan ends are sent only if you ask for them with the switch on your account page; every one of them has a one-click unsubscribe link, and one click ends them all. These emails have no tracking pixels and no tracked links. Our software never tells us what you do with it, so these emails go by the time since you signed up, not by what you did.
This website
No advertising, and no third-party scripts other than the analytics below. Apart from the analytics, the ad landing page test and the note of which ad or link brought you, all described below, one cookie, set only when you sign in, keeps you signed in for up to 30 days; it is needed for signing in. While you sign in with Google, one more cookie lasts at most 10 minutes to check that the answer from Google belongs to your browser. Your light or dark choice is kept in your browser, and so are whether you have taken or turned off the account pages' tour and whether you were signed in on your last visit (so the top of each page can show "Account" at once); a chat question you have started but not sent is kept until you close the tab.
Affiliate links. When you arrive through an affiliate's link (an address ending in ?ref= and a code), we count the click with the code, the time and the page, and nothing about you, and ask whether to remember who sent you. Only if you say yes does a second cookie keep that affiliate's code and the time of the click, for up to 90 days, so that the affiliate is paid if you buy a plan later. If you say no or don't answer, your browser keeps the code only until you close the tab (session storage). If you sign in or buy a plan while either is set, the code is kept with your account and passed to Stripe with your subscription. You can delete the cookie in your browser at any time.
Analytics
Whether we ask first depends on where you are. To decide, the website asks our server, which looks at the country Cloudflare (our host) works out from your IP address and answers only "ask" or "don't ask"; neither the country nor the answer is stored.
Where the law asks for consent first, and whenever we cannot tell where you are, the first visit shows a small box: "Allow analytics?". These places are the European Union and the rest of the European Economic Area, the United Kingdom, Jersey, Guernsey, the Isle of Man, Gibraltar, Switzerland, Turkey, South Korea, China, Vietnam and Québec. Until you click "Allow analytics", nothing of our analytics services is loaded: no script, no cookie and no request to PostHog, Google or Microsoft. Your answer is kept in your browser (local storage), and "Privacy choices" at the bottom of every page in these places lets you change it at any time. If your browser sends Do Not Track or Global Privacy Control, we take that as no and do not ask. The box names the services this website uses.
Everywhere else, the analytics below start when a page loads. We do not respond to Do Not Track or Global Privacy Control signals in these places. If you answered the box in a place where it is shown, that answer still applies when you visit from elsewhere. You can also block analytics with your browser's settings or an extension. We never sell personal information.
While analytics run, three services receive the following. None of them is told who you are: we never send your email address, name, account, payment details or anything you type, and we set no user ID.
- PostHog, hosted in the European Union (Frankfurt), counts visits and sign-ups: the pages you view (their address without anything after
?or#) and what kind of page each is; the site that sent you (its name only) and any campaign tags in the link (such asutm_source); whether you started or finished creating an account, and how (email code, password or Google); whether you started or finished buying a plan or minutes, and which one; and what any website receives from your browser, such as its type, language, screen size, time zone and your IP address, from which PostHog works out a rough location. It also shows us how our public pages work for visitors: how long you stay on a page, how fast it loaded and answered your clicks, where on a page visitors click (and clicks that did nothing), errors in our page code, and a recording of the page's layout and of your clicks, scrolling and pointer, which we can replay. In these, every input is hidden and any text with an@is replaced before anything leaves your browser, and clicks are noted by the element, never its text. Like Clarity, PostHog never records the pages that show your account, sign-in, billing, cloud phones or minutes, a shared phone's watch page, an affiliate's dashboard, or the newsletter's confirm and unsubscribe pages: recording is stopped before you go there. Your browser keeps a random visitor ID for PostHog in local storage, no cookie. - Google Analytics receives the same page views and the same sign-up and purchase steps, with the same addresses cut short, except that a page address keeps any campaign tags and ad click ID in the link you followed (such as
utm_sourceorgclid, nothing else after?), so we can see which campaigns bring visitors, and what your browser sends to any website (as above), from which Google works out a rough location and the device type. Google Signals, advertising features and ad personalisation are off. It sets two cookies on this site,_gaand_ga_followed by our measurement ID, holding a random visitor ID, for up to two years. - Google Ads is told when a sign-up or a purchase happens, so we can see which of our Google ads lead to them. Nothing goes that says who you are. For a purchase, Google Ads also gets its amount before tax, its currency, and the random ID Stripe gave that payment page, so the same purchase is never counted twice. If you came from one of our Google ads, Google matches it to that ad click through cookies on this site (
_gcl_au, and_gcl_awafter an ad click) for up to 90 days. Remarketing and ad personalisation are off: we don't use your visit to show you ads. - Microsoft Clarity shows us how our public pages are used: where visitors click, scroll and move the pointer, and the page's layout, which Clarity can replay as a recording. Every text and every input on the page is hidden before anything leaves your browser, so a recording shows blocks, not words. Clarity never runs on the pages that show your account, billing, cloud phones or minutes, a shared phone's watch page, an affiliate's dashboard, or the newsletter's confirm and unsubscribe pages: it is not started there and is stopped when you go there. It sets two cookies on this site,
_clck(a random visitor ID, up to one year) and_clsk(your current visit, one day), and Microsoft may read its own cookies on its own domains.
Testing our ad landing page. When you arrive on one of our pages from a Google or Microsoft (Bing) search ad, in a place where the analytics above start by default, we may show you one of two versions of that page's headline and first button, to learn which helps visitors more. A cookie, bf_ab, keeps which version you saw (the test's name and the version, nothing else) for up to 180 days, so you see the same one next time, and the analytics above note the version with what they already count. The ad's campaign tags are counted as described for PostHog; the ad platforms' click IDs in the link (gclid, msclkid) are never kept or sent to our analytics. Where we ask before analytics start, you always see the usual page and no such cookie is set.
Which ad or link brought you. In the same places, when you arrive through a link with campaign tags (such as utm_source) or from a Google or Microsoft (Bing) search ad, a cookie, bf_src, keeps the first such visit's campaign tags (source, medium, campaign and search term), the page you landed on and whether the click came from Google's or Microsoft's ads, for up to 90 days. It holds nothing that identifies you and never the ad platforms' click IDs. If you buy a plan or a pack of minutes while it is set, these details are passed to Stripe with your purchase, so we can tell which ads and links lead to sales. A later visit does not replace it. You can delete it in your browser at any time; where we ask before analytics start, it is never set.
If you choose "No thanks" later, all three stop at once: PostHog's ID is deleted from your browser, Google's and Clarity's cookies on this site are deleted, and nothing more is sent. Cookies that Google or Microsoft keep on their own domains are outside this website's reach; your browser's settings can delete them.
Affiliates
When you apply to the affiliate programme we store your name, email address, website or channel, audience size and how you plan to promote BenchFleet, and later the figures for your link (clicks, sign-ups, the customers you referred by plan, and your commission and payouts). If you tell us where you heard about the programme, that answer is only in the email that tells us about your application; we don't store it. Customers you refer are never named to you.
Chat messages
When you send a question through the chat bubble on this website, we keep your email address, your message, the page you sent it from and the time, to answer you. The message is emailed to our support mailbox, and our answer comes back to you by email from a person. Nothing is mailed to you automatically, and we keep no IP address with the message. Messages are deleted 12 months after they were sent (spam after 30 days), or sooner if you ask.
Newsletter
If you sign up for the newsletter, we keep your email address, whether you have confirmed it, the page you signed up on and when, and which of two wordings of the sign-up credit the box showed you (we compare how many sign-ups, accounts and first purchases each wording leads to; nothing is stored in your browser for this). Nothing is sent to the address except one email with a confirmation link until you use that link; if you never do, the address is deleted after 7 days. Our emails have no tracking pixels and no tracked links: we do not know who opens or clicks them.
How to leave: use the one-click unsubscribe link at the bottom of any newsletter email, or your mail app's own Unsubscribe button. Your address is deleted at once. You can also write to support.
The sign-up credit: if a credit comes with your confirmation, we keep a one-way hash of your normalised address (never the address itself), the credit's amount and dates, and once you use it the account, its Stripe customer ID and a one-way hash of the card's fingerprint as Stripe reports it. We keep these after you unsubscribe and after the credit is used or ends, so that each person gets the credit only once.
Testimonials
If you send us a quote about BenchFleet from your account page, we keep it with the name, role and company you chose, your account and the plan you had then. It is shown on this website only after we approve it, exactly as you wrote it and with the name you chose, and never with your email address. You can withdraw it on the same page at any time and it is removed from the website at once; a withdrawn or rejected quote is deleted 30 days later, and all of them when you delete your account.
Cloud phones
If you rent our cloud phones:
- What we keep: each rental (when, how long, which account, what it cost), your minutes (packs, refunds, what each minute was drawn from) and your spending limit; the phone's connections to the internet (where to, when, how much, never what was sent); and, when you use a phone on the website, how many inputs you made each minute by kind (taps, key presses, characters typed, other), never what or where. If you share a phone: each watch link in a scrambled form (never the link itself), when it ends and how often it was opened, and the email addresses you invite to control it, with the rental's record.
- What we do not keep: the phone's screen, what you type on it, its apps or files. Apps and files you send to a phone from the website go to the server it runs on and onto the phone, never into our storage. The phone is deleted with everything on it when the rental ends. Your Hub's connection to a phone is encrypted end to end, so the service that rents it to you never sees your commands, workflows or secrets; the phone itself runs on our server, so what happens on it exists there while it runs.
- Why: to provide the phones and charge for them (our contract with you), and to handle abuse and meet our hosting providers' rules (our legitimate interest, and the law where it applies).
- How long: rental and connection records for 12 months; input counts for 90 days, longer only while an abuse report about the rental is open; your minutes as long as your account exists.
- Who processes it: our phone hosts run on servers we rent in Europe.
Why we use your data
- To provide your account, licences and plan: this is needed for our contract with you.
- To send the tips: your permission, given with the switch on your account page and withdrawn with any unsubscribe link. The welcome email and the minutes note are part of providing your account.
- To keep the service safe: limits on sign-in attempts and short-lived security records, which store your email address and IP address only as one-way hashes. This is our legitimate interest in protecting the service and you.
- To run the affiliate programme: an affiliate's details are needed for our agreement with them; the affiliate cookie is set only when you say yes; counting clicks and keeping the code with an account are our legitimate interest in paying affiliates for the customers they send.
- To answer you: when you write to us, by email, with the contact form or through the chat bubble, we use your message and email address to reply. The contact form does not store them: it emails them to our support mailbox; the chat keeps them as described above.
- To show testimonials: your permission, which you give with the tick on the form and can withdraw at any time.
- To compare the credit's two wordings: our legitimate interest in describing the offer clearly; we count from the records above and keep nothing else.
- To count visits and sign-ups with analytics: where the law asks for consent first, your permission, which you give with "Allow analytics" and withdraw with "Privacy choices" at the bottom of any page; elsewhere, our legitimate interest in knowing which pages help.
- To send the newsletter: your permission, which you give by confirming your address and withdraw by unsubscribing. Keeping the sign-up credit's hashes so it is given once per person is our legitimate interest in offering it fairly.
How long we keep it
- Your account, computers, licences and subscription status: until you delete your account, then all of it is deleted. A licence's record is also deleted about a year after it ends.
- Account emails: your tips choice and which of these emails we sent, until you delete your account.
- Sign-in codes and links: deleted a day after they expire. Website sign-ins end after 30 days at most.
- Email address changes: the old and new address and the time, 30 days after the change (an unused code, a day after it expires).
- Security records: deleted after two days.
- Payments: Stripe keeps the payment, tax and invoice records as the seller, under its own privacy policy.
- Your emails and contact-form messages to us: as long as we need them to help you.
- Chat messages: 12 months; spam, 30 days.
- Testimonials: while they are shown; withdrawn or rejected ones, 30 days.
- Newsletter: your address until you unsubscribe (unconfirmed sign-ups, 7 days); the sign-up credit's hashes, dates and amounts for as long as the credit is offered, so it is never given twice.
- Analytics: your answer stays in your browser until you change it or clear the site's data; the events in PostHog are deleted after 12 months at most.
- Affiliate links: the cookie expires after 90 days; the code kept for a visit, when you close the tab. Affiliates' details and commission records: while you are an affiliate, then as long as we need them for payment and tax records; an application we decline, until you ask us to delete it. The commission records of a customer an affiliate referred (their Stripe customer ID and the amounts of their payments, never a name or an email address) are kept for those payment records, also after the account is deleted.
Who processes data for us
The subprocessors page lists these companies in one table, with the date it was last checked.
- Payments: Stripe sells the plans for us as the merchant of record, through Link, its service for this, and processes card details, tax and invoices under its own privacy policy; we never see full card numbers.
- Email: Resend sends our sign-in emails and the newsletter, and the contact form's and the chat's messages to our support mailbox, from the European Union. Emails you send to our addresses, and those messages, reach us through Cloudflare's email forwarding and Google's mail service.
- Analytics: PostHog, in the European Union, Google (Google Analytics and Google Ads) and Microsoft (Clarity), as described under This website.
- Hosting: Cloudflare runs the website and the account service; the account database, which also keeps chat messages, testimonials and the newsletter list, is kept in Western Europe.
These providers may process data outside the UK, for example in the United States, under the safeguards the law requires, such as the UK's international data transfer agreements.
Your rights
You can ask for a copy of your data, have it corrected or deleted, object to how we use it, or have it sent to you in a portable form. Most of this you can do yourself on your account page: download a copy of your data ("Download my data"), change your email address, see and remove your computers, download licence files, and delete your account once no subscription is active. For anything else, write to support. If you are unhappy with how we handle your data, you can complain to the UK Information Commissioner's Office (ico.org.uk) or the data protection authority where you live.