Urgentor Privacy Policy

Last updated: August 17, 2026

This Privacy Policy explains how Urgentor (“Urgentor”, “we”, “us”, or “our”) collects, uses, stores, and protects information when users access or use the Urgentor application and related services.

Urgentor is an operational communication, notification, alarm, team, and shift-management application intended for authorized members of organizations.

This Privacy Policy provides information about how personal information is processed when you use Urgentor.

1. Information We Collect

Urgentor collects and processes only information required to provide its core functionality.

Profile information

When a user creates or maintains a profile, Urgentor may process:

• first name;
• last name;
• phone number;
• an internal Firebase user identifier (UID).

The phone number is entered by the user as part of the Urgentor profile.

Urgentor uses Firebase Authentication to maintain application accounts and user identifiers.

Where Firebase Phone Authentication is used, the phone number provided for authentication may also be sent to and stored by Google Firebase for authentication, SMS verification, security, spam prevention, and abuse-prevention purposes.

Organization and operational information

Depending on the user’s role and use of the application, Urgentor may process information including:

• organization membership;
• user role;
• team or operational group;
• shift assignments;
• absences;
• shift changes and replacements;
• alarm creation and alarm responses;
• operational status related to alarms;
• notices and their delivery or read status;
• activity and administrative records;
• timestamps relating to operational actions.

This information is used to provide Urgentor’s organization, alarm, communication, accountability, and shift-management functionality.

Push notification and device information

Urgentor uses push notifications for operational alarms and notices.

For this purpose, Urgentor may process:

• Firebase Cloud Messaging (FCM) push tokens;
• Firebase Installation IDs and related technical identifiers used by Firebase for notification delivery;
• device manufacturer and model;
• application version and build number;
• notification permission status;
• alarm notification channel readiness;
• sound and vibration readiness;
• whether the device reports support for vibration;
• timestamps relating to device notification testing.

These technical details are used to deliver operational notifications and to determine whether a device is appropriately configured to receive Urgentor notifications and alarms.

Firebase Cloud Messaging uses Firebase Installation IDs to identify app installations for message delivery. Firebase may retain these identifiers according to its applicable data retention and deletion procedures.

2. Information We Do Not Use for Current Urgentor Functionality

The current version of Urgentor does not use the following for its application functionality:

• precise or approximate location;
• contacts or address book;
• camera;
• microphone;
• photos or videos;
• advertising identifiers.

Urgentor does not contain advertising functionality and does not use user information for behavioral advertising or cross-app tracking.

As of the date of this Privacy Policy, Urgentor does not use Firebase Analytics or Firebase Crashlytics.

3. How We Use Information

Information processed by Urgentor is used to:

• create and maintain user profiles;
• authenticate users;
• manage organization membership and roles;
• organize operational teams and shifts;
• deliver alarms and operational notifications;
• record user responses to alarms;
• manage notices;
• manage absences and shift changes;
• maintain operational and administrative records;
• provide device notification readiness testing;
• maintain security and access control;
• investigate technical or operational problems;
• protect the integrity and reliability of the service.

Urgentor does not sell personal information.

Urgentor does not use personal information for advertising or cross-app tracking.

4. Firebase and Google Services

Urgentor uses Google Firebase and Google Cloud services required for the operation of the application.

These services currently include:

• Firebase Authentication;
• Cloud Firestore;
• Cloud Functions;
• Firebase Cloud Messaging.

These services provide authentication, database storage, backend processing, and push notification delivery.

Google and Firebase may process technical and account-related information as necessary to provide these services, including Firebase Authentication information, Firebase Installation IDs, and Firebase Cloud Messaging identifiers.

Information processed through these services is subject to the applicable contractual, security, data-processing, and privacy practices of Google and Firebase.

Urgentor does not use these services for behavioral advertising or cross-app tracking.

5. Who Can Access Information

Access to information within Urgentor depends on the user’s organization and assigned role.

Authorized organization administrators, operators, and members may have access to information necessary for the operational functions available to their role.

Technical access to backend systems may also be available to authorized persons responsible for operating, maintaining, securing, or supporting Urgentor.

Information is not sold to third parties.

Information may be processed by service providers, including Google Firebase and Google Cloud, where necessary to provide Urgentor functionality.

Information may also be disclosed where required by applicable law, a valid legal request, or where necessary to protect the security and integrity of the service.

6. Data Storage and Security

Urgentor uses Firebase and Google Cloud infrastructure to store and process application data.

Reasonable technical and organizational measures are used to protect information against unauthorized access, alteration, disclosure, or destruction.

Access to application data is controlled through authentication, authorization rules, backend security controls, and organization-based access restrictions.

Data transmitted between the application and backend services is transmitted using the security mechanisms provided by the applicable Firebase and Google Cloud services.

No internet-based service can guarantee absolute security, but Urgentor is designed to limit access to information according to the operational role and organization of the user.

7. Data Retention

Information is retained for as long as necessary to provide Urgentor functionality and maintain legitimate operational, security, accountability, and organizational records.

Retention periods may depend on:

• the type of information;
• its operational purpose;
• the status of the user’s account;
• organizational accountability requirements;
• security and system-integrity requirements;
• applicable legal or regulatory obligations.

Current account and profile information is maintained while the account is active.

Operational records may be retained where necessary to preserve the integrity and history of organizational activities.

When an account is deleted, directly identifying profile information is removed or replaced where technically and operationally appropriate.

Certain historical operational records, internal identifiers, timestamps, or deletion and audit records may remain where necessary for security, accountability, system integrity, fraud or abuse prevention, or applicable legal or regulatory requirements.

Retained historical records are designed to avoid retaining unnecessary directly identifying information such as the deleted user’s name and phone number.

Certain technical information processed by third-party infrastructure providers may remain for the retention periods applicable to those services.

8. Account and Data Deletion

Users can initiate permanent account deletion directly from Urgentor:

Urgentor → My Account → Delete Account

The application requires confirmation before account deletion.

When account deletion is successfully completed:

• the user’s Firebase Authentication account is deleted;
• stored push notification tokens associated with the account are removed;
• directly identifying profile information is removed;
• personal identifying information in relevant organizational history is removed or replaced where appropriate;
• access to the organization and Urgentor services is revoked.

Certain historical operational records may remain in de-identified or pseudonymized form where necessary to preserve operational history, system integrity, security, accountability, prevent abuse, or comply with applicable legal or regulatory requirements.

Information that is not required to be retained for these purposes is not intentionally retained after account deletion.

Users who no longer have access to the Urgentor application may also request account and associated data deletion through the external:

Urgentor – Delete Your Account

page available on the Urgentor website.

Identity may be verified before an external deletion request is processed in order to prevent unauthorized deletion of another person’s account.

9. Requests Submitted Through the Website

If a user submits an account deletion or privacy request through the Urgentor website, information voluntarily provided through that request is used only to:

• identify the relevant Urgentor account;
• verify the request where necessary;
• communicate with the user regarding the request;
• process the requested privacy or account action;
• maintain appropriate security or compliance records relating to the request.

Information submitted through such a request is retained only for as long as reasonably necessary to process the request and maintain appropriate security, accountability, or compliance records.

10. User Rights and Privacy Requests

Depending on applicable law, users may have rights relating to their personal information, including rights to request:

• access to personal information;
• correction of inaccurate information;
• deletion of personal information;
• information about how their data is processed.

Users may exercise account deletion directly within Urgentor or contact Urgentor regarding another privacy request.

Requests may be subject to reasonable identity verification where necessary to protect user accounts and prevent unauthorized access or deletion.

11. Children’s Privacy

Urgentor is designed for authorized members and users of organizations and is not designed as a service for children.

Urgentor does not intentionally provide advertising, behavioral advertising, or tracking services directed at children.

12. Changes to This Privacy Policy

This Privacy Policy may be updated when Urgentor’s functionality, data practices, legal requirements, or third-party services change.

When material changes are made, the updated version will be published on this page with a revised “Last updated” date.

Users should review this Privacy Policy periodically for information about how Urgentor processes personal information.

13. Contact

For questions about this Privacy Policy, personal information, account deletion, or other privacy requests, contact:

Urgentor Privacy Contact

Email: newsletter@kotorfisherman.com

Country: Montenegro