---
title: Vet Vendor AI Security & Subprocessors | futurecoworker.ai
description: Screen AI and SaaS vendors fast with targeted security questions covering zero-data-retention APIs, LLM subprocessors, SOC 2 Type II, and tenant isolation.
canonical: "https://futurecoworker.ai/j/draft-vendor-security-and-ai-subprocessor-questionnaire"
modified: 2026-11-14
author: futurecoworker.ai editorial team
source: "https://futurecoworker.ai"
category: RFP Scoring, Vendor Audits & SaaS Procurement
category_url: "https://futurecoworker.ai/j#group-rfp-vendor-evaluation-and-procurement"
---

# Vet Vendor SOC 2 Scope, Model Training Policies, and Subprocessor Data Retention

> Skip generic 300-row firewall questionnaires and ask the 15 sharp questions that expose whether an AI vendor trains on your data or logs prompts for 30 days.

## Prepared starting prompt

Our Sales & Ops teams want to connect an AI email & meeting assistant to Google Workspace and HubSpot. Draft a targeted 15-question AI Security & Subprocessor Screening Questionnaire so we spot red flags before looping in formal InfoSec.

### Quick scenarios
- **15-question AI vendor fast screen:** List the 15 highest-signal questions vetting LLM model training, zero-retention API contracts, subprocessor chains, and OAuth scope breadth.
- **Spot OAuth permission overreach:** Explain how to audit requested Google Workspace / Microsoft 365 / Slack OAuth scopes (read-all-org vs user-forwarded) during vendor vetting.
- **Decode SOC 2 Type I vs Type II claims:** Give business buyers a 5-point cheat sheet spotting 'SOC 2 hosted on AWS' marketing spin vs real audited SOC 2 Type II reports.

- [Preview Workflow & Join Waitlist](https://futurecoworker.ai/#waitlist-2e2d44)

*Pre-screening checklists help business buyers eliminate high-risk tools early; formal vendor security approval, Data Processing Agreements (DPAs), and compliance attestations must be signed off by InfoSec and Legal.*

## Five red flags business buyers can catch BEFORE bothering InfoSec

1. **Distinguish 'Hosted on SOC 2 AWS' from the vendor's OWN SOC 2 Type II** — Early startups often slap a SOC 2 badge on pricing pages because AWS has SOC 2—ask explicitly for the vendor's own audited SOC 2 Type II report and bridge letter.
2. **Verify 'Zero Data Retention (ZDR)' at the underlying LLM subprocessor layer** — A vendor promising 'we don't train our models' means little if they call standard non-enterprise LLM APIs that retain prompts 30 days for abuse review—check subprocessor terms.
3. **Audit OAuth Scope Blast Radius (`Read All Mail` vs `Scoped Alias/Label`)** — Reject tools demanding tenant-wide super-admin read/delete permissions across the CEO's mailbox when scoped user-level or forwarded-thread permissions suffice.
4. **Confirm hard deletion SLAs for vector embeddings, caches, and backups** — Ask what happens within 30 days of contract termination or GDPR erasure: do derived vector search indexes and cached summaries purge alongside primary rows?

## Frequently Asked Questions

### What is the difference between SOC 2 Type I and SOC 2 Type II?

Type I only verifies that security controls existed on paper on a single snapshot date, whereas Type II proves an independent auditor tested that controls actually operated over 6–12 months.

### Why should we check a vendor's `/subprocessors` page before signing?

An AI app is only as private as the third-party transcription, analytics, session-replay, and LLM hosts it pipes your text into—verify their subprocessor notification window.

### Can we turn off human support-engineer access to our prompts inside AI tools?

Good enterprise vendors enforce explicit 'Customer-Initiated Support Access Only' with audit logs so vendor engineers cannot browse tenant workspace prompts without your ticket permission.

## Learn more

- [Will your team survive the AI communication revolution?](https://futurecoworker.ai/enterprise-ai-communication-platform.md)
- [Legal secretary roles: beyond administrative support](https://futurecoworker.ai/legal-secretary.md)
- [Risks of hiring someone to process data](https://futurecoworker.ai/hire-someone-to-process-data.md)
- [AI-driven enterprise collaboration: separating hype from reality](https://futurecoworker.ai/ai-driven-enterprise-collaboration.md)
- [Enterprise AI workflow automation tools: rewards and hidden risks](https://futurecoworker.ai/enterprise-ai-workflow-automation-tools.md)
- [Hire someone to sort emails or use AI instead?](https://futurecoworker.ai/hire-someone-to-sort-emails.md)

## Related tasks in this category

- [Build a Weighted RFP Evaluation Matrix That Separates Real Capabilities From Demo Hype](https://futurecoworker.ai/j/build-weighted-rfp-vendor-scoring-matrix.md)
- [Uncover Per-Seat Minimums, AI Credit Caps, and Auto-Renewal Traps in SaaS Quotes](https://futurecoworker.ai/j/audit-saas-per-seat-pricing-and-hidden-overage-traps.md)
- [Audit Seat Utilization and Overlapping Tools 90 Days Before Vendor Renewal](https://futurecoworker.ai/j/prepare-saas-renewal-consolidation-and-negotiation-brief.md)
- [Evaluate Total 3-Year Cost of Building an Internal Script vs Buying Enterprise Software](https://futurecoworker.ai/j/compare-build-internal-tool-vs-buy-enterprise-saas.md)
- [Compare Three Competing Vendor Proposals Side-by-Side for Finance & Exec Sign-Off](https://futurecoworker.ai/j/summarize-three-competing-vendor-proposals-for-cfo.md)
- [Define Hard Pass/Fail Pilot Criteria Before Starting a 14-Day Vendor Trial](https://futurecoworker.ai/j/script-proof-of-concept-pilot-success-criteria.md)

---

*Published by **Wondel.ai sp. z o.o.** · [futurecoworker.ai](https://futurecoworker.ai) · [About](https://futurecoworker.ai/about) · [Editorial Guidelines](https://futurecoworker.ai/editorial) · [Contact](https://futurecoworker.ai/contact) · [Wondel.ai Products](https://wondel.ai/products)*