

Privacy policy
Last updated 16 September 2026
Who we are
Provly is a proof of delivery app and website for small businesses. It is run by Logistics Training (UK) Ltd, 128 City Road, London EC1V 2NX ("we", "us").
If you have a question about your information, email hello@provly.co.uk.
Our role
- For people with a Provly account (business owners, office staff and drivers), we are the controller of your account information: we decide how it is used.
- For a business's own customers (the people who order and receive deliveries), the business is the controller and we are its processor. We hold and use that information only to run Provly for that business.
If you are a customer of a shop that uses Provly, please contact the shop first about your information. We will help the shop answer you.
What we store
- Accounts: business name and logo, your name, email address and password (stored only in a scrambled form we cannot read), your role, and invitations sent to new team members.
- Customers and deliveries: customer and recipient names, delivery addresses, phone numbers and email addresses, order details and items, delivery dates and times, delivery instructions and notes.
- Proof of delivery: photos, videos, signatures, the name of the person who took the delivery, where it was left, whether payment was collected, the driver's name, the time, and the phone's GPS position when the delivery was recorded.
- Other: feature requests you send us, and a push notification token for your phone if notifications are switched on.
We do not sell your information, and we do not use it for advertising.
Location
The app reads your phone's location only at these moments: when a driver marks a delivery as on its way, arrived, delivered or not delivered, and when you choose "Where I am now" as the start of a route to sort it. It does not track you in the background, and it does not ask for background location. If you do not allow location, the app still works and the delivery is saved without a position.
Why we use it
- To run Provly: store deliveries, record proof, sort routes and check postcodes.
- To send emails you or your business ask for, such as invitations, password resets and proof of delivery.
- To keep Provly secure and working, and to answer you when you contact us.
Our lawful reason for account information is the contract with you or your business, and our legitimate interest in keeping the service secure and working.
Emails to a business's customers
A business can use Provly to email its own customers, for example to send them proof that their order was delivered. The business decides whether to send these emails and is responsible for having a lawful reason to use its customers' details. Provly sends them on the business's behalf.
Who we share it with
We use these companies to run Provly. Each receives only what it needs.
- Supabase: our database, file storage and sign-in. Everything above is stored with Supabase in London (UK).
- Vercel: hosts this website. Pages are served from London (UK).
- Google (Routes API and Geocoding API): the map positions of a route's start and stops, to sort the route; and the first line and town of an address, to suggest a postcode when one looks wrong. Never a customer's name, phone number or email.
- postcodes.io: postcodes and town names only, to check postcodes and find their map position.
- Anthropic (Claude): when you use "Type or paste" or "Upload" to add orders, the text, photos and screenshots you give (including the text of an uploaded document) are sent to Anthropic so the orders can be read. Tables in spreadsheets are read by Provly itself and are not sent. Under Anthropic's commercial terms, this is not used to train its models. We keep only a count of what was read, not the text or images.
- Resend: sends Provly's emails (invitations, password resets, proof of delivery). It receives the email address, the email and any attachment.
- Google Firebase Cloud Messaging: when notifications are switched on, it delivers them to your phone. It receives your phone's notification token and the notification text.
- Apple, Google Play and RevenueCat: when you subscribe, they handle the payment and tell us whether your subscription is active. We never see your card details.
Some of these companies process information outside the UK, for example in the USA or Ireland. Where they do, they protect it under their data processing terms with us.
We may also share information if the law requires it.
How long we keep it
- Photos, videos and signatures: one year from when the delivery was recorded, then deleted automatically. The delivery record keeps a note that there was a photo or signature and when it was removed.
- Proof links: a link shared to show proof of delivery stops working 90 days after it was shared.
- Everything else: for as long as the account is open.
Deleting an account: in the app, go to ☰ → Settings → Delete account (also in Settings on app.provly.co.uk). When a business owner deletes their account, we delete the business and all its information, including its routes, deliveries, customers, photos, videos and signatures, and then the owner's login. When anyone else deletes their account, we remove them from the business, replace their name with “Former driver” and delete their login; deliveries they made stay with the business as its proof of delivery. You can also email hello@provly.co.uk from the email address you log in with, and we will delete your account within 30 days. Copies in our providers' backups are removed as those backups expire.
Your rights
You can ask us for a copy of your information, ask us to correct it, or ask us to delete it. Email hello@provly.co.uk. We will reply within one month.
If you are unhappy with how we have used your information, you can complain to the Information Commissioner's Office (ICO) at ico.org.uk. We would like the chance to put it right first.
Children
Provly is for businesses. It is not for anyone under 18.
Cookies
This website uses only the cookies needed to keep you logged in, and remembers your light or dark choice on your computer. It uses no advertising or tracking cookies.
Changes
If we change this policy, we will update the date at the top of this page.