SDK Opt-In and Opt-Out Practices

Important: Guidelines on this page do not constitute legal advice. Please consult with your legal team on compliance with privacy laws.


Compliance to privacy focused laws is fully capable within the Singular platform and we continually provide you the tools needed to utilizing Singular to its fullest while remaining in compliance as new laws are enacted or old ones are newly interpreted.

General privacy laws such as GDPR, CCPA and others can require online services to have either an integrated consent gate or user selectable options to disable tracking (generally referred to as the “Opt-In” and “Opt-Out” methods respectively).

Children's privacy laws such as COPPA can require online services that target mixed audiences of children and older users to have an Age Gate upon entry before any tracking of children can take place. This should be treated like the “Opt-In” method described below.

Note: For apps targeting solely children, please contact your account team for additional details on how to effectively utilize Singular in compliance with COPPA.


For the Opt-In Method, you should refrain from initializing Singular until you receive consent. Once consent is granted, you can initialize Singular and proceed as normal. Users should still have the opportunity to Opt-out at a later time. For this case, also implement and follow the logic for the Opt-Out method.



For Opt-Out, initialize Singular on App Opens but be sure to provide a mechanism that allows for opting out. If a user then proceeds to Opt-out through the mechanism provided within the app, proceed to call the following to prevent anything further from being sent to Singular:


If the user later decides to opt back in, call the following to resume sending data to Singular:



Note: These methods are generally considered acceptable at this time, but full interpretation of these laws and your compliance with them should be determined by your own privacy or legal teams.


Was this article helpful?