1. Current service register
| Service | Current position |
|---|---|
| Production application and database hosting | Scaleway dedicated servers in France host the web application and PostgreSQL database. Encrypted recovery backups are stored on a separate Scaleway server in France. Administrative access is restricted. Contractual records and the full provider register are under review. |
| Map tiles | The current dashboard requests tiles from tile.openstreetmap.org when there are current driver coordinates. This discloses network information and map area. Assess its role, policy and suitability; do not assume an Article 28 subprocessor contract exists. |
| Fonts | Geist is downloaded at build time and self-hosted by Next.js. The frontend does not direct visitor font requests to Google Fonts. |
| Email, SMS and customer support | PureSMS (divergent Connect) is configured for transactional text messages using the dropLog sender. It processes recipient phone numbers and message content when SMS delivery is enabled. MXroute has been selected for email, but SMTP setup is pending and public registration remains paused. No support-ticket provider is configured. Processing terms and international-transfer arrangements remain under review. |
| Mobile push notifications | Google Firebase Cloud Messaging is configured for Android Driver notifications. It processes device registration tokens and generic notification content. Firebase Analytics is enabled for usage metrics across mobile apps. Apple APNs support is implemented but remains disabled pending Apple Developer credentials. Device delivery has not yet been validated. No customer addresses, receipt contents or payment amounts are included in push previews. |
| Payments and subscription invoicing | A Stripe-hosted Checkout and customer-portal integration is implemented but live billing is not configured. Before enabling it, confirm the contracted Stripe entity, roles, processing terms, international transfers, retention and applicable disclosures. Stripe may act in different roles for different payment activities; do not assume all processing is solely on our instructions. |
| OCR and route optimisation | The native Driver apps implement receipt recognition using Android ML Kit and Apple Vision on the device, and a server-side Tesseract module is available for receipt OCR on our own server. A Google Routes adapter is implemented but paid route services are not enabled in production. |
| AI-assisted receipt reading (server-side, optional and configurable) | Receipt image and/or extracted text — which may include customer name, address, phone number and order amounts — may be submitted to a third-party AI language model service selected by the platform administrator. Approved categories: general-purpose large language model services (currently Groq; optionally Google Gemini, Anthropic Claude or OpenAI) and self-hosted inference servers. Providers are currently based or primarily operated outside the UK/EEA. See section 3 (Before appointing a provider) below and the data processing schedule; adequate transfer safeguards must be confirmed before activation. These providers are not appointed until the feature is configured for a business. |
| AWS Rekognition — face comparison and Face Liveness (Driver Pool verification, conditional) | AWS Rekognition CompareFaces is used for automated face comparison: it compares the reference selfie with an identity document photograph (document match) and with periodic re-verification selfies. Processing runs in London (eu-west-2, United Kingdom). AWS Face Liveness is used for the certified liveness check: video frames from the app are streamed to AWS in Ireland (eu-west-1, EEA) during the liveness session. Face Liveness is iBeta ISO/IEC 30107-3 Level 1 and Level 2 certified. The transfer of data from the UK to Ireland relies on the adequacy regulations made under section 17A of the Data Protection Act 2018. Both services are covered by the AWS Data Processing Addendum. The operator's AWS account must have opted out of AI-services data use via an AWS AI Services Opt-Out Policy covering these regions before either feature is enabled; this is confirmed in the platform settings and stated in the consent screen. No biometric template is stored by the platform or by AWS. Face comparison is invoked only for drivers who have given explicit, separate consent to automated comparison. Face Liveness is invoked only for drivers who have given explicit, separate consent to AWS liveness processing. Neither service is appointed until the feature is configured, the DPIA is acknowledged and the relevant consent conditions are met. |
| Analytics and advertising | Product analytics are collected via PostHog (US Cloud) and Firebase Analytics to understand usage patterns and improve the platform; PostHog is configured as a first-party analytics processor and its data is processed in the United States. No third-party advertising network is integrated. A contextual ad slot on the tracking page serves approved images from restaurants and takeaways that use dropLog; no external network, cookie or cross-site tracker is involved. Promotional SMS and WhatsApp messages are sent via PureSMS and Meta Business APIs only to customers who have opted in. No advertising data is shared with analytics providers. |
2. Development is not production hosting
The local PostgreSQL container, GitHub source repository and generated marketing artwork do not establish where customer data will be hosted in production. Secrets and local database files are excluded from source control. The generated artwork is an illustration, not a customer testimonial.
3. Before appointing a provider
Record the provider’s legal identity, purpose, information processed, country/region, remote-access locations, contract and applicable transfer safeguards. Assess whether the provider is a processor, subprocessor or independent controller. Complete customer notice/authorisation procedures before any change that requires them.
Official guidance & references
The sources below inform the review. They do not certify this product or replace the company’s operational responsibilities.
EDPB: controller and processor responsibilitiesOpenStreetMap Foundation privacy policyOpenStreetMap tile usage policy