Privacy
The short version: we run our own servers, we do not use analytics or advertising trackers, and the only thing we hold about you is what you typed into the contact form or the chat. Everything below is the long version of that sentence.
Applies to ssvstudio.dev. Last updated 5 September 2026.
Who this is
SSV Studio is an independent software studio run by 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
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 analytics. No page-view counting, no session recording, no heatmaps.
- No advertising or tracking pixels, and nothing shared with an ad network.
- No cookies for visitors. The only 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.
Two 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. And 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.
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.
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.