Sub-processors

Last updated: 30 August 2026

Levered AI Ltd, trading as Marklet, uses the following sub-processors to provide the Marklet service. This is the current list referred to in Schedule 3 of the Marklet Data Processing Agreement.

We give workspace administrators at least 30 days' notice by email before a new sub-processor begins material processing of customer personal data, except where an urgent change is reasonably necessary for security, continuity or law.

Current sub-processors

Supabase

Purpose: Database, authentication and file storage

Primary location: Ireland / EEA; provider is US-established

Transfer position: Adequacy for EEA hosting; appropriate safeguard where a restricted transfer occurs

Railway

Purpose: Application hosting and infrastructure

Primary location: Netherlands / EEA; provider is US-established

Transfer position: Adequacy for EEA hosting; appropriate safeguard where a restricted transfer occurs

Google Cloud

Purpose: AI inference and processing

Primary location: European Union; contracting entity in Ireland

Transfer position: Adequacy for EEA processing

Resend

Purpose: Transactional email delivery

Primary location: United States

Transfer position: Applicable adequacy or appropriate safeguard under provider contract

Cloudflare

Purpose: Edge network, security and Turnstile bot protection

Primary location: Global

Transfer position: Applicable adequacy or appropriate safeguard under provider contract

Google, Apple and Mozilla

Purpose: Optional browser push notification delivery

Primary location: Global

Transfer position: Applicable adequacy or appropriate safeguard under the relevant provider terms

Questions and objections

Questions about a sub-processor, or an objection to a change under the DPA, may be sent to privacy@marklet.io. A provider the customer selects and connects itself, such as an accounting integration, is not a sub-processor appointed by Marklet; its own role is determined by its arrangement with the customer. Those providers are described in the Privacy Policy.