Privacy Policy
Updated: 23 September 2026
This document explains what happens to data on peremovyny.org and inside the Peremovyny product. It is written to be checked: every statement describes what the system does today, not what is planned.
The product is in private demo. Access is granted by hand; there is no public sign-up.
Who processes the data
The controller is Peremovyny. Write to the address below with any question about this policy or about your data.
When a company uses the product to train its own team or to assess candidates, that company is the controller of the data, and we act as a processor on its instructions and under a contract.
This website
The site sets no cookies, carries no analytics or counters and shares nothing with advertising networks. Fonts are served from our own domain rather than a third-party service.
In your browser's local storage the site keeps exactly two values and sends neither anywhere: your choice in the cookie banner (pv-consent) and whether you muted the sound of the "Hold the conversation" game (pv-game-mute). The game runs entirely in your browser: its answers and results are not stored anywhere.
The cookie banner is the switch any analytics would have to go through. There is no analytics today, so the choice in the banner turns nothing on.
The only third-party component on the site is Cloudflare Turnstile in the access form. It is there to keep bots out of the form and loads only on the page that carries it.
- No cookies; local storage holds only the cookie choice and the game's mute switch
- No analytics, counters or advertising pixels
- Fonts and images served from our own domain
- Cloudflare Turnstile in the access form only
The access request form
The form collects a name, a work email, a company name, a phone number, your message and your wishes for features. Everything except the name and the email is optional. The data is used to get in touch with you about the demo, and we read the wishes to decide what goes into the product.
The legal basis is taking steps at your request before entering into a contract. The request reaches the working inboxes of our sales team and stays in our mail queue for 90 days, after which it is deleted. Inside that queue the contact details are held encrypted.
Along with the request, Cloudflare receives the technical data it needs to establish that a person filled the form in: an IP address and details about the browser.
The product: what a training session collects
Using the product needs an account: a name, a work email, a role on the team. It is created by the company that gives you access.
A training conversation is recorded in stereo - your voice and the counterpart on separate tracks - and turned into a transcript. The transcript is what the criteria-by-criteria score is built from, with quotes from your own call.
Before your first recorded conversation you see the recording terms and confirm that you have read them; without that confirmation the conversation does not start. For candidates in an assessment this is not a notice but a separate consent, and its text is stored together with its hash - so it stays possible to show exactly what a person agreed to.
We may use the audio of training calls and their transcripts to improve the quality of the system: to check speech recognition, to compare scores against what was actually said, and to tune how the counterpart behaves. This is our own work on the product, not a handover of your data to somebody else.
Who the data is shared with
We do not sell data and we do not share it for advertising. Part of the processing is done by providers the product cannot work without: speech recognition, conversation analysis, email delivery, hosting and storage.
The list of providers, and what each one receives, is available on request - write to the address below.
What does not leave our perimeter
The counterpart voice is synthesised on our own instance inside our perimeter - the text of its lines is not passed to a third-party service.
The media server the conversation runs through is ours as well: the voice does not travel through a vendor cloud.
How long data is kept
The retention term for recordings and transcripts is agreed at rollout; the usual value is 180 days from the end of the conversation. The company using the product sees that term in the recording notice shown before a call.
Requests from the form on this site are kept for 90 days.
The access log for recordings is kept for 12 months: it shows who opened a recording and when.
Protection
Signing in requires two-factor authentication and it cannot be switched off. Access is granted by role, and each company’s data is isolated inside the database itself, by its own policies and its own connections.
Recordings have no public links: every playback goes through the application and lands in the log. Data travels over TLS, disks are encrypted, and sensitive fields are encrypted separately with AES-256-GCM.
Your rights
You may ask for a copy of your data, for correction, deletion or restriction of processing, and you may object to processing. Where the data is processed on your employer’s instructions, we pass the request on to them and help them answer it.
A decision about a person in an assessment is made by a person, not by the system. You have the right to ask for your assessment to be reviewed by a human.
Changes
If this policy changes, we update the date at the top of the page. Material changes affecting data already collected are announced separately.
Contact
Write to the address below with questions about this policy or about your data - we answer within a reasonable time.
sales@smiddle.com