Privacy Policy
Relations App

Last updated: 2026-08-23

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
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.

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:

• name and surname,
• phone number,
• email address,
• contact photo,
• additional contact information entered by the user.

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:

• does not upload contact data to the developer’s own servers,
• does not maintain its own cloud database for contact data,
• does not share contact data with the developer as part of the App’s core contact-management functionality,
• does not sell contact data.

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 Anonymous User Feedback (Google Firebase)

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

Feedback submitted through this form is intended to be anonymous. The App does not require a user account for feedback submission and is not designed to identify a specific person through the feedback workflow alone.

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

• mood,
• issueDescription,
• suggestions (optional),
• appName,
• appVersion,
• appBuild,
• debugBuild,
• buildDateTimeUtc,
• platform,
• platformVersion,
• packageName,
• locale,
• deviceManufacturer,
• deviceModel,
• sdk.

This information is used solely to review user sentiment, 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.

Although the feedback workflow is intended to be anonymous, free-text fields may contain information voluntarily entered by the user. For that reason, 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:

• app-instance ID,
• Advertising ID (subject to device settings, availability, and applicable consent/configuration choices),
• masked IP address information used to derive coarse location,
• app lifecycle and engagement events such as first opens, app opens, sessions, screen views, and app updates,
• device and app information such as operating system, device model, app version, and similar technical data,
• developer-configured analytics events and parameters, if such events are implemented in the App.

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:

• crash traces and stack traces,
• relevant application state at the time of a crash or error,
• relevant device metadata collected at the time of a crash,
• Crashlytics installation UUID,
• Firebase installation ID,
• diagnostic and stability information related to app failures.

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)

After the user accepts this Privacy Policy, the App may use OneSignal to deliver push notifications and in-app messages. Before that acceptance, the OneSignal SDK is configured not to collect or send data.

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.

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:

• Advertising ID,
• device identifiers,
• IP address,
• device information,
• approximate location,
• app interaction data,
• diagnostics data.

This data may be used for:

• serving personalized or non-personalized ads,
• measuring ad performance,
• preventing fraud,
• improving advertising services.

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.

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, and, after acceptance of this Privacy Policy, delivering push notifications and in-app messages through OneSignal.

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:

• providing contact-management functionality within the App,
• allowing users to create, edit, organize, and use contact data locally on the device,
• receiving and reviewing anonymous feedback voluntarily submitted by users,
• diagnosing issues and improving App quality, stability, and usability,
• measuring app usage and engagement,
• displaying and measuring advertisements through AdMob,
• ensuring security, integrity, and proper operation of the App and connected services.

5. Data Sharing

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

Data related to anonymous feedback, analytics, and crash reporting may be processed with the assistance of:

• Google Firebase / Google Cloud, as infrastructure used to receive and store feedback submissions and to support analytics and crash reporting services,
• Google Analytics for Firebase, as a service used to measure app usage and engagement,
• Firebase Crashlytics, as a service used to report crashes and diagnostics.

Advertising-related data may be processed by:

• Google AdMob,
• Google’s advertising partners or ad network participants, as applicable.

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:

• Article 6(1)(b) GDPR – processing necessary to provide the App’s core contact-management functionality requested by the user,
• Article 6(1)(f) GDPR – the developer’s legitimate interest in receiving and analyzing anonymous feedback, improving the App, measuring product quality, diagnosing crashes and technical issues, ensuring security and reliability, and understanding aggregate app usage,
• Article 6(1)(a) GDPR – user consent, where required by applicable law or platform rules, including where consent is used for personalized advertising or certain analytics or advertising-related processing.

If consent is used as the legal basis for certain analytics- or advertising-related processing, users may withdraw that consent at any time using the available consent options, device settings, Google privacy controls, or other controls made available to them.

7. Data Safety and 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 crash-reporting data may be transmitted to Google Analytics for Firebase and Firebase Crashlytics.

Data transmitted by these Google services is encrypted in transit using secure communication protocols such as HTTPS/TLS.

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.

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.

Anonymous feedback submitted through Firebase is retained only for as long as reasonably necessary to review feedback, diagnose issues, improve the App, and maintain internal product records. Unless a longer retention period is necessary for a specific support, security, or legal reason, the developer currently intends to retain such feedback for up to 24 months from submission.

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.

Data processed by OneSignal is retained according to OneSignal’s applicable retention settings and policies.

Uninstalling the App does not automatically delete contacts stored in the device’s system account, feedback already submitted through Firebase, analytics records already generated, or crash reports already received by Google services.

10. User Rights

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

• access their personal data,
• rectify inaccurate data,
• request deletion of data,
• restrict processing,
• object to processing,
• withdraw consent, where processing is based on consent,
• lodge a complaint with a competent supervisory authority.

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 regarding anonymous feedback submitted through Firebase may be sent to privacy@igsoft.net or support@igsoft.net. To the extent the developer is able to identify the relevant feedback entry from the information provided, the developer will review the request and respond as required by applicable law.

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.

For OneSignal messaging, users may withdraw notification permission in the device settings. Requests concerning information processed by OneSignal may also be directed to OneSignal under its privacy documentation.

11. Children’s Privacy

The App is intended for users aged 13 and older.

The App is not directed to children under 13.

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:

• Google Privacy Policy
• Firebase Privacy and Security Information
• Google Analytics Privacy Controls
• Google AdMob Help Center
• OneSignal Privacy Policy

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

If you have any questions regarding this Privacy Policy, please contact:

IGSoft.Net
Support email: relations-support@igsoft.net
Privacy email: relations-privacy@igsoft.net