Simple reusable DialogFragment
.
This library offers following:
- supports
DialogFragment
orBottomSheetDialogFragment
style - supports multiple services, already defined ones are AdMob and Firebase
- supports intermediator services as well, also supports to load your ad providers from AdMob
- supports custom service definitions
- is set up via a setup class that allows you to select which possibilities you give the user - any combination of personalised ads, non personalised ads and paid version, depending on what you want. Examples:
- allow personalised ads or paid version only
- allow personalised ads, non personalised ads or paid or free version
- combine whatever you want here...
- optionally enable google's check if user is requesting consent form within the EAA and even use fallback methods to using
TelephoneManager
and/orTimeZone
- optionally adds a
Checkbox
for age confirmation - uses soft opt in by default if you offer e.g. a personalised ads vs non personalised ads version
- it closes the app if the user did not give any consent (i.e if the user clicks the back button in the dialog)
- it manages the user's selected consent decision and remembers it (including location, date and app version)
- it automatically reshows the dialog if the user did not give any consent or if the setup defines that the app is not allowed to be used without ads and the user has not accepted ads at all yet
Such dialogs must always be adjusted to the use case in general, although this one should be fine in most cases.
Checkout following to find out more: EU GDPR
Just to make this clear, I'm no lawyer and I can't guarantee that you are save if you use this library.
Gradle (via JitPack.io)
- add jitpack to your project's
build.gradle
:
repositories {
maven { url "https://jitpack.io" }
}
- add the compile statement to your module's
build.gradle
:
dependencies {
implementation 'com.github.MFlisar:GDPRDialog:1.2.2'
}
- Init the singleton in your application
GDPR.getInstance().init(this);
- call following in your activities
onCreate
GDPRSetup setup = new GDPRSetup(GDPRDefinitions.ADMOB) // add all networks you use to the constructor, signature is `GDPRSetup(GDPRNetwork... adNetworks)`
// everything is optional, but you should at least provide your policy
.withPrivacyPolicy("www.my-privacy-policy.com")
.withAllowNoConsent(true)
.withPaidVersion(allowNonPersonalisedOptionAsWell)
.withExplicitAgeConfirmation(true)
.withCheckRequestLocation(true)
.withCheckRequestLocationFallbacks(true /* fallback to TelephoneManager */, true /* fallback to TimeZone */)
.withCheckRequestLocationTimeouts(readTimeout, connectTimeout)
.withBottomSheet(true)
.withForceSelection(true)
.withCustomDialogTheme(theme)
.withShortQuestion(true)
.withLoadAdMobNetworks(publisherId(s))
.withNoToolbarTheme(noToolbarTheme)
;
GDPR.getInstance().checkIfNeedsToBeShown(this /* extends AppCompatActivity & GDPR.IGDPRCallback */, setup);
- implement the
GDPR.IGDPRCallback
in your activity
public class ExampleActivity extends AppCompatActivity implements GDPR.IGDPRCallback {
@Override
public void onConsentInfoUpdate(GDPRConsentState consentState, boolean isNewState) {
// handle consent here
}
@Override
public void onConsentNeedsToBeRequested() {
// we need to get consent, so we show the dialog here
GDPR.getInstance().showDialog(this, mSetup);
}
}
- Other usages
// get current consent anywhere in the app after user has given consent
GDPRConsentState consentState = GDPR.getInstance().getConsentState();
// get location, time, app version of given consent
GDPRConsent consent = consentState.getConsent(); // the given constent
GDPRLocation location = consentState.getLocation(); // where has the given consent been given
long date = consentState.getDate(); // when has the given consent been given
int appVersion = consentState.getVersion(); // in which app version has the consent been given
// check if you can use personal informations or not
boolean canCollectPersonalInformation = GDPR.getInstance().canCollectPersonalInformation();
Check out the MinimalDemo to get something to start with or check out the DemoActivity with the example setups for a more complex example
You can simply do this in the GDPRDefinitions. Of course you can always define new networks in project only as well, but if you think you use a service many others do use as well, fell free to add it to the definitions.
Migrations will be explained in the release notes
-
At least translations for all official languages within the european union should be added
- Bulgarian
- Croatian
- Czech
- Danish
- Dutch
- English
- Estonian
- Finnish
- French
- German
- Greek
- Hungarian
- Irish
- Italian
- Latvian
- Lithuanian
- Maltese
- Polish
- Portuguese
- Romanian
- Slovak
- Slovenian
- Spanish
- Swedish