Privacy Policy
We don't collect your data because we can't. A comprehensive look at our client-side architecture.
Fundamental Commitment
Architecturally unable to access your data.
"We don't collect data because we can't access it."
This is not a conventional privacy policy where we list what data we collect. Instead, this document explains why we cannot collect your data. Fiscally operates on a client-only model there is no backend server capable of receiving, processing, or storing your financial data.
No Server Storage
We do not maintain databases, cloud storage, or backup servers for user data.
No Network Transmission
Form data never leaves your device via HTTP/HTTPS requests.
No Third-Party Analytics
We don't track financial values or form inputs.
No User Accounts
No emails, passwords, or session tokens are ever generated.
Technical Verification
Understanding the data lifecycle.
For tax professionals who require technical verification of privacy claims, here is the data lifecycle:
Step 1
Initial Page Load
HTML/JS files downloaded from CDN. Zero user data exists.
Step 2
Local Data Entry
Data stored in browser memory (React state) and IndexedDB (local).
Step 3
Computation
Calculations run entirely in your browser's JavaScript engine.
Step 4
File Generation
JSON file constructed in memory and offered as download.
Verify Yourself:
Open DevTools (F12) → Network Tab. Complete a form and generate a file. You will observe zero POST requests to any API endpoint.
Third-Party Dependencies
Minimal external interactions disclosed.
Vercel / Cloudflare CDN
RequiredHosts static assets (HTML/JS/CSS). Receives standard HTTP headers (IP, User Agent) but NO form data.
Google Fonts
OptionalLoads typography. Receives font request metadata only.
Note: We do NOT use Google Analytics, Facebook Pixel, or Mixpanel.
Privacy Assurance
We recognize that handling client financial data is a position of trust. Our privacy-by-design architecture is not a marketing claim it is a verifiable technical reality.