Security controls and service boundaries.

• Same-site, HTTP-only authenticated sessions and same-origin mutation checks.
• Wallet-control challenges with replay protection before account linkage.
• Bounded request bodies, rate limits, concurrency limits, and risk holds.
• GPU, provider-cost, and access-endpoint admission before billable time starts.
• Encrypted temporary access credentials with revocation at lease close.
• Idempotent lease and settlement processing with recovery after interruption.
• Maximum escrow, maximum duration, dispute window, and emergency pause enforced onchain.

Cloud workspaces run in fresh containers with temporary direct access. This limits accidental persistence between leases, but the infrastructure provider controls the physical host and may be able to observe workload data.

Do not place private keys, production credentials, regulated data, proprietary model weights, or other confidential material in a beta workspace. Prism does not currently provide a hardware-backed trusted execution environment, confidential GPU memory, durable storage, or a service-level agreement.

Lease funding and settlement execute through deployed Robinhood Chain contracts. Configuration changes pass through a 48-hour timelock, while the governance Safe holds emergency and dispute authority. The initial contracts are unaudited beta software.

Contract addresses, roles, state transitions, settlement calculations, and operational parameters are published in the developer documentation.

Send security reports to security@prismnetwork.tech or use GitHub private vulnerability reporting.

Include the affected component, impact, reproduction steps, and a safe proof of concept. Do not test against mainnet user funds, disrupt public capacity, access other users' data, or publish an unresolved vulnerability.