COVU Vero Text Module Schedule

Document ID: `covu.veroskills.vero-text.schedule.v1.0` Version: 1.0 Release date: July 30, 2026 Provider: COVU Inc. VeroSkill: Vero Text (`vero.text_ai.v1`)

This Vero Text Module Schedule (this “Schedule”) supplements the COVU OS Lite Terms of Service, Additional Module Order, Data Processing Addendum, Security Exhibit, Privacy Notice, Subprocessor List and Messaging Terms accepted for the Agency. It also functions as the Agency's Feature-Specific Consent for Vero Text.

This Schedule becomes effective for an Agency only when a current Agency owner or administrator accepts it with an immutable Activation Summary. The Activation Summary identifies the Agency, workflow and configuration being activated and is incorporated into this Schedule.

1. Activation Summary

The Activation Summary must display and preserve:

• the Agency legal name and Agency ID;
• this Schedule's document ID, version and SHA-256;
• the Vero Text workflow ID and version;
• the selected Agency numbers or sender accounts;
• whether inbound, outbound or both directions are enabled;
• whether Vero Text may classify only, draft only or send after Agency review;
• the permitted message purposes and recipient population;
• whether marketing or solicitation is enabled;
• the required Agency reviewer and human-escalation rule;
• the content and metadata processed;
• each material provider receiving content and its purpose;
• the retention and deletion configuration;
• the rate-card version, billable unit, rate, allowance, billing cadence and any optional spending limit;
• the payment authorization or approved invoicing reference;
• the effective date, cancellation terms and revocation method; and
• a canonical configuration digest.

An omitted, unreadable, internally inconsistent or stale Activation Summary does not activate Vero Text.

2. What Vero Text may do

Within the accepted Activation Summary, Vero Text may receive and classify messages, retrieve relevant Agency-approved context, prepare summaries or drafts, and send a message only when the accepted action level permits it.

Unless a later accepted Activation Summary expressly and lawfully adds the capability, Vero Text will not:

• send without the required Agency review;
• initiate marketing, solicitation, cross-sell or upsell campaigns;
• contact a suppressed or opted-out recipient;
• make a coverage, underwriting, claims, fraud, cancellation, nonrenewal, legal or eligibility decision;
• bind, issue, alter or cancel insurance;
• write to a carrier or agency-management system;
• route a task to the Service Network;
• create a charge outside the accepted Additional Module Order; or
• represent that an automated statement is a licensed insurance determination.

3. Agency authorization and responsibilities

The Agency represents and agrees that:

1. it is authorized to use each number, account and sender identity in the Activation Summary;
2. it has a lawful basis and any required consent for the selected message types and recipients;
3. it will supply accurate sender, purpose, recipient, consent and time-zone information;
4. it will not instruct COVU to send an unlawful, misleading, discriminatory, abusive, emergency or prohibited message;
5. it will maintain legally required consent and internal do-not-contact records;
6. it will designate qualified reviewers and escalation contacts;
7. it will not treat Vero output as a coverage, legal or regulated decision; and
8. it will promptly notify COVU when a number, sender authorization, consent, employee authority or permitted purpose changes.

The Agency's representations do not authorize COVU to disregard applicable law, provider requirements or a recipient's revocation.

4. Consent, suppression and recipients

COVU and the Agency will apply the accepted Messaging Terms. Recipient consent must match the sender, channel, purpose and message type. A valid opt-out or revocation stops later messages to the extent required by law and the accepted suppression policy.

Vero Text must fail closed when required sender registration, consent evidence, suppression status, calling-hour treatment or provider configuration cannot be verified.

Messaging is not for emergencies. The Agency must provide another method for urgent matters and monitor escalations identified in the Activation Summary.

5. Automated assistance and human review

Vero Text is an automated assistant. Its classifications, summaries and drafts may be incomplete or inaccurate. The Agency remains responsible for the final message and every insurance decision.

Where Agency-reviewed sending is selected, Vero Text may send only after the designated Agency reviewer approves the final content. Activating Vero Text does not itself send a message.

Autonomous sending requires a later accepted Activation Summary identifying the eligible message classes, consent basis, safety controls, escalation, suppression and audit evidence.

6. Data and providers

COVU will process message content and related data under the DPA, Security Exhibit, Privacy Notice, Subprocessor List and accepted Activation Summary.

COVU will identify each material content processor receiving message content and its purpose before activation. COVU does not authorize those providers to use identifiable Agency Customer Data to train generally available models.

7. Pricing and payment

Pricing, usage calculation, optional spending limit, billing cadence, disputes, credits, failed payments and suspension follow the accepted Additional Module Order and Activation Summary.

No separate contract acceptance is required for each ordinary authorized message within the accepted scope and rate. A materially different billable unit, rate increase, optional spending-limit increase or paid scope requires fresh acceptance.

8. Revocation and suspension

The Agency may turn off Vero Text through VeroSkills or the revocation method shown in the Activation Summary. Revocation:

• stops new and queued Vero Text processing and sends;
• preserves required suppression, consent, billing, security and legal records;
• begins deletion or return under the displayed retention schedule and DPA; and
• leaves unrelated OS Lite access and separately accepted modules active.

COVU may narrowly suspend Vero Text for legal, recipient-harm, security, provider, sender-registration, suppression or undisputed-payment risk.

9. Changes

Fresh acceptance is required before a materially different purpose, direction, action level, recipient population, content processor, retention period, autonomous sending, marketing use, rate or accepted spending limit becomes effective.

Password rotation, technical bug fixes and nonmaterial clarifications do not require fresh acceptance when they do not materially change the accepted purpose, risk, data use, authority or price.

10. Electronic acceptance

The final review screen must require an unselected checkbox displaying:

> I represent that I am a current owner or administrator authorized to bind the Agency identified in the Activation Summary. On the Agency's behalf, I accept the displayed Vero Text Additional Module Order, this Schedule, the Messaging Terms and the Activation Summary. I authorize only the displayed numbers, purposes, action level, data processing, providers, price and billing terms.

The activation button must read:

> Accept and turn on Vero Text

COVU will preserve the Activation Summary, canonical configuration digest, every accepted document version and SHA-256, displayed acceptance language, checkbox state, accepter identity and role, authority attestation, timestamp, payment or invoicing reference, supersession and revocation in the agreement ledger and provide a downloadable receipt.

Activation alone does not send a message, arm autonomous sending or satisfy a recipient-consent requirement.