Privacy Policy
The company responsible for Kelvin Code and this policy is ANDERSON DE ALMEIDA MELO TECNOLOGIA DA INFORMACAO LTDA. Contact for support, privacy and requests about your data: security@kelvincode.com.
Kelvin for Mac offered for download on this site executes on your Mac and connects to Kelvin Code Cloud. To receive jobs and share sessions, it transfers app data, live frames and evidence to Kelvin services.
When you connect an MCP host to Remote Live MCP, it receives the results of actions it requests, such as run status and live frames. Those responses pass through Kelvin servers before reaching the MCP host; the host and your chosen model provider may process them under their own terms and privacy settings.
Kelvin Code Cloud is in closed alpha. For shared runs, it receives the app and run artifacts, execution evidence — which may include video, captures, transcript and hashes — and live session frames. The Mac connects outbound only; Kelvin opens no inbound port on it.
Retention, said the way it actually works today: what you sent to the Cloud stays for as long as your organization exists. Nothing is deleted on a schedule — no process sweeps evidence, and an expiry shown on a screen is the ceiling of what that package could survive, never a countdown.
To have something deleted, write to security@kelvincode.com and say what: we delete it by hand, because there is no button and no routine that does it on its own. The audit trail does not go with it — a trail that could be erased by removing its subject would not be an audit trail.
What does get deleted is a room's state when it ends: chat, proposals, tickets and seats. No storage is public, and the signed addresses that serve the images last minutes, not days.
Cloud sub-processors: Cloudflare (control plane, database and evidence storage), Vercel (the dashboard and this site) and Brevo, which delivers the named invitation to read a piece of evidence. Brevo receives that address in order to deliver the message; we do not keep the address, only a fingerprint of it. When you authorize a Jev call, TypeSafe AI also processes the limited data described below.
About that e-mail, something we would rather not have had to write: the provider account still has its default tracking on, so the message being opened and the accept link being clicked both go through it. The message itself carries no image, no remote font and no attachment — what tracks there is the account, not the text you receive.
Data follows the regions and jurisdictions contracted with those providers. The Cloud Alpha does not promise Brazilian data residency.
When the agent requests Jev navigation, TypeSafe AI receives a short goal and limited accessible control labels. For incident triage, your chosen Sentry or Datadog MCP obtains the records; Kelvin receives structural metadata, and TypeSafe AI receives severity classes, indicators and counts only. Credentials for those services remain with the MCP you chose.
Kelvin for Mac sends no usage telemetry or automatic crash report. It sends Cloud the operational state needed to run jobs, such as connection, capability and job progress. Incident triage happens only when your agent calls the tool with authorization asserted. Updates are downloaded manually from the releases page.
This site uses anonymous analytics only after your consent. We do not sell data. A privacy question, support request or request about your data: security@kelvincode.com.
PortuguêsEnglish