Yoley Limited ("Yoley", "we", "us") is the data controller responsible for your personal data.
| Registered name | Yoley Limited |
| Registered address | Sterling House, F2/F3, Davidson Road, Lichfield, England, WS14 9DZ |
| Company number | 14113958 |
| ICO registration number | ZC181753 |
| Privacy contact | privacy@yoley.com |
The app stores records you create directly on your device, including:
Why: To provide the core functionality of the app — you cannot use Yoley without creating these records.
When you scan a receipt, the app uses Google's ML Kit text recognition to read it. This processing happens entirely on your device — the receipt image and its text are never uploaded anywhere by Yoley.
Yoley never sees or stores your customer's card details. When you take a payment, the app asks Monek to create a secure payment link and your customer enters their card details on Monek's own hosted checkout page — not inside Yoley. The app only records that a payment was requested and, if you mark it so, that it was received.
If you apply for a Monek merchant account from inside the app, the details you enter on that form — your name, date of birth, address, company details and bank account — are sent to Monek Merchant Services Limited, together with information from your device session, to process your application. This only happens if you choose to apply. As an FCA-authorised payment institution, Monek will check your details with a credit reference agency and verify the identity of applicants for anti-money-laundering and fraud-prevention purposes.
Subcontractor UTR and National Insurance numbers are encrypted on your device using a key held in the Android Keystore. That key cannot leave your device, which means these fields cannot be read from a backup restored onto a different phone — you will be asked to re-enter them.
When adding a customer you can choose Import from contacts. Android shows you its own contact picker and you pick one person; the app then copies that person's name, phone number, email address and postal address into a new customer record on your device. The app asks for contacts permission at that point, only reads the one contact you pick, and never uploads your address book. If you would rather not grant the permission, you can type customer details in by hand instead.
Two features use your location. The job diary can show a job on a map, which uses your device's approximate location on your device only. The weather forecast needs a place to forecast for, so an approximate location is sent to our weather provider (see section 4) — if you have allowed location access that is your device's approximate position, and if you have not, it is the postcode of the business address you entered in Settings. Nothing more precise than that is sent, your location is never stored in your records, and it is never sent to Yoley. You can refuse the location permission and everything still works; the forecast simply uses your business postcode instead.
All business records you create are stored on your device, in a local database (Room/SQLite). There is no Yoley server, no Yoley account, and no synchronisation between devices. Yoley staff cannot see, access or recover your records.
Android backup: the app takes part in Android's standard backup, which copies the app's database and settings to your own Google Drive. This is a Google service governed by Google's privacy policy; Yoley has no access to it. It exists so you can restore your data on a new phone. You can turn it off in your device settings under System › Backup. You can also export a backup file yourself from Settings inside the app.
We do not sell your data, and we never share it for advertising. Some features send limited information to the outside services below in order to work. Each is listed with exactly what is sent and when.
| Service | What is sent | When |
|---|---|---|
| Monek (UK payment provider) | Payment amount and reference; for merchant applications, your own name, date of birth, address, company and bank details plus device session information (shared onward with a credit reference agency and for AML/fraud identity checks) | When you take a card payment or apply for a merchant account |
| Disify | A customer's email address | When you enter or edit a customer email, to check the address is real and not disposable |
| Companies House (UK) | The company name or number you type | When you look up a limited company |
| HMRC | The VAT number you type | When you verify a VAT registration |
| Fetchify (Royal Mail address data) | The postcode and any house name or number you type | When you use postcode lookup to fill in an address |
| OpenWeather | An approximate location — your device's approximate position if you have allowed location access, otherwise the postcode of your business address | When the job diary or dashboard shows a weather forecast |
All of these connections use HTTPS encryption. We do not send your quotes, invoices, customer lists, expenses or receipt images to any of them, or to anyone else.
Optional AI help assistant: the in-app help assistant answers from content built into the app. If you choose to add your own Anthropic API key in Settings, your typed question is sent to Anthropic to generate an answer. This is off unless you add a key yourself.
The app contains no advertising SDKs, no third-party analytics, and no cross-app or cross-site tracking.
As a UK resident you have the right to access, correct, delete, restrict, or port the data held about you, and to object to processing. Because all Android app data is stored locally on your device, you can exercise most of these rights directly within the app (edit or delete records) or by deleting the app. For any other privacy questions, contact privacy@yoley.com. We will respond within 30 days.
If you are unhappy with how we handle your data, you have the right to lodge a complaint with the Information Commissioner's Office (ICO) at ico.org.uk or 0303 123 1113.
Yoley is a business tool intended for users aged 18 and over. We do not knowingly collect personal data from anyone under 18.
We may update this policy from time to time, for example as Android features (such as cloud sync or in-app payments) are added. We will update the effective date above when we do. Continued use of the app after changes take effect constitutes acceptance of the revised policy.