Sign inRequest a demo

Sub-processors

Last updated 26 August 2026

Every third party that can process personal data on our behalf, what each one does, and whether it can reach customer content or only account data. Changes are notified ten days in advance.

  1. 1The list

    Sub-processorWhat it doesWhat it can reach
    Microsoft AzureUnited States (Central US) by defaultHosting for the application, the database and project media. This is where the platform runs and where customer content is stored.Can process customer content
    ResendUnited StatesDelivery of transactional email: invitations, notifications about work, and security messages. Receives the recipient address and the text of the message; it has no access to project data.Account data only

    That is the whole list. It is short because the platform is built to keep it short: analytics, session recording, support widgets, advertising and chat tools are not used, and none of them run on pages where customer content appears.

  2. 2What counts as a sub-processor here

    A sub-processor is a third party that processes personal data on our behalf in the course of providing Largwit. Vendors that never touch personal data belonging to a customer, such as a source-code host or an accounting package, are not listed, because listing them would pad the page and make the entries that matter harder to find.

    The column that matters most is the third one. Can process customer content means the party could, in principle, hold a customer’s datasets and the work produced from them. Account data only means it sees who uses the platform, not what they are working on.

  3. 3Model providers

    Largwit can be configured to use model endpoints for automated evaluation. That is off for every organization until its owner turns it on, and the provider engaged for it is named in that customer’s data processing terms before the feature is enabled for them.

    No model provider is engaged by default, and no customer content is sent to any model provider unless a customer has configured that themselves. Where a customer brings their own endpoint, the relationship is theirs and the provider is not our sub-processor.

  4. 4How you find out about a change

    Before a new sub-processor may process customer content we give at least ten days’ notice, and a customer may object within that window on reasonable data protection grounds. The full mechanism, including what happens if an objection cannot be resolved, is in section 6 of the Data Processing Addendum.

    To be told directly rather than having to watch this page, write to hello@largwit.com and ask to be added to the notification list.

  5. 5Regional hosting

    The region above is the default. Where an engagement requires data to stay in a particular jurisdiction, that is agreed as part of the engagement and the hosting region is set accordingly. Ask before signing rather than after.