The service terms should be clear about three things: how the product can be used, who owns what, and where the final responsibility still lives when AI is part of the workflow.
What should be clear already
Struvo owns the platform. The customer owns customer content and customer-specific deliverables. Final review still stays with the customer.
Policy
These pages are meant to be readable by a real customer, not just a lawyer. They summarize the operating boundaries in plain language.
Struvo is for lawful business use. Users are responsible for their credentials, their workspace access, and the material they choose to upload.
The service can include standard production features, beta workflows, and assisted rollout structures depending on what has been agreed commercially.
As between the customer and Struvo, the customer keeps its rights in uploaded files, project data, and customer-specific outputs.
Struvo keeps the software, prompts, templates, workflow design, and de-identified aggregate service know-how that does not identify a customer or project.
Struvo is AI-assisted software, not a substitute for professional judgment.
Customers remain responsible for reviewing outputs, verifying facts, and deciding whether something is ready to issue or rely on externally.
Pricing, allowances, and beta structures are governed by the applicable plan, proposal, or written commercial agreement.
Beta or pilot offerings exist to validate workflow fit and may include more assisted setup or tuning than steady-state use.
Customers cannot freely assign the agreement without consent. Struvo can assign the agreement in a merger, acquisition, reorganization, or sale of substantially all assets if the successor assumes the obligations.
That keeps the company sellable without turning customer data promises into fiction.
Final step
Struvo can support tighter diligence with a DPA, subprocessor register, retention standard, and written security and AI-handling language when needed.