01Overview
VesperWise uses a small number of third-party service providers (“subprocessors”) to help us operate the Service.
We give each subprocessor only the minimum data required to perform their service. No subprocessor receives access to API keys or billing data (except Polar for payment processing). Enrichment providers receive only the company domain or person identifiers needed for each lookup, never your uploaded lists as a whole.
02Current subprocessors
The table below lists the infrastructure subprocessors we use and the service they provide.
| Provider | Service | Location |
|---|---|---|
| Clerk | Authentication, MFA, session management (bot protection on sign-up runs on Cloudflare) | United States |
| Polar.sh | Payment processing (billing, subscription management, card data storage) | Norway (EEA) |
| Supabase | Postgres database, object storage | United States |
| Vercel | Hosting, serverless functions, edge CDN | United States |
| OpenRouter | AI model routing | United States |
| Resend | Transactional email (contact form, notifications) | United States |
| Google Analytics | Website usage analytics — only after cookie consent | United States |
Data enrichment providers
When you score a company or a person, we look up public signals with commercial data providers under contract. They receive only the company domain, company name, or person identifiers needed for that lookup, not your account details.
Card data: VesperWise never receives or stores raw card data. Polar.sh collects payment details and stores them with Stripe. We receive only metadata (last 4 digits, brand, expiry) via webhook.
AI processing: OpenRouter proxies requests to AI providers. See our Privacy Policy § 06 AI processing for details.
03Change notice
Before adding a new subprocessor, we will update this page. For questions about subprocessor changes, email support@vesperwise.com.
04Security standards
We select subprocessors that maintain encryption in transit and at rest. For full security details, see our Security page.