Protect the vendor file from submission through decision.

DueFiles applies clear boundaries to every stage of vendor insurance compliance. Public marketing pages, authenticated organization workspaces, scoped vendor submission links, document processing, requirement evaluation, human review, and data export serve different participants and purposes.

That separation keeps outside submission access distinct from operator access and keeps extracted information distinct from a confirmed review decision. The security model protects both the customer data in the workflow and the authority of the people accountable for the result.

• Workspace access: operator routes require an active account session and organization context.
• Submission access: vendors and brokers use a separate upload-only link, not an operator account.
• Link lifecycle: submission links expire, and authorized operators rotate them from the workspace.
• Organization context: vendor, requirement, document, extraction, and review records carry an organization identifier.
• Session handling: application sessions use server-set, HTTP-only cookies with same-site restrictions.
• Advanced identity: Enterprise programs define identity-provider, provisioning, role, and access-review requirements during security evaluation.

The current submission flow accepts text or JSON exports and enforces file type and size limits in the browser and on the server. A valid, unexpired submission token is required before processing. Submitted content is associated with the intended organization and vendor before extraction begins.

Vendor and broker participants use the submission path issued by the requesting organization. The path exposes the request and upload action for the assigned vendor without exposing the operator workspace. Authorized operators can rotate the path when recipient access changes.

DueFiles first applies deterministic field and endorsement parsing. Provider-backed extraction sends document text to the configured provider and returns structured fields with per-field confidence. The extraction instruction requires unknown policy numbers and limits to remain empty instead of being invented.

Per-field confidence and source context remain available for review. Low-confidence critical fields stay in the review queue, and a rejected extraction returns the vendor to a pending state. The organization's authorized users control approvals, rejections, exceptions, and configured requirements.

DueFiles records document ingestion, extraction review, requirement changes, reminders, exceptions, and vendor decisions as workspace activity. A missing packet and unreviewed extraction remain pending. Required endorsement forms are evaluated separately from certificate checkboxes. A confirmed result retains the requirement, evidence, reviewer action, and subsequent renewal work in one review history.

Web traffic is encrypted in transit with TLS. Service providers process data for assigned infrastructure, authentication, communications, extraction, monitoring, and support functions. The Privacy Notice explains data categories, purposes, disclosures, retention factors, and privacy rights. Enterprise review defines deployment-specific retention, deletion, residency, backup, subprocessor, incident, and contractual requirements.

Each customer governs the people, recipients, requirements, decisions, and exports in its vendor program:

• granting access only to authorized users and removing access when responsibilities change;
• sending submission links only to the intended vendor, broker, or representative;
• rotating a link that reaches an unintended recipient or is otherwise exposed;
• reviewing source context and extraction uncertainty before confirming a decision;
• protecting exported data and connected systems; and
• reporting suspected account misuse, document exposure, or security events promptly.

Send security reports to security@duefiles.com with the affected route or feature, impact, reproducible steps, and a safe proof of concept. Do not include live customer data, credentials, insurance documents, or submission tokens. Use the subject "Security report" so the message is routed correctly.

Research must use accounts and data you control. Do not access another person's information, degrade the service, use social engineering, demand payment, retain data, or disclose an unresolved issue publicly. Stop testing and report immediately if you encounter customer information.

DueFiles will not pursue legal action for good-faith research that follows these rules, avoids harm, and gives DueFiles a reasonable opportunity to investigate and remediate the issue. This safe-harbor commitment does not authorize testing of third-party services or conduct prohibited by law.

Enterprise evaluations map architecture, identity, access, data flow, extraction providers, subprocessors, retention, deletion, incident handling, continuity, connected systems, implementation, and contract controls to the customer's procurement requirements.

Contact security@duefiles.com with the organization, deployment scope, data categories, identity requirements, required review material, connected systems, and procurement context. DueFiles records deployment-specific commitments in the signed Enterprise agreement.

How do vendors submit without workspace access? They use a scoped, expiring submission link tied to the intended organization and vendor. The link supports document intake and remains separate from operator routes.

What happens to uncertain extraction? Critical low-confidence fields remain in review. An authorized operator inspects the source context and approves or rejects the extraction.

How does DueFiles create accountable status? The vendor file connects the requirement, submitted evidence, review state, operator action, exception context, and renewal history.

Where should vendor documents be sent? Use the scoped submission path from the requesting organization. Public contact and security-report addresses are for communication, not live vendor packets.