Subprocessors
UNTAP LLC uses the following third parties to provide the service. Each is bound by a written agreement that restricts its use of customer data to providing its service to us, and we remain responsible for their performance.
"Return content" means uploaded tax-return files and the data extracted from them.
| Subprocessor | Purpose | Data processed | Receives return content? | Location |
|---|---|---|---|---|
| Google LLC (Google Cloud) | Application hosting (Cloud Run); file storage (Cloud Storage); AI document extraction (Vertex AI); background job queue (Cloud Tasks, which holds only a return's id and when it was queued) | Return content (stored files, and during processing); beta requests made on our website before we launched paid plans (email and the details people chose to give); operational logs (no return content) | Yes | United States (us-central1; AI in Google's US multi-region). Operational logs are kept in us-central1 for 30 days. Google keeps its own audit log of administrative changes to our cloud project (no customer data) in a global store that cannot be moved |
| Supabase, Inc. (infrastructure on Amazon Web Services) | Database, user authentication | Return content (extracted data and financials); account data (names, emails); feedback sent in the app; beta requests made on our website before we launched paid plans (email and the details people chose to give) | Yes | United States (region: us-west-2 (Oregon)) |
| Google LLC (Google Workspace) | Our email, including support | Messages customers send us, and any files attached to them | Only if a customer emails it to us. Please upload returns through the app instead; support never needs them by email | United States |
| Twilio Inc. (SendGrid) | Account emails: verification codes, password-reset and invitation emails, notifications; until we launched paid plans, beta requests emailed to our team. Click and open tracking off | Account data (names, email addresses); beta requests made on our website before we launched paid plans | No | Twilio's global infrastructure (a US company; not limited to one country) |
| Stripe, Inc. (Stripe) | Payment processing (billing) | Admin email address; payment details entered at checkout or in the billing portal. We keep only Stripe customer and subscription ids and billing dates | No | United States |
Changes
We give customers at least 30 days' notice before adding or replacing a subprocessor, by email to each customer's admins and by updating this page. A customer may object in writing during that period; if we cannot reasonably accommodate the objection, the customer may terminate and receive a pro-rata refund of prepaid fees (Terms §8).
§7216 note for CPA firms: your clients' consents must cover every subprocessor that receives return content through the service (Terms §3.2). A new one that receives return content is not covered by consents your clients have already signed; the 30-day notice exists partly so you can collect updated consents.
History
| Date | Change |
|---|---|
| October 22, 2026 | Initial list |
| October 31, 2026 | Said where operational logs are kept and what the job queue holds. No subprocessor added or removed |
| November 4, 2026 | The §7216 note now says your clients' consents must cover every subprocessor. No subprocessor added or removed |
| November 10, 2026 | Beta requests are now described as made before we launched paid plans. No subprocessor added or removed |
Last updated: November 10, 2026