Consent to Publish and Disseminate Personal Data

1. Controller, contact and affirmative action

1.1. Controller: Rzaev Omar Rzaevich, an individual residing in Azerbaijan.

1.2. Contact the Controller at voonapp@mail.ru. You can ask questions about a publication and request help at any stage — before publishing, while the route is visible in the feed and after it is deleted — for example, to hide data, set your own conditions, withdraw consent or stop display. The same address is the channel for legally significant notices.

1.3. Consent is given by a separate “Agree and publish” action before the first publication and is not preselected. VOON records the user ID, document/version, language, method and server time. A materially broader publication requires renewed consent.

2. Purpose and audience

2.1. The purpose is to display a sports route in the VOON feed and map, let signed-in users view, save and use it for activity planning, permit moderation, and allow VOON to show the post in reviews and screenshots of the app in materials about VOON.

2.2. The audience is an indefinite number of people, primarily signed-in VOON users. Dissemination takes place in VOON services — in the feed, on the route map and on author pages — and in reviews and screenshots of the app in materials about VOON. The feed is not intended for search-engine indexing, but users may technically make screenshots or copies.

3. Data authorised for publication

3.1. Author profile. Data: nickname, avatar, bio, sports and optional social handles. Condition: displayed with the post and author page.

3.2. Route. Data: title, description, region, sport, surface, difficulty, start/end and complete GPS geometry. Condition: only the route affirmatively submitted.

3.3. Metrics. Data: distance, duration, elevation gain/loss and metrics shown in the publication preview. Condition: heart rate, weight, sex, birth date, calories and raw sensor data are not public unless a new interface and consent expressly say otherwise.

3.4. Media. Data: up to four selected photos after technical metadata removal. Condition: only files selected for that post.

3.5. Interactions. Data: saves, follows and moderation status to the extent shown by the interface. Condition: within VOON features.

3.6. The author may at any time ask us to hide individual details of their post — for example, the avatar, bio, photos or duration — by writing to voonapp@mail.ru. If individual details cannot be hidden, we will hide the whole post at the author’s request.

4. Conditions and restrictions

4.1. The user permits VOON to collect, store, organise, technically transform, moderate, display and provide the listed data to operate VOON and in materials about VOON (section 2).

4.2. By consenting, the user sets the following restrictions for recipients: they must not use it to locate a home or stalk anyone; build advertising, credit, insurance or employment profiles; sell or scrape it; bypass settings; harass or discriminate; unlawfully identify a person; or combine it with external databases. Personal sports-planning use is permitted subject to law and the Community Rules. The user may add to or change these conditions at any time by writing to us (section 1). If a new condition cannot technically be met, we will hide the post it applies to.

4.3. VOON uses photos in which a person can be recognised in materials about the service only with that person’s consent.

5. What other users will see

5.1. The route is published in full, including its start and end points, text and photos. If a ride starts or ends near home or another personal place, you can trim its start and end before publishing (“Edit route” on the ride’s page).

5.2. Before publishing, the user checks that the route, text and photos show only what they are happy to share. If VOON offers automatic hiding of part of a route, it helps but does not replace this check. Do not publish routes or photos that show where other people are, or private property without the owner’s permission.

6. Moderation and publication time

6.1. After submission, the post may be shown to other users after review. Review concerns compliance with the Rules only and does not confirm that a route is safe, passable or lawful. VOON may reject, hide or remove content under the Rules or law.

7. Duration, withdrawal and stopping dissemination

7.1. Consent lasts until withdrawn or the account is deleted. It is one-time for this document version and covers later posts, each of which still requires a separate publish action.

7.2. Withdraw at voonapp@mail.ru. Hide or delete your post in the app. From the moment the withdrawal is received, VOON stops dissemination: no new posts go out and published data is no longer shown to other users. New publication requires renewed consent.

7.3. Withdrawal is prospective and cannot recall copies previously made outside VOON’s control.

8. User confirmation

8.1. The user confirms they are at least 16 and understand the public nature of the route and the related risks.

8.2. Consent is expressed by tapping “Agree and publish” on a separate screen before the first publication. The screen explains what signed-in VOON users will see after moderation: the profile, complete GPS route, displayed metrics, description and selected photos. Tapping it means consent to publication only; the Community Rules apply under the Terms.