Repository navigation
🛡️ Add investor notice procedures - #12
Merged
Merged
Conversation
Member
Author
|
blocked by #38 |
* 📜 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>
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
marked this pull request as ready for review
June 3, 2026 01:38
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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
Subsection (a)(4)(i): notification obligation
Subsection (a)(4)(ii): affected individuals
Subsection (a)(4)(iii): timing
Subsection (a)(4)(iv): notice contents
Subsection (a)(5)(ii): service-provider notice on behalf of covered institution
Subsection (a)(5)(iii): covered institution remains responsible
Subsection (d)(9): sensitive customer information
Changes to be made