What we don't collect
- We do not ask for your name, email, employer, or any account information. There are no accounts.
- We do not run analytics, tracking pixels, advertising tags, or session recorders.
- We do not log your inputs, the scenarios you model, or the URLs you share.
- We do not contact any third-party APIs or services from inside the app.
What stays in your browser
- Scenario state — your cap table, sliders, grant inputs, and any edits — is encoded into the URL hash (the part after the
#). By design, URL hashes are never sent to a server. - Theme preference (light or dark) is stored in your browser's localStorage and never leaves your device.
- CSV exports are generated and downloaded entirely in your browser. No file ever touches a server.
When you share a scenario
Clicking Share scenario copies a URL to your clipboard. That URL contains your scenario state encoded as a base64 string in the hash. If you send the URL to a coworker, they will see your scenario when they open the link — but only because the data is in the link itself. The data does not pass through any service we run.
What your host may see
If you (or someone else) deploys this app on a hosting service like Vercel, Netlify, AWS, or a personal server, that host may log standard HTTP request metadata (IP address, user-agent, timestamps). The contents of the URL hash are not transmitted to the host, but the path (e.g. / or /privacy) is. Refer to that host's privacy policy for details. We do not control or have access to those logs.
Changes to this policy
If we change this policy we will update the effective date at the top of this page.
Contact
This is an educational, open-source tool. If you find a privacy issue, please open an issue on the source repository.