GDPR FAQ
What is Skippables's approach to the GDPR?
Skippables, complies with current EU data protection law, and will comply with GDPR. We understand that our publisher partners and advertising demand partners all have a requirement to comply with the Regulation. Skippables cannot advise you as to whether you are GDPR compliant. However, Skippables has publishers and advertisers that span the globe, so we are working to ensure that our services comply with GDPR, and that these partners can continue to use the Skippables Services after GDPR takes effect on 25 May 2018. Partners should review our Privacy Policy, our Policies for publisher partners and advertising demand partners, and our Terms of Service, which will be updated, before continuing to use the Skippables Services after the GDPR comes into effect.
Skippables products after May 25, 2018
A. Will the Skippables Software Development Kit obtain consent for Skippables's processing of personal data?
Skippables will release an updated Software Development Kit (SDK) before May 25, 2018. By default, the updated SDK will obtain consent from users located in the European Economic Area, the United Kingdom, and Switzerland for the processing of personal data by Skippables and our partners (including advertising demand partners, supported advertising mediation partners, data partners, and fraud and measurement partners) for personalized advertising purposes. Some publisher partners may be allowed to obtain consent on behalf of Skippables and our partners through their own consent solution if they agree to additional terms.
B. I'm a publisher. What happens if I don't update my apps to the new SDK?
To provide continuity of our services to our publisher partners and give your users sufficient time to update their apps to versions using our latest SDK, we will continue to support older versions of the SDK during a short transition period. During this time, older versions of the SDK will continue to collect personal data. However, in order to protect your users' privacy, we will not store, use, or share such personal data, and we will only return contextual ads to your users in the European Economic Area, the United Kingdom, and Switzerland. After this transition period, we will no longer serve ad requests from older versions of the SDK in GDPR applicable regions.
C. What will the Skippables SDK's consent solution look like, and when will the user see it?
We've designed the Skippables SDK consent solution to be a publisher-friendly and out-of-the-box compliance solution. As a publisher partner, you will be able to decide when to show the consent request to your users in your app. Here is what it will look like to your users:

D. What happens if the user does not consent?
If the user does not consent, we will not collect personal data such as the user's advertising identifier, precise location, or interest or demographic information such as age and gender. We may still receive data such as the user's IP address for limited purposes based on separate legal grounds for processing, such as legal necessity or legitimate interests. Our Privacy Policy, which will be updated and available for review before May 25, 2018, will explain our legal bases for processing in further detail.
E. Can the user withdraw consent?
Yes, the user will be able to withdraw consent at any time, as required by GDPR. Publishers who are allowed to use their own consent solution must also provide users with a GDPR-compliant withdrawal of consent mechanism. In addition, all users in the EEA, the UK, and Switzerland will be able to signal their withdrawal of consent to Skippables by enabling the Limit Ad Tracking setting on iOS devices or the Opt out of Personalized Ads setting on Android devices and revisiting an app that has integrated the Skippables SDK. In each case, Skippables will also share the fact that the user has withdrawn consent with our current partners so that they, as independent controllers of that data, can also respect the user's choice.