Privacy Policy

This policy covers the CoreGuard app registered with the Pi Network Developer Portal, its Pi Sign-In integration, and the public pages served from coreguard-trust-and-defense.lovable.app — including /networks/pi-network, /privacy and /terms.

It does not cover third-party Pi Network services, DApps, wallets or merchant applications. Each of those has its own policy.

When you choose to sign in with Pi Network, the Pi OAuth implicit flow returns a Pi user identifier (such as your Pi username or uid) and an access token limited to the scopes you approved. We use it to associate verification records with your account.

We do not receive or store your Pi account password, your wallet secret key, or your recovery phrase. Sign-in is optional — every public page works without it.

To produce an execution receipt we process: the declared intent, the policy decision (ALLOW / DENY / HOLD), a commitment hash, the receipt body, and the anchor reference. Receipts carry hashes and proofs, not private keys.

When a network transaction is verified, its transaction identifier and ledger position are processed as public on-chain data.

Wallet secret keys, seed phrases, Pi account passwords, and full payment-instrument details. We do not ask for them, and they are never required to use CoreGuard.

Anchoring publishes a commitment hash and a receipt reference. Anything written on-chain is public and permanent — on Core (chain 1116), on Stellar, and on Pi mainnet once that integration is prepared and live. Personal data must never be anchored.

To produce and verify execution receipts, to hold an action when verification is uncertain, to support verified merchant badges and dispute evidence packs, and to keep the service secure and available.

No advertising profiles, no behavioural scoring, and no sale of personal data.

Off-chain verification records are kept only as long as needed to replay a receipt or answer a dispute, then deleted or aggregated. Sign-in identifiers are kept while your integration is active. On-chain hashes cannot be deleted by anyone.

We do not sell or rent personal data. We share the minimum necessary with infrastructure providers that run the service under contract, or where the law requires it.

Fail-closed by default: an action that cannot be verified is held, not passed. Least-privilege access, no secrets in browser storage, no platform credentials in client code. No system is perfect — VERIFIED ≠ SAFE.

You can use every public page without signing in. You can ask what off-chain records we hold about you, request correction, and request deletion of off-chain records that are not required for an open dispute.

CoreGuard is not directed to children under 13, and we do not knowingly collect their data.

Changes are posted on this page with a new effective date. Continued use after a change means you accept the updated policy.

Open an issue at https://github.com/coreguard-global/CoreGuard/issues, or use the contact page. The repository is public, so the issue tracker is the fastest and most auditable route.