Privacy

Public proof, local secrets.

Froglet is an Apache-2.0 open source protocol. This page explains the privacy boundary for the public website, hosted proof trial, and local/self-hosted usage. Last updated: April 29, 2026.

Short version

Do not paste secrets into hosted demos.

The hosted proof is designed for public demo inputs. Local private keys, Lightning macaroons, Stripe keys, x402 credentials, card data, production API tokens, and private datasets should be configured only in your own local or self-hosted environment.

01 · website

Public docs and pages

froglet.dev serves public documentation and marketing pages. The hosting layer may keep standard request logs needed for security, abuse prevention, debugging, and reliability. The site does not ask for account signup or payment details.

02 · hosted proof

Anonymous demo sessions

try.froglet.dev can mint short-lived anonymous sessions and write demo descriptor, offer, deal, and receipt artifacts for public free demo.*services. Those artifacts are proof material, not private storage.

03 · local mode

User-controlled configuration

Local install plans tell you which secrets or wallets a rail requires, but those values belong in your shell, config files, keychain, or self-hosted node. They should not be pasted into the hosted demo.

Data by tool

What local MCP tools process.

`status`, `invoke_service`, and service actions

Connect to the provider/runtime URLs you configured, read local token files from your machine, and send the inputs you explicitly provide to your selected local or remote provider.

`plan_install`

Uses install preferences such as target agent, Docker/source/binary footprint, Tor or clearnet, and payment rail choice. It reads public GitHub release metadata and the tag-specific bootstrap bytes to bind their hashes. It returns a plan; it does not write to your machine, run shell commands, or need your secrets.

`publish_artifact` and settlement actions

Use local artifact paths, payment configuration, wallet state, and receipt metadata from your configured node. They are production-capable surfaces, so do not send secrets to untrusted providers.

Retention and sharing

Public artifacts are intentionally auditable.

Froglet receipts and feed artifacts are designed to be verifiable later. Hosted demo artifacts may remain visible as part of the public proof feed. Froglet does not sell personal data. If you need deletion, correction, or privacy support, open a GitHub issue or contact the maintainer througharmanas.dev. Usage rules and the takedown process for the hosted services live on theterms page.