Luawl does not set, read, collect, or require cookies. It does not use browser storage for identity, login, preferences, analytics, advertising, tracking, or protected code. A short-lived browser-only scroll offset may be kept solely to restore your viewport after a reload; it is never sent to Luawl and contains no account or program data.

1. Wallet access

Authentication happens in the compatible wallet or identity agent you choose. It presents a DID, optional credential, and one-time cryptographic proof when you approve an action. Luawl does not replace that proof with a cookie, local browser session, password, or stored account token.

2. Direct payment

Payment is initiated by your wallet. Luawl does not use a hosted checkout, recurring wallet charge, or payment cookie. Wallets, browsers, blockchains, RPC services, and networks may keep their own records; those independent records are not Luawl cookies.

3. No tracking

There are no advertising identifiers, retargeting, behavioral measurement, session replay, heatmaps, fingerprinting, social pixels, or cross-site profiles. Luawl does not sell or share browser identifiers.

4. Changes and contact

Luawl will update this policy before introducing any cookie or browser storage. It will not silently add a saved login or tracking identifier.

Questions about this policy can be sent to [email protected].