Making changes requested by legal [netlify-build]

Author: forstisabella

src/privacy/hipaa-eligible-segment.md

@@ -22,6 +22,13 @@ Ensure your Workspace is eligible for HIPAA before you configure and send any pe
 With the BAA signed and Workspace confirmed as eligible, you can start building. For more information about starting a HIPAA compliant implementation, see Twilio's [Architecting for HIPAA on Twilio](https://twil.io/architecting-for-hipaa){:target="_blank"}, which outlines the shared responsibilities and requirements for building and maintaining HIPAA-compliant workflows in Segment.
 
 ## HIPAA Auditing
-Segment maintains audit logs of every read and update action a user performs in the Segment app that may or may not involve PHI/PII. These logs can be provided upon request.
+Segment maintains audit logs of every read and update action a user performs in the Segment app that may involve PHI/PII. 
 
-For specific requests, please reach out to [[email protected]](mailto:[email protected]){:target="_blank"}.
+Data captured in the HIPAA audit logs includes:
+ - `workspace_id`: unique identifier of the workspace
+ - `actor_user_id`: unique identifier Segment assigns to the logged in user
+ - `event_type`: The action performed by the user. For example, `Source Debugger Raw Viewed`, `Destination Filter Modified`, or other events
+ - `end_user_id`: Segment sometimes assigns this unique identifier to an end-user, event, audience, or journey, depending on the event type
+ - `timestamp`: Time, in UTC, when the action occurred
+
+These logs can be provided upon request. For specific requests, please reach out to [[email protected]](mailto:[email protected]){:target="_blank"}.