Back to Sessionkeep

Sub-processors

The third parties we rely on to run Sessionkeep, what each one does, and where it processes data.

Last updated August 4, 2026

How to read this page

How to read this page

When you use Sessionkeep to hold clinical records, you are the data controller and we act as your processor. To provide the service we in turn rely on the sub-processors listed below. Each one is bound by a written contract that imposes the same data protection obligations we owe you.

The database that holds your clinical records sits in the European Union and never leaves it. Where a sub-processor operates outside the EEA, the transfer is covered by the European Commission's Standard Contractual Clauses.

Current sub-processors

Current sub-processors

ProviderPurposeProcessing locationTransfer basis
SupabaseDatabase, authentication, file storageEuropean Union (Frankfurt, Germany)No transfer outside the EEA
VercelApplication hosting and content deliveryEuropean Union and United StatesStandard Contractual Clauses
OpenAIAI drafting, extraction, transcription and embeddingsUnited StatesStandard Contractual Clauses, zero data retention where available, no training on submitted data
ResendTransactional email (agenda, reminders, portal, sign-in)European Union (Ireland)No transfer outside the EEA
StripeSubscription payments and billingEuropean Union and United StatesStandard Contractual Clauses
Daily.coVideo sessions (telehealth). Media is relayed, never recordedUnited States and global relay networkStandard Contractual Clauses
SentryError monitoring. Client data is stripped before events are sentEuropean Union (Germany)No transfer outside the EEA
CloudflareDNS and domain registrationGlobal networkStandard Contractual Clauses

What never reaches a sub-processor

What never reaches a sub-processor

  • Clinical content is never sent to our error monitoring: identifiers, request bodies and local variables are stripped before an event leaves the application.
  • Video sessions are not recorded by the video provider. Recording and transcription happen only through the consent-gated capture flow inside Sessionkeep.
  • Email never carries clinical content. Agenda, reminder and portal emails contain only names, dates, times and links.
  • Data submitted to the AI provider is used to produce your output and is not used to train models.

Changes to this list

Changes to this list

We will update this page before a new sub-processor starts processing personal data on your behalf, and we will notify account holders by email. If you object to a new sub-processor on reasonable data protection grounds, you may terminate your subscription and export your data before the change takes effect.

Contact

Contact

WORKSJO LTD, 71-75 Shelton Street, Covent Garden, London WC2H 9JQ, United Kingdom. Companies House 15824979. privacy@sessionkeep.app