What we collect, and why
VKVstudio is built to need as little of your data as possible:
- Language preference — determined entirely by the page URL (/en/ or /ru/); it isn't stored in a cookie or any other persistent identifier.
- Standard hosting logs — like effectively every website, requests to this site pass through Cloudflare's edge network, which records ordinary connection metadata (IP address, user agent, timestamp, requested URL) for security and performance purposes. This site doesn't read or process those logs directly — see 'Third-party processors' below.
- Text you type into a Lab tool — handled as described in 'What stays on your device' and 'What may reach a server' below.
- Conversation history with Synapse, the AI assistant — only if and when its backend is enabled (see below); it isn't part of the default static deployment of this site.
Cookies & local storage
This site sets no cookies at all — none for tracking, none for advertising or analytics, and currently none for any other purpose either. Your interface language is read from the page URL (/en/ or /ru/), not persisted anywhere.
What the site does use is your browser's own local storage (localStorage and IndexedDB) — a different, non-cookie mechanism that isn't sent to any server automatically. It's used only for on-device functionality: remembering that you've dismissed the notice you may have seen, caching Lab-tool data and downloaded model weights on your device so they don't have to be re-fetched, and, if the Synapse assistant's backend is enabled, keeping a local copy of your chat history. None of this is used for tracking or shared with anyone.
Because there's currently nothing non-essential here to opt out of, the notice you may have seen simply states this rather than offering a granular accept/reject choice. If that ever changes — for example, if cookie-based analytics is added — this policy and the notice will be updated to disclose it and, where required, to offer a real choice before any such cookie is set.
What stays on your device
The Tokenizer Profiler and Prompt Architect run entirely in your browser using WebAssembly/WebGPU. Text you type into them is tokenized or otherwise processed locally on your device and is never uploaded anywhere by default. (The Tokenizer's exact-count mode for a few models is the one exception — it sends that text to the inference backend, which relays it to the model provider's token-counting API; see "Third-party processors" below.)
The Embedding Space Explorer computes its vectors on the inference backend, not in your browser: the passages and search queries you embed are sent to the backend (running Google's EmbeddingGemma) and turned into vectors there. Like Synapse, this backend isn't part of the default static deployment — if it isn't running, the Explorer doesn't work. The text is embedded on the fly and is not stored by the embedding endpoint.
If you use Synapse, the AI assistant, your conversation history is also cached locally in your browser using IndexedDB, so it persists across visits on the same device and browser.
What may reach a server
A few features can, under specific conditions, send text off your device:
- Embedding Space Explorer — the passages and search queries you embed are sent to VKVstudio's own inference backend and turned into vectors by Google's EmbeddingGemma running there. They're embedded on the fly and are not stored by the embedding endpoint. Like the other features here, this backend isn't part of the default static deployment; if it isn't running, the Explorer doesn't work.
- Token 'verification' in the Tokenizer Profiler — some proprietary models (Claude, Gemini) don't publish a client-side tokenizer, so an exact count requires an API call. If you opt into 'exact' verification for one of these models, the text you're tokenizing is sent to VKVstudio's own inference backend, which forwards it to Anthropic's or Google's API to get an exact count, then returns just the number. This only happens when that backend is configured and reachable — in the default static deployment of this site it isn't running, and the tool falls back to a local approximation instead.
- Synapse conversations, server-side — server-side storage only happens if you sign in with Google. When you do, your history is stored twice: once locally (above) and once in a server-side database, keyed to your Google account's unique id — not your name, email, or IP address. If you don't sign in, your conversations never leave your browser and nothing is sent to the server. As with the rest of Synapse, this needs the backend running, which isn't part of the default static deployment.
- Synapse voice input — if you speak to Synapse (the mic button), your recorded audio is sent to VKVstudio's own inference backend and transcribed there by a self-hosted Gemma model. The audio is NOT sent to any third-party speech-to-text service; it's transcribed on our server and not retained after transcription. As with the rest of Synapse, this needs the backend running.
Third-party processors
- Hugging Face — hosts the tokenizer model/vocabulary files the Tokenizer Profiler downloads for some models (run locally in your browser). Your browser fetches these files directly from Hugging Face's CDN; the text you tokenize is never sent there. (The Embedding Space Explorer no longer downloads a model to your browser — it embeds on the inference backend instead; see “What stays on your device”.)
- Anthropic / Google — reached only if you use exact tokenizer verification and the inference backend is live (see above); the specific text you asked to verify is sent to whichever provider's API matches the model you selected.
- Cloudflare — hosts this site and, as with any site behind its network, processes standard request/connection metadata for routing, caching, and abuse protection.
No sale of data
We don't sell data, and we don't share it with anyone outside the processors listed above.
Data retention
- Notice-dismissal flag (localStorage) — persists until you clear your browser's local storage for this site.
- Local IndexedDB conversation history (Synapse) — stays on your device until you clear your browser storage or delete conversations in the app.
- Server-side conversation history (Synapse, only if you sign in with Google) — retained until you delete the conversation, or automatically purged 30 days after it was last updated, whichever comes first.
- Cloudflare request logs — retained per Cloudflare's own standard log-retention policy, outside our control; see Cloudflare's own privacy documentation.
Your rights
If you are in the Republic of Armenia, the Law of the Republic of Armenia "On Protection of Personal Data" gives you the right to:
- know what personal data concerning you is processed, and why;
- access a copy of it;
- request correction of inaccurate data;
- request erasure of your data, where there's no legitimate ground for us to keep it;
- object to, or request restriction of, processing;
- lodge a complaint with the Personal Data Protection Agency of the Republic of Armenia, the state body supervising compliance with this law.
Exercising these rights in practice
Because the site is visible internationally and used by an EN/RU audience beyond Armenia, we apply these same rights as a matter of practice to every visitor, regardless of location — in line with GDPR-style best practice, even where GDPR doesn't directly apply to this site.
In practice, exercising these rights is simple: clearing your browser's local storage/site data for this domain removes the notice-dismissal flag, any cached Lab-tool data, and any locally cached Synapse history immediately, and emailing us (see 'Contact' below) is enough to request access to, or deletion of, anything stored server-side.
International data transfer
Data described above may be processed outside Armenia: Hugging Face's CDN and Cloudflare's network are both globally distributed, and Anthropic's and Google's APIs (reached only during tokenizer verification) run on infrastructure that isn't based in Armenia. We rely on these providers' own security and compliance programs for that processing; no additional data-transfer mechanism beyond what's described in this policy is currently in place.
Children's privacy
This site isn't directed at children, and we don't knowingly collect data from them. If you believe a child has submitted data to the Synapse backend, contact us and we'll remove it.
Changes to this policy
This policy will be updated whenever what the site's code actually does changes — for example, if the Synapse backend or analytics are enabled in production. The 'last updated' date at the top of this page reflects the most recent revision.
Data controller & contact
- VKVstudio, operated by Valery — data controller. Formal registration details (registered legal name and address, and any Republic of Armenia data-operator registration) are being finalised before public launch.
- [email protected] — contact for privacy requests