Subprocessor and Data Location Mapping
Find where data goes through your suppliers.
Added October 15, 2026. Written with AI assistance and checked for clarity and placeholders; not reviewed by a lawyer, accountant, clinician or other professional. How these prompts are made
The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.
[VERIFY] is an editorial flag, not a blank to fill. Wherever the prompt shows [VERIFY], check that item against a reliable source before you use it (what [VERIFY] means).
Map data flows. Vendors and the data each receives: [VENDOR_DATA]. Their subprocessors and locations if known: [SUBPROCESSORS]. Our commitments to customers: [COMMITMENTS]. Draw the flow in text, mark transfers abroad, repeated holders of the same data and vendors that lack information. Compare with our commitments and flag mismatches. Return a map table, questions to ask vendors and a register template. Cross-border rules need professional advice [VERIFY] for [JURISDICTION]. Add a worked data flow in text: customer form to our website, then to the email tool in country A, then to the vendor's support platform, whose subprocessor stores backups in country B. Mark the cross-border transfers and the entities that hold copies. Compare with the commitment that data stays in one region and flag the mismatch. Provide a register with columns for vendor, data, purpose, location, subprocessors, last reviewed. Add a worked register row: vendor, email tool; data, names and emails; purpose, newsletters; location, country A; subprocessors, support platform in country B; last reviewed, date. Add a schedule for review and a trigger when a vendor announces a new subprocessor.
Fill in before use
Optional: type your details and the prompt above updates. Nothing is saved or sent.
Replace each bracketed placeholder with your own details, then paste into Any AI or another assistant.