Legal

Privacy Policy

Pelorus Signal LLC · Effective April 2026 · Version 1.0 · Questions: privacy@pelorusai.com

This Privacy Policy describes how Pelorus Signal LLC collects, uses, processes, and protects information in connection with the Pelorus AI-powered submission triage platform.

Enterprise scope. This Policy applies to enterprise customers and their Authorized Users who access the Services under a signed Terms of Use or Pilot Agreement. It does not apply to the personal information of insurance applicants or insureds whose information may appear incidentally within Submission documents uploaded by Customers. Customers are responsible for their own privacy obligations with respect to such individuals.

1. Information We Collect

1.1 Customer-Provided Data

When a Customer uses the Services, we receive and process the following categories of information:

  • Submission Documents — Insurance application packages, ACORD forms, loss runs, schedules of value, broker cover letters, inspection reports, and other materials uploaded by Authorized Users.
  • Carrier Guidelines — Underwriting guidelines, hard stop rules, referral triggers, and eligibility criteria uploaded by Customer.
  • Account Information — Company name, billing contact, designated Authorized Users, and other information provided at onboarding or in an Order Form.
  • Usage Data — Log data associated with Authorized User sessions, including timestamps, query inputs, and interactions with the platform, collected for security monitoring and service delivery.

1.2 Automatically Collected Technical Data

We collect standard technical data to operate and secure the Services, including IP addresses, browser type and version, session identifiers, and error logs. This data is used solely for security, troubleshooting, and platform reliability purposes.

1.3 What We Do Not Collect

We do not collect personal information from insurance applicants, insureds, or brokers whose information may appear within Submission documents. We do not operate a consumer-facing platform and do not collect consumer personal data directly.

2. How We Use Information

We use Customer Data exclusively for the following purposes:

  • Service Delivery — Processing Submission documents against Carrier Guidelines to generate Output, operating the chatbot, and generating correspondence drafts.
  • Security and Fraud Prevention — Monitoring access logs and usage patterns to detect unauthorized access, abuse, or security incidents.
  • Support and Troubleshooting — Diagnosing and resolving technical issues reported by Authorized Users.
  • Legal Compliance — Fulfilling obligations under applicable law, responding to lawful legal process, and enforcing our agreements.

We do not use Customer Data for marketing, profiling, analytics beyond service delivery, or any purpose not listed above without Customer's prior written consent.

3. No Model Training on Customer Data

Absolute Prohibition

Pelorus does not use Customer Data — including Carrier Guidelines, Submission documents, Output, or any derivative thereof — for the purpose of training, fine-tuning, benchmarking, or improving any AI or machine learning model. This prohibition is absolute and survives termination of the Agreement.

Any future engagement of Customer Data for model improvement purposes would require Customer's express prior written consent and would be governed by a separate data processing addendum.

4. Data Sharing and Disclosure

4.1 No Sale of Customer Data

Pelorus does not sell, rent, or trade Customer Data to any third party under any circumstances.

4.2 Subprocessors

To deliver the Services, Pelorus engages third-party subprocessors, which may include AI model API providers and cloud infrastructure providers. All subprocessors are bound by data protection agreements requiring protections substantially equivalent to those in this Policy.

Pelorus maintains a current list of material subprocessors available to Customers upon written request. We will provide thirty (30) days' advance notice before adding any new subprocessor that will have access to Customer Data.

4.3 Legal Disclosure

We may disclose Customer Data to comply with applicable law, a valid court order, regulatory requirement, or lawful government request. Where permitted, we will notify Customer prior to any such disclosure and cooperate with Customer's reasonable efforts to limit the scope of disclosure.

4.4 Business Transfers

In the event of a merger, acquisition, or sale of substantially all of Pelorus's assets, Customer Data may be transferred to the acquiring entity, subject to the same protections as this Policy. We will notify affected Customers in advance of any such transfer.

5. Data Residency and International Transfers

Customer Data is processed and stored within the United States. Pelorus does not transfer Customer Data outside the United States without Customer's prior written consent.

If a Customer requires specific data residency commitments — such as state-level data segregation or compliance with New York DFS cybersecurity regulations — those requirements should be addressed in the applicable Order Form or a separate Data Processing Addendum.

6. Data Retention and Deletion

6.1 Active Term Retention

Pelorus retains Customer Data for the duration of the applicable Agreement and for a period not to exceed ninety (90) days following termination or expiration, after which Customer Data is securely deleted or returned as directed by Customer.

6.2 Backup Retention

Pelorus may retain Customer Data in secure, encrypted backup archives for up to thirty (30) additional days beyond the standard deletion window, solely for disaster recovery purposes. Data in backup archives remains subject to all confidentiality and no-training obligations.

6.3 Deletion Requests

Customers may request deletion of their Customer Data at any time by written notice. Pelorus will complete the deletion within thirty (30) days of receipt, subject to any obligations to retain data under applicable law.

6.4 Customer Retention of Output

Customers may retain Output for their own legitimate internal business, compliance, and regulatory purposes. Retained Output may not be used to reverse engineer, replicate, or develop a competing service that incorporates Pelorus's analytical methodology, scoring framework, or prompt architecture.

7. Security

Pelorus implements and maintains commercially reasonable administrative, technical, and physical safeguards to protect Customer Data. Our measures include:

  • Encryption of Customer Data in transit (TLS 1.2 or higher) and at rest
  • Access controls limiting Customer Data access to personnel required to deliver the Services
  • Audit logging of access to Customer Data
  • Regular review of security controls and subprocessor compliance

Pelorus will provide Customers with reasonable information about its security practices upon written request and will cooperate with Customer's vendor security assessment process.

7.1 Breach Notification

In the event of a confirmed security breach involving Customer Data, Pelorus will notify the affected Customer without undue delay, and in no event later than five (5) business days after becoming aware of the confirmed breach. Notification will describe the nature of the breach, the categories of data affected, and Pelorus's response and remediation steps.

8. Customer Responsibilities as Data Controller

For Submission documents containing personal information of insurance applicants, insureds, or other individuals, Customer acts as the data controller. Customer is solely responsible for:

  • Ensuring it has a lawful basis to upload such personal information to the Services
  • Providing any required notices to data subjects regarding AI-assisted processing
  • Complying with applicable data protection laws, including state insurance privacy regulations, CCPA, NYDFS cybersecurity regulations, and similar state frameworks
  • Responding to data subject requests (access, deletion, correction) with respect to personal data contained in Submission documents

Pelorus processes personal information within Submission documents solely as a data processor acting on Customer's instructions, and solely for the purpose of delivering the Services.

9. Cookies and Tracking

The Pelorus platform uses session cookies and similar technologies solely for authentication and platform functionality. We do not use advertising cookies, behavioral tracking, or third-party analytics cookies. No Customer Data or Submission content is shared with advertising or analytics platforms.

10. Policy Updates

We may update this Privacy Policy from time to time to reflect changes in our practices, applicable law, or the Services. We will notify Customers of material changes at least thirty (30) days in advance by email or platform notification. Continued use of the Services after the effective date of an updated Policy constitutes acceptance of the updated terms.

Customers operating under a signed Agreement that contains specific data processing terms should note that those contractual terms control over this Policy to the extent of any conflict.

11. Contact

For questions about this Privacy Policy, data handling practices, subprocessor requests, or to submit a data deletion request:

Pelorus Signal LLC · Boston, Massachusetts · pelorusai.io · Version 1.0 · April 2026