Privacy Policy

NU MONEY collects the minimum data required to operate the claim flow:

• —Credential hashes — claims are indexed by salted hashes of the link token and claim code, never by their plaintext values.
• —Session records — claim-verification sessions, attempt counters and temporary lockouts used to rate-limit credential guessing.
• —Public on-chain data — transfer records, statuses and settlement data read from the chain.

Claim links and claim codes are generated client-side in this demo and, in production, are stored only as salted hashes. A compromised backend must not be able to reconstruct a working credential. Anyone who shares the claim link or code — including us — can claim the funds. Treat both as private keys.

• —Claim pages (/claim/…) are served with a no-referrer policy so the link token is not leaked to third parties via referrer headers.
• —Claim pages carry noindex directives and must never appear in search results or be indexed.
• —Analytics and tracking scripts are excluded from claim pages. [TBD]

Wallet addresses, transaction hashes and (for publicly-amount claims) transfer amounts are recorded on a public blockchain by design. They cannot be anonymized after settlement and are visible to anyone. Marking an amount private at creation hides it from the public preview and receipt, not from the chain itself.

This MVP uses browser localStorage only — no tracking cookies:

• —Demo state — the mock backend persists transfers, balances and sessions under numoney.* keys so the Create → Share → Claim loop survives reloads.
• —UI preferences — connect state and display toggles.
• —All of it is local to your browser and can be erased at any time via RESET DEMO DATA in the footer or by clearing site data.

In the demo, no data leaves your browser. Production retention windows for session records and hashed credential indexes are [TBD]. On-chain data cannot be deleted by anyone, including us.

Privacy questions or requests: [TBD].