Skip to main content

Consent to personal data processing

Last updated: 2026-11-13 Version: 1.2

By ticking "I consent to the processing of my personal data" next to the run button of the demo at veriqa.app/demo, next to the sign-in button of the demo applications Nova and Helio, or under the enquiry form at veriqa.app/contacts, I freely and in my own interest consent to the processing of my personal data by the operator, Dmitrii Erusov, an individual and the developer of Veriqa (contact: devs@veriqa.app), on the following terms. The box is shown on the Russian version of the Website.

Purpose

  • The demo builder: to show me how a sign-in or the confirmation of an action works with Veriqa, by running what I set up and showing me the result.
  • The demo applications Nova and Helio: to show what signing in to an application and using it looks like, by keeping my session while I am in the application and carrying out what I do there: confirmations, requests in Helio, completing the profile.
  • The enquiry form: to receive my enquiry and answer it through the same channel.

The data

What the channel I choose (a messaging app, email, or another channel) provides:

  • the identifier in the channel, which may itself be an email address or a telephone number;
  • a name, display name, or username;
  • a profile picture;
  • language;
  • the outcome of the sign-in or confirmation.

Also what I enter myself: in Nova, a date of birth and a favourite genre; in Helio, the text of requests, a telephone number, an email address, a company, and a job title; in the enquiry form, a subject and a text. And the technical data of the request: IP address, browser and device details, and time.

What is done with it

It is collected, recorded, stored, used for the purposes above, and deleted. The processing is automated.

The demo builder, Nova, and Helio hold the data in the server's working memory (RAM) only. None of it is written to the server's persistent storage, such as a disk or a database.

An enquiry from the form is saved to a file on the server so that it can be answered. The team gets an email notice of it with the enquiry number, subject, text, my name, channel, language, and time, but not my channel identifier.

The data has no other recipients. The channel data reaches the server from the channel I chose myself, which I use under its own terms. If I chose email, the code or link arrives at my address as an ordinary email.

Where it is processed

On a server in the Republic of Türkiye. I consent to my data being transferred there. Türkiye is a party to the Council of Europe Convention for the Protection of Individuals with regard to Automatic Processing of Personal Data.

How long it is kept

  • The demo builder: the data from the channel is deleted as soon as the result screen has shown it, and at the latest five minutes after the sign-in if the screen is never opened.
  • Nova and Helio: while I stay in the application; the session is dropped after a day without activity. Helio requests disappear when the application restarts.
  • The enquiry form: until the enquiry has been answered and is no longer needed for follow-up, or earlier at my request. The notice in the team's mailbox is kept and deleted on the same terms.

Separately, the web server keeps a technical log of requests to protect and troubleshoot the Website. For each request it records the IP address, the time, the page requested, the response code, the page the request came from, and the browser details. It holds no data from the channel. The log is kept for the short time needed to protect the Website.

Duration and withdrawal

This consent applies to the demo runs, sign-ins to the demo applications, and enquiries I start, until I withdraw it. The browser remembers the tick for a year in the veriqa_consent cookie, so that it is not asked every time; unticking the box removes it. I can withdraw it by writing to devs@veriqa.app. Without consent the demo and the demo applications do not start and the enquiry is not sent; the rest of the Website works as before.

More about how data is handled: Privacy Policy.