Workframe

Subprocessors

Last updated 24 August 2026 · Back to workframeapp.com

Draft — not yet in force. The values highlighted like this are unresolved and must be filled in, and the whole set needs a lawyer's review, before these pages are linked from the product or relied on by an ethics committee. Until then this page describes intended practice, not a binding commitment.

These are every third party that processes personal data on our behalf. The list is complete, and we will notify account holders before it changes.

ProviderWhat it does for usData it can reachLocation
Cloudflare, Inc. Edge compute (Workers), study database (D1), media storage (R2), DNS and CDN Everything Workframe stores: researcher accounts, studies, uploaded media, and all participant study data United States, with processing at global edge locations
Clerk, Inc. Researcher sign-in and account identity The email address a researcher signs in with, and the session that keeps them signed in. Nothing else — the participant hostname never calls Clerk, so no participant or study data reaches it. United States

What is deliberately absent

No analytics provider. No advertising or marketing platform. No session-replay or product-telemetry vendor. No error-reporting service. No email marketing tool. No third-party font, script or image host on any surface, including this one. Nothing on the participant surface at all.

Transfers

Both providers are US companies. Transfers out of the UK/EEA rely on the Standard Contractual Clauses, and the UK International Data Transfer Addendum where relevant, as incorporated in each provider's own data processing terms. Copies are available on request.

Changes

We will notify account holders [notice period — 30 days is the usual commitment] before adding or replacing a subprocessor, so that there is time to object. Objection rights are set out in the Data Processing Agreement.