Privacy Policy
Relations App

Last updated: 2026-11-02

1. General Information

This Privacy Policy describes how the mobile application Relations (“the App”) processes personal data and other information related to the use of the App.

Data Controller:
IGSoft.Net – Marcin Kuszczak
Support email: relations-support@igsoft.net
Privacy email: relations-privacy@igsoft.net

The App is designed in accordance with the principles of privacy by design and data minimization.

Advertising, analytics, diagnostics, and purchase data is also collected directly by third-party service libraries, primarily those provided by Google and RevenueCat. The scope of processing depends on the service, App variant, settings, and required consent. The controller does not receive all data collected by these services or have direct access to all their systems. Sections 5 and 10 describe the respective responsibilities and how to submit requests.

The App is intended for users aged 13 years and older.
It is not directed to children under 13.

2. Data We Process

2.1 Contact Data (Local Processing)

The App accesses and processes contact information stored on the user’s device, including for example:

All contact data used by the core contact-management features of the App is processed locally on the user’s device and/or within the system account configured by the user on the device.

The App:

Contacts may be synchronized with the user’s Google account or another account provider depending on the device and account settings selected by the user. Such synchronization is handled by the relevant account provider under its own terms and privacy policy.

2.2 User Feedback (Firebase Firestore)

The App may allow users to voluntarily submit feedback about the App through a feedback form.

The App does not require a user account or the user's name or email address to submit feedback. However, user-entered content and metadata may contain personal data, so feedback is not assumed to be anonymous in all cases. The Firestore database used by the App stores feedback.

When feedback is submitted, the following information may be transmitted to and stored using Google Firebase and related Google Cloud infrastructure:

This information is used solely to analyze user feedback, understand reported problems, reproduce bugs, improve the App, and support product development.

The developer asks users not to include unnecessary personal data, passwords, payment data, contact data of third parties, or other confidential information in free-text feedback fields.

Users should submit only the information necessary to describe the issue or suggestion.

2.3 App Usage Analytics (Google Analytics for Firebase)

The App may use Google Analytics for Firebase to measure app usage, engagement, and product quality.

Depending on the App’s configuration, Google Analytics for Firebase may automatically collect and process categories of data such as:

The developer does not intentionally use Google Analytics for Firebase to directly identify users by name, phone number, email address, or contact-book content.

Analytics data is used to understand how the App is used, improve features, evaluate performance, and make product decisions.

2.4 Crash Reporting and Diagnostics (Firebase Crashlytics)

The App may use Firebase Crashlytics to detect crashes, diagnose errors, and improve the App’s stability.

Firebase Crashlytics may automatically collect and process categories of data such as:

The App also sends reports of non-fatal errors, diagnostic metadata, and recent App logs that help identify the cause of a problem.

If Google Analytics for Firebase is also enabled, Crashlytics may use Analytics breadcrumb logs to help identify the actions or events that occurred shortly before a crash.

The developer does not intentionally configure Crashlytics to include direct personal identifiers such as names, phone numbers, email addresses, or contact-book content in crash reports.

2.5 Push Notifications and In-App Messages (OneSignal)

OneSignal integration is included only in selected App variants. The currently distributed version does not use OneSignal and handles reminders locally on the device. The following description applies only to variants that include this integration; other variants do not send data to OneSignal.

In variants with OneSignal, the service delivers push notifications and in-app messages. The OneSignal library is configured to block data collection and transmission until consent is recorded in the App. Reading this Privacy Policy does not replace consent to processing where consent is required by law.

OneSignal necessarily processes the technical information required to provide messaging, such as a OneSignal subscription identifier, push token, and device, operating-system, app-version, language, and network information made available by its SDK and the notification platform.

The App does not send OneSignal any contact-book content, names, phone numbers, email addresses, photos, user accounts, external identifiers, tags, or location data. The only App-defined events sent to OneSignal are the names of the three reminder lifecycle events; they have no properties or contact identifiers.

Users can decline or later disable push notifications through the device settings. In-app messages may still be shown while the App is open if they are configured in OneSignal. Disabling notifications does not delete data stored by OneSignal or withdraw consent to all processing carried out by the service.

2.6 Advertising Data (Google AdMob)

The App displays advertisements provided by Google AdMob.

AdMob and its partners may collect and process certain data, which may include for example:

This data may be used for:

Advertising data is processed by Google in accordance with Google’s own terms and privacy documentation.

The developer does not use AdMob data to directly identify specific users and typically receives only aggregated or limited reporting made available by Google.

2.7 In-App Purchases and Revenue Measurement (Google Play Billing and RevenueCat)

The App uses Google Play Billing and RevenueCat to handle, verify, and restore purchases and determine access to paid features. Google handles payment through Google Play, while RevenueCat processes purchase and entitlement information.

The data processed includes a customer identifier assigned by RevenueCat, product identifiers, transaction history and details, purchase dates, and the status of entitlements to paid features, as well as technical information required to operate the service. A RevenueCat identifier does not mean that a user account has been created in the App. The controller does not receive full payment card details as part of this process.

The RevenueCat integration with AdMob also sends events about ad loading, impressions, and interactions, as well as revenue data when made available by AdMob. This data is associated with the RevenueCat customer identifier and used to analyze advertising and purchase revenue. The App does not send the contact book to RevenueCat.

2.8 Remote Configuration (Firebase Remote Config)

The App uses Firebase Remote Config to retrieve App settings, including advertising configuration. The service uses a Firebase installation ID to deliver the configuration for a particular installation. The App does not transmit the contact book as part of this feature.

2.9 Correspondence with Support and the Controller

If a user makes contact by email, the controller processes the sender's address, message content, attachments, and information needed to handle the inquiry or data-related request. Users should provide only the information necessary to resolve the matter.

3. App Permissions and Access to Device Data

To provide its core functionality, the App requires access to certain features and data stored on the user’s device. Permissions are requested only when necessary and are used strictly for the purposes described below.

Access to Contacts

The App requires access to the device contacts in order to display, create, edit, and manage contact information. Contact data is processed locally on the device and is not transmitted to the developer’s own servers as part of the App’s core contact-management functionality.

Access to Phone Features

The App may access phone functionality to allow users to initiate phone calls directly from a contact entry and to display relevant call-related information within the contact interface. The App does not transmit call data to the developer’s own servers for these features.

Access to Camera and Photos

The App may access the device camera and photo library to allow users to capture or select images for contact profiles. Images are stored locally on the device or in the device’s selected account infrastructure and are not uploaded to the developer’s own servers by the App for this feature.

Access to Network Connection

The App requires internet access to support features that involve network communication, including displaying advertisements through Google AdMob, transmitting voluntarily submitted feedback through Google Firebase, sending analytics events to Google Analytics for Firebase, and sending crash and diagnostics data to Firebase Crashlytics, retrieving configuration from Firebase Remote Config, and handling purchases and measuring revenue through Google Play Billing and RevenueCat. In variants that include OneSignal, internet access is also used to operate that service as described in section 2.5.

Contact data is not transmitted over the network to the developer’s own servers by the App’s core contact-management functionality.

4. Purposes of Processing

The App processes data for the following purposes:

5. Data Sharing

The App does not share locally processed contact data with the developer.

Data related to feedback, analytics, diagnostics, and remote configuration is processed with the assistance of:

Advertising-related data may be processed by:

Purchase data is processed by Google Play and RevenueCat. RevenueCat also receives advertising measurement data through its integration with AdMob. OneSignal receives data only from variants that include that integration.

Service provider libraries transmit data directly to their infrastructure. The controller uses the dashboards, reports, and tools they provide within the scope of the available permissions. This does not provide access to all data held by a given provider.

Where a provider processes data on the controller's behalf, the controller is responsible for fulfilling user rights in cooperation with that provider. This applies in particular to feedback stored in Firestore. Where a provider processes data as an independent controller, for example Google account or Google Play payment data for its own purposes, requests concerning that processing should be directed to the provider under its privacy procedures. Provider documentation is listed in section 12.

The App does not sell personal data.

6. Legal Basis for Processing (GDPR)

Where the GDPR applies, the legal bases for processing are as follows:

Where processing is based on consent, users have the right to withdraw it without affecting the lawfulness of prior processing. Available advertising and privacy settings apply to the scope specified by each control; they do not disable all services. For processing for which the controller is responsible, users may contact the controller as described in section 10. For processing by a provider acting as an independent controller, users should follow that provider's procedures. Accepting this Privacy Policy does not constitute blanket consent to all processing described in it.

7. Data Security

Contact data used by the App’s core functionality is stored locally on the user’s device and protected primarily by the security mechanisms of the Android operating system and the user’s device configuration.

Feedback submitted through the App is transmitted over the network and stored using Google Firebase and related infrastructure.

Analytics and diagnostic data is transmitted to Google services, and purchase and measurement data is also sent to RevenueCat. Connections to the Google services described in this policy and to RevenueCat use encryption in transit, such as HTTPS/TLS.

Providers secure their infrastructure in accordance with the documentation for each service. The controller manages access to its own projects and the data made available to it in those services.

Reasonable technical and organizational measures are used to protect data against unauthorized access, misuse, and accidental loss. However, no method of transmission or storage can be guaranteed to be completely secure.

8. International Data Transfers

The App itself does not transfer locally processed contact data internationally on behalf of the developer.

Data processed by Google services used by the App, including Firebase, Google Analytics for Firebase, Firebase Crashlytics, and AdMob, may be processed in countries outside the user’s country of residence, including outside the European Economic Area, in accordance with Google’s applicable legal safeguards and contractual arrangements. RevenueCat and, in variants with the relevant integration, OneSignal may also process data outside the EEA. Information about processing locations and transfer safeguards is available in each provider's privacy documentation and data processing terms listed in section 12.

9. Data Retention

Contact data remains stored on the user’s device and/or selected account provider until deleted by the user or removed through the relevant system or account tools.

The controller retains data under its control for as long as needed for the purposes described in this policy and then deletes it, taking into account legal obligations and the need to establish, exercise, or defend legal claims.

Feedback submitted to Firestore is used to analyze submissions and improve the App. It is regularly deleted on a 90-day cycle. Feedback entries that can be identified are also deleted on request as described in section 10.

Correspondence is retained for as long as needed to handle the matter and meet related legal obligations or protect legal claims, and is then deleted.

Analytics data is retained in accordance with the retention settings configured for the relevant Google Analytics property and Google’s applicable policies.

According to Firebase documentation, Crashlytics keeps crash stack traces and associated identifiers for about 90 days before beginning removal from live and backup systems.

Advertising-related data retention is governed by Google’s policies and settings.

RevenueCat purchase and measurement data is retained for the purposes of managing purchases and entitlements to paid features and analyzing revenue, in accordance with the service's settings and terms. Data processed by Google as an independent controller, including Google account and Google Play payment data, is subject to Google's retention policies.

In variants that include OneSignal, retention of data in that service depends on its settings and policies. The Firestore feedback deletion cycle does not determine retention periods in other services.

Uninstalling the App does not automatically delete contacts stored in the device’s system account, feedback already submitted through Firebase, analytics records already generated, crash reports already received by Google services, or RevenueCat purchase and measurement data. In variants with OneSignal, uninstalling the App also does not constitute a request to delete data in that service.

10. User Rights

Subject to applicable law, users may have the right to:

Because contact data used by the App’s core functionality is not stored on the developer’s own servers, users typically exercise control over such data directly through their device, contact provider, or account settings.

Requests to delete data or exercise other personal data rights may be sent by email to the privacy address listed in section 1. Users should describe their request and provide information that helps locate the data, such as the approximate feedback submission date and a distinctive excerpt. The controller may ask for additional information necessary to identify the data or confirm that the requester is entitled to make the request. Users should not send passwords or full payment card details.

The controller deletes feedback entries stored in Firestore that can be identified. If the available information does not allow the data to be linked to the requester, or there is a legal basis for retaining it, the controller explains the limitation and its reason. Sending an email does not guarantee deletion of all data processed in connection with the App.

The controller handles requests concerning processing for which it is responsible, including where providers process data on its behalf. However, the controller does not have direct access to all data in providers' systems and cannot itself delete data they process as independent controllers. For such data, for example Google account and Google Play payment data, users should contact the relevant provider through its procedures listed in section 12.

Requests are answered without undue delay, generally within one month of receipt. If an extension is necessary under applicable law, the controller informs the requester of the extension and its reasons within the first month. A refusal to act on a request must explain the grounds and the available legal remedies.

For Analytics and AdMob-related processing, users may also use Google- and device-provided privacy controls, including advertising, consent, and privacy settings, where such controls are available.

In variants with OneSignal, users may disable notifications in the device settings. This does not delete data already stored in the service. Requests concerning processing on the controller's behalf should follow the procedure described above; requests concerning OneSignal's own processing should be directed to OneSignal.

11. Children’s Privacy

The App is intended for users aged 13 and older.

The App is not directed to children under 13.

The 13+ age designation does not replace requirements for consent from a parent or legal guardian. Where processing requires consent, the laws determining the age at which users may give consent independently in their country apply.

If the developer becomes aware that personal data from a child under 13 has been collected unintentionally in a way that requires deletion under applicable law, appropriate steps will be taken to address the issue.

12. External Services and Documentation

For more information about external services used in connection with the App, users may consult the relevant privacy documentation, including:

13. Changes to This Privacy Policy

This Privacy Policy may be updated from time to time to reflect changes in functionality, legal requirements, or the App’s data-processing practices.

The updated version will be published with a revised “Last updated” date.

14. Contact

Privacy questions and data-related requests should be sent to the privacy email address listed in section 1. For technical assistance, users should use the support address listed in the same section.