# Legal representative consent for a child's data in ГоГулять

> DRAFT 2026-11-08-draft. LEGAL REVIEW REQUIRED. For the Russian release; this does not replace COPPA verifiable parental consent.

Effective date: {{EFFECTIVE_DATE}}.

I am the adult legal representative of the child identified on the account creation or management screen. My identity, authority and relationship to the child are established through the controller's verification process. This consent applies to this child only; each child requires a separate consent.

Controller: {{OPERATOR_FULL_NAME}}, country {{OPERATOR_COUNTRY}}, address {{OPERATOR_ADDRESS}}. Data requests and withdrawal: {{PRIVACY_EMAIL}}. The [policy](privacy.md) is available before consent.

## Purposes and separate choices

| Purpose                  | Scope and action                                                                                                                                          |
| ------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Main (`service`)         | Profile, friendships, places, walks and necessary settings described below; a separate initially unchecked consent field. Required to operate the account |
| Notifications (`push`)   | Push-token/subscription storage and notification delivery; a separate initially off switch before the system permission request                           |
| Statistics (`analytics`) | Account-linked daily activity, platform and app version; a separate initially off switch, retained for up to 13 months                                    |

Refusing `push` and `analytics` does not prevent basic account use. A guardian decides separately for each child. Accepting the main consent or terms does not grant these optional purposes.

## Authorised processing

For the child's managed account, walk arrangements and parental controls, I authorise processing of:

- nickname, catalogue avatar, colour, birth year, language and time zone;
- representative relationships and control settings, friendship requests, friendships and blocks;
- place names/icons, manually selected map-cell centres and radii, walk plans, participation and preset reactions/statuses;
- device, session and notification-setting information necessary for these features.

Sources are my actions, the child's actions and necessary technical events. Operations include collection, recording, organisation, accumulation, storage, correction, retrieval, use, access for defined recipients, blocking, deletion and destruction through automated systems and necessary human handling.

Recipients are permitted friends and walk audiences, the child's representatives and, within parent-mode permissions, other children's representatives, and authorised service providers. Access is limited by function. Actual providers and countries are listed in policy section 5; consent must not be requested before that table is confirmed.

Authorised recipients see the nickname and walk information. A private place used in an open walk is temporarily visible to its audience. This is defined-recipient disclosure, not permission for public dissemination. A QR code, email confirmation or adult question does not itself verify representative authority.

## Exclusions

This does not permit data sales, third-party advertising trackers, behavioural profiling, a public directory, marketing messages, model training or unspecified future purposes. Daily statistics requires separate guardian consent for `analytics`. The profile does not require the child's passport, telephone, real surname, photo or exact birth date. Device location permission is optional, and exact location is not sent to the API.

Push delivery may be enabled separately. Detailed notification text exposes the included nickname, place and time to the push provider; details can be disabled. This is not consent to marketing push or to foreign transfers overriding legal restrictions.

Withdraw `push` and `analytics` in app settings, or in “Child consents” for a child. Withdrawing `push` deletes tokens and prevents queued notifications from being sent; withdrawing `analytics` immediately stops recording and deletes daily records. If login is unavailable, contact {{PRIVACY_EMAIL}} or the controller’s postal address. Withdrawal of the main `service` purpose uses account deletion; for a child, the owner acts after effects are explained.

## Duration and withdrawal

Consent ends on withdrawal, the end of its purpose or child-account deletion. Policy section 6 limits individual retention periods. I may request access, a copy, correction, cessation of individual processing or destruction through {{PRIVACY_EMAIL}} or the postal address. My authority is checked; other children's data is protected.

For withdrawal, I identify the child account and purpose. Deleting the entire account is not required to withdraw consent for an individual feature. If the child cannot receive the service without particular processing, the controller explains why. Another lawful basis may justify limited retention for a specific period. [Ordinary deletion](delete-account.md) allows seven days to cancel; shorter mandatory deadlines take precedence.

**Separate interface action:** “As this child's legal representative, I consent to processing their data for the main `service` purpose.” Initially unchecked. Authority confirmation and acceptance of terms are separate actions. The child's own decision is also considered where they exercise the relevant rights independently under applicable law.