Repository navigation
📝 Define sensitive customer information - #34
Conversation
* 📄 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>
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. |
* 🛡️ 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>
This can be a standalone page in conjunction with a public disclaimer (now drafted as direct commits) communicating the clarification through #21.