Last updated: 18 October 2026
Every third party that can touch personal data held in TAPPI is listed below, with what it does, where it processes and the safeguard we rely on if that is outside the UK or EEA. Nothing is omitted because it is awkward.
This page is part of our data processing agreement. We give at least 30 days' notice before a new or replacement sub-processor starts processing, and you can object — clause 4 of the DPA says what happens then.
| Provider | What it does | Data it can see | Where |
|---|---|---|---|
| Supabase | Primary database, authentication and file storage | All data held in TAPPI accounts, including business-customer records | EU — Ireland (eu-west-1) |
| Vercel | Website and application hosting; serverless functions; cookieless page-view counts and page-speed measurement on the public site (Web Analytics, Speed Insights) | Request data in transit, application logs; for the public-site counts: page path, referrer, country, device and browser class — no cookie, nothing stored on the device | EU — Dublin (functions pinned to dub1); global edge network for static assets |
| Stripe | Subscription billing for TAPPI; payment processing on each business’s own connected Stripe account for top-ups and gift cards | Name, email, billing address, card metadata (we never receive full card numbers) | Ireland and United States Stripe’s own SCCs / UK Addendum |
| Resend | Transactional and campaign email delivery | Recipient name and email address, message content; for our own emails about TAPPI, delivery, bounce and link-click events (the clicking device’s IP address and browser pass through Resend and are not kept by TAPPI) | United States SCCs / UK Addendum |
| Upstash | Rate limiting and short-lived caching | IP addresses and hashed keys, held for minutes | EU (Frankfurt) |
| Sentry | Error monitoring. Configured with sendDefaultPii disabled, no session replay | Stack traces, URL, browser and OS version | United States SCCs / UK Addendum |
| Google Google Ireland Ltd / Google LLC | Google Wallet passes, Google Business Profile connection, Sign in with Google, Smart Tap, business lookup on Google Maps when signing up | Pass holder name and email, wallet object identifiers, review data, business name searched on Google Maps | Global EU-US Data Privacy Framework / SCCs |
| Apple Apple Distribution International Ltd | Apple Wallet passes, push notifications to passes (APNs), Sign in with Apple | Pass holder name, device push token, pass serial | Global SCCs |
| Cloudflare | Turnstile anti-bot check on public website forms | IP address, browser signals | Global SCCs / UK Addendum |
| Calendly Calendly LLC | Booking a call with TAPPI from the website. The calendar is Calendly’s page, shown inside ours | Name, email, the time you pick and anything you type into the booking form; your IP address when the calendar loads | United States EU-US Data Privacy Framework / SCCs |
| GitHub GitHub, Inc. (Microsoft) | Running TAPPI’s scheduled background jobs (retention cleanup, campaign dispatch, gift and billing crons) | No direct access to account data; triggers authenticated calls to TAPPI’s own endpoints | United States EU-US Data Privacy Framework / SCCs |
| Anthropic | Three uses. Drafting business-to-business outreach emails, generating the replies of the assistant on our public website, and suggesting loyalty card designs from a business’s own logo when the owner asks for them in the dashboard. Never used for a business’s customer records | Business name and public business information for outreach. For the website assistant: the messages you type into it and the replies it has already given in that conversation. We do not store the conversation — it lives in your browser tab until you close it — and we never send it your name, your email or anything you have not typed into the chat. For card design suggestions: the business’s logo, name, type of business and brand colour, and a photo from its own website when the owner chooses one, sent only when the owner presses the button, and nothing about the business’s customers | United States SCCs |
| Expo (EAS) | Building and distributing the TAPPI Business mobile app | No customer data; build artefacts and developer accounts only | United States SCCs |
| OpenStreetMap, CARTO and OpenFreeMap | Map tiles on signed-in screens: the dashboard and the partner portal map. Loading a map sends the viewer’s IP address to these services | IP address of the TAPPI user viewing the map. No customer data is sent | Global Contacted directly by the viewer’s browser, not by TAPPI. Listed for transparency rather than because it is a transfer we make |
| Shopify Not active in production | Fulfilment of NFC chip orders | Recipient name, delivery address, order contents | Global SCCs / UK Addendum |
| Square Block, Inc. / Square Europe Ltd Not active in production | Optional till connection a venue switches on: we read a paying customer's email or phone from the venue's own Square account to find their loyalty card | Payment id, amount, location; the paying customer’s email and phone as held by Square | United States SCCs / UK Addendum |
| SumUp POS Pro SumUp (SumUp POS Pro, formerly Goodtill) Not active in production | Optional till connection a venue switches on: the venue’s SumUp till looks up a loyalty card by its code, name or email, shows the balance and rewards, and sends us the completed sale | Cardholder name, email, phone, points or stamp balance and available rewards (to the till); sale id, outlet, total and items (from the till) | United Kingdom None (UK) |
The database that holds your account and your customers' records is in Ireland. The application functions that read and write it run in Dublin. Neither is a default — both are pinned.
Some of the providers above process elsewhere for a narrow purpose: email delivery, error monitoring, wallet passes, the scheduler that triggers our own background jobs. Each row says where, and what covers the transfer.
Companies we pay that never touch personal data held in TAPPI — a domain registrar, a design tool, an accountant's software — are not sub-processors and are not listed. Neither are the payment rails your own customers use: when someone tops up a balance at your venue, the payment runs on your connected Stripe account, under your relationship with Stripe.
Email hello@thetappi.com and we will add you to the notification list for changes to this page.