diff --git a/conduct/COC_POLICY.md b/conduct/COC_POLICY.md
index 5803d3d5..8c01314e 100644
--- a/conduct/COC_POLICY.md
+++ b/conduct/COC_POLICY.md
@@ -53,7 +53,7 @@ The number and relevant details of the reported incidents, escalation requests,
 
 ## Record keeping
 
-A record of all communications related to an incident report, escalation request, or appeal must be kept.
+A record of all information and communications related to an incident report, escalation request, or appeal must be kept, while ensuring that the requirements of OpenJS’s [privacy policy][] are met.
 
 ## Confidentiality
 
@@ -97,7 +97,8 @@ Projects may opt-in to enforce the code of conduct themselves provided they meet
 6. Publicly document their decision-making process for responding to incident reports.
 7. Document the foundation's escalation and appeal process alongside the code of conduct.
 8. Participate in good faith in the [escalation](#escalation) and [appeal](#appeals) processes.
-
+9. Raise questions or concerns arising during management of an incident report with the CoC Team.
+ 
 ## Moderation
 
 Each project is free to implement moderation processes appropriate for the size and scope of the project provided these processes abide by the code of conduct and by this policy.
@@ -110,7 +111,7 @@ The CoC Team is empowered to manage escalation requests of incident reports mana
 
 If the CoC Team finds that the escalation request has merit, the CoC Team may decide to take over the management of the incident report or refer the issue to the Cross Project Council which may request changes to the existing management process. 
 
-Projects are expected to participate in good faith in the escalation process and to share all the information related to the incident report with the CoC Team. The CoC Team is expected to consider project and community needs during the escalation process and may involve the Cross Project Council if necessary and project leadership if appropriate.
+Projects are expected to participate in good faith in the escalation process and to share all [records][] related to the incident report with the CoC Team. The CoC Team is expected to consider project and community needs during the escalation process and may involve the Cross Project Council if necessary and project leadership if appropriate.
 
 ## Appeals
 
@@ -118,7 +119,7 @@ Harmed individuals and accused individuals have thirty (30) days after a respons
 
 If the initial report was already managed by the CoC Team, a different set of CoC Team members should be chosen to manage the appeal process. The CoC Team may choose to involve external people if needed.
 
-If the appeal follows an incident report managed by a project, the project is expected to participate in good faith in the appeal process and to share all the information related to the incident report with the CoC Team. The CoC Team is expected to consider project and community needs during the appeal and may involve the Cross Project Council if necessary and project leadership if appropriate.
+If the appeal follows an incident report managed by a project, the project is expected to participate in good faith in the appeal process and to share all [records][] related to the incident report with the CoC Team. The CoC Team is expected to consider project and community needs during the appeal and may involve the Cross Project Council if necessary and project leadership if appropriate.
 
 Appeals do not delay or block the execution of decisions communicated in the response.
 
@@ -126,3 +127,5 @@ Appeals do not delay or block the execution of decisions communicated in the res
 [Charter]: https://github.com/openjs-foundation/cross-project-council/blob/main/CPC-CHARTER.md
 [CoC Team Charter]: https://github.com/openjs-foundation/cross-project-council/blob/main/conduct/COC_TEAM_CHARTER.md
 [incident management processes]:  https://github.com/openjs-foundation/cross-project-council/blob/main/conduct/COC_PROCESS_FOR_INCIDENT_MANAGEMENT.md
+[privacy policy]: https://privacy-policy.openjsf.org/
+[records]: #record-keeping
diff --git a/conduct/COC_TEAM_CHARTER.md b/conduct/COC_TEAM_CHARTER.md
index edcd7aa0..77a4a3f1 100644
--- a/conduct/COC_TEAM_CHARTER.md
+++ b/conduct/COC_TEAM_CHARTER.md
@@ -15,6 +15,7 @@ The CoC Team's responsibilities are to:
 - Handle code of conduct [incident reports][incident report].
 - Handle code of conduct [escalation requests][escalation].
 - Handle code of conduct [appeals][appeal].
+- Address or escalate questions and concerns raised by a project that is handling an incident report.
 - Keep the CPC up to date on cases requiring the CPC's attention.
 - Provide regular transparency reports to the CPC.
 - Uphold this charter, the [code of conduct][CoC], and the [code of conduct policy][CoC Policy].