Data processing at Pereval

This page describes how the Pereval site processes data technically. Platform applications, documentation inquiries, partner dashboards and network user profiles are separate data sets.

Platform applications

We store the platform name, address and type, the audience, locations and description you provide, your contact name and email. These are used to review the application and contact the platform representative. We also store the IP address to limit submissions, form language, consent version and server-recorded acceptance time, the decision and confirmation sending status.

The application, contact details and decision comments are deleted from the live database 90 days after final approval or rejection, by the next automatic hourly cleanup. This is a live-database period, not a total including backups. Open applications do not expire based on their submission date. An approved platform's active partner and team records remain separately in the dashboard: deleting the application does not delete the dashboard.

Inquiries, support and data requests

You can ask a question or submit a data processing or deletion request without signing up. We store the topic and message, an optional email for outgoing notifications, page address and section heading, language, IP address to limit submissions, consent version and server-recorded acceptance time, replies and processing records. If you are signed in, your verified session email is used. Entering someone else's email does not authorize access or deletion: requests require manual verification, and Via account deletion remains in Via settings.

A reply does not itself close an inquiry. An administrator explicitly closes a completed inquiry; the question, contact details and correspondence are deleted from the live database 90 days after closure, by the next hourly cleanup. This does not include separate backup retention. Open inquiries are not automatically deleted based on age.

Delivery and access

Applications and inquiries are available to administrators and their author through the private link shown after submitting; they are not published in the site directory. Save the link and do not share it: it grants access to read and continue the conversation. Only the access key hash is stored in the database. Entering an email does not recover anonymous access. Application decisions are posted to their conversation and close it; its deletion period starts at the decision.

Correspondence takes place on this site. Incoming email is not accepted. If you provide an email, confirmations and notifications including reply text are sent through a mail service; administrator notifications may also be sent through Telegram. Acceptance by a mail server does not guarantee inbox delivery and does not affect the saved reply's availability on this site.

The dashboard uses a session cookie for sign-in. Pages load Google Fonts, which makes the browser contact Google's service. The automatic cleanup periods above apply to inquiry records in the portal database, not to messages already delivered to email inboxes or external notification services.

When you switch the site's language, your browser remembers your choice in a cookie for up to a year. The site uses that choice when you open its main address.

Site analytics

Public information pages in both languages load Yandex Metrica when you open them to measure visits.

Your browser sends visit and device information to Yandex, including your IP address and cookie identifiers. Our pageview event contains the URL without query parameters or fragments, the referring domain and the page language. Session replay, form recording, click maps and automatic outbound-link tracking are off. The counter is absent from sign-in, dashboard, admin and private support pages, application and contact forms, and the test site.

See Yandex’s privacy policy for how Yandex processes this data.

Network profiles and messages

Users manage participation in the app where they registered. Turning participation off hides the profile but does not delete existing conversations. Deleting network data closes matches and removes the profile; the other person's history remains without the name and photos. Network messages are retained for up to 90 days from sending. If an erased chat has a report, a hidden moderation copy is retained for 90 days from erasure. Integration events are retained for 7 days. This does not promise complete erasure of another person's chat history.

The network has a separate period for reports and personal photo-check materials, including unresolved disputes: up to 60 days in the live database from original report submission or check creation, then up to 30 days in closed backups. Appeals, updates and decisions do not extend the limit. Materials are deleted without approving photos or lifting restrictions; seek review before the 60-day deadline. This does not replace the site's application/inquiry periods or message, hidden archive and event periods. An expired public link cannot open a check or its photos.

The network receives coordinates from the app and stores rounded coordinates. Other users do not receive coordinates. It does not receive a user's phone number or email as profile data; this does not apply to a platform representative's email submitted in an application or inquiry.

Explanation for users · Safety and network rules · Deleting a profile through your app

Contact

Platform onboarding, documentation and data processing questions: contact form, no sign-up required. Participation settings and profile deletion are available in the user's original app. This page describes the Pereval site and network processing; it does not replace a description of Via's own data and processes.