1. Who is responsible for your data
This policy describes data processing on the restmap.app promotional website and in the RestMap mobile app. RestMap helps people find places and events and share information about them.
RestMap is provided by Dmitrii Petrov as an individual, based in Armenia. He is responsible for personal data processing in RestMap. For service and privacy enquiries, email com.restmap.app@gmail.com.
2. What data is processed
RestMap uses your location when you grant access, or an area selected on the map, to show relevant places and events nearby. The service does not provide or maintain a user history of movements or visited places.
Coordinates of places and events are stored in the catalogue. Search requests send the area coordinates, radius and filters to the server. Map providers process requests needed to display maps and related features.
RestMap does not use separate user behaviour analytics tools. App Store and Google Play reports are used for statistics. Application and infrastructure logs may contain diagnostic information and request parameters; their contents and retention periods are considered separately.
| When you use the service | Data that may be processed | Purpose |
|---|---|---|
| Sign-in and profile | Account ID, name and email; identifiers from your chosen Apple, Google or Telegram sign-in method; Telegram username, if provided. | Create an account, verify sign-in, display your profile and protect access. |
| Searching for places and events | Coordinates of the selected map area, radius, categories, dates and other filters. The search area may correspond to your location. | Display results in the relevant area. |
| Your contributions and activity | Places and events you add, text, photos, ratings, corrections, reports, likes and event attendance selections. | Publish content, record your activity, check information and handle reports. |
| Publication checks | Account-linked trust scores and the confirmation status of contributions. | Assess contributions and determine eligibility for automatic confirmation. |
| Voluntary support for the project | Store purchase identifier or token, purchase or subscription status and the associated account. | Verify and record support for the project and handle purchase enquiries. The current support model does not unlock additional features. |
| Security and support | Sign-in verification data, authentication times and attempts, and information about your request. Server logs may contain your IP address, the time and request parameters. | Prevent misuse, investigate errors and respond to requests. |
| Promotional website language | Browser language preferences, IP address and approximate connection country; after a manual choice, a cookie containing the language code. | Display the website in a language you understand. |
3. What other users can see
Public contributions are linked to the author’s account identifier; reviews also include the author’s name. Added places, events, descriptions and published photos are available to other users. Contact information in an event listing may also become public.
Before posting, make sure you have the right to share the text, images and information about other people. Photos may contain metadata, including where they were taken; automatic removal of such metadata has not been confirmed in the current upload handler.
An attendance selection is used for your lists and the total attendee count. No list identifying individual attendees was found in the public listings reviewed.
4. Purposes and legal bases
Data is used to provide the features you request: sign-in, your profile, search, contributions, subscription verification and support. Sign-in and activity information also helps protect the service and review user content.
Where the GDPR applies, processing that is objectively necessary to provide the requested service may be based on performance of a contract. Security and prevention of misuse may rely on legitimate interests after assessing how they balance against your rights. Mandatory retention requires a specific legal basis. Processing that requires consent must offer a separate, clear choice and a way to withdraw consent.
Reading this policy does not, by itself, constitute consent to advertising, optional analytics or any other data processing.
5. Service providers and external sources
The RestMap server and database are hosted on Google Cloud. Photos and files are stored in Google Cloud Storage. Google, Yandex and Apple mapping services are used depending on the platform and selected feature. Some place information comes from OpenStreetMap. Sign-in uses Apple, Google, Telegram or an email code; purchases and reports involve the relevant app store.
A separate RestMap process obtains event information from public sources, including Telegram. It may process the post text, link, date, venue and published contact details using OpenAI and geocoding services from Google, Yandex or OpenStreetMap Nominatim. This describes the processing of event sources; it does not assert that users’ location histories are sent to OpenAI.
If your personal data appears in a listing from an external source, you can request its correction or deletion. Information being publicly available does not remove applicable data protection rights.
When you follow a ticket link or a link to another external website, the relevant provider determines how data is processed there.
6. Countries where data is processed
The RestMap server, database, photos and files are hosted in Google Cloud infrastructure in Frankfurt am Main, Germany (europe-west3). The server zone is europe-west3-a. Database backups have been created on the RestMap server in this region before technical updates. The locations of technical logs and other infrastructure copies require separate verification.
7. Retention and deletion
Data is retained to operate the account, publications, support and the other purposes described here. Database backups may contain information as it stood when they were created. Deletion from the live database does not mean that all backups and copies temporarily retained by providers are erased at the same time; you can ask RestMap about these copies and their retention periods.
To start deletion in the app, open Profile → Info → Delete. Once the server confirms acceptance, the account becomes unavailable on all devices, personal content is hidden and linked records and files are cleared on the server. You can check the request without signing in using the receipt saved on your device. If it is unavailable, email com.restmap.app@gmail.com.
Deletion covers the profile, linked activity, personal content and files belonging to the user. Independently verified shared cards may remain without a link to the deleted user or that user’s personal contribution. The account may already be deleted while the RestMap team is still reviewing ownership of legacy files; the request status shows this separately and does not mean that all erasure is complete. Any specific lawful retention exception is explained when responding to the request.
8. Your rights and requests
Depending on applicable law, you may request access, correction, deletion, restriction of processing and portability, object to certain processing or withdraw consent. These rights may be subject to conditions and exceptions set out in law.
Write to com.restmap.app@gmail.com, providing the email address or identifier linked to your account and explaining your request. To protect your account, proportionate verification that the data relates to you may be required. Do not send passwords or sign-in codes.
For requests governed by the GDPR, the law requires a response without undue delay, usually within one month. Any extension requires the grounds and notification provided for by law. Your right to complain to a competent data protection authority remains available whether or not you contact support.
9. Younger users
RestMap’s App Store age rating is 4+. This is a content rating and does not itself establish a child’s ability to independently create an account, accept terms or consent to data processing.
Where applicable law requires a legal representative’s involvement or consent for a minor’s use of the service or data processing, that requirement must be met. Questions about a child’s data can be addressed to the RestMap team at com.restmap.app@gmail.com.
10. Changes to this policy
The current approved version must be available at a permanent address. Significant changes to processing purposes or users’ rights require a clear way to notify users. If new processing requires consent, updating this text does not replace that consent.