Subprocessor list template for Vercel and Supabase startups
Teams that ship on Vercel and Supabase usually have a straightforward stack, but the public vendor page still needs enough detail for customers, procurement, and counsel to understand what changed.
The goal is to organize facts and evidence so the page stays current and reviewable. Your counsel decides the actual disclosure requirements.
Why stack-specific pages help
A generic vendor list often forgets the vendors that matter most to a modern SaaS startup: cloud hosting, database hosting, authentication, analytics, and email delivery. If the list is too vague, customer review turns into a manual audit of your architecture.
This template keeps the public page simple while leaving the private tracker to handle reviewers, approval notes, and objection history.
Suggested public fields
- Vendor name and service purpose.
- Data categories that may be processed.
- Processing region or transfer context.
- Status: active, planned, replacing, or under review.
- Page last updated date.
- Contact method for customer questions or objections.
Example table for a modern stack
| Vendor | Purpose | Data categories | Region | Status |
|---|---|---|---|---|
| Vercel | Static hosting and edge delivery | Site requests; account metadata; log data | United States; global edge network | Active |
| Supabase | Database and authentication services | User records; application data; auth tokens | United States; European Union | Active |
| Transactional email provider | Account notices and delivery | Email addresses; delivery metadata | United States | Planned |
What to keep private
Your internal tracker can hold the details customers do not need to see. That helps you avoid overpublishing architecture while still keeping the workflow defensible.
- Internal reviewer name.
- Approval date and evidence location.
- Customer segment affected by the change.
- Notice date and objection deadline.
- Any unresolved legal or procurement questions.
Common gaps for small SaaS teams
Missing update date
Without a visible update date, customers cannot tell whether the page reflects the current stack.
Only listing infrastructure vendors
Cloud vendors are obvious, but delivery and analytics tools are often the ones customers ask about first.
No contact route
Teams need one path for customers to ask questions or object to a change.
No change history
Save the old page version and the new page version so the update can be explained later.
Need the working template?
NoticeKit Starter and Pro include the subprocessor list template, CSV format, notice copy, and evidence workflow that fit this kind of stack page.