Luawl is a zero-retention decentralized application. A compatible wallet or identity agent presents a decentralized identifier, an optional verifiable credential, and a one-time cryptographic proof. Luawl runs supported Lua inside an attested, hardware-isolated environment and returns protected output without creating a server-side profile.

1. The boundary

Luawl's application servers have no code path, log sink, or durable storage layer for submitted source, protected output, or request contents. Those values exist only in volatile memory for the authorized run and are discarded when it ends. Luawl does not build an execution history, behavioral profile, analytics record, or training dataset from your program.

2. Identity and payment

Your wallet or identity agent keeps its own keys and credentials. Luawl checks only the proof needed for the action you choose and never asks for a private key, seed phrase, password, or biometric. Payment is a direct transaction authorized by your wallet. The public network may preserve transaction metadata permanently; that record is not a Luawl account or payment database.

3. Decentralized records

You may keep encrypted identity or usage records in a decentralized system you control. Luawl does not hold the keys to read, alter, or delete those records. Public networks, wallets, browsers, and infrastructure providers can create records under their own rules; Luawl cannot erase records that it does not operate.

4. No integrations or tracking

Luawl does not connect to third-party business applications, send protected code to an AI provider, sell information, run advertising, or create cross-site tracking profiles. It does not intentionally retain network metadata for profiling. Independent wallets, networks, and hosting providers remain responsible for records created in their own systems.

5. Verification and accountability

Luawl's security claims are tied to the measured runtime and its attestation evidence. A verification record can show the result and handling status of a valid run without exposing the protected program. Attestation provides evidence about a declared environment; it is not a promise that every device, wallet, network, or protected program is impossible to compromise.

6. Contact and changes

Do not send source code, private keys, seed phrases, or other secrets by email. Luawl will post a new date before changing this zero-retention boundary.

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