Skip to content

🛡️ Add investor notice procedures - #12

Merged
JFWooten4 merged 7 commits into
mainfrom
customer-notice-procedures
Jun 3, 2026
Merged

JFWooten4 merged 7 commits into
mainfrom
customer-notice-procedures

Conversation

@JFWooten4

Copy link
Copy Markdown
Member

Creates customer notice procedures for Regulation S-P compliance under 17 CFR § 248.30(a)(4). The procedures should define when BlockTransfer must provide notice to affected individuals, how notice determinations are made, what information must be included in the notice, how the 30-day timing requirement is tracked, and how service-provider incidents are handled.

Recordkeeping implementation is out of scope for this PR and should be handled separately under the transfer-agent recordkeeping issue.

Regulatory basis

Subsection (a)(3)(iii): customer notification procedures

Notify each affected individual whose sensitive customer information was, or is reasonably likely to have been, accessed or used without authorization in accordance with paragraph (a)(4) of this section unless the covered institution determines, after a reasonable investigation of the facts and circumstances of the incident of unauthorized access to or use of sensitive customer information, that the sensitive customer information has not been, and is not reasonably likely to be, used in a manner that would result in substantial harm or inconvenience.

Subsection (a)(4)(i): notification obligation

Unless a covered institution has determined, after a reasonable investigation of the facts and circumstances of the incident of unauthorized access to or use of sensitive customer information that occurred at the covered institution or one of its service providers that is not itself a covered institution, that sensitive customer information has not been, and is not reasonably likely to be, used in a manner that would result in substantial harm or inconvenience, the covered institution must provide a clear and conspicuous notice, or ensure that such notice is provided, to each affected individual whose sensitive customer information was, or is reasonably likely to have been, accessed or used without authorization. The notice must be transmitted by a means designed to ensure that each affected individual can reasonably be expected to receive actual notice in writing.

Subsection (a)(4)(ii): affected individuals

If an incident of unauthorized access to or use of customer information has occurred or is reasonably likely to have occurred, but the covered institution is unable to identify which specific individuals' sensitive customer information has been accessed or used without authorization, the covered institution must provide notice to all individuals whose sensitive customer information resides in the customer information system that was, or was reasonably likely to have been, accessed or used without authorization. Notwithstanding the foregoing, if the covered institution reasonably determines that a specific individual's sensitive customer information that resides in the customer information system was not accessed or used without authorization, the covered institution is not required to provide notice to that individual under this paragraph.

Subsection (a)(4)(iii): timing

A covered institution must provide the notice as soon as practicable, but not later than 30 days, after becoming aware that unauthorized access to or use of customer information has occurred or is reasonably likely to have occurred unless the United States Attorney General determines that the notice required under this rule poses a substantial risk to national security or public safety, and notifies the Commission of such determination in writing, in which case the covered institution may delay providing such notice for a time period specified by the Attorney General, up to 30 days following the date when such notice was otherwise required to be provided.

The notice may be delayed for an additional period of up to 30 days if the Attorney General determines that the notice continues to pose a substantial risk to national security or public safety and notifies the Commission of such determination in writing.

In extraordinary circumstances, notice required under this section may be delayed for a final additional period of up to 60 days if the Attorney General determines that such notice continues to pose a substantial risk to national security and notifies the Commission of such determination in writing.

Beyond the final 60-day delay under this paragraph (a)(4)(iii), if the Attorney General indicates that further delay is necessary, the Commission will consider additional requests for delay and may grant such delay through Commission exemptive order or other action.

Subsection (a)(4)(iv): notice contents

The notice must:

(A) Describe in general terms the incident and the type of sensitive customer information that was or is reasonably believed to have been accessed or used without authorization;

(B) Include, if the information is reasonably possible to determine at the time the notice is provided, any of the following: the date of the incident, the estimated date of the incident, or the date range within which the incident occurred;

(C) Include contact information sufficient to permit an affected individual to contact the covered institution to inquire about the incident, including the following: a telephone number (which should be a toll-free number if available), an email address or equivalent method or means, a postal address, and the name of a specific office to contact for further information and assistance;

(D) If the individual has an account with the covered institution, recommend that the customer review account statements and immediately report any suspicious activity to the covered institution;

(E) Explain what a fraud alert is and how an individual may place a fraud alert in the individual's credit reports to put the individual's creditors on notice that the individual may be a victim of fraud, including identity theft;

(F) Recommend that the individual periodically obtain credit reports from each nationwide credit reporting company and that the individual have information relating to fraudulent transactions deleted;

(G) Explain how the individual may obtain a credit report free of charge; and

(H) Include information about the availability of online guidance from the Federal Trade Commission and usa.gov regarding steps an individual can take to protect against identity theft, a statement encouraging the individual to report any incidents of identity theft to the Federal Trade Commission, and include the Federal Trade Commission's website address where individuals may obtain government information about identity theft and report suspected incidents of identity theft.

Subsection (a)(5)(ii): service-provider notice on behalf of covered institution

As part of its incident response program, a covered institution may enter into a written agreement with its service provider to notify affected individuals on the covered institution's behalf in accordance with paragraph (a)(4) of this section.

Subsection (a)(5)(iii): covered institution remains responsible

Notwithstanding a covered institution's use of a service provider in accordance with paragraphs (a)(5)(i) and (ii) of this section, the obligation to ensure that affected individuals are notified in accordance with paragraph (a)(4) of this section rests with the covered institution.

Subsection (d)(9): sensitive customer information

Sensitive customer information means any component of customer information alone or in conjunction with any other information, the compromise of which could create a reasonably likely risk of substantial harm or inconvenience to an individual identified with the information.

Changes to be made

  • Create written customer notice procedures for incidents involving unauthorized access to or use of sensitive customer information.
  • Define the reasonable-investigation process used to determine whether notice is required.
  • Define when notice must be provided to each affected individual.
  • Define when notice must be provided to all individuals whose sensitive customer information resides in an affected customer information system.
  • Add a 30-day notice timing workflow measured from awareness that unauthorized access to or use of customer information has occurred or is reasonably likely to have occurred.
  • Create a notice template containing each required notice-content element from Subsection (a)(4)(iv).
  • Define the process for documenting any Attorney General delay notice or national-security/public-safety delay.
  • Define when a service provider may provide notice on BlockTransfer's behalf.
  • Clarify that BlockTransfer remains responsible for ensuring affected individuals are notified even when a service provider sends the notice.
  • Cross-reference the separate incident response program, assessment procedure, service-provider oversight, and transfer-agent recordkeeping workstreams.

@JFWooten4 JFWooten4 self-assigned this May 18, 2026
@JFWooten4 JFWooten4 changed the title 🛡️ Add customer notice procedures 🛡️ Add investor notice procedures May 18, 2026
@JFWooten4

Copy link
Copy Markdown
Member Author

blocked by #38

JFWooten4 and others added 4 commits May 26, 2026 22:14
* 📜 Add open-source collaboration licenses (#17)

* 📄 Add code and content licenses

Co-authored-by: Codex <noreply@openai.com>

* 📄 Normalize AGPL license text

---------

Co-authored-by: Codex <noreply@openai.com>

* 📝 Define customer information

Co-authored-by: Codex <noreply@openai.com>

* 📝 Define investor information tiers

* 📝 Clarify investor information tiers

---------

Co-authored-by: Codex <noreply@openai.com>
Co-authored-by: Codex <noreply@openai.com>
Co-authored-by: Codex <noreply@openai.com>
Co-authored-by: Codex <noreply@openai.com>
@JFWooten4

Copy link
Copy Markdown
Member Author

As much as the templating is blocked by 38 for the contact locale, we need to get the procedure prior to written output in place for the staff compliance deadline.

@JFWooten4
JFWooten4 marked this pull request as ready for review June 3, 2026 01:38
@JFWooten4
JFWooten4 merged commit 0bb646b into main Jun 3, 2026
@JFWooten4
JFWooten4 deleted the customer-notice-procedures branch June 3, 2026 01:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

1 participant