Description🔗

In connection with the adoption of the GDPR law in the countries of the European Union, it is not possible to collect users' data without their agreement. MRGS offers you a convenient tool for easy GDPR integration into your product.

MRGS allows you to:

• Display the agreement window using our resources:
  • Show HTML-based window:
    • Your HTML layout is used for display.
    • Our standard HTML layout is used for display.
  • Call delegate methods based on the results of user actions.
  • Set display options.
  • Localize the agreement.
• Find out the version that the user has agreed to.
• Work with your fully custom interface.
  • You just tell us the result of user actions.

Examples🔗

Display using our resources by use of the HTML layout🔗

Our standard agreement (left) and an example of a custom agreement (right):

Using your own interface🔗

If you don't want to use HTML to render the agreement, and you'd like to control the process yourself, then you can use our methods that enable work with your interfaces and just tell us if the user has accepted the agreement.

Here's an example of custom agreement working with our API:

Key features🔗

• Simple universal API. You can quickly and easily implement GDPR use on any platform due to the simplicity of the API.
• Support for multiple display options. You can show either our agreement or custom, made up either using HTML or built with native.
• Automatic localization. We support localization of the agreement (available only for display option using HTML).

Steps to implement into the project🔗

Step 1. Decide which option to choose🔗

Next you need to decide which option to take:

• Display and rendering of the interface using our resources by use of HTML layout.
  • Pros:
    • Extremely easy to implement, just a few lines of code needed.
    • Built-in localization.
    • We keep agreements up to date.
  • Cons:
    • HTML layout needed for custom design.
    • There may be a slight delay in loading on older devices.
• Display and rendering of the interface by your means, with the results of actions reported to us.
  • Pros:
    • The agreement interface will be identical to the application interface.
    • Fast loading.
  • Cons:
    • Need to draw the interface yourself.
    • Harder to embed and maintain.
    • Must add your own localization.

Step 2. Add SDK to the client🔗

Depending on the option chosen, add the SDK to the client:

• Display and rendering of the interface using our resources by use of HTML layout.
• Display and rendering of the interface by your means, with the results of actions reported to us.

Step 3. Conduct Integration Testing🔗

To verify that GDPR is correctly displayed and the integration was successful, you can use any of three methods below (provided that the onlyEU flag is set to true ):

1. Change the locale on the device. Change the device locale to any of the included in GDPR (you can find the list below in the "Countries" section), start the application - the GDPR window should appear.
2. VPN. Set a locale that is not affected by GDPR (for example, Russia) on the device. Use a VPN to emulate a situation when the user is in a country falling under GDPR (the list is given below in the "Countries" section), start the application - the GDPR window should appear.
3. Turning off the Internet. Set a locale that is not part of GDPR (for example, Russia) on the device, turn off the network services on the device, start the application - the GDPR window should appear.

MRGSGDPR features🔗

If the onlyEU flag is set, we can determine where the user is from. The country is determined by the user's IP. The IP request time does not exceed 5 seconds. The agreement will also be shown in case of failure to determine the country by IP.

Countries🔗

We show the agreement to the users from the following countries (if OnlyEU flag is set): «BE», «FR», «DE», «IT», «LU», «NL», «DK», «GB», «GR», «PT», «ES», «AT», «FI», «SE», «CY», «CZ», «EE», «HU», «LV», «LT», «MT», «PL», «SK», «SI», «BG», «RO», «HR», «NO», «LI», «IS».

Shown agreement🔗

You can get acquainted with the documents that are shown to the user by following the links:

1. Terms of usage (EULA)
2. Privacy Policy

To view the agreement in other languages, substitute the language you want instead of lang=en at the end of the link, for example,lang=ru. Available languages: ru, en, zh, "zh-CN", "zh-TW", fr, de, it, ja, ko, pt, es, tr (in the future, their number may change, you can check actual supported languages with the getSupportedLocalizations method in the client SDK)

List of personal data🔗

Deletion of personal data🔗

According to the GDPR law, the user can request that his user data be removed from the systems. To do this, usually, the user must first delete the application, and then write to support with a request to delete personal data.

In case you have received a request from a user to delete personal data, you need to set a task for the MRGS project (if you do not have access to JIRA, you can contact us directly), and specify the user's ID. We will then delete all user data.

Reset Settings🔗

This method will be useful if the user has requested the deletion of their user data collected by the project. If the project satisfies his request and deletes his account, then when creating a new account, you need to show the acceptance window GDPR for the new user account again. In this case, it is enough to call the following method, which will delete all the local saved data of the MRGSGDPR module and reset the settings to their original position, which will make it possible to show the GDPR window to the user again:

MRGSGDPR.Instance.ResetModule();

MRGSGDPR.getInstance().resetModule();

[[MRGSGDPR sharedInstance] resetModule];

import games.my.mrgs.gdpr.MRGSGDPR;

MRGSGDPR.getInstance().resetModule(Context);