Data handling
This page states facts rather than claims a posture. It is written for the person who opens it during a vendor review, so it leads with the answer that most often ends one: Fruxal's infrastructure is hosted in the United States, not in Canada.
Every third party that can hold or process data for Fruxal, what it does, and where it processes. The last three serve features of the Fruxal platform and never see a review. This list is maintained as the stack changes.
| Service | Purpose | Processing region |
|---|---|---|
| Vercel | Application hosting and content delivery | United States (us-east-1) |
| Supabase (AWS) | Primary database and document storage | United States (AWS us-east-1) |
| Anthropic | Analytical API. Reads extracts to classify line items and draft findings. No training on submitted data. | United States |
| Plaid | Bank connection, where the client chooses to connect one. Credentials never reach Fruxal. | United States and Canada |
| Intuit (QuickBooks) | Ledger extraction, where the client authorises it | United States |
| Stripe | Payment processing. Card numbers never touch Fruxal systems. | United States and Ireland |
| Resend | Transactional email | United States |
| PostHog | Product analytics on the public site | United States |
| Sentry | Error monitoring | United States |
| Email (Google Workspace), meeting scheduling and optional sign-in | Google data centres, United States and elsewhere | |
| Amazon Web Services (S3) | Storage of files uploaded to the Fruxal platform | United States (us-east-1) |
| OpenAI | Fruxal platform only: text-to-speech and search indexing | United States |
| Cohere | Fruxal platform only: search indexing | North America |
| AssemblyAI and Vapi | Fruxal platform only: call transcription and voice calls | United States |
Last reviewed: