GDPR Compliance

The Neerby SDK allows compliance with the GDPR regulation. The end user must give his explicit permission to the app to collect data & store data.

Depending on the terms of your contract with Ezeeworld, one or multiple purposes are created and attached to your application. Each purpose is defined by a name (e.g tech.purpose.purpose_name) and a retention period for each data type (sessions, user properties, stop locations, ATR data).

Enabling a purpose

To enable a purpose the app must asks the user (using a modal dialog, a setting panel....) and call the following method:

[[B4SSingleton sharedInstance] setStatus:TRUE forPurpose:@"tech.purpose.purpose_name"];

B4SSingleton.sharedInstance().setStatus(true, forPurpose:"tech.purpose.purpose_name`")

Disabling a purpose

To enable a purpose the app must asks the user (using a modal dialog, a setting panel....) and call the following method:

[[B4SSingleton sharedInstance] setStatus:FALSE forPurpose:@"tech.purpose.purpose_name"];

B4SSingleton.sharedInstance().setStatus(false, forPurpose:"tech.purpose.purpose_name")

Getting a purpose status

To get the status of a purpose:

[[B4SSingleton sharedInstance] statusForPurpose:@"tech.purpose.purpose_name"];

B4SSingleton.sharedInstance().statusForPurpose("tech.purpose.purpose_name")