Privacy
The short version: we run our own servers, we do not advertise to you or sell anything about you, and the only thing we hold is what you typed into the contact form or the chat. We do count visits, with a cookie-free counter that runs on our own server and with Google Analytics, which sets cookies only if you accept them — the section below says exactly what each one receives and how to stop it. Everything below is the long version of that sentence.
Applies to ssvstudio.dev. Last updated 16 September 2026.
Who this is
SSV Studio is an independent software studio run by Product Delivery Manager Serhii Skrynnikov. If you want anything on this page acted on — a copy of what we hold, a correction, a deletion — one email is enough: support@ssvstudio.dev.
This policy covers this website only. Each product we run has its own policy on its own domain, because each one handles different data. And when we build or operate something for you as a client, the personal data inside that system is yours: we process it on your instructions under the contract for that project, and this page does not govern it.
What we collect, and only when you send it
Apart from the visit counting described further down, nothing on this site is collected by browsing it. Two things ask you for information, and both are things you choose to use.
- The request form. Your name and email, because we cannot answer without them, plus the optional company, topic, budget and timeline you pick and the message you write.
- The chat widget. The messages you send, and a name and email if you choose to give them.
With either one we also store your browser's user-agent string and a keyed hash of your IP address — not the address itself. The hash cannot be turned back into an address without a secret held on the server, and it exists for one purpose: to stop the same source flooding the form.
What we do not do
- No session recording and no heatmaps. Nobody watches a replay of your visit, and nothing you type is ever part of the counting.
- No advertising or tracking pixels, and nothing shared with an ad network.
- The only cookies for visitors are Google's analytics ones, and only after you accept them. The other cookie this domain sets is the sign-in session for our own admin, which you will never be issued.
- Nothing sold, rented or handed to a data broker. Ever.
Three honest exceptions, because "no third parties" is a claim worth checking rather than repeating. Typefaces are loaded from Google Fonts, so opening a page tells Google's servers your IP address and which browser you use. The chat stores one random token in your browser's local storage so a conversation survives a reload — clearing site data for this domain ends it. And the third is visit counting, which has a section of its own below.
Counting visits
We count how many people read a page, which pages they read, and roughly where they came from. That tells us whether writing something was worth the day it took. It is the only reason we collect it, and we do not use it for advertising. Two counters do this, and they follow different rules.
Both counters also receive a few named steps, never their content: that someone started writing in the request form, sent it, or the sending failed (and which of a few fixed kinds of failure it was); that someone opened the chat, started it, or sent a message; and which priced offer someone clicked. Never what anyone wrote, never a name, never an email address, and never anything that could tell us who you are. Before anything goes to our own counter, the page checks every value against a fixed list in its own code and drops anything that is not on it.
Our own counter, on our own server
It runs for everyone who has not said no, and it sets no cookies. It is
Umami, run by us on the same server
in Germany as the rest of this site, and nothing it receives goes to anyone else. It stores
nothing on your device — no cookie, no local storage, no identifier. What it receives is the
address of the page (without anything after a ? or #), the page's title,
the site you came from (the site only, never its full address), your browser's language, your
screen size, and your browser, operating system and device type. It also receives your IP
address, which it uses only to work out a rough location (country, region and city) and to tell one
visit from another. It does
not store the address. To recognise a returning visitor without a cookie it keeps a one-way code
computed from that address, your browser and a secret that changes every month, so the same
visitor is recognised within a month and never across months.
To stop it, choose “No thanks” on the banner at the bottom of the page: it stops counting you straight away, and the choice is remembered in your browser. If your browser does not let this site store anything, we cannot read a choice you made on an earlier page, so this counter does not count you at all — unless you choose “Accept” on the page you are reading, and then only on that page. If you chose “Accept” earlier and changed your mind, use the “Change cookie choice” button at the end of this section. A content blocker that blocks it works too; we do not try to get around one. The counts have no automatic deletion date yet; they hold no name, no email address and no IP address.
Google Analytics
Google's script loads on every page, but it stores no cookie until you choose
“Accept”. Before that — and for good if you choose “No thanks” — it sends Google
cookieless signals: that a page was opened (its full address, including anything after a
?) and which of the named steps above happened. With your agreement, Google sets cookies in your
browser to recognise a returning visitor. In both cases Google receives your IP address, which it
shortens before storing, along with the page you opened, your approximate country, and your
browser and device type. We never send your name, your email, or anything you typed into the form
or the chat. Google processes this on our behalf and may hold it on servers outside your country;
their handling is governed by
Google's privacy policy. We keep it for 14
months, the shortest retention Google offers.
If you accepted and changed your mind, use the “Change cookie choice” button below and choose “No thanks”: Google sets no new cookies from then on. The ones it already set stay until you clear this site's data in your browser.
If you would rather Google did not count you at all, any of these works and we do not attempt to defeat any of them: a content blocker or privacy extension, Google's own opt-out add-on, or your browser's setting to block third-party cookies.
Everything else on this site keeps working either way — nothing here is gated behind being measured.
If you are in the EU or the UK and would like your analytics record removed, write to the address in the footer and say so. We will not ask you why.
Where it goes
Onto our own server in Germany, in a small database we operate. A copy of a new request or chat message is pushed to a private Telegram chat so that somebody sees it within minutes rather than the next working day, and — if email delivery is switched on — to our own inbox. That is the whole list of places your message travels to.
How long we keep it, and how to end that
Until you ask us to delete it. We would rather say that than publish a retention period we do not actually enforce: there is no automatic deletion job on this site today, so a request from 2026 is still in the database in 2027 unless somebody removes it.
Write to the address above and we will delete your request or conversation, and tell you when it is done. You can also ask what we hold, ask for a copy of it, or ask us to correct it. If you are in the EU, the EEA or the UK, the basis we rely on for handling a message you sent us is our legitimate interest in replying to it — and you can object to that, which in practice means the deletion above.
Children
This is a site about business software. It is not aimed at children and we do not knowingly collect anything from them.
Changes
This page carries the date it was last changed. If we ever start collecting something new, that date moves and the section above it says what changed — a policy that quietly grows is not a policy.
Changed 16 September 2026: added our own cookie-free counter (see “Counting visits”), said more exactly what Google Analytics receives before you choose, and added the “Change cookie choice” button.
This is a plain-language description of what our software actually does, written by the people who wrote the software. It is not legal advice, and if you need a compliance guarantee for a specific regime, have a lawyer read it against your requirements.