Get Started with Glispa Connect

Overview

Examples

Android

Overview

- Native Ads

List/Feed

Custom

- Standard IAB Formats

Banner

Interstitial

Video

- Others

GDPR

Troubleshooting

Admob Android Adapter

Mopub Android Adapter

DFP Android Adapter

iOS

Overview

- Native Ads

List/Feed

Custom

- Standard IAB Formats

Banner

Interstitial

Video

- Others

GDPR

Troubleshooting

- Adapters

Admob iOS Adapter

Mopub iOS Adapter

DFP iOS Adapter

API Documentation

Reporting API

Help

GDPR FAQ

General

Earnings

Payments and Accounting

Integration

Reporting

Legal and Privacy

Updates

SDK Deprecation Schedule

SDK Change Log

Android Change Log

iOS Change Log

GDPR FAQ

Updated 3 weeks ago by Chris

GDPR FAQ

What is Glispa Connect approach to the GDPR?

Glispa Connect, a product of Glispa, complies with the current EU data protection law , and will comply with GDPR. Our partners including Publishers, SSPs (Supply Side Platforms) and DSPs (Demand Side Platforms) should review our Privacy Policy, our Data Protection Addendum ("DPA") for publishers and advertisers and our Terms & Conditions, which will be updated, before continuing to use the Glispa Connect Services after the GDPR comes into effect.

Is Glispa Connect a controller or a processor?

Glispa Connect is the controller of the data we process of European data subjects as part of our Services. We use that data in accordance with our Privacy Policy. Glispa Connect relies on its publishers to have the appropriate legal grounds or consent for Glispa Connect to process such data.

What data does Glispa Connect collect through its advertising services?

We collect data (including IFA/IDFA, IP addresses, lat long info) to optimize our in-app advertising network and to enhance performance and targeting.

Where can I see your Terms & Conditions, DPAs and Privacy Policy?

You can see our Terms & Conditions, DPA and Privacy Policy in the bellow links:

How a consent gathering solution should look like, so I can gather the consent of my users?

You should implement an app dialog in your app and we recommend you to use a similar language to the following:

What happens if I do not implement a consent gathering solution by May 25, 2018? Will Glispa stop serving ads to my users?

If you do not implement a consent gathering solution, either ready-made or custom by you, you will not be able to pass the consent of your users to our SDK. This means that we will not store, use, or share any personal data, and we will only return contextual ads to your users in the European Economic Area, the United Kingdom, and Switzerland. 

What if the user rejects, they will still able to see ads from Glispa?

If the user rejects on the consent window, then you should pass the negative consent of the user to our SDK. This means that we will still able to serve ads to your users in  the European Economic Area, the United Kingdom, and Switzerland, but only contextual ads. Also, we will not store, use, or share any personal data for the users that rejected at the consent window.

Will the consent dialog has to be redisplayed when Glispa adds new Demand Partners?

No. You don’t have to display the consent dialog again when we add new partners. We will update the list on our website. However, if you add or change partners you are working with, make sure that you update this information on your privacy policy or website.

Should the consent dialog list all of the partners that Glispa Connect shares personal data with?

No, we recommend to create a custom text in the consent dialog and use a language similar to the following.

"We allow third-party companies to serve ads and collect certain anonymous information when you visit our app. These companies may use anonymous information such as your Google Advertising ID, your device type and version, location and other technical data relating to your device, in order to provide advertisements. Please see more to our privacy policy".

Make sure that you redirect your users to your privacy policy which should include a clear statement that you are using Glispa to serve ads with a link to our privacy policy or website.

On our website we publish the list of all our demand partners and it’s available to the public.

Will Glispa collect the consent from end-users?

No, as you (the publisher) have the right to speak to your users, we require you to request consent for us and to pass a value of the consent to our SDK as described for Android and iOS.

Do I have to collect consent from end-users that are located only on EEA?

Officially, you’re only required to collect user consent within EEA, Switzerland and the UK. However, as best practice, we recommend gathering consent from all users at once, no matter where they are currently located in order to avoid any mistakes of not collecting consent form EU residents who are traveling or are on vacations elsewhere. 

Is it possible to use Google's Consent SDK or other consent gathering solution instead of creating a custom one by our side?

Yes, you can do that as long as you collect consent and pass the value of obtained consent to our SDK. You can see how to pass the consent if you are using Google's or MoPub's consent gathering solution for Android or iOS.


Was this article useful?