Annual privacy notice and opt-outs

How do we deliver the GLBA privacy notice on its cycle to every customer who must receive it, capture opt-outs, and record delivery and elections against the policy?

Make the notice cycle a computation on the customer base and the opt-out a recorded election. Callvu determines for each customer whether the annual notice is due (or whether the annual notice exception applies because the carrier shares only within the exceptions and the notice has not changed), delivers the notice in the form and channel the rule allows (paper, or electronic with the customer's consent, or by a reasonable means under the alternative delivery method), presents the opt-out choices for sharing with non-affiliated third parties and for affiliate marketing where they apply, captures the election on a secure screen or from the reply, applies it across the policy, claims and marketing systems, and writes the delivery, the version and the election against each policy.

In scopeSimpleCallvu moves: write back

Talk to an expert Try it in the sandbox

Last updated November 7, 2026.

The problem today

The opt-out came back on a paper reply card, was keyed a month later into the policy system, and the marketing platform never heard about it.

Today, without Callvu

Every year the carrier mails a privacy notice to every customer, whether or not the rule requires it that year, at a cost that would fund a small team. The reply cards come back; the elections are keyed into one system; the marketing platform keeps its own list. A customer who opted out receives a joint-marketing offer, and the complaint cites the notice they returned.

GLBA and Regulation P require an initial notice at the start of the relationship and an annual notice thereafter, with an exception since 2015: no annual notice is required while the carrier shares nonpublic personal information only under the exceptions that need no opt-out and its practices have not changed since the last notice. The notice must offer an opt-out of sharing with non-affiliates (and the affiliate marketing opt-out under the FCRA where it applies), the opt-out must be honored as soon as reasonably practicable and remain until revoked, and the carrier must be able to show delivery. The states' insurance privacy regulations add their own content and timing.

The notice is a rule about who must receive what; the opt-out is a record that every system must obey.

How it runs

From the requestto the system of record.

The notice cycle date arrives, a customer relationship begins, or the carrier's privacy practices change. Callvu runs the notice determination across the customer base.

Customer: Receives the notice and makes any opt-out election on a secure screen or by reply.
Privacy officer: Owns the notice version and decides exceptions in the Decision Desk.
Policy, claims and marketing systems: Receive and apply the elections.
Callvu: Determines who is due, delivers, captures elections, applies them and writes the record.

Determine who is due
For each customer the rule is computed: an initial notice for a new relationship, the annual notice for an existing one unless the annual notice exception applies (the carrier shares only within the exceptions and the notice is unchanged since the last delivery), a revised notice where practices changed, and the state's additional requirements; the determination is recorded per customer with its reason.
Deliver in an allowed form
The notice version in force is delivered in a form the rule allows: on paper, electronically to a customer who has consented to electronic delivery, or by the alternative delivery method (posted continuously on the website with a statement in another required communication and a toll-free number to request a copy) where its conditions are met; the delivery with its version, channel and date is recorded against the policy.
Capture and apply the opt-out
The notice presents the opt-out choices that apply (sharing with non-affiliated third parties, affiliate marketing) with a reasonable means to exercise them; an election made on a secure screen, by phone or by reply is captured with its time, applied as soon as reasonably practicable to the policy, claims and marketing systems and to the vendor feeds, and kept until the customer revokes it; a customer with a joint account or a joint policy is handled under the joint-account rules.
Write back and prove
The delivery, the notice version, the channel and the election are written against each policy as the record of compliance, a customer's later request for a copy is fulfilled from the version in force, and the privacy officer sees exceptions (an undeliverable address, a conflicting election across products) in the Decision Desk.

Where it ends: Every customer who had to receive the notice did, in an allowed form, with the exception applied where the rule permits, and every opt-out is a recorded election every system obeys. The Decision Trace shows the per-customer determination and its reason; the Audit Trace shows the delivery, the election and each system's application with their times. The Callvu move in this process is write back: the determination, the delivery and the election are written against the policy.

Runtime enforcement

What is enforcedwhile the work runs.

The regulations preloaded in Callvu Studio and the bank's own policies, applied as steps that run, not lines in a binder. A step that breaks a rule does not run, so a completed run was compliant.

Regulations

GLBA (15 USC 6801 to 6809) and the privacy notice rules in Regulation P (12 CFR 1016.4, 1016.5, 1016.7, 1016.9 and 1016.10): A financial institution must provide a clear and conspicuous initial privacy notice to a customer no later than when the relationship is established and an annual notice during each twelve-month period thereafter, except that no annual notice is required while the institution shares nonpublic personal information only under the exceptions in sections 1016.13 to 1016.15 and has not changed its practices since the last notice (section 1016.5(e)); the notice must describe the categories of information collected and shared and provide a reasonable means to opt out of sharing with non-affiliated third parties, which must be honored as soon as reasonably practicable and remain in effect until revoked; delivery must be such that the customer can reasonably be expected to receive actual notice, in writing or electronically with consent, or by the alternative delivery method where its conditions are met.
State insurance privacy regulations (NAIC Model #672 and Model #670 as adopted) and the FCRA affiliate marketing opt-out (15 USC 1681s-3, 12 CFR 1022 Subpart C): The states' insurance privacy regulations mirror GLBA for licensees with additional content and health information rules, and the affiliate marketing rule requires a separate opt-out notice before an affiliate uses eligibility information for marketing, valid for at least five years.
E-SIGN Act (15 USC 7001) consent for electronic delivery: Electronic delivery of the notice to a consumer requires the consumer's affirmative consent given in a manner that reasonably demonstrates they can access the information in the electronic form, which the delivery record captures.

Company policies

The notice determination runs per customer on the rule, including the annual exception, never a blanket mailing.
Delivery is recorded with the version, the channel and the date against the policy as the proof of compliance.
An opt-out is a single recorded election applied to every system and vendor feed, kept until revoked.
The policy system holds the delivery record and the election as the system of record.

Controls

Per-customer notice determination with the exception test.
Allowed-form delivery with electronic consent check.
Opt-out capture with time.
Election applied across policy, claims, marketing and vendor feeds.
Decision Desk for exceptions.
Policy-level record of version, delivery and election.

Clocks and deadlines

GLBA annual notice: Once in each twelve-month period for customers not covered by the annual notice exception; the initial notice at the start of the relationship.
Opt-out application: As soon as reasonably practicable after the election, kept until revoked.
Revised notice: Before the carrier shares in a way the last notice did not describe.

Documents and checks

The per-customer determination with its reason
The notice version and the delivery record
The opt-out election with time and channel
The application confirmations from each system
The policy-level compliance record

In the Decision Trace

The determination and the exception test per customer.
The delivery form chosen and why.
Any exception decision and the privacy officer.

In the Audit Trace

The delivery with time and version.
The election with time.
Each system's application with time.

The handoff

Between the front doorand the back office.

The front door

The notice in the customer's channel of consent; the opt-out on a secure screen, by phone or by reply.

The back office

The privacy officer owns the version and sees exceptions; every system reads one election record.

The Decision Desk

An undeliverable notice, a conflicting election across a customer's products or a joint-account question goes to the privacy officer in the Decision Desk with the record and only the allowed outcomes: redeliver by another allowed form, apply the most restrictive election, or record the reason.

Proof

In scope.Proof at scale, not one process at a time.

The kind of process Callvu runs in production for customers in this industry. Ask for a reference on this exact process. The results below are the industry's published proof; each claim code links to its record on agents.callvu.com.

Phoenix put more than 100 processes live in under 3 months.

Across Callvu customers

More than 1,000 processes are live across Callvu customers.

Across Callvu customers

Questions

What buyers ask next,answered plainly.

Does every customer get an annual notice?

No. Under Regulation P the annual notice is not required while the carrier shares only within the exceptions and its practices are unchanged; the process computes the determination per customer and records the reason.

How is an opt-out applied?

As one recorded election, applied as soon as reasonably practicable to the policy, claims and marketing systems and the vendor feeds, and kept until the customer revokes it.

Can the notice be delivered electronically?

Yes, to a customer who has given E-SIGN consent, or by the alternative delivery method where its conditions are met; the delivery record shows the form and the consent.

Related processes

Privacy and data access requests Policyholder address and contact change Customer complaint intake and response Try it in the sandbox All insurance processes

Bring this process, or the one that costs you most.

We build it against your policies and your systems, train your team and stay with you through launch. You are live in weeks.