Privacy Notice

This notice explains what RestoFleet collects, why it is used, who receives it, and the choices available to restaurants, couriers, customers, and website visitors.

Last updated: 22 November 2026 godelivery.live@gmail.com

1. Who is responsible for the data

RestoFleet is the controller for its own website visitor, account administration, security, subscription, and billing data. A restaurant or delivery business is normally the controller for its customer orders, staff records, courier locations, shifts, arrival records, notes, and operational reports. In that workspace context, RestoFleet acts as a processor under the Data Processing Addendum.

Privacy requests about a restaurant’s delivery or workforce data should normally go to that restaurant first. Requests about RestoFleet’s own processing can be sent to godelivery.live@gmail.com. The restaurant and RestoFleet may need to cooperate to complete a request.

2. Information collected

  • Account data: name or business details supplied by the user, email address, authentication identifiers, role, workspace membership, login events, and legal-document acceptance records.
  • Restaurant data: restaurant name, location and workplace coordinates, settings, invitation codes, subscription status, and trial-location records used to prevent repeated trials.
  • Order data: selected delivery address and postcode, coordinates, optional recipient telephone number and notes, order status, assignment history, route information, timestamps, and related exports.
  • Courier and shift data: courier profile, device identifier, GPS location fixes, accuracy and movement data supplied by the device, distance travelled, restaurant entry and exit events, customer arrival events, clock-in and clock-out evidence, workplace distance, correction requests, manager notes, and approvals.
  • Notification data: browser push endpoint, encryption keys, device or browser information needed for delivery, notification permission and preferences, and subscription status.
  • Billing data: plan, billing interval, our payment processor customer and subscription identifiers, payment status, invoices, tax and transaction records. RestoFleet does not receive or store a customer’s full card number or card security code.
  • Technical data: logs, error reports, security events, browser and device information, approximate country, referring page, and interactions needed to operate and protect the service.

3. Why data is used and legal bases

RestoFleet uses data to create and secure accounts, provide the contracted service, process payments, issue invoices, prevent repeat free trials, deliver notifications, provide support, diagnose faults, prevent abuse, and meet legal obligations. Depending on the activity, the legal basis is performance of a contract, compliance with a legal obligation, legitimate interests in operating and securing a business service, or consent where required.

For restaurant-controlled order and workforce data, the restaurant determines the purpose and lawful basis. Restaurants must inform delivery recipients and couriers and must not use optional notifications or device permissions as a substitute for a valid employment-law basis for tracking. Withdrawing browser notification permission stops future push messages but does not by itself erase existing operational records.

4. Courier location and working-time information

On iPhone and Android, the separate Traccar Client app sends device location information to RestoFleet using a courier-specific device credential. The RestoFleet browser and Home Screen apps provide the setup instructions and operational workspace. RestoFleet records those updates only while that courier has an open shift. Location can support live assignment, distance and arrival records, route history, and workplace-distance evidence. Accuracy depends on the phone, permissions, battery settings, network, and GPS configuration.

Restaurants must not track couriers off duty. Couriers should clock out at the end of work and can stop Traccar Client through its controls, although doing so during work may affect the quality of operational records. Location records are not used by RestoFleet to make solely automated decisions producing legal or similarly significant effects.

5. Visitor analytics

Privacy-friendly visitor analytics is enabled on the published site. It uses no cookies, stores nothing on the visitor’s device, does not keep IP addresses, and does not identify visitors. It is used only to measure and improve RestoFleet.

It records pages visited, where visitors came from, country, browser, operating system, device type, time on site, page-load speed, errors, and button and link clicks. The editor preview is not counted. Detailed data is kept for 90 days and daily summaries for one year. There is currently no analytics consent banner on this site, so these analytics items are recorded for every visitor, subject to the provider’s technical limitations, without cookies and without identifying anyone.

6. Service providers and recipients

RestoFleet shares only the information needed with providers that support the service. Infrastructure providers host authentication and the database. Our payment processor provides checkout, subscription billing, invoicing, fraud prevention, and payment records. Mapping providers supply address search, road routes, map tiles, and fonts. Map data © OpenStreetMap contributors. Traccar Client supplies courier GPS updates. Browser and operating-system push providers deliver notifications. Hosting and visitor-analytics providers operate and measure the published website.

Providers may receive IP addresses, requested URLs, device details, location queries, account identifiers, or other data necessary for their service. Our payment processor and some other providers act as independent controllers for their own regulatory, fraud, and payment-processing purposes. Information may also be disclosed to professional advisers, authorities, or other parties where legally required, to protect rights and security, or as part of a business transaction subject to appropriate safeguards.

7. International transfers

Some providers may process data outside the European Economic Area, including in the United States. Where required, RestoFleet or the relevant provider uses an approved transfer mechanism, such as an adequacy decision or Standard Contractual Clauses, together with supplementary safeguards where appropriate. Users may contact RestoFleet for available information about the safeguard applying to a particular transfer.

8. Retention

Data is kept only as long as necessary for the purposes described, including account administration, service delivery, security, support, dispute handling, and legal compliance. Restaurant-controlled operational records are retained according to the restaurant’s lawful instructions and operational needs, then deleted or anonymised when no longer required. Billing and accounting records may need longer retention under tax and commercial law.

Deleted data may remain in encrypted backups or security logs for a limited additional period before routine removal. Visitor-analytics retention is stated in section 5. Browser push subscriptions remain until removed, expired, or no longer needed. Legal acceptance and transaction evidence may be retained to demonstrate contractual and payment history.

9. Your rights

Subject to applicable law and identity verification, individuals may request access, correction, deletion, restriction, portability, or objection to processing, and may withdraw consent for future processing where consent is the basis. Signed-in users can start account deletion under Account & privacy; restaurant-controlled business records may require a separate request to the restaurant. Couriers and delivery recipients should normally contact the relevant restaurant for workspace data. A request to RestoFleet may be redirected where RestoFleet acts only as processor.

Individuals may complain to the data-protection authority where they live or work, or where the alleged issue occurred. In Poland, this is the President of the Personal Data Protection Office (UODO). RestoFleet asks for a chance to resolve concerns first, but this is not a condition of making a complaint.

10. Security, breaches, and children

Reasonable organisational and technical measures are used, including authenticated access, tenant-scoped permissions, protected server operations, credential-based GPS ingestion, and encrypted connections. No system is guaranteed secure. Users must protect their accounts and report suspected unauthorised access.

Where legally required, RestoFleet will notify authorities and affected people of qualifying personal-data breaches and will notify affected restaurant controllers without undue delay after becoming aware of a breach affecting their processed data. The service is for business users and is not directed to children; users must not create accounts for children.

11. Updates and contact

This notice may change when the service, providers, or legal requirements change. The latest version will carry a revised date and material changes will be communicated where required. Questions and requests can be sent to godelivery.live@gmail.com. These documents were last updated on 22 November 2026.