Last updated 2026-09-08
This page describes how the platform works today, and we keep it current as the product changes. It is not legal advice.
This list is a draft and must be confirmed before launch
🔴 THE TABLE BELOW HAS NOT BEEN CONFIRMED AGAINST THE RUNNING SYSTEM, AND IT IS THE SINGLE MOST IMPORTANT OUTSTANDING ITEM ON THIS SITE. Publishing an inaccurate sub-processor list breaches the Data Processing Agreement on the previous page, which is a promise made to your own customers. It is presented as a draft rather than left empty because an empty page tells a reader nothing at all, but nobody should rely on it until it is verified.
Two entries are listed because there is direct evidence in the platform that they are used. Four categories are listed as unfilled because the platform must use something for each of them and this page cannot guess what. Fill both parts in from the services actually in production, then delete this section so the table stands on its own.
| Sub-processor | What it does | Data it can reach | Status |
|---|---|---|---|
| Stripe | Takes payments and holds the subscription for each workspace | Billing contact and payment details. No workspace records | ⚠️ Confirm |
| Google Analytics | Counts visits to this marketing website only | Website usage. No account data, no workspace records | ⚠️ Confirm |
| Hosting provider | Runs the servers and the database | Everything, by definition | 🔴 Not filled in |
| Email delivery | Sends transactional mail and anything your workspace sends | Recipient addresses and message content | 🔴 Not filled in |
| AI provider | Generates the drafts and suggestions described in the privacy policy | Only what is sent with a specific request. Never used for training | 🔴 Not filled in |
| Error reporting | Records crashes so they can be fixed | Technical context, which can incidentally include a record identifier | 🔴 Not filled in |
The "Where it operates" column that this table should also carry is deliberately absent rather than guessed. It is required for the transfer statements in the DPA and must be added with the rest.
What a sub-processor is, and what it is not
A sub-processor is a company we use that can reach personal data you gave us. A supplier we buy something from that never touches your data is not one, and padding this list with those would make it longer and less useful.
Your own connected accounts are also not sub-processors. If you connect a mail account, an ad platform or your own AI provider key to a workspace, you have instructed us to talk to a service you chose. That relationship is yours, it is governed by your agreement with them, and you can disconnect it.
How changes are announced
We publish a new sub-processor on this page before it starts processing, and we email workspace owners who have asked to be told.
You can object on reasonable data protection grounds. If we cannot resolve the objection, either by keeping your data with the existing arrangement or by finding another route, you can end the agreement without penalty for the unused remainder of your term.
To be notified of changes, write to support@execcortex.com and ask to be added to the list.
Questions about any of this, or want to exercise a right? Open a data request or write to us.