WHO HELPS OPERATE EACH FEATURE.
Providers & Integrations
A functional directory of infrastructure, communications, payment, AI, maps, push, advertising and connected services.
- Reviewed
- Approved month
- February 2026
- Effective
- 2026-11-16
- Status
- effective
4th Floor 20 Fenchurch Street London EC3M 3BY United Kingdom
Country of establishment: United Kingdom
support@pullup.atAT A GLANCE
- The feature and configuration determine which recipient receives information.
- Not every provider is a processor; some run an independent service.
- A directory is not a claim that all contracts, regions or transfer safeguards are identical.
A reading guide. Read the full clauses for their conditions and scope.
On this page
Use your browser’s Find control to search the full text on mobile.
1. How to read this directory
Feature availability and the actual agreement matter.
The directory identifies services found in the reviewed implementation and the general information used for their function. A listed integration can be optional, conditional, limited to a release or an external destination; it is not proof that it processes every user's data.
Some recipients act on instructions, while payment networks, external sellers, app stores, organisers and connected services may act independently for their purposes. The actual processing and contract determine the legal role.
Supplier legal entity, configured region, subprocessor chain and applicable transfer mechanism must match the deployed account/agreement. This page does not invent a signed data-processing contract, universal UK/EU-only hosting or enabled zero-retention arrangement.
2. Functional recipient directory
Only information relevant to the requested function should be shared.
| Provider/service | Enabled function | Information that may be involved |
|---|---|---|
| Vercel | Website/functions, AI Gateway and consent-gated analytics. | Requests, network/operational data; selected model prompts/context; permitted analytics. |
| Supabase | Database, access-controlled storage and real-time/backend functions. | Account/product records, files and encrypted payloads according to their feature. |
| Resend; AWS SES | Enabled transactional, campaign and hosted-email delivery/receipt. | Addresses, subject/body, attachments or their metadata, delivery and safety records. |
| Stripe; PayPal; SumUp | Configured checkout, recurring payments, settlement and refunds. | Order/customer details, provider payment credentials/tokens, payment/risk and settlement status. |
| OpenAI; Groq | Configured assistance/search/moderation models, directly or via gateway. | The prompts, permitted context/excerpts and outcomes described in the AI notice. |
| Google translation; Puter image tools | Translation and optional external image generation. | Selected text/prompts, browser/network data and the provider's account/payment context. |
| Cloudflare STUN; configured TURN operator | WebRTC connectivity and configured call relay. | IP/network addresses, connectivity, timing and relay/session metadata. |
| Apple APNs/PushKit, CallKit and app-store services | Supported app/call notifications and store functions. | Device/push tokens, call/message routing metadata, purchase records where that channel is used. |
| Google account/Gmail; Instagram; music connections such as TIDAL | Chosen account connection or permitted imported content. | Authorised account/profile/content data, scopes and access/refresh tokens as applicable. |
| Mapbox; TfL; OpenStreetMap/Nominatim; Postcodes.io; ipapi | Enabled directions, map, geocoding/postcode and IP-location functions. | Entered routes/coordinates, location queries and network data relevant to the feature. |
| Stay22; external accommodation providers | Nearby accommodation referrals and the external booking service. | Venue/event coordinates, referral/session information and details entered with that provider. |
| Ticketmaster; Eventbrite; Skiddle | External discovery/listing/booking links where enabled. | Search/location criteria and external referral/booking information. |
| Google AdSense; Snap | Consent-gated enabled advertising and measurement. | Permitted browser/device identifiers, network and page/activity data. |
| Security/rate-limit/captcha services, including configured hCaptcha/Upstash paths | Abuse checks and reliability. | Request, network, challenge/session and rate-limit signals. |
| Authorised host/workspace staff and selected apps/webhooks | Event/service operations and scoped business connections. | Permitted guest/order/calendar/business records, selected payloads and action/audit data. |
3. External destinations and authorisation
Following a link or connecting an account changes the context.
A Stay22 or external ticket-provider booking can take place under the external merchant's terms/privacy. A direct Pullup room/service booking is a different workflow and can create records in Pullup as well.
A connected Gmail read-only scope is not hosted Mail ownership or permission for Pullup to send from Gmail. Authorise only scopes needed; revocation stops future authorised access as implemented, not copies already obtained.
A business must have authority for a webhook recipient or connected app. API keys, refresh tokens and webhook secrets are credentials; do not paste them into public channels or model prompts.
4. International processing and safeguards
A global service name does not identify the actual storage region.
Processing/support can occur outside your country. Where restricted-transfer rules apply, the operator must establish a valid mechanism for the relevant data/recipient, such as an applicable adequacy decision or appropriate contractual safeguards with necessary supplementary measures.
A provider's general public policy is not evidence that a particular customer's configuration/contract provides every available safeguard. Ask support for the relevant recipient, country, safeguards and accessible copy/information, subject to lawful redaction.
Further processor changes require the notice, authorisation and objection process in the actual processing agreement/law. A public directory does not replace a business processing schedule.
5. Provider information and questions
Read the relevant service policy as well as Pullup's notice.
Provider public information can change; it does not amend Pullup's accepted commitments automatically. Ask for details tied to the feature and revision rather than assuming every provider uses identical retention/training rules.
For account data and Pullup's processing, use the privacy-rights contact. For an independent external purchase or provider account, that provider may also need to answer. Share a relevant reference, never a password or token.