Struvo is built for professional project documentation, so the privacy story has to be simple: your project content stays yours, we use it to deliver the service, and we do not quietly turn it into something else later.
What should be clear already
Customer content is for delivering the service, not for surprise model training or vague future monetization.
Policy
These pages are meant to be readable by a real customer, not just a lawyer. They summarize the operating boundaries in plain language.
We collect the information needed to run the site, create accounts, communicate with customers, and process project workflows.
That can include contact details, uploaded files, notes, photos, audio, transcripts, generated outputs, project metadata, and basic usage diagnostics.
We use information to provide, secure, support, and improve the service.
That includes generating reports and records, maintaining continuity across visits, responding to support issues, and monitoring reliability and abuse.
Struvo uses third-party providers for model processing, hosting, storage, email, and observability.
Customer project content is not authorized for third-party foundation-model training unless the customer gives prior written consent.
We separate redacted external telemetry from restricted internal quality traces.
Core customer project records are generally retained for the life of the account unless deletion is requested or a legal or contractual reason requires narrower handling.
Struvo can be sold, reorganized, or transferred as a business. That does not mean customer project data becomes a free asset to exploit.
If information transfers in a merger, acquisition, bankruptcy, or similar transaction, the successor should use it consistently with the promises made here and applicable law.
Final step
For firms with heavier diligence or contract review, Struvo can also work from a DPA, customer addendum, or tighter written security requirements.