Privacy Policy

pursuant to Article 13 of Regulation (EU) 2016/679 ("GDPR")

Effective date: October 23, 2026 ·Versione italiana

1. Scope

This policy describes the processing of personal data in connection with the use of the mobile application Riviera Rush (application id com.zipangulu.lidorush), available for Android and iOS and published by Claudio Pellegrino.

2. Controller

The controller is Claudio Pellegrino, who publishes the application (the "Controller"), and who can be contacted at rivierarush.game@gmail.com.

3. Data processed and purposes

3.1 Data stored on the device. The application stores the user's game progress and preferences in the app's private storage on the device. This data is not transmitted to the Controller or to third parties and is deleted when the application is uninstalled. The application does not require an account and does not collect identifying data such as name, email address or contacts, except when the user chooses to write to the Controller (section 3.8).

3.2 Advertising. The application is free and is funded by advertising provided by Google AdMob (Google Ireland Limited). For the delivery, measurement and fraud prevention of ads, the following may be processed: the device's advertising identifier; the IP address, from which an approximate location may be derived; technical information about the device and the application; data relating to interactions with ads. On iOS the advertising identifier is used only if the user allows it through Apple's tracking request.

3.3 Notifications. If the user allows them, the application schedules local notifications, generated by the device itself, which involve no transmission of data.

3.4 Error and performance diagnostics. The application is built with the Unity engine, whose diagnostics service (Unity Technologies) sends the Controller reports on crashes, freezes and performance, so that errors can be found and fixed. These reports may include: technical information about the device and its operating system (for example model, system version, memory and graphics hardware); performance data of the application; a pseudonymous identifier of the installation; and, when an error occurs, the related technical report. They do not include data that directly identifies the user.

3.5 Usage statistics. To understand how the application is used and to improve it, the Controller uses Google Analytics for Firebase (Google Ireland Limited). The following may be processed: game events (for example sessions, progress, use of features, rewarded ads watched); an identifier of the application installation; technical information about the device and the application (for example model, operating system and application version, language); the country, roughly derived from the IP address; date and length of sessions.

On Android devices, and only where the user allows it when required (section 4), the statistics are also used to measure the effectiveness of the advertising campaigns through which the Controller promotes the application on Google Ads, for example which campaign led to the installation and whether the application is then used. For this purpose the device's advertising identifier and the game events may also be processed and shared with Google Ads. The statistics are not used to show the user personalised advertising.

3.6 Crash reports. If the application closes because of an error, Firebase Crashlytics (Google Ireland Limited) sends the Controller a technical report, so that the error can be found and fixed. The report may include: where in the program the error occurred; technical information about the device and its operating system; the state of the device at that moment (for example available memory); pseudonymous identifiers of the installation, among them the support code described in section 3.8. It does not include data that directly identifies the user.

3.7 Remote settings. Through Firebase Remote Config (Google Ireland Limited) the application receives some game settings, so that they can be adjusted without updating it. For this purpose an installation identifier and the necessary technical information (for example application version, platform and language) are transmitted.

3.8 Messages to the Controller. From the pause card of the application the user can report a problem or send an idea or a question. The application then opens the user's own email app with a message already addressed to the Controller, which the user may change or not send at all. If the user sends it, the Controller receives the user's email address, the message and the technical details written at its end: application version, device model and operating system, screen size, memory and graphics hardware, language, beach and day of the game, and the support code. The support code is a random code created by the application on the device; it is also attached to the crash reports of section 3.6, so that a reported problem can be matched with its report. These data are used only to answer the user and to fix the problem.

4. Legal basis and consent

For users located in the European Economic Area, the United Kingdom and Switzerland, the processing of data for personalised advertising is based on the user's consent (Article 6(1)(a) GDPR), collected at first launch through Google's consent management platform, before the advertising services are activated. In the absence of consent, ads with limited data processing may be shown, in accordance with Google's policies.

The user may change or withdraw consent at any time from the application's menu, under "Privacy settings". Withdrawal does not affect the lawfulness of processing carried out before it. The advertising identifier can also be reset or deleted in the device settings.

For the same users, the statistics described in section 3.5 are based on consent (Article 6(1)(a) GDPR), collected through the same Google platform: they stay switched off until the user consents to the storage of information on the device and to the measurement of content, and they are switched off if consent is withdrawn from "Privacy settings". For users located elsewhere, they are based on the Controller's legitimate interest in improving the application (Article 6(1)(f) GDPR).

For the same users, the measurement of the Controller's advertising campaigns described in section 3.5 also requires consent to the measurement of advertising performance, given on the same platform and extended to Google; without it the statistics, if allowed, are limited to improving the application. For users located elsewhere it is based on the Controller's legitimate interest in promoting the application (Article 6(1)(f) GDPR).

The processing described in sections 3.4, 3.6 and 3.7 is based on the Controller's legitimate interest in keeping the application working, fixing its errors and adjusting its settings (Article 6(1)(f) GDPR). The user may object to it at any time by writing to the address given in section 2.

The processing described in section 3.8 is based on the request of the user who writes to the Controller (Article 6(1)(b) GDPR) and on the Controller's legitimate interest in replying and fixing the problems reported (Article 6(1)(f) GDPR).

5. Recipients and transfers

The data referred to in section 3.2 is processed by Google as an independent controller, in accordance with its own policies: How Google uses information from sites or apps that use its services and the Google Privacy Policy. Google may also process the data outside the European Economic Area, with the safeguards provided for by the GDPR.

The data referred to in section 3.4 is processed by Unity Technologies to provide the diagnostics service, in accordance with the Unity Privacy Policy. Unity may also process the data outside the European Economic Area, with the safeguards provided for by the GDPR.

The data referred to in sections 3.5, 3.6 and 3.7 is processed by Google, as a processor on behalf of the Controller, to provide the Firebase services: Privacy and Security in Firebase. For the campaign measurement described in section 3.5 the data is shared with Google Ads, under the Google Ads Data Processing Terms. Google may also process the data outside the European Economic Area, with the safeguards provided for by the GDPR.

The application is distributed through Google Play and through Apple's App Store and TestFlight, which process their own data about downloads, installations and, where the user has allowed it, errors and performance, in accordance with their respective policies. Within testing programmes, the platform provides the Controller with the email address the user joined with, which is used solely to manage the test. The request to rate the application that may appear in the game is shown by Google Play or the App Store: the Controller receives no data from it, other than the review the user chooses to publish.

The messages described in section 3.8 reach the Controller's mailbox at Google (Gmail), which processes them to provide the email service in accordance with its own policies.

6. Retention

The Controller does not keep users' personal data on its own systems. The statistics referred to in section 3.5 are kept by Google on behalf of the Controller for 2 months, the reports referred to in section 3.6 for 90 days. Other data processed by Google and by Unity is retained in accordance with their respective policies. Email addresses of test participants are kept for the duration of the testing programme. The messages referred to in section 3.8 are kept in the Controller's mailbox only as long as needed to answer and to follow up the request.

7. Children

The application is not intended for children under 13, and the Controller does not knowingly collect personal data from children.

8. Rights of the data subject

Users have the right to request access to their personal data, its rectification or erasure, the restriction of processing and data portability, to object to processing and to withdraw consent at any time, and to lodge a complaint with a supervisory authority (in Italy, the Garante per la protezione dei dati personali, www.garanteprivacy.it). For data processed by Google, these rights may also be exercised directly with Google. Requests to the Controller can be sent to rivierarush.game@gmail.com.

9. Changes

This policy may be updated, in particular when new services are introduced. The updated version is published at this address, with its effective date, before the version of the application concerned is distributed.

Riviera Rush · All apps by Claudio Pellegrino