Security and data

Controls for sensitive invoice workflows

Invoice documents contain financial and project information. Denize is designed to limit access, preserve review, and use customer data only to operate the service.

How Denize approaches invoice security

Denize uses encrypted connections, secure sessions, access controls, and encrypted private storage for pending invoice attachments. Procore authentication uses OAuth, so Denize does not receive your Procore password. No internet service can promise perfect security.

Core controls

Security follows the invoice from access through submission

Procore OAuth

Users authenticate through Procore. Available company and project records depend on the connected user’s Procore access.

Protected invoice access

Pending invoice attachments are kept in encrypted private storage and served through authenticated application controls.

Human-controlled submission

Extracted fields and matching suggestions remain editable. Denize requires review and an explicit submission choice.

Company-level history

Authorized team members share invoice history at the connected company level rather than through isolated personal copies.

AI processing

What happens when AI helps prepare an invoice

AI providers process invoice content for extraction or matching requests under their API terms and configured data controls. Denize does not intentionally use uploaded invoice content to train AI models.

Data lifecycle

Retention and customer choices

  • Invoice documents and extracted data are processed to provide the service.
  • Pending attachments are removed after submission or dismissal, subject to operational backups.
  • Account, invoice-history, security, and billing records are retained as reasonably needed for the service, audit, security, disputes, and legal obligations.
  • Denize does not sell personal information.
  • Customers may request access, correction, or deletion where applicable.

Review the workflow before connecting your Procore company.

Start with a controlled trial, confirm access and review responsibilities, and expand only when the workflow fits your team.