Skip to content

📝 Define sensitive customer information - #34

Merged
JFWooten4 merged 5 commits into
customer-notice-proceduresfrom
define-customer-information
May 27, 2026
Merged

JFWooten4 merged 5 commits into
customer-notice-proceduresfrom
define-customer-information

Conversation

@JFWooten4

Copy link
Copy Markdown
Member

This can be a standalone page in conjunction with a public disclaimer (now drafted as direct commits) communicating the clarification through #21.

JFWooten4 and others added 2 commits May 19, 2026 11:48
* 📄 Add code and content licenses

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

* 📄 Normalize AGPL license text

---------

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

Copy link
Copy Markdown
Member Author

If the only way to log in or control the account is a seed phrase, then the seed phrase is very likely an access device because 18 U.S.C. § 1029(e)(1) includes any “code” or other means of account access that can be used to obtain value or initiate a funds transfer. Reg S-P pulls that access-device definition into the sensitive customer information examples at 17 CFR § 248.30(d)(9)(ii)(A)(4).

That sounds good, and I'm happy to write that carve-out in. The only thing I'm iffy on is putting phone numbers down as Tier-2 data since it doesn't make sense in T3, but it's also not used for authentication. I'm putting it there for now because we don't have a full and proper account recovery support workflow, which would spell out how to deal with a lost private key without using the phone as a means of verification and risk mitigation without mediation.

@JFWooten4
JFWooten4 marked this pull request as ready for review May 27, 2026 02:13
@JFWooten4
JFWooten4 merged commit 04ffc48 into customer-notice-procedures May 27, 2026
@JFWooten4
JFWooten4 deleted the define-customer-information branch May 27, 2026 02:14
JFWooten4 added a commit that referenced this pull request Jun 3, 2026
* 🛡️ Add customer notice procedures

* 📝 Define sensitive customer information (#34)

* 📜 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>

* 📝 Add notices file

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

* 🧹 Remove completed notice issue note

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

* 📝 Add breach notice procedures

* ✏️ Clean up breach notice procedures

---------

Co-authored-by: Codex <noreply@openai.com>
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