Use the least sensitive data the question requires.
Cenva can build useful forecast workspaces from public holdings, filings, company disclosures, and cited web sources. Customer-provided material is scoped deliberately rather than assumed.
Public-source posture
Many investment questions can be framed using public information: reported holdings, SEC and regulatory filings, company disclosures, public datasets, and cited reporting. Where that is sufficient, Cenva does not need client PII or account-level information.
Customer-provided context
A customer may choose to provide a portfolio universe, thesis, assumptions, source URLs, notes, or documents. Access and processing requirements should be agreed before sensitive information is supplied. The public request form must not be used for confidential information.
Organization separation
Customer-facing product records are associated with an organization and account. Authentication, organization membership, and staff-only operations are separated in the application. Detailed architecture and deployment documentation can be provided during technical diligence.
Evidence provenance
Cenva preserves source references and retrieval context alongside evidence used in forecasts and reports. Client-facing exports include representative source records while internal orchestration identifiers and process language are removed.
Human review
Workspace readiness is evaluated separately from whether an answer exists. Missing evidence, unresolved caveats, and degraded fallback paths can prevent an output from being considered ready for external distribution. The customer decides what is ultimately shared.
Current assurance posture
Cenva does not claim SOC 2 certification on this website. Security, subprocessors, retention, deployment, and deletion requirements should be reviewed for the specific engagement.
Questions
Include data-handling or deployment requirements when you bring us a question. We will address them before requesting sensitive material.