Skip to content

Commit

Permalink
Merge pull request #554 from SourcePointUSA/tom-win87-patch-1
Browse files Browse the repository at this point in the history
Add note about when to use .supportLegacyUSPString
  • Loading branch information
andresilveirah committed Mar 1, 2024
2 parents 387ec58 + 83159a5 commit c1c2fcf
Showing 1 changed file with 5 additions and 0 deletions.
5 changes: 5 additions & 0 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -504,6 +504,11 @@ var consentManager = SPConsentManager(
## Support U.S. Privacy (Legacy) with U.S. Multi-State Privacy

If you're transitioning from U.S. Privacy (Legacy) to U.S. Multi-State Privacy, you may want to continue supporting the legacy US privacy string (`IABUSPrivacy_String`).

> Since U.S. Privacy (Legacy) does not have support for sensitive data categories, any organization who require sensitive data opt-ins should not use this approach. Additionally, this approach should not be used by organizations who ***only*** require Sharing of Personal Information/Targeted Advertising. A `uspString` will only be set if you use either of the following privacy choices:
> - Sale of Personal Information
> - Sale or Sharing of Personal Information/Targeted Advertising
To do so, when instantiating the SDK, make sure to set the flag `.supportLegacyUSPString` to true. Example:
```swift
var consentManager = SPConsentManager(
Expand Down

0 comments on commit c1c2fcf

Please sign in to comment.