Privacy

Publishers are responsible for maintaining compliance with applicable privacy laws and regulations. The HyprMX SDK provides a number of flags publishers can use to pass the appropriate value to HyprMX to protect and maintain user data and privacy.

These flags support compliance with the General Data Protection Regulation (GDPR), US privacy laws (CPRA, CPA, VCDPA, etc.), Children's Online Privacy Protection Act (COPPA), and other regional privacy laws. However, consent and privacy requirements may extend beyond these circumstances and should be applied accordingly.

Publishers are required to utilize the ConsentStatus parameter during initialization to indicate a user’s consent status. This flag will be used to indicate a user’s opt-in or opt-out consent for the collection and use of personal data under applicable laws and jurisdictions (GDPR, CPRA, etc.).

If a user provided consent in jurisdictions that require opt-in consent or did not opt out of collection or usage of personal data in jurisdictions that require opt-out consent, set a user’s consent status as below in the initializer:

HyprMX.initialize(withDistributorId: distributorId,
                      userId: userId,
                      consentStatus: CONSENT_GIVEN, // If user provided consent, set this to CONSENT_GIVEN
                      ageRestrictedUser: false, // If you don't know the user is age restricted, set this to false
                      initializationDelegate: hyprDelegate)

If a user did not provide consent in jurisdictions that require opt-in consent or opted out of collection or usage of personal data in jurisdictions that require opt-out consent, set a user’s consent status as below in the initializer:

HyprMX.initialize(withDistributorId: distributorId,
                      userId: userId,
                      consentStatus: CONSENT_DECLINED, // If user declined consent, set this to CONSENT_DECLINED
                      ageRestrictedUser: false, // If you don't know the user is age restricted, set this to false
                      initializationDelegate: hyprDelegate)

If you do not know the user’s consent status set it as unknown in the initializer:

HyprMX.initialize(withDistributorId: distributorId,
                      userId: userId,
                      consentStatus:CONSENT_STATUS_UNKNOWN, // If you don't have consent status for the user, set this to CONSENT_STATUS_UNKNOWN
                      ageRestrictedUser: false, // If you don't know the user is age restricted, set this to false
                      initializationDelegate: hyprDelegate)

Age-restricted User Flag

To adhere to the strictest laws and policies, HyprMX treats users under 16 as children. HyprMX’s Age-restricted User flag assists publishers with child-directed treatment of users to support compliance with applicable regional laws and regulations such as COPPA, GDPR, and Apple App Store policies. The publisher is responsible for determining when to flag the end user as age-restricted user and adhering to applicable laws and policies that require child-directed treatment.

The parameter must be set during initialization. If the user requires a child-directed treatment, set the ageRestrictedUser parameter to true in the initializer.

HyprMX.initialize(withDistributorId: distributorId,
                      userId: userId,
                      consentStatus:CONSENT_STATUS_UNKNOWN, // If you don't have consent status for the user, set this to CONSENT_STATUS_UNKNOWN
                      ageRestrictedUser: true, // Set this to true if the user is under 16 or requires child-directed treatment
                      initializationDelegate: hyprDelegate)

If the user doesn't require a child-directed treatment, set the ageRestrictedUser parameter to false in the initializer.

HyprMX.initialize(withDistributorId: distributorId,
                      userId: userId,
                      consentStatus:CONSENT_STATUS_UNKNOWN, // If you don't have consent status for the user, set this to CONSENT_STATUS_UNKNOWN
                      ageRestrictedUser: false, // Set this to false if the user is not under 16 or if you don't know whether the user is age restricted
                      initializationDelegate: hyprDelegate)

For added protection, if your app is primarily directed at children, indicate to your HyprMX Account Manager so the app can be designated as a child-directed app in the backend. Additionally, you may use the ageRestrictedUser flag to prevent access to IDFA for end-users flagged as children.

If your app is directed at a mixed audience, including children, use the ageRestrictedUser flag to appropriately flag any user who is considered a child under applicable jurisdiction as age-restricted user to prevent access to IDFA for end-users flagged as children.

Last updated