Privacy Policy for the «Rest API Client» Mobile Application

Effective date: 2026-02-06
Last updated: 2026-02-06 

This Privacy Policy (the «Policy») describes what data may be collected and processed when using the «Rest API Client» mobile application (the «Application»), by whom and for what purposes, and what rights users have.

Personal data controller: Gib Nikita, registered as a payer of professional income tax (hereinafter «We»).

By using the Application, you confirm that you have read this Policy.

1. Terms

  • Personal data – any information relating to a user who is directly or indirectly identifiable.
  • Processing – any actions with data (collection, recording, systematization, storage, use, transfer, deletion, etc.).
  • Device – the user’s smartphone/tablet on which the Application is installed.
  • Third-party services – third-party SDKs and service providers (e.g., Firebase, Google AdMob) that may process data as processors or as independent controllers.

2. What data we may collect

The specific set of data depends on the Application’s features and your OS settings/permissions.

2.1. Data you provide yourself

We may process:

  • contact details: email (e.g., to communicate with support);
  • content and materials you work with in the Application;
  • support requests: messages, attachments, as well as technical information you voluntarily send for diagnostics.

The Application is intended for working with APIs. Data that you send to third-party servers through the Application is processed by the respective owners of those servers in accordance with their policies.

2.2. Data collected automatically

We may collect (including via third-party SDKs):

  • device technical data: model, manufacturer, OS version, language, time zone, app settings;
  • app usage data: events and actions in the interface, session duration, diagnostic events;
  • identifiers: Advertising ID (Google Advertising ID / GAID on Android; IDFA on iOS), installation identifier;
  • crash and diagnostics data: logs, dumps, error and performance information (e.g., via Crashlytics);
  • network data: IP address, network type, approximate connection parameters.

3. Device permissions

The Application may request OS permissions required for certain features:

  • Full network access / Internet access (Full network access): required to send API requests and receive responses, upload/download data, run ads, and use Firebase services.
  • Access to files/media (Photos/Files/Storage): required so you can select and send files in requests (e.g., multipart/form-data) and save/import data.
  • Notifications.

You can change permissions in your device settings. Without certain permissions, the corresponding features may be unavailable.

4. How we use data (purposes of processing)

We use data to:

1.    provide the Application’s features (including network requests, file transfer, saving settings);

2.    ensure operability, security, and prevent abuse;

3.    respond to support requests;

4.    improve the product (analytics, testing, diagnostics, bug fixing);

5.    display ads and measure their effectiveness (including personalization);

6.    comply with legal requirements and respond to requests from authorized bodies where required by law.

5. Legal bases for processing

Depending on applicable law (e.g., GDPR/UK GDPR, local laws), we process data based on:

  • performance of a contract (providing the Application’s functionality);
  • your consent;
  • legitimate interests (e.g., security, preventing failures, basic analytics);
  • legal obligations (where applicable).

If you withdraw consent, processing based on consent stops, but this does not affect the lawfulness of processing carried out before withdrawal.

6. Advertising (Google AdMob) and advertising identifiers

The Application may display ads via Google AdMob. To show and measure ads, the following may be processed:

  • advertising identifiers (e.g., GAID/IDFA);
  • device and app technical data;
  • impression/click data/limited diagnostic events.

7. Firebase and related services

The Application may use Firebase (Google) services, including for example:

  • Firebase Analytics (usage analytics);
  • Firebase Crashlytics (crash reporting);
  • Firebase Remote Config (remote configuration/feature toggles);

These services may collect and process technical and diagnostic data, as well as identifiers required for SDK operation.

8. Cookies and similar technologies

In mobile applications, instead of cookies the following may be used:

  • local storage (local storage/SQLite/Keychain/Keystore);
  • tokens, installation identifiers, SDK identifiers;
  • advertising identifiers.

We use these technologies to save settings, ensure functionality, analytics, security, and advertising.

9. Transfer of data to third parties

We may transfer data to:

  • service providers (processors): analytics, diagnostics, infrastructure, mailings, support;
  • advertising partners: to show/measure ads (e.g., Google AdMob);
  • government authorities/courts: if required by law.

9.1. Examples of categories of service providers

  • Advertising: Google AdMob
  • Analytics: Firebase Analytics
  • Error collection: Firebase Crashlytics
  • Remote configuration: Firebase Remote Config

10. International data transfers

Because we use infrastructure and SDKs of major international providers (e.g., Google/Firebase/AdMob), data may be processed outside your country of residence.

11. Data retention and periods

We store data:

  • for as long as necessary for the purposes described in the Policy;
  • longer if required by law (e.g., to resolve disputes and comply with requirements).

Content that you send to third-party API servers through the Application is stored according to the rules of the relevant third-party services/server owners.

12. Security

We apply reasonable organizational and technical security measures, including:

  • encryption in transit (TLS/HTTPS, if supported by the target server);
  • access restrictions and infrastructure protection measures;
  • crash diagnostics and monitoring.

However, no method of transmission/storage can guarantee absolute security.

13. Links to third-party resources

The Application may contain links to third-party websites/services. We do not control their policies and are not responsible for their practices. We recommend reviewing third-party policies.

14. Changes to the Policy

We may update this Policy from time to time. The new version becomes effective upon publication in the Application or on the relevant site/policy page and may apply without separate notice to users. Users are responsible for periodically reviewing the current version of the Policy. Continued use of the Application after changes are published means acceptance of the updated Policy.

15. Contacts

If you have questions about the Policy or data processing, contact us:
Email: info@kiges.cc