Loading
Loading
Last updated: April 6, 2026
Viva La Tax may be used in self-hosted mode or through a separately operated hosted deployment. This Privacy Policy explains how project code handles data and what a hosted operator may collect to provide the service. If you disagree with this policy, stop using the Service or, for the official hosted Viva La Tax service, contact support@vivalatax.com. If you use another hosted deployment, contact that operator instead.
In self-hosted mode, your return data is stored in browser localStorage on your device by default. The project does not send that local data to a project-operated remote service unless you explicitly use optional features in your deployment that call an external provider. If you enable optional AI helper or document-analysis features, selected prompts, summaries, or document text may be sent transiently to the providers you configured. There are no advertising trackers in the project code, and your local data remains under your control.
In hosted mode, account identity, subscription state, reminder settings, AI usage and budget metadata, and privacy-safe workspace shells are stored in a Postgres database solely to provide the Service's hosted software functionality. Authentication is handled via BetterAuth-compatible session cookies. Billing is handled via Stripe, and Stripe's privacy policy applies to payment data. We do not store your credit card numbers, and we do not durably store raw uploaded tax forms on our servers.
We collect your email address for authentication, basic account information, Stripe customer and subscription metadata, workspace identifiers, progress markers, checklist state, reminder settings, AI usage and budget records, and redacted derived summaries needed to operate the hosted account. Billing information such as card number and billing address is collected and processed by Stripe, and we receive payment status metadata only. If you invoke optional AI helper or document-analysis features, selected prompts, redacted workspace summaries, or redacted document text may be transmitted transiently to configured model providers. We do not durably collect raw uploaded tax forms, raw OCR output, extracted source-document JSON, Social Security numbers, routing numbers, or account numbers on our servers.
We never sell your data. We never use your data for advertising. We do not train our own AI or machine learning models on your tax data. We do not monetize your personal information. We do not keep raw tax forms in durable hosted storage. When third-party payment or model providers are used to deliver a feature you invoked, those providers process data under their own terms and privacy policies.
Like most web services, we collect routine technical information including IP addresses, device type, browser details, timestamps, and referring pages. This information is used for server administration, security monitoring, and understanding aggregate usage patterns. None of this information personally identifies you on its own.
You can delete your data at any time. In self-hosted mode, clear your browser's localStorage. For the official hosted Viva La Tax service, email support@vivalatax.com to request account deletion. If you use another hosted deployment, contact that operator instead. Deletion removes your stored workspace shells, reminder settings, AI usage and budget metadata, and account metadata from hosted storage. Raw uploaded forms are not retained in durable hosted storage after processing completes. Third-party providers may retain transient request or logging data under their own policies.
Hosted deployments may use third-party services such as Stripe for payment processing and model providers such as OpenAI or Google Gemini for optional AI helper or document-analysis features. Those providers have their own terms and privacy policies, and we do not control them. Review the policies of the deployment and providers you choose to use.
Viva La Tax does not address anyone under the age of 18. We do not knowingly collect personal information from children. If you believe a hosted deployment has collected information from a child, contact that deployment's operator.
We use commercially reasonable measures to protect your data, including encryption in transit (HTTPS) and at rest. However, no method of transmission over the Internet and no method of electronic storage is 100% secure. We cannot guarantee absolute security, but we take it seriously and continuously work to improve our protections.
All data-handling code in this project is auditable. You do not have to take an operator's word for how your data is handled. Review the repository you cloned or the published source for the deployment you are using.
If you are a California resident, you have the right to know what personal information we collect, request deletion of your personal information, and opt out of any sale of personal information (we don't sell it). For the official hosted Viva La Tax service, email support@vivalatax.com to request access, correction, or deletion of your hosted account data. If you use another hosted deployment, contact that operator's support address.
To the maximum extent permitted by law, the project maintainers and any independent hosted operator disclaim liability for damages arising from your use of the Service or any breach of this Privacy Policy.
Any hosted deployment may publish its own governing-law and jurisdiction terms. For self-hosted use of the open-source project, consult the repository license and any terms published by the operator of the deployment you choose to use.
We may update this Privacy Policy from time to time. For material changes, we will notify you by email or by posting a prominent notice on the Service before the changes take effect. Your continued use of the Service after changes are posted constitutes acceptance of the revised policy.
If you have questions or concerns about this Privacy Policy for the official hosted Viva La Tax service, email support@vivalatax.com. If you cloned or self-hosted the project yourself, use the repository support channels or contact your own deployment operator.