FundView Subprocessor List
FundView Finance LLC d/b/a FundView uses the subprocessors below to deliver the FundView service. Each one is bound by its own contractual confidentiality and security obligations, and each is limited to the processing described here.
Current subprocessors
| Subprocessor | Role in the Service | District Data it processes | Location | Retention |
|---|---|---|---|---|
| Supabase, Inc. (United States, on Amazon Web Services) | The District's dedicated PostgreSQL database, authentication directory, and object storage for uploaded files | All District Data at rest, including financial records, projections, uploaded documents, and user records | United States | For the life of the deployment. Automated daily backups retained seven days. |
| Vercel Inc. (United States) | Application hosting, serverless compute, and content delivery for the District's deployment | District Data in transit during a request, held only for the duration of processing. Standard request and function logs. | United States | No District Data stored at rest. Provider request and function logs follow the provider's documented retention. |
| Anthropic PBC (United States) | The AI model behind narratives, analysis, the assistant, and document extraction | Only the District Data included in a given prompt, which is the minimum reasonably necessary for the requested feature | United States | Anthropic does not train its models on inputs or outputs from its commercial API by default, and FundView has not opted District Data into any training or feedback program. Anthropic deletes API inputs and outputs from its backend within 30 days of receipt or generation, except where its published policy requires longer to enforce its usage policy. |
| OpenAI OpCo, LLC (United States) | The GPT-6 Sol model, through the OpenAI API, for Ask FundView (the in-app assistant), and as a backup model for narratives, analysis, the assistant, and document extraction when Anthropic, the primary AI provider, declines a request or is unavailable | Only the District Data included in a given prompt, which is the minimum reasonably necessary for the requested feature | The United States and other countries where OpenAI and its cloud infrastructure providers operate, as listed on OpenAI's published sub-processor list. | OpenAI does not use data sent to its API to train or improve its models unless the customer opts in, and FundView has not opted District Data into any training or data-sharing program. FundView sends each request with OpenAI's store setting turned off. OpenAI keeps abuse monitoring logs, which may include prompts and responses, for up to 30 days by default, or longer where required by law or reasonably necessary to protect its services or others from harm. |
| Resend (Plus Five Five, Inc.) (United States) | Transactional and notification email, such as report reminders, board digests, deadline nudges, and operational alerts | Recipient name and District email address, and the contents of the message, which may include figures drawn from District Data | United States | Message and delivery records follow the provider's documented retention. |
| Google LLC (United States) | Identity provider for Sign in with Google, using the District's own Google Workspace account | Name, email address, and profile image presented at sign-in. No other District Data is sent to Google. | United States | Governed by the District's own agreement with Google. FundView stores the email address and name in the District's own deployment. |
Notes
FundView does not use analytics, advertising, session-recording, or user-profiling services inside a District's deployment.
Vercel Web Analytics runs on the public marketing site at fundviewk12.com only. It does not run inside any District deployment and processes no District Data.
FundView does not grant any subprocessor administrative access to a District's deployment. Each subprocessor has only the access inherent in operating the infrastructure it provides.
Changes to this list
FundView will give each District at least 30 days written notice before a new or replacement subprocessor begins processing District Data, except that an emergency replacement may be made first with notice promptly afterward. A District may object during that period on reasonable data-protection or security grounds, and the process in Section 8 of the Data Protection and Security Addendum applies.
Questions about this list may be sent to support@fundviewk12.com.
Change log
| Date | Change |
|---|---|
| September 29, 2026 | Version 1.1. Added OpenAI OpCo, LLC as a second AI model provider. Version 1.0 remains available at /legal/v1/subprocessors. |
| August 28, 2026 | Version 1.0 published. First list published under the Data Protection and Security Addendum version 2.0. |