Trust

Security & Data Protection

Last updated: September 28, 2026

OwnerWise is still under development. The controls below describe the intended production security model and must be validated through implementation and testing before sensitive financial or tax records are accepted.

Separation of public and private data

The public Nuvessra website contains company and product information only. Private company documents, tax records, financial data, and account content should reside in authenticated product systems and should never be embedded into public static website files.

Access controls

Production OwnerWise is intended to require authenticated access, apply least-privilege permissions, support multi-factor authentication where available, and allow account owners to grant and revoke collaborator access.

Encryption and transport security

Production systems should use modern TLS for data in transit and encryption at rest for supported data stores and file storage. Sensitive credentials and API keys should remain server-side rather than in public website code or mobile application bundles.

Document processing

Document and AI workflows should transmit only the information needed for the requested task, use approved processors, maintain auditable processing boundaries, and avoid exposing source documents to unauthorized users.

Logging and review

Production systems should maintain security-relevant logs, access history, and administrative audit trails sufficient to investigate account activity and sensitive-document access.

Data deletion

OwnerWise is intended to provide clear deletion and retention controls. Backup and legal-retention exceptions should be documented in the product-specific privacy policy before launch.

Responsible disclosure

Security concerns can be reported to legal@nuvessra.com.

Connected-data safeguards

Production account connections should use provider-hosted authorization flows, server-side token storage, least-privilege scopes, encrypted secrets, revocation controls, and auditable access. Email and invoice ingestion should use private authenticated connectors or dedicated forwarding infrastructure rather than public upload links. Vendor matching should use least-privilege mailbox scopes, server-side tokens, source fingerprints for duplicate prevention, and review thresholds before an email can create or change a Purchase record.