Skip to main content

Sub-processors

Effective date: 19 November 2025 · Last updated: 30 October 2026

To operate our Services securely and reliably, Bleepy engages a small number of trusted third-party providers that process personal data on our behalf.

Overview

To operate our Services securely and reliably, Bleepy ("we," "us," or "our") engages a small number of trusted third-party providers ("sub-processors") that process personal data on our behalf.

We only use sub-processors that:

  • Meet security, privacy, and compliance standards consistent with UK GDPR and EU GDPR;
  • Operate under written data-processing terms; and
  • Provide appropriate technical and organisational safeguards, including, where data leaves the UK, UK adequacy regulations or the UK International Data Transfer Agreement (IDTA) or UK Addendum to the EU Standard Contractual Clauses.

This list reflects our current sub-processors and may change as our Services evolve.

1. Infrastructure and hosting

ProviderPurposeRegion of processingSafeguards
SupabaseDatabase and file storage only. Sign-in is NextAuth (session cookie), not Supabase Auth.UK (London)DPA signed; data stored in the London region
Vercel Inc.Website hosting and deployment, and anonymous page-speed measurementGlobal (edge network)DPA signed, SCCs and regional routing controls
Cloudflare, Inc.DNS for bleepy.co.ukGlobal (data centres worldwide)DPA signed, GDPR-compliant, SCCs in place

2. Communications

ProviderPurposeRegion of processingSafeguards
Microsoft 365 / AzureEmail services and certificate deliveryEU / UKDPA automatically included in Microsoft Online Services Terms
Browser push services (Google, Mozilla, Apple, Microsoft)Deliver push notifications you have switched on; the message content is encryptedThe browser maker's own serviceThe service sees only where to deliver each message and when, not what it says

3. AI, analytics and location services

ProviderPurposeRegion of processingSafeguards
OpenAIOptional AI features, which each organisation can switch off: help drafting text, reading uploaded timetables and documents, describing pictures, summarising feedback, suggesting curriculum links, and answering questions from Bleepy's help articles and about reports. Only the text or picture sent for that task. No patient data.USDPA signed, SCCs in place. Not used to train OpenAI's models; kept by OpenAI for up to 30 days to check for misuse
Google AnalyticsWebsite analytics and usage statisticsUS / EUSCCs and GDPR-compliant processing
Google Maps / PlacesMaps on event pages, and finding a venue when staff set up events and organisationsUS / EUGoogle Cloud DPA / CDPA accepted; SCCs
Google reCAPTCHABot protection on the contact, site-feedback and create-account forms (on the sign-in page, only once the create-account form is opened)US / EUGoogle Cloud DPA / CDPA accepted; SCCs
OpenWeatherSigned-in dashboard weather for the organisation locationEU / USNo account personal data; city or coordinates only
OpenStreetMap NominatimFinding the town staff type when they set the organisation's location for the dashboard weather, when OpenWeather finds nothing; called from our serverUK / EUNo personal data; only the place name typed

4. Payments

ProviderPurposeRegion of processingSafeguards
Stripe, Inc. / Stripe Payments UK LtdCard payments for paid teaching events via Stripe Connect. Card numbers stay at Stripe and never hit Bleepy.EU / UK / US (Stripe)DPA, PCI DSS. The organisation is the merchant. Bleepy does not store card data.

Updates

We review our sub-processors periodically and update this page as needed.

Material changes are communicated to organisational customers where required by agreement.

The “Last updated” date above shows the most recent revision.

Contact

For questions about our sub-processors, please contact us at:

This sub-processors list is effective as of 19 November 2025 and was last updated on 30 October 2026.

Sub-processors | Bleepy