Privacy Policy

• - No accounts, no sign-up, no telemetry.
• - The library runs entirely on your machine - no data is sent anywhere unless you explicitly trigger a command that makes a network request.

pyRPC makes no network requests on its own. The CLI only reaches out when a command needs it, and always to destinations you configure:

• - pyrpc pull and local codegen introspect your Python module and write files locally. No network.
• - pyrpc dev and pyrpc serve start a server on localhost (127.0.0.1 by default) and probe only that address to detect a running instance.
• - Codegen can fetch an introspection schema from a server URL you explicitly pass (typically your own dev server).
• - npm install @pyrpc/client and uv add pyrpc-core use standard package managers (npm, uv) which fetch from their respective registries.

Nothing. pyRPC has no telemetry, no analytics, and no backend server. We don’t run analytics on this site, don’t set tracking cookies, and don’t embed third-party trackers. The only data we see is what you voluntarily send: GitHub issues, PRs, or emails to the addresses below.

The site loads static assets such as fonts and icons from public CDNs. Those providers see standard request metadata (IP address, user agent) for asset delivery; nothing identifying you is sent to us or stored by us.

If this policy changes, the “Last updated” date at the top of the page changes with it.

Privacy questions: info@pyrpc.com. Source: github.com/pyrpc/pyrpc.