Qmo Sub-processor List
Contents
Last updated: [TBD] · Map2Close Inc. · legal@map2close.com
Map2Close uses the sub-processors below to provide Qmo. Each is bound by a written contract with data protection obligations at least as protective as our Data Processing Addendum, and AI and transcription providers are prohibited from training their models on customer data. We give at least 30 days' notice before adding a new sub-processor; to receive notices, ask your account administrator or email legal@map2close.com.
[TBD: Youssef to complete every row, delete unused rows, and confirm the last two columns against each provider's contract and account settings. The two right-hand columns are for internal review and come off before publishing.]
| Sub-processor | Purpose | Customer data processed | Location |
|---|---|---|---|
| [TBD] | Cloud hosting and compute | All Customer Data | [TBD] |
| [TBD] | Database and file storage | All Customer Data | [TBD] |
| [TBD] | Large language model (AI) processing | Transcripts, CRM context, cards, prompts | [TBD] |
| [TBD] | Speech-to-text transcription | Call audio | [TBD] |
| [TBD] | Telephony and dialer | Call audio, phone numbers | [TBD] |
| [TBD] | Transactional email | Names, email addresses, message content | [TBD] |
| [TBD] | Payments | Billing contact details (card data handled by the processor) | [TBD] |
| [TBD] | Error monitoring and logging | Usage data, technical data | [TBD] |
| [TBD] | Product analytics | Usage data | [TBD] |
Connected Accounts that a customer chooses to link, such as its CRM or calendar, are not our sub-processors; they act for the customer under the customer's own agreement with them.
