Who is responsible
DriverDrops is currently operated by Mateusz Goralczyk, an individual developer. Contact driverdrops@bentolabs.co.uk about support or privacy.
We are the controller for our business accounts, service security and support. Restaurants normally control their delivery, worker, location and pay records; DriverDrops processes those records on their instructions. Their own privacy notices also apply. We can help you identify the responsible restaurant.
Information used by the service
Accounts use names, email addresses, identifiers, invitations, restaurant memberships and roles. A manager may provide your details when inviting you. An email address is required for account access.
Restaurant records can include customer contact details, addresses, postcodes, order references, confirmed ticket information, notes, delivery status, shift times, rates and calculated pay. Users or restaurants supply this information to coordinate deliveries and keep records.
Support messages, access records and filtered technical errors help us respond to requests, secure the service and repair faults. Hosting providers also receive normal network request information, such as an IP address.
Website subscriptions through Stripe are planned. The intended checkout will use purchaser and billing details, subscription identifiers, invoices and payment status to manage access. These payment arrangements are not yet active under this draft.
Why information is used
We rely on contract where processing is necessary for our contract with an individual, legitimate interests in managing business contacts, operating and securing the service and resolving support, and legal obligations for records we must keep. A restaurant must explain its own lawful basis for employment and operational records.
DriverDrops does not sell personal information or use it for targeted advertising. It does not make automated hiring, dismissal or credit decisions. Ticket extraction and pay calculations assist users; check the results and raise corrections with your restaurant.
Location is a separate choice
Sorting stops can use your current position on the device after permission. This does not enable restaurant location sharing. Sharing requires a separate in-app choice during an active shift and can include background updates.
Authorised restaurant owners and operational staff can see the latest shared position. DriverDrops does not provide customers with a live driver map. Shift timing and delivery records can be used without sharing location.
Stop sharing in the app, end your shift or change device permissions to stop updates. Connectivity and device settings affect freshness; an old or missing position is not proof of where someone is. Device permission does not replace the restaurant's responsibility to justify and explain worker monitoring.
Ticket recognition and service providers
Google ML Kit recognises tickets on the device. The ticket recognition flow sends confirmed delivery fields to DriverDrops, not the ticket image. Temporary working images are cleaned up after use, although interruption can leave a file for later cleanup. Original photo-library images remain under your control.
Google's SDK also collects technical information for diagnostics and usage analytics. On-device recognition does not mean no information reaches Google. Other providers support hosting, sign-in, email, errors, postcode lookup and maps.
Access depends on restaurant membership and role. Owners can access financial records; operational staff views exclude driver wage details. Service administrators may access information for operations, support and investigation.
The main application database is configured in London. Provider operations, support access and backups can involve other countries. Ask us about the destinations and safeguards relevant to your service; this draft does not claim all processing stays in the UK.
Retention and deletion
Customer-identifying delivery details have an application deadline of 90 days after capture or receipt, whichever is earlier. Cleanup removes names, contact details, full addresses and postcodes, identifying order references, notes and destination coordinates. This is an operational ceiling, not a statutory period.
Location storage keeps the latest shared fix rather than route history. A fix stops appearing as recent after five minutes. Separate scheduled cleanup removes remaining fixes once their server receipt is at least 23 hours and 55 minutes old. Stopping sharing, shift end or access revocation can remove the applicable position sooner. Hiding a fix is not deletion.
Necessary financial evidence follows the restaurant's recorded obligations and valid holds. Restaurants must keep legally adequate payroll and accounting evidence in their own systems. Financial retention does not justify retaining GPS or customer contact information for the same period.
Account, support and business records remain while needed for service access, a request or dispute, security or applicable legal record keeping. Provider logs and backups have separate arrangements. Downtime, locked records and backlogs can delay scheduled cleanup, and a powered-off phone cannot run local cleanup.
Delete account in the current iPhone/iPad build removes login and profile information, invitation identity and live position, closes open shifts and clears that account's device working data. Necessary restaurant evidence can remain with direct account identifiers removed; this is not guaranteed irreversible anonymity. Sole-owner deletion does not delete or automatically transfer the restaurant. Signing out, cancelling a subscription and deleting an account are different actions.
Your rights and questions
Depending on the circumstances, you can request access, correction, erasure, restriction or portability, object to processing based on legitimate interests and withdraw consent where it is the lawful basis. We may need proportionate identity checks and will explain any lawful limits. For restaurant-controlled records we help the restaurant handle the request.
Email driverdrops@bentolabs.co.uk to raise a concern. You can also complain to the UK Information Commissioner's Office. Material changes to this notice will be communicated as appropriate.