Skip to main content
Start trial

Tipslip sub-processor register

Version 1.2. Effective date: 2026-09-30.

On this page

This page lists everyone else who touches your data when you use Tipslip, what they do with it, and where it's processed. It's written for a skip-firm owner, not a lawyer. If a word needs a lawyer to understand, we've failed at this page.

A "sub-processor" is a company we hire to help run Tipslip, who ends up handling some of your (or your customers', or your drivers') personal data as part of that job. We stay responsible for what they do with it: using one doesn't let us pass the buck.

We check this list against what the product actually does. Where each company processes data, and the terms it works under, come from that company's own published documents. If we could not check something, we have left it out rather than guess.

Sub-processors

Sub-processorWhat it does for TipslipPersonal data it may receiveProcessing locationSafeguard
SupabaseOur database and file storage, and sign-in for office staff accountsEverything in the product: firm, driver and customer contact details, job data, photos, signatures, generated PDFs, office staff loginsLondon, UK. Our Supabase project is in its London region, and Supabase stores a project's database and files in the region chosen for it. Files are delivered through a content delivery network, which can keep a copy for a short time on a server near the person opening the fileSupabase's data processing addendum, which is part of its terms, with Supabase Pte. Ltd (Singapore). For data leaving the UK, the addendum uses the EU standard contractual clauses with the UK Addendum
VercelHosts the office app, the website and the driver app, and runs our background jobsEverything that passes through those apps, and the request logs Vercel keepsThe office app, which runs our background jobs, and the website run in Vercel's London region. The driver app is a set of files Vercel delivers from its servers around the world; it sends your data to the office app and the database in London. Vercel says its main processing facilities are in the United StatesVercel's data processing addendum, which applies to accounts on its Pro and Enterprise plans, with Vercel Inc. (US). Vercel Inc. is certified under the UK Extension to the EU-US Data Privacy Framework, and its addendum also includes the UK international data transfer addendum
ResendSends our emails: transfer notes, to each of these that has an email address: your customer, on a collection; your firm and your site, on a tip; and another firm whose lorry brought waste to your site, when Tipslip makes the note for that load; sign-up and password-reset links to your office staff, billing reminders to you, status-page alerts, and replies to people who contact us through our website. Holds our website mailing listThe email address of each person we email and what the email contains, including any PDF attached. Name, email address and message of people who use our website contact form. Email addresses on our mailing listUnited States. Resend stores its customers' data, including email content and delivery logs, in the USResend's data processing addendum, which applies when an account is opened, with Plus Five Five, Inc. (trading as Resend, US). For data leaving the UK, the addendum uses standard contractual clauses with the UK Addendum. Resend's addendum also says it complies with the UK Extension to the EU-US Data Privacy Framework
StripeBilling: checkout, the customer portal, invoices, add-on chargesYour firm's name and contact email address, your plan and subscription status. Card and payment details you enter go straight to Stripe and never reach our own systemsStripe's agreement says personal data goes to Stripe, LLC in the United States, and may go to Stripe companies and suppliers in other countriesStripe's data processing agreement, which is part of its services agreement, with Stripe Payments Europe, Limited (Ireland) for UK accounts. Stripe's agreement says Stripe decides for itself how it uses personal data for some purposes, such as preventing fraud and meeting anti-money-laundering rules. For data leaving the UK: the UK Extension to the EU-US Data Privacy Framework, which Stripe, LLC is certified under, and otherwise the UK addendum to the standard contractual clauses
InngestSchedules and retries our background jobs: submitting to Defra, the billing sweep, generating and emailing documents, deadline alerts. The jobs themselves run on our Vercel servers in LondonRecord numbers for firms, jobs and receipts. When an office user asks for a Defra submission to be retried, that user's email addressUnited States. Inngest runs its service and holds its data in the eastern United StatesInngest offers a signed data processing agreement to customers on paid plans; it does not publish one
CloudflareHosts our public status page and an automated health check ("canary"); DNS for the status page's addressStatus page: email addresses, and mobile numbers if given, of people who sign up for incident alerts. Canary: test data only, never a real customer's dataCloudflare runs the status page on its servers around the world. The subscriber list is kept in a Cloudflare database whose location is set when the database is createdCloudflare's data processing addendum, which is part of its terms, with Cloudflare, Inc. (US). Cloudflare, Inc. is certified under the UK Extension to the EU-US Data Privacy Framework, and the addendum also uses the EU standard contractual clauses with the UK Addendum
GoogleHosts our support mailbox (Google Workspace / Gmail) at support@tipslip.co.ukWhatever a customer, driver or prospect writes to support, including any attachments, and messages sent through our website contact formGoogle may process this data in any country where it or its suppliers have facilitiesGoogle's Cloud Data Processing Addendum, which is part of Google's Workspace terms. For data leaving the UK: the UK Extension to the EU-US Data Privacy Framework, which Google LLC is certified under, and standard contractual clauses with the UK Addendum where that does not apply
Google (Google Analytics and Google Ads)Visit statistics and ad measurement on our website, tipslip.co.uk, only for visitors who accept them in our cookie banner. Not used in the Tipslip appWebsite visitors' cookie identifiers, pages viewed, the page they came from, device and browser type, and rough location. Google Analytics does not store IP addresses from UK visitors. None of your firm's recordsCollected through Google servers in the EU, Switzerland or the UK; Google may then process it in the US and other countries where it has facilitiesGoogle Ads Data Processing Terms, with Google Ireland Limited; Google Analytics is a processor service under those terms. Transfers to the US: the UK Extension to the EU-US Data Privacy Framework, and standard contractual clauses where that does not apply

Whose data each one handles. Supabase, Vercel, Resend, Inngest and Google can handle personal data in your firm's records, so under our data processing agreement they are sub-processors of your data. Stripe, Cloudflare and Google Analytics handle only data we control ourselves (billing contacts, status-page subscribers, website visits); we list them here so you can see everyone we use.

Other recipients (not sub-processors)

Defra's Waste Tracking service. When your driver, or a gate operative (a login you give a member of your staff to record loads that other firms bring to your site), records a delivery to a permitted site, Tipslip submits the movement to Defra because the law requires it. That's the whole point of the product. Defra is not doing this "for us" the way a sub-processor does; Defra is a regulator receiving a statutory report, and is its own independent controller of what it does with it. What we send: waste codes, weights, site/permit details, the carrier's registration number, the vehicle registration, the weighbridge ticket number where one was recorded, and hazardous-waste details where they apply. When the waste came in on another firm's lorry, that firm is named as the carrier: its name, its registration number or the reason it has none, its address and contact details where you hold them, and its lorry's registration. Tipslip collects no location or GPS data, and we do not send anyone's photos or signatures to Defra: the record we build only carries the fields Defra's own schema defines.

Not used

None of the following are used in Tipslip today, checked directly against the product rather than assumed:

  • AI / LLM services (e.g. OpenAI, Anthropic): no such service is called by any deployed app or worker function.
  • SMS: no SMS provider processes customer or driver data. Twilio is named only in our own internal outage alerting, no Twilio account exists yet, and it never touches customer, driver or firm data.
  • Error tracking (e.g. Sentry): the product itself does not use an error-tracking service.
  • Session replay (e.g. tools that record what a visitor does on screen): none found.
  • SheetJS (the xlsx library the spreadsheet importer uses to read CSV/Excel files): the package tarball is downloaded from the vendor's CDN at install time, on the build machine. The library itself runs inside our server and never makes a network request; no customer data reaches SheetJS.

How we change this list

  • New sub-processor: we'll email the account owner at least 30 days before a new sub-processor starts processing your data, naming who they are and what they'll do.
  • Like-for-like replacement: if we're swapping one sub-processor for a directly equivalent one purely for security or availability reasons, we'll give 14 days' notice instead, and say why.
  • Objecting. You can object by emailing us within the notice period. If we can't resolve your objection, you may terminate the affected service and we'll refund any fees you've already paid for the part of the term you won't be using.

How we keep this current

Every change to Tipslip's code goes through an automatic check. It looks for any new outside service the code calls, any new supplier software, and any new supplier password or key, and stops the change if that supplier is not on this page.

Change history

VersionDateChange
0.12026-09-25First version.
0.22026-09-25Added Google (Google Workspace / Gmail support mailbox) as a sub-processor; noted that Defra receives the vehicle registration.
0.32026-09-27Removed Plausible, which we never switched on and no longer plan to use.
0.327 September 2026Added Google (Google Analytics and Google Ads), for visit statistics and ad measurement on our website for visitors who accept them in our cookie banner.
0.42026-09-27Filled in where each company processes data and the terms it works under, from each company's own published documents. Corrected what Resend, Stripe, Inngest, Cloudflare and Google receive.
1.02026-09-28First approved version. Approved and in force 28 September 2026. Plainer wording in "Not used".
1.12026-09-30Resend: who gets transfer notes on a collection, on a tip, and on a load another firm's lorry brings to your site, each only where there is an email address; "and receipts" removed, because the documents Tipslip emails are transfer notes. Defra: a gate operative can record the delivery; what we send now includes the weighbridge ticket number, and on a load brought in on another firm's lorry that firm's details as the carrier; we send no one's GPS coordinates, photos or signatures, not only no driver's. No new sub-processor.
1.22026-09-30Location (GPS) capture removed from the driver app. Supabase's row no longer lists GPS coordinates among the data it receives. The Defra row now says Tipslip collects no location or GPS data, and drops the GPS line from what we do not send Defra (we never sent Defra photos or signatures either).

Read the small print. Then log a load. From £49 a month.

One site and up to five drivers on Starter. Three sites and twelve drivers on Pro at £99, with extra sites and drivers added as you grow.

Start your 7-day trial

Set up today. No card needed.