Subprocessors
Last updated June 18, 2026
We use the following subprocessors to provide the service. Each receives only the data needed for its function. We'll update this page and notify customers before adding or changing a subprocessor.
| Subprocessor | Purpose | Data shared | Location |
|---|---|---|---|
| Clerk | Authentication & org/member identity | Name, email, org/team membership | USA |
| Stripe | Subscription billing & payments | Billing contact, subscription state (no card data seen by us) | USA / global |
| Neon | Postgres database hosting | All stored roll-ups, scrubbed abstracts, identity/billing metadata | USA |
| Vercel | Application hosting & CDN | Request metadata; serves the app + API | USA / global |
| OpenAI | Embeddings of scrubbed insight abstracts (text-embedding-3-small) for search | Scrubbed abstract text only — never prompts, keys, or per-call data | USA |
| Resend | Transactional email (alerts, deletion confirmations) | Recipient email + message content | USA |
Notably absent: there is no provider-token proxy — we never receive your OpenAI/Anthropic/etc. keys or route your model calls, so those providers are your processors, not ours.
Questions or to subscribe to change notifications: privacy@llmspendguard.com.
Ensight.ai · 204 2nd Ave, #204, San Mateo, CA 94401 · privacy@llmspendguard.com (privacy) · support@llmspendguard.com (support)
Privacy · Terms · DPA · Subprocessors