tenhaw / kit

Privacy and data boundaries

Installed CLI, libraries, templates and stdio MCP have no usage telemetry. Local collectors contact GitHub or Jira only when requested. Tokens are read from your environment and are not written into cache files or reports.

Starter imports and edits stay in browser localStorage. There is no shared customer-data service. Clearing browser storage removes the local copy; JSON export lets you retain a copy under your own control.

The remote MCP processes supplied calculation inputs transiently. It rejects customer credentials and raw delivery events, does not persist request bodies and applies request-size, computation and rate limits. Hosting providers process operational request metadata for delivery and abuse controls.

This reference site ships without analytics. If site analytics are enabled later, this page must first describe the provider, event fields and retention. No assessment answers, ROI inputs, event arrays or register content may be sent as analytics properties.

Support: hello@tenhaw.com.