POLICE911 SocialAll-Ukrainian Public Organization “Ukrainian Rescue Service”Department for Assistance and Support to Socially Vulnerable People
UA · EN · RU
Contact us
← Home

Privacy Policy

POLICE911 Social and the POLICE911 Telegram bot

Last updated: October 22, 2026

This Privacy Policy describes what data may be processed when using the POLICE911 Social website, when contacting us through the published contact details, and when using the AI-based POLICE911 Telegram bot, as well as how such data is stored, used, changed and deleted.

POLICE911 Social is the website and public name of the activities of the Department for Assistance and Support to Socially Vulnerable People of the All-Ukrainian Public Organization “Ukrainian Rescue Service”.

1. Privacy on the POLICE911 Social website

This section applies directly to the POLICE911 Social website and to contacts with the Department for Assistance and Support to Socially Vulnerable People through the contact details published on the website. The specific features of data processing in the POLICE911 Telegram bot are described separately in Section 2.

1.1. Purpose of the website

The website provides information about the department’s activities, social assistance, rescue assistance and first aid, completed projects, practical work, contact methods and ways to obtain consultation, support or assistance.

The website serves informational and communication purposes. Users are not registered directly on the website, and personal visitor cards are not created there.

1.2. Contact details and direct contact with the department

A person may choose any contact method published on the website and contact the department with a question, for a consultation, with a request for practical assistance, regarding a specific life or crisis situation, or regarding another person who needs help.

These channels include the official email address, contact telephone number and other contact methods expressly listed in the website’s “Contact” section.

The website does not contain a form for sending messages directly through the web page. Contacting us through the published contact details does not automatically register a person in any additional information systems.

1.3. Information a person may voluntarily provide when contacting us

To understand a specific life situation, a person may sometimes need to provide information about themselves or another person who needs help. Depending on the situation, this may include information about health, disability or reduced mobility, family and social circumstances, homelessness, violence or threats of violence, location, the need for accompaniment or transport, or the need for social, rescue, medical or first-aid assistance.

Such information is provided voluntarily and in relation to a specific request. POLICE911 Social does not ask people to disclose sensitive information merely for the purpose of accumulating such information. Users are advised to provide only the amount of personal and sensitive information genuinely necessary to understand the situation and identify a possible solution.

1.4. Data the website does not specifically collect

The POLICE911 Social website is not designed for mass collection of visitors’ personal data. In the current website architecture:

  • users are not registered and personal accounts are not created;
  • there are no contact forms directly on the web pages;
  • Google Analytics and advertising analytics are not used;
  • marketing or advertising profiles of visitors are not created;
  • special tools are not used to track a specific person;
  • POLICE911 Social does not maintain its own database of visitors’ IP addresses for profiling, advertising or behavioral analysis.

The amount of information collected by the website itself is limited to what is necessary for its operation and for understanding the overall use of the resource.

1.5. De-identified website usage statistics

POLICE911 Social may maintain simple de-identified technical statistics, including the total number of website visits and the total number of clicks from the website to the POLICE911 Telegram bot.

This counter does not create user profiles, identify visitors or track their subsequent activity. It does not use advertising technologies or special user-identification tools.

1.6. Technical hosting and server information

During normal website operation, the server or hosting provider may automatically process standard technical information and maintain server logs. Such processing may be necessary to deliver web pages, maintain website availability and security, diagnose errors, prevent abuse and operate the server infrastructure normally.

Since October 22, 2026 (Australia/Sydney), Nginx has been configured on the VPS for the static website. The access log records time, HTTP method, page path without query parameters, response status, response size and processing time. IP address, User-Agent and Referer are not included in the access log. The Nginx error log at warn level and above may contain an IP address and details of a problematic request. These data are used for diagnostics and security, not advertising profiling.

1.7. Transition to the POLICE911 Telegram bot

The website contains an interactive link to the POLICE911 Telegram bot, an automated AI-based information and consultation system. Use of the Telegram bot is voluntary and is not required in order to view the website or contact the department directly through the published contact details.

Direct communication with department staff and use of the POLICE911 Telegram bot are different technical channels. Message processing, use of artificial intelligence, voluntary creation of participant cards and interaction with external technology services are described in the following sections of this Policy.

2. Privacy when using the POLICE911 Telegram bot

The POLICE911 Telegram bot is an automated AI-based information and consultation system intended to provide information and consultation support and, where possible, to assist in finding practical help in the social, rescue and first-aid fields. Use of the Telegram bot is voluntary.

2.1. User and participant in the POLICE911 information-and-rescue system

There are two forms of interaction when using the POLICE911 Telegram bot:

  1. using the system as a user;
  2. participating in it as a participant in the POLICE911 information-and-rescue system.

A user is a person who contacts the POLICE911 Telegram bot for information or consultation in connection with a specific social, rescue, first-aid or other life situation. Such contact does not require registration or creation of a participant card. Simply using the Telegram bot does not make a person a participant in the POLICE911 information-and-rescue system.

Depending on the nature of the request, the user may voluntarily provide the Telegram bot’s artificial intelligence with information needed to understand the specific situation. The user provides such information only to the extent that it relates to the request and is necessary for consultation or assistance.

A participant is a person who voluntarily decides to provide the POLICE911 information-and-rescue system with information about their capabilities, resources, knowledge and contact methods in order to assist other people when needed. For this purpose, a participant card is created — a structured record containing the information voluntarily provided by the participant.

A participant card is created only by the person’s voluntary decision and after separate confirmation of consent. A user who only needs a consultation may use the Telegram bot without creating a participant card.

2.2. POLICE911 does not create a database of all Telegram bot users

Ordinary use of the POLICE911 Telegram bot does not automatically create a card, register the person as a participant or add the person to the structured participant database.

Structured participant cards are created only for people who voluntarily decide to become participants in the POLICE911 information-and-rescue system, provide information about their capabilities and separately confirm consent to the creation of the card.

The participant-card database is a working mechanism for matching a person’s specific need with participants’ available capabilities and is not a database of all Telegram bot users.

2.3. Participant card and its purpose

The participant card allows POLICE911 to record capabilities voluntarily provided by the participant and, when a specific need arises, match them with the request of a person who needs help.

The card is not required in order to use the Telegram bot and is not a public profile. It is not intended for unrestricted viewing by all users of the POLICE911 Telegram bot.

The purpose of the card is not to accumulate personal data as such, but to create a working tool for finding an appropriate resource and possible assistance in a specific situation.

2.4. Information contained in a participant card

When creating a card, the participant independently and voluntarily provides information necessary to describe their capabilities, resources and contact methods. The card may contain:

  1. name or preferred form of address;
  2. organization or initiative group, if represented by the participant;
  3. participant’s role or function;
  4. the territory in which the participant can provide assistance;
  5. work contact details;
  6. preferred contact method;
  7. areas in which the participant can help;
  8. transport capabilities;
  9. ability to accompany people;
  10. ability to provide temporary accommodation;
  11. work-related connections and contacts that may be useful for specific tasks;
  12. special capabilities of the participant;
  13. limitations that should be taken into account when using the participant’s capabilities.

The participant’s surname is not a mandatory field. Date and year of birth are not requested in the card.

The system also creates a limited set of technical data required for the card to function: Telegram user ID, Telegram username (if one exists), current technical status of the card, time of consent, and the technical identifier of the card file in Google Drive.

The telephone number is not automatically extracted from the Telegram account. If the participant considers it necessary to provide a telephone number or another contact method, they enter it themselves.

2.5. Voluntary consent to create a participant card

Creation of a participant card is entirely voluntary. Completing the information fields does not by itself create the card: after the required fields have been completed, the person is separately asked to confirm consent to creation of the card and processing of the information provided within the functions of the POLICE911 information-and-rescue system described in this Policy.

The card is not created until the person explicitly confirms consent using the relevant button. If consent is not confirmed, the card is not created, but the person may continue to use the POLICE911 Telegram bot as an ordinary user.

When the card is created, the system records the time at which consent was given. The participant may later end participation, delete the card and thereby withdraw consent to its further use.

2.6. Data received from Telegram

For technical operation of the POLICE911 Telegram bot, the system receives a limited amount of data provided by the Telegram platform. Primarily, a unique Telegram user ID is used to distinguish users technically and link the current interaction to the relevant Telegram account. If the user has a Telegram username, it may also be available to the system.

The telephone number is not automatically extracted from the Telegram account. Additional contact or other information is provided independently and voluntarily by the person if needed for a specific request or for participation in the POLICE911 information-and-rescue system.

2.7. Sensitive information in requests

The nature of requests to the Telegram bot may involve voluntary disclosure of information about health, disability, location, homelessness, violence, family or social circumstances, the need for evacuation, accompaniment, transport, medical care or first aid. Such information is processed only in connection with a specific request and only to the minimum extent necessary. Additional rules for sensitive data are set out in Section 7.

2.8. Information about third parties

A user may contact POLICE911 about another person and provide information necessary to describe that person’s situation. Such information is considered only in the context of the specific request and does not automatically create a participant card for the third party. The data-minimization principle and rules for third-party data are set out in Section 7.2.

2.9. Correspondence and working context

The POLICE911 Telegram bot does not create a separate permanent complete archive of all user correspondence in Google Drive or Google Sheets.

To continue an ongoing interaction, the system may retain a limited working context: the user’s latest request, the system’s latest response, information about an active situation, and a limited number of the most recent interaction elements necessary to continue the dialogue.

After POLICE911 was moved to the server, part of this working state may be stored in a local SQLite database so that an unfinished dialogue can continue after the program restarts. This is a technical working mechanism, not a separate permanent archive of all correspondence.

Messages located directly in Telegram are processed and stored by Telegram itself under its own rules. Deleting messages in Telegram and deleting data controlled by POLICE911 are separate technical actions.

2.10. Use of artificial intelligence and OpenAI

The POLICE911 Telegram bot uses the OpenAI API as an artificial-intelligence technology service to process user requests, generate information and consultation responses, and recognize voice messages.

For a specific request, the text of the request and the necessary working context may be sent to OpenAI. If resolving a situation requires matching a person’s need with participants’ available resources, the minimum necessary information from relevant active participant cards may be included in the working context.

The user’s Telegram ID is not sent to OpenAI as a separate field intended to identify the user. If a user sends a voice message, the POLICE911 server may temporarily send the audio file to the OpenAI speech-recognition service; after processing is completed, the temporary local audio file is deleted.

3. Storage and processing of participant data

Participant data is processed using several technical components. Their purpose is to support creation, search, updating and use of participant cards within the POLICE911 information-and-rescue system.

3.1. Google Drive

A complete participant card is stored in the POLICE911 working storage on Google Drive as a separate JSON file. It contains information voluntarily provided by the participant and the required technical fields. Cards are not published and are not intended for unrestricted viewing by Telegram bot users.

3.2. Google Sheets

The main working information from participant cards is synchronized with Google Sheets. The sheets are used as an internal working index that allows the system to find relevant information more quickly and match a specific request with participants’ available capabilities. Google Sheets may also be used for technical statistics on system requests.

3.3. POLICE911 server and local SQLite database

A limited working state needed to preserve dialogue continuity and correct system operation may be stored on the server in a local SQLite database. SQLite is not intended to create a complete permanent archive of all user correspondence or a separate copy of all participant cards.

3.4. OVHcloud server infrastructure

The server side of the POLICE911 Telegram bot and related components operate using OVHcloud infrastructure. The server runs technical processes necessary for the Telegram bot, interaction with Google Drive, Google Sheets and the OpenAI API, storage of limited working state, error diagnostics and stable operation of the system.

3.5. Who has access to participant data

The POLICE911 server obtains technical access to participant cards through Google OAuth to the extent necessary for working with the POLICE911 Google Drive and Google Sheets resources.

Administrative access may be held by the administrator of the POLICE911 information-and-rescue system and by persons specifically granted the relevant administrative permissions for the server, Google Drive or other parts of the working infrastructure.

Ordinary Telegram bot users do not have unrestricted access to the participant-card database. Internal searches use only active cards and only the amount of information that may be necessary to resolve a specific situation. Access to participant data is not provided more broadly than necessary to perform a specific working function of the POLICE911 information-and-rescue system.

4. Google OAuth and Google API

Google Drive and Google Sheets are used as components of the POLICE911 working infrastructure. Google OAuth is used for authorized technical access by the server to these services. This mechanism applies to POLICE911’s centralized working database and does not connect the personal Google accounts of Telegram bot users.

4.1. Purpose of Google OAuth

Google OAuth provides the POLICE911 server with technical access to the working Google Drive and related Google Sheets. This access is necessary to create, read, search, modify and delete participant cards and to work with the relevant working spreadsheets.

4.2. Whose Google account is connected through OAuth

Google OAuth authorization is completed by the POLICE911 administrator.

Ordinary users of the POLICE911 Telegram bot and participants in the POLICE911 information-and-rescue system do not connect their personal Google accounts to POLICE911, do not complete Google OAuth in order to use the Telegram bot, do not grant POLICE911 access to their personal Google Drive, and do not provide POLICE911 with their Google-account password.

4.3. Scope of access to Google Drive and Google Sheets

According to the technical review performed on October 21, 2026, the running POLICE911 service uses one Google OAuth scope: https://www.googleapis.com/auth/drive . No separate Google Sheets scope is present in the authorization currently used; Google Sheets operations are performed under the stated Google Drive permission. Google classifies this scope as Restricted; technically, it grants broad permission to view, create, modify and delete files in the authorized account’s Google Drive.

POLICE911 program logic directs working operations only to defined resources of the working database — the participant-card folder and the corresponding working spreadsheet — but the OAuth permission itself is not limited to a single folder. POLICE911 uses the granted access only for the functions of the information-and-rescue system described in this Policy. The personal Google Drives of Telegram bot users and participants are not connected to POLICE911.

4.4. Use of data obtained through Google API

Data accessed by POLICE911 through the Google Drive API and Google Sheets API is used only for the functions of the POLICE911 information-and-rescue system described in this Policy: storing, searching and updating cards; matching a specific need with participants’ available capabilities; managing card status; carrying out actions to modify or delete a card; and supporting technical operation of the system.

Such data is not sold and is not used for advertising, advertising profiling, retargeting, creditworthiness assessment or other purposes unrelated to the stated work of POLICE911.

4.5. Compliance with Google Limited Use requirements

Information obtained through Google Workspace APIs is used in accordance with the Google API Services User Data Policy and applicable Google Workspace user-data requirements, including Limited Use requirements.

POLICE911 uses such data only for the stated functions of the information-and-rescue system and does not use it for advertising, sale of personal data, creation of commercial user profiles or other unrelated purposes.

Data obtained through Google Workspace APIs is not used by POLICE911 to create, train or improve general-purpose, universal or non-personalized artificial-intelligence or machine-learning models.

4.6. Transfer of certain data to OpenAI to perform a specific function

If processing a specific request requires matching a person’s need with participants’ capabilities or resources, the minimum necessary amount of information from relevant active participant cards may be sent through the OpenAI API as a technology component of the POLICE911 Telegram bot.

Such transfer is carried out only to process the specific request and perform the stated system function. POLICE911 does not use data obtained through Google Workspace APIs to train or improve general OpenAI models or other general-purpose artificial-intelligence models.

Under the current OpenAI API rules, API data is not used by default to train or improve OpenAI models unless the API organization owner has specifically enabled such use. OpenAI may, however, retain the content of API requests and responses in abuse-monitoring logs for a limited period in accordance with its current data-retention rules.

5. Managing your data

Users and participants may manage personal data controlled by POLICE911 within the functions provided by the system.

5.1. Editing a participant card

A participant may change information in their card if their data, contacts, capabilities, resources or limitations change. The system supports editing the card and changing the participant’s availability status. Updating information does not create a new registration; the existing card is updated.

5.2. Withdrawal of consent and ending participation

A participant may end participation in the POLICE911 information-and-rescue system at any time. To do so, the participant deletes their card using the function provided in the POLICE911 Telegram bot. Deleting the card constitutes withdrawal of consent to its further use as a participant card.

After ending participation, the person may continue to use the POLICE911 Telegram bot as an ordinary user without a participant card.

5.3. Deleting a participant card

A participant may independently delete their card using the deletion function provided in the POLICE911 Telegram bot. After selecting the function and confirming the action, the system:

  • excludes the card from further working use;
  • deletes the participant record from the Google Sheets working index;
  • deletes the card information from the system’s operational state;
  • moves the card file in Google Drive to deletion/trash status.

After these actions are completed, the person is no longer considered a participant in the POLICE911 information-and-rescue system, but may continue to use the Telegram bot as an ordinary user.

Deleting the card does not mean immediate physical destruction of every possible technical copy. Certain backup copies of working state may remain for a limited time under recovery mechanisms, while the file in Google Drive is subsequently handled under Google Drive’s deletion mechanisms.

5.4. Deleting correspondence in Telegram

A participant card and the history of communication in Telegram are different types of data and are managed separately. A user may delete a chat or messages using Telegram’s own tools. Such deletion is not an automatic instruction to delete a participant card.

Similarly, deleting a participant card does not automatically delete messages stored directly in Telegram.

5.5. Changing or deleting other personal data

If a user or participant believes that POLICE911 controls other personal data relating to them that needs to be clarified, corrected or deleted, they may contact the POLICE911 administrator using the contact details in Section 11.

6. Technical storage, logs and backups

For stable and secure operation of the POLICE911 information-and-rescue system, technical mechanisms are used for working-state storage, system logs and backup recovery. They are intended to maintain operability, diagnose errors, support security and recover from technical failures, not for advertising or commercial profiling of users.

6.1. Server logs

Service messages and errors from the Telegram bot are recorded using systemd/journald; rsyslog also runs and stores certain system events in text logs. journald stores data on disk, but no fixed maximum retention period by age is configured: MaxRetentionSec is not set, so rotation and deletion of older records depend on storage-volume limits and free disk space. syslog, auth.log and kern.log use weekly rotation with four archives plus the current file, which under regular activity generally corresponds to approximately 4–5 weeks, but is not a strict retention period for every individual record.

Other security and maintenance system logs have their own rotation rules. The POLICE911 architecture limits the output of secret technical information and protects tokens, API keys and other technical secrets from appearing in ordinary diagnostic logs. POLICE911 does not maintain a separate user database of Telegram users’ IP addresses; logs are used for technical operation, diagnostics and security, not for advertising profiling.

6.2. Backups

For the working state of the POLICE911 server side, consistent backup copies of local SQLite databases are created daily with integrity checks. As of the review date, backups cover the databases for dialogue state and user settings, the Google Sheets synchronization queue, and artificial-intelligence usage counters. The copies are stored on the same VPS; at each daily run, working-state archives older than 7 days are deleted.

Separate one-time technical copies may also be retained when created before system updates; as of the review date, no automatic deletion period is configured for these copies, and the 7-day rule does not apply to them. The current scheme does not create a complete image of the VPS and does not create a separate backup of Google Drive or Google Sheets content. Backups are intended for system recovery and do not constitute a separate user database.

6.3. Retention periods for technical data

There is no single retention period for all POLICE911 technical logs and backups. Daily SQLite working-state backups are subject to deletion of archives older than 7 days during the next daily run; journald has no fixed age-based retention period; individual system logs have their own rotation rules; and one-time technical copies created before updates may remain without a configured automatic deletion period.

Website access and error logs rotate daily, keeping six archives plus the current file, corresponding to approximately seven days under normal daily operation. Archives older than seven days are also removed during the next rotation; individual records are not deleted exactly after 168 hours. Automatic rotation has been tested. The website has no separate server application or third-party analytics; aggregate visit and bot-click counters are not enabled yet. System and Telegram bot log rules are described separately and were not changed during website installation.

6.4. Security of the technical infrastructure

POLICE911 applies organizational and technical measures intended to limit unauthorized access and maintain stable system operation. These include limiting administrative access, authorized access to Google Drive and Google Sheets, restricting ordinary users’ access to the participant-card database, protecting API keys and tokens, and maintaining backups.

No information system can guarantee absolute protection against every possible technical risk. POLICE911 applies reasonable security measures within the current architecture and available resources.

7. Special categories of data

The nature of requests to POLICE911 may involve voluntary disclosure of information relating to a person’s private, social, medical or other sensitive circumstances. Such information is processed only when and to the extent that it relates to a specific request and is necessary to understand the situation, provide consultation or offer possible assistance.

7.1. Health information and other sensitive circumstances

Depending on the situation, a user may provide information about health, illness or injury, disability, reduced mobility, the need for first aid or medical care, location, homelessness, violence or threats of violence, family and social circumstances, or the need for evacuation, accompaniment or transport.

POLICE911 does not request such information for the purpose of creating a separate database of sensitive data. Users are advised to provide only information directly related to the specific situation and necessary for its consideration.

7.2. Information about third parties

A user may contact POLICE911 about another person who needs consultation, support or assistance. In that case, only information necessary to describe the situation and identify a possible solution should be provided whenever possible.

If the matter can be considered without a surname, exact address, detailed medical data or other identifying information about the third party, users are advised not to provide such information. Information about a third party provided in connection with a specific request is not intended to create a separate card or separate database about that person and does not make that person a POLICE911 participant.

7.3. Data concerning minors

POLICE911 activities may involve situations in which assistance is needed by a child or another minor. When information about a minor is provided, it should be limited to the minimum amount directly relevant to the situation.

Unless necessary, full personal details of a child, documents, an exact residential address, detailed medical information, photographs or other materials that identify the child should not be provided.

Information about a minor provided in connection with a specific situation is used to understand the request and provide possible consultation or practical assistance. The mere fact that a third party provides such information does not automatically create a participant card for the minor.

8. Rights of users and participants

A user of the POLICE911 Telegram bot and a participant in the POLICE911 information-and-rescue system may control personal data relating to them that is under POLICE911’s control. Specific technical methods for managing data are described in Section 5.

8.1. Obtaining information about data processing

A user or participant may contact the POLICE911 administrator for clarification about what data relating to them is under POLICE911’s control, the purposes for which it is used, where it is stored, which technology services may receive it, and how it may be changed or deleted.

8.2. Correction and updating of data

A participant may change and update information in their card. If a user without a participant card believes that other personal information controlled by POLICE911 is inaccurate or needs clarification, they may contact the POLICE911 administrator.

8.3. Withdrawal of participant consent

A participant may end participation at any time and withdraw consent to further use of their card by deleting it. After the card is deleted, the person may continue to use the Telegram bot as an ordinary user.

8.4. Deleting a participant card

A participant may independently delete their card using the deletion function provided in the POLICE911 Telegram bot. The consequences of deletion and the handling of related data are described in Section 5.3 of this Policy.

8.5. Deleting other personal data

To delete or clarify other personal data controlled by POLICE911 that is not deleted through the participant-card function, a user or participant may contact the POLICE911 administrator using the contact details in Section 11.

8.6. Managing correspondence in Telegram

Users manage their own correspondence using Telegram’s tools within the capabilities of the platform. Deleting correspondence in Telegram and deleting a participant card are separate actions.

8.7. Obtaining clarification

If a user or participant does not understand how their data is processed, they may contact POLICE911 for additional clarification before or after providing the relevant information.

9. External services

External technology services are used to operate the website, official communication channels and the POLICE911 information-and-rescue system. Information is transferred to them only to the extent necessary for the relevant technical or working function.

9.1. Telegram

Telegram is used as the platform for the POLICE911 Telegram bot. Messages and data located directly in Telegram are also processed by the Telegram platform in accordance with its own rules and privacy policy.

9.2. OpenAI

OpenAI is used to process text requests, generate information and consultation responses, process necessary working context and recognize voice messages. Only information necessary to perform the relevant function of the POLICE911 Telegram bot is sent to OpenAI.

Under the current OpenAI API rules, data is not used to train models by default unless the API organization owner enables such use. OpenAI may retain some content and metadata of API requests in abuse-monitoring logs for the period specified by its current rules and the settings of the relevant API service.

9.3. Google Drive

Google Drive is used as working storage for complete participant cards in separate JSON files. Server access is provided through Google OAuth as described in Section 4.

9.4. Google Sheets

Google Sheets is used as the internal working index of participants and may also be used for technical statistics relating to requests to the POLICE911 information-and-rescue system.

9.5. Email

Messages sent to the official POLICE911 email address are technically processed and stored by the email service in use. When contacting POLICE911 by email, users should understand that the content of the message passes through the infrastructure of the relevant email provider.

9.6. OVHcloud

OVHcloud is used as the server infrastructure for the POLICE911 server side. It runs processes necessary for the Telegram bot, interaction with Google Drive, Google Sheets and OpenAI, storage of limited working state and diagnosis of technical errors.

9.7. No advertising or marketing systems

The current POLICE911 architecture does not use a separate CRM, advertising system or advertising analytics. Personal data of users and participants is not transferred to external services for advertising, advertising profiling or sale of personal data.

10. Changes to the Privacy Policy

This Policy may be changed and supplemented as the POLICE911 Social website, the POLICE911 Telegram bot, the POLICE911 information-and-rescue system, the technology services used and data-processing methods develop.

The Policy is updated if there are material changes to the types of data processed, the purposes for which it is used, methods of storage, transfer or deletion, external services used, operation of Google OAuth and Google APIs, server infrastructure, or applicable privacy and data-protection requirements.

The current version of the Policy is published on a separate page of the POLICE911 Social website with the date of the latest update. If a change materially affects data processing, the relevant information must be reflected in the Policy before the new processing arrangement begins to apply.

11. Privacy contacts

For questions about this Policy, processing of personal data and use of information within the POLICE911 Social website and the POLICE911 information-and-rescue system, a user or participant may contact:

POLICE911 Social
Department for Assistance and Support to Socially Vulnerable People
All-Ukrainian Public Organization “Ukrainian Rescue Service”
EDRPOU: 33151635

Email: pehterev@police911.org
Phone: +38 067 181 17 68
Website: police911social.org

A request may concern clarification of data processing, confirmation of what information relating to a person is held, correction or updating of information, deletion of data, withdrawal of consent to use a participant card, and questions about storage or transfer of information to external technology services.

If the question concerns a participant card, the participant may also use the card-management functions provided in the POLICE911 Telegram bot, including independent deletion of the card.

Contact usHome