Skip to content

Commit dc83256

Browse files
committed
Add note from Atit about type validation
1 parent 3c2e436 commit dc83256

File tree

1 file changed

+5
-3
lines changed

1 file changed

+5
-3
lines changed

src/privacy/hipaa-eligible-segment.md

Lines changed: 5 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -35,12 +35,14 @@ These logs can be provided upon request. For specific requests, please reach out
3535

3636
## Data encryption
3737

38-
When workspace owners add new destinations to a HIPAA eligible Segment workspace, they can encrypt any fields [marked as yellow in the Privacy Portal](/docs/privacy/portal) before data is sent to the destination.
38+
You can automatically encrypt the data in any fields [marked as yellow in the Privacy Portal](/docs/privacy/portal) before data is sent to your destinations.
3939

40-
> info "Auto encryption is currently in public beta"
40+
After Segment encrypts the data, it converts the data type to `string`. Any validation that looks for the datatype `integer` will fail for encrypted values.
41+
42+
> info "Data encryption is currently in public beta"
4143
> This means that the data encryption features are in active development, and some functionality may change before it becomes generally available. [Contact Segment](https://segment.com/help/contact/){:target="_blank"} with any feedback or questions.
4244
>
43-
> During the public beta, data encryption only supports event-streaming, cloud-mode destinations.
45+
> During the public beta, data encryption supports event-streaming, cloud-mode destinations.
4446
4547

4648
### Configure data encryption for a new destination

0 commit comments

Comments
 (0)