Why we use third parties
Building on specialised, security-focused providers lets us ship a better, safer product than reinventing every layer ourselves. We choose providers carefully and limit what we share with each.
What we rely on
| Category | Providers | Purpose |
|---|---|---|
| Authentication & database | Supabase | Sign-in and core data for Vault One |
| Payments | Stripe | Subscription billing |
| Resend, mijn.host | Transactional email, mailboxes, and DNS | |
| Hosting | Vercel, Railway | Websites and application/API hosting |
| Monitoring | Sentry (optional) | Error and performance monitoring |
| Sign-in providers | Google, Apple | Optional OAuth sign-in you choose to use |
| Finance connectors (product) | bunq, Kraken, generic APIs | Read-only, device-side connections you authorise in Vault One |
Their terms
Each provider operates under its own terms and privacy policy. Where they process personal data on our behalf, they appear on the Subprocessor List. Connectors and sign-in providers you choose act under their own agreements with you.