Skip to content

Commit 9dda82f

Browse files
chore: Replace HTML with info
1 parent c03cb37 commit 9dda82f

File tree

1 file changed

+4
-10
lines changed

1 file changed

+4
-10
lines changed

src/privacy/consent-management/onetrust-wrapper.md

Lines changed: 4 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -20,15 +20,9 @@ The OneTrust consent banner has three key UI configurations that control how the
2020
- **Opt-In:** The user, by default, does not consent to all categories (except those that you deem to be mandatory). The user is required to select categories that they consent to share data with (or, "opt-in" to data collection)
2121
- **Opt-out:** The user, by default, does consent to all categories. The user can choose to select categories that they do not consent to share data with (or, "opt-out" of data collection)
2222

23-
<div class="premonition info">
24-
<div class="fa fa-info-circle"></div>
25-
<div class="content">
26-
<p class="header">Segment's Analytics.js OneTrust wrapper assumes the following:</p>
27-
<p markdown=1>
28-
**Opt-In** and **Implied** statuses are treated in Segment's OneTrust wrapper as `Opt-In`. **Notice Only**, **Custom**, or **Opt-Out** statuses are treated in Segment's OneTrust wrapper as `Opt-Out`.
29-
</p>
30-
</div>
31-
</div>
23+
24+
> info "Segment's Analytics.js OneTrust wrapper assumes the following:"
25+
> **Opt-In** and **Implied** statuses are treated in Segment's OneTrust wrapper as `Opt-In`. **Notice Only**, **Custom**, or **Opt-Out** statuses are treated in Segment's OneTrust wrapper as `Opt-Out`.
3226
3327
<!-- TODO (IG, 4/2024): the above callout would not render correctly in markdown - figure out why that happened-->
3428

@@ -200,4 +194,4 @@ The following table explains how Segment's OneTrust wrapper works with different
200194
| One or more categories are enabled | No unmapped destinations <br> **or** <br> All unmapped destinations are disabled | All destinations are disabled | No data flows to Segment |
201195
| One or more categories are enabled | No unmapped destinations <br> **or** <br> All unmapped destinations are disabled | One or more destinations are enabled | Data flows to Segment |
202196
| One or more categories are enabled | One or more destinations are enabled | All destinations are disabled | Data flows to Segment |
203-
| One or more categories are enabled | One or more destinations are enabled | One or more destinations are enabled | Data flows to Segment |
197+
| One or more categories are enabled | One or more destinations are enabled | One or more destinations are enabled | Data flows to Segment |

0 commit comments

Comments
 (0)