Protected solution content is stored in a dedicated table with forced row-level security and no buyer-facing policies. Direct access is revoked from anonymous and ordinary authenticated database roles. All writes go through authorized server functions that verify ownership or organization admin role, and privileged writes use a server-side service-role client. For protected listings, the marketplace UI, setup submission, approval packet, and public API do not return the underlying prompt template. This reduces exposure of proprietary logic — it does not guarantee that behavior cannot be inferred from a solution's outputs.