Privacy

We collect very little. No ad pixels, no fingerprinting, no cross-site tracking, no selling or sharing data, ever. Your tax facts are computed and returned, never stored. The site runs one product-analytics tool (PostHog, disclosed fully below) that honors your browser's Do Not Track setting. The only personal data we ever hold is an email address you explicitly gave us, and you can delete it with one message.

We use PostHog for product analytics: page views, anonymous usage events (clicks and form submissions on this site only), and session replays in which every input field is masked, so nothing you type is recorded. Profiles stay anonymous unless you identify yourself (e.g., by signing up). If your browser sends Do Not Track, analytics is disabled entirely. PostHog stores a device identifier in your browser to tell visits apart; your light/dark preference is kept in local storage and never leaves it. Our hosting provider (Vercel) keeps standard, short-lived request logs, as every host does.

If you sign up for updates (on the site, or via opentax signup), we store exactly three things: your email address, when you signed up, and where the signup came from (site or CLI). Signup is double opt-in, and the confirmation link expires in 48 hours, and if you never confirm, you are never emailed. Application logs record a one-way hash of the address, not the address itself.

We never sell, share, or enrich the list. Unsubscribe or request deletion any time: founders@invaro.ai and everything tied to your address is removed.

The published CLI and MCP server send one anonymous usage ping: an event name ("cli", "mcp-stdio", or "mcp-http"), the package version, the operating system name, and the Node major version. Nothing else: no arguments, no tax data, no identifiers, no IP retention. The first run prints a notice saying exactly this.

Opt out with OPENTAX_TELEMETRY=0 or DO_NOT_TRACK=1.

The hosted MCP endpoint (opentax.invaro.ai/mcp) is stateless: the tax facts in your request are computed in memory and the answer is returned. It is not stored, logged, or used for anything else. For usage metering we record only the JSON-RPC method name, the tool name, the connecting client's self-reported name and version, and a timestamp. IP addresses are used transiently in memory for rate limiting and are not written to our storage.

Don't want to trust that? The engine is AGPL, so run npx -y @invaro/opentax locally or self-host the HTTP server, and nothing touches our infrastructure at all.

founders@invaro.ai reaches a human.