What this site collects

Analytics, and what it records

Until 10 August 2026 this page said the site ran no analytics and set no cookies. That is no longer true, and the change is described here rather than substituted silently.

The site runs Yandex.Metrica (counter 111470927), operated by Yandex, from the moment you arrive. It sets cookies whose names begin _ym_ to recognise a returning browser, and it reports to Yandex servers. It measures the ordinary things — which pages are read, where readers arrive from, which links are followed.

It also includes Webvisor, which is session recording: mouse movement, clicks, scrolling and typing can be replayed as a session. This is more intrusive than page counting, which is why it is named separately here rather than folded into the word “analytics”.

The enquiry form is excluded from it. The form carries the markup that tells Webvisor not to record the block or the contents of its fields, so what you type into it — your address, and your description of a decision you may not want described anywhere — does not appear in a recording. That exclusion is what keeps the rest of this notice true.

There is no consent banner, and the counter loads on arrival.That is a deliberate choice by the operator and it is stated here rather than left for you to discover. If you would rather not be measured, three things work and none of them needs our cooperation: any content blocker, your browser’s tracking protection, or Yandex’s own opt-out at yandex.com/support/metrica/general/opt-out.html, which applies across every site using Metrica. The pages are static files and read identically with the counter blocked.

The contact form

When you submit the form, the fields you filled in are sent to a small relay on our server, which forwards them to an operator inbox and then forgets them. What you typed goes nowhere else; a short arrival notice does leave our server, and the last point below says exactly what that notice may contain. Specifically:

• Nothing is written to a database. There is no database on this surface.
• The relay writes your email address, the content of your message, and your IP address to no application or access log. This is a statement about the relay, which is the only thing that ever sees what you submitted — the analytics above is excluded from the form and never receives any of it.
• The relay returns the same response for every accepted submission, so the response cannot be used to test whether an address is known to us.
• After forwarding, your message lives in an ordinary email inbox and is subject to that provider’s retention, like any email you send anyone.
• A separate notification tells the operator that an enquiry arrived. It goes to a Telegram bot, which means it leaves our server, so it is built only from the fixed choices on the form — the regions you ticked, the asset class, the kind of exposure, and the time. It carries no name, no email address, and no part of what you wrote, and it cannot: the free-text fields are not passed to it at all. Until 2026-08-12 that notification carried the whole enquiry, and this page did not say so.

The lawful basis is your consent, given by the checkbox, for the single purpose of replying to your enquiry. There is no marketing list and you will not be added to one.

Server logs

The web server records the fact that a page was requested in order to operate and secure the site. Those records are kept short and are not joined to form submissions. The server is located in the Russian Federation, which is disclosed here because where a request is logged is a fact a reader may care about.

Your rights

You can ask what we hold about you, ask for it to be corrected or deleted, and withdraw consent at any time. In practice, for anyone who has only used the contact form, what we hold is an email in an inbox, and deletion means deleting that email. Ask through the same contact form, or by replying to any message you have received from us.

Analytics is the exception, because we do not hold it in a form we can search by person — it sits with Yandex, keyed to a cookie rather than to you. The control that actually works there is blocking or the opt-out described above, which stops the collection rather than asking for it back afterwards.

Changes

If this notice changes materially, the change is described here rather than substituted silently.