Reley runs on your machine. No account, no sign-in, no analytics ping. This page exists so you do not have to dig through source to confirm that.
What Reley does not collect
- No telemetry, no analytics, no crash-report uploads.
- No keystrokes, no clipboard, no screen capture.
- No wallet keys, mnemonics, or signed-transaction payloads.
- No account on any backend - Reley has no backend.
What stays on your disk
Project state, cloned program binaries, cloned account blobs, IDLs, snapshots, keypairs, and workflow definitions are written under your project root. Default location: ~/.relay-cli-project for the CLI, <projectRoot>/.relay for the desktop app.
Sandbox keypairs are stored in plaintext by default - they are for local test use only. Do not paste a real funded key into Reley.
Network requests Reley makes
- Solana RPC. When you clone a program, account, or replay a transaction, Reley calls the RPC endpoint you configured. Choose any provider you trust.
- App updates (desktop only). The packaged macOS app may check for new versions on launch. Disable this in
Settings - Auto-updateif you prefer.
This website
The marketing site uses no analytics, no cookies, no third-party trackers. If the binary download link points to a CDN (R2 / S3 / GitHub Releases), that provider may log the request in its own access logs - we do not see those logs.
Children
Reley is a developer tool. It is not directed at children under 13. We do not knowingly collect data from anyone, including children.
Changes
If the policy changes, the new effective date appears at the top of this page. Material changes are noted in the changelog inside the app.
Contact
Questions about this policy go to github.com/hoangtuanictvn/reley. Open an issue or a private security advisory.