[netlify-build]

forstisabella · forstisabella · commit 9454977d7b7c · 2023-08-24T14:17:57.000-04:00
diff --git a/src/privacy/hipaa-eligible-segment.md b/src/privacy/hipaa-eligible-segment.md
@@ -40,7 +40,7 @@ Segment encrypts the data in select fields [marked as yellow in the Privacy Port
 > info "Data encryption is currently in public beta"
 > Data encryption only supports event-stream, cloud-mode destinations. Only data fields in `context`, `traits`, and `property` objects can be encrypted. 
 >
-> After Segment encrypts the data, the encrypted data value will always be a `string`. Any downstream validation that looks for `integer` data types will fail for encrypted values.
+> After Segment encrypts the data, the encrypted data value will always be a `string`. Any downstream validation that looks for `integer` or `boolean` data types will fail for encrypted values.
 
 ### Configure data encryption for a new destination
 

Original file line number	Diff line number	Diff line change
`@@ -40,7 +40,7 @@ Segment encrypts the data in select fields [marked as yellow in the Privacy Port`
`40`	`40`	`> info "Data encryption is currently in public beta"`
`41`	`41`	> Data encryption only supports event-stream, cloud-mode destinations. Only data fields in `context`, `traits`, and `property` objects can be encrypted.
`42`	`42`	`>`
`43`		-> After Segment encrypts the data, the encrypted data value will always be a `string`. Any downstream validation that looks for `integer` data types will fail for encrypted values.
	`43`	+> After Segment encrypts the data, the encrypted data value will always be a `string`. Any downstream validation that looks for `integer` or `boolean` data types will fail for encrypted values.
`44`	`44`
`45`	`45`	`### Configure data encryption for a new destination`
`46`	`46`