Skip to content

Commit 53142c6

Browse files
committed
Update hipaa-eligible-segment.md
1 parent b7a0c2a commit 53142c6

File tree

1 file changed

+6
-6
lines changed

1 file changed

+6
-6
lines changed

src/privacy/hipaa-eligible-segment.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -36,7 +36,7 @@ These logs can be provided upon request. For specific requests, please reach out
3636

3737
## Data encryption
3838

39-
Segment encrypts the data in fields [marked as yellow in the Privacy Portal](/docs/privacy/portal) using a key pair. 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.
39+
Segment encrypts the data in fields [marked as yellow in the Privacy Portal](/docs/privacy/portal) using a key pair. After Segment encrypts the data, it converts the data type to `string`. Any downstream validation that looks for the datatype `integer` will fail for encrypted values.
4040

4141
> info "Data encryption is currently in public beta"
4242
> 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.
@@ -49,12 +49,12 @@ Segment encrypts the data in fields [marked as yellow in the Privacy Portal](/do
4949
To configure data encryption while setting up a new destination:
5050
1. From the Destinations page in the Segment App, click **Add destination**.
5151
2. Select a destination from the catalog and click **Configure**.
52-
3. On the Select data source page, select the source you want to connect to your destination.
53-
4. Click **Next**.
52+
3. On the destination's overview page, click **Add destination**.
53+
4. On the Select data source page, select the source you want to connect to your destination and click **Next**.
5454
5. On the Setup page, give your destination a name, fill in any optional settings, and select the **Have Segment encrypt sensitive data** checkbox.
5555
6. Open the **Fields** dropdown, select one or more fields you'd like to encrypt and click the **Generate Encryption Keys** button.
5656
7. Copy the Private Key to a secure location - **once you finish setting up the destination, this key cannot be retrieved**.
57-
8. Click **Save**.
57+
8. Click **Create destination**.
5858

5959
> error "Private Key is not recoverable"
6060
> Segment does not save the private key created during the data encryption setup flow, and cannot retrieve the key after you finish setting up your destination. You can generate a new key without decrypting your data using the instructions in the [Configure new key pairs](#configure-new-key-pairs) section.
@@ -80,15 +80,15 @@ If you lose access to your initial private key, you can generate a new key pair
8080
To generate a new key pair:
8181
1. Open the [My destinations page](https://app.segment.com/goto-my-workspace/destinations){:target="_blank”} in the Segment app.
8282
2. Select a destination, and click **Settings**.
83-
3. On the Settings page, deselect the **Have Segment encrypt sensitive data** checkbox.
83+
3.
8484

8585
<!---todo: after test env access, verify steps beyond step #3--->
8686

8787
### Remove encryption
8888

8989
Disabling the **Have Segment encrypt sensitive data** setting removes encryption on all data that comes into a source after the setting was disabled. Disabling the **Have Segment encrypt sensitive data** setting does not decrypt any data that has already been encrypted.
9090

91-
To remove encryption from future data coming into a destination:
91+
To remove encryption from incoming data:
9292
1. Open the [My destinations page](https://app.segment.com/goto-my-workspace/destinations){:target="_blank”} in the Segment app.
9393
2. Select a destination, and click **Settings**.
9494
3. On the Settings page, deselect the **Have Segment encrypt sensitive data** checkbox.

0 commit comments

Comments
 (0)