Simple answers. No return promises.

The implemented provider returns structured naming, lore, metadata, community copy, launch copy, and one image-generation prompt. It does not create image/video files or alter program code.

Only when an OpenAI-compatible provider, model, worker, entitlement, and queue are configured. Otherwise the UI reports a not-configured or unavailable state.

The current program initializes a launch-configuration PDA only. Token minting, bonding curves, trading, liquidity migration, and fee collection are not implemented and require new code plus legal, security, audit, and operational gates.

No. Wallet, payment, and launch preparation paths target Solana Devnet. Mainnet actions and real-value product flows are disabled.

No. The configuration-only program source is unaudited, and its public Devnet deployment still requires owner-supplied release inputs and verification.

The app shows an explicit unavailable state instead of invented activity.

Session expiry is distinct from deletion. Authenticated API routes provide a wallet-data export and an explicit private-workspace purge request; plan retention removes expired unlaunched private work, while public Solana and mandatory integrity evidence is retained. The final policy and response commitment still require owner/legal approval.

Never. Seed phrases, private keys, and recovery phrases never enter TrenchForge systems. We only read your public wallet address from the blockchain.

Devnet transfers are not reversible by the app after confirmation. Wallet-owned support cases can request review and audited restoration or revocation of unused application access, but they do not refund or rewrite the on-chain transfer. The final refund and support policy still requires named owner/legal approval; read the working payment disclosure.

A confirmed payment activates only the exact database entitlement shown before signing. It does not mint a token, launch a market, trade, migrate liquidity, or claim fees.