Question 1

What is the InsuranceFlow Privacy Policy?

Accepted Answer

The InsuranceFlow Privacy Policy explains how InsuranceFlow collects, processes, protects, retains, and manages personal data, customer data, website data, and commercial insurance data. It applies to the InsuranceFlow website, business communications, authorized use of InsuranceFlow services, and configured insurance workflow connections. The final policy should state its effective date, last-updated date, legal entity, and geographic scope after verification.

Question 2

What are the data-handling roles of InsuranceFlow and its customers?

Accepted Answer

InsuranceFlow may handle information for its own website, account administration, service delivery, support, security, and business operations. InsuranceFlow may also process customer-controlled data under customer instructions when providing submission intake, document processing, AMS integration, and related workflow automation. Customers are responsible for determining what data they submit, configuring authorized access, providing required notices, and making insurance decisions. Controller, processor, service provider, or comparable legal roles must be confirmed against applicable law and customer contracts before publication.

Question 3

What types of data does the policy cover?

Accepted Answer

The policy covers personal data, customer data, website data, and commercial insurance data handled by InsuranceFlow. Depending on verified practices and customer configuration, this may include names, business contact details, account information, communications, submission emails, insurance documents, structured fields, workflow status, integration records, device information, usage events, and cookie data. The published policy should separate required information from optional information and list only categories InsuranceFlow actually collects or processes.

Question 4

Where does InsuranceFlow receive data from?

Accepted Answer

InsuranceFlow may receive data directly from visitors, prospects, customers, and authorized users. Customer-controlled information may also arrive through submitted emails and documents, AMS integrations, connected systems, and configured workflow connections. Any automated collection through cookies, analytics, logs, or similar technologies should be disclosed only after confirming the tools and data involved. Differences among standard, configurable, and private deployment options must also be verified before they are described.

Question 5

How does InsuranceFlow process commercial insurance data?

Accepted Answer

InsuranceFlow is designed to convert document-heavy insurance information into structured, enriched, ready-to-review work. Depending on the configured workflow, processing may involve classifying incoming materials, extracting fields from documents such as ACORD forms or loss runs, validating information, enriching records, routing visible exceptions, and sending approved outputs to connected systems. Automation supports repetitive work, while authorized people remain responsible for review, corrections, approvals, underwriting judgment, and other decisions.

Question 6

Does InsuranceFlow use customer data to train AI models?

Accepted Answer

The available business context does not verify whether customer data is used for model training. The published policy must provide a direct answer and distinguish processing required to provide the service from product improvement, evaluation, model training, and support. It should also explain any customer controls, opt-out rights, contractual restrictions, de-identification practices, vendor involvement, and differences for private deployment. This section must be confirmed before publication.

Question 7

When may InsuranceFlow share or disclose data?

Accepted Answer

The final policy should identify verified disclosures to customer-authorized users, connected systems, integration providers, infrastructure or service vendors, subprocessors, professional advisers, and authorities when legally required. It should explain that customers control their systems, users, workflow configuration, and submitted data, while InsuranceFlow is responsible for its own services and approved vendors. The policy must separately state the verified position on selling personal data, sharing for cross-context behavioral advertising, targeted advertising, and profiling rather than relying on a broad assurance.

Question 8

How does InsuranceFlow protect data?

Accepted Answer

The published policy should describe verified technical and organizational safeguards, permissions, deployment boundaries, and access controls without promising zero risk or absolute security. Relevant details may include access management, authentication, encryption, monitoring, logging, incident procedures, personnel controls, and vendor review, but only where confirmed. Private deployment can change data location, access, infrastructure responsibility, and operational boundaries, so those differences should be documented from current architecture and contracts. Human oversight and visible exceptions help authorized teams review automated outputs.

Question 9

How long does InsuranceFlow retain data?

Accepted Answer

No verified retention periods are provided in the available context. The final policy should state a period or objective retention criteria for each material category, including website inquiries, account data, customer-controlled insurance data, support records, security logs, and cookie or analytics data. Retention may depend on customer instructions, contracts, service needs, legal obligations, dispute preservation, and security requirements. The policy should explain return or deletion after termination and distinguish active-system deletion from the later expiration of protected backups.

Question 10

How can I exercise privacy rights or ask a privacy question?

Accepted Answer

The published policy should list only rights that apply under relevant law, which may include access, correction, deletion, portability, objection, restriction, opt-out, or appeal rights. It should provide a verified request channel, identity-verification steps, authorized-agent requirements where applicable, expected response workflow, and any lawful exceptions. Until a dedicated privacy contact is verified, visitors may use the Contact page. Material policy changes should be communicated through an updated notice, a revised date, or another verified method appropriate to the change. Legal, security, product, and operations teams should review the policy before publication.

InsuranceFlow Privacy Policy and Data Practices

Privacy practices at a glance

InsuranceFlow privacy policy details