Privacy policyPrivacy policy

Vishot is a tool that turns text dialogue into an editable 3D scene in Unreal Engine 5 or in the web studio. Most of the work happens on your own computer. This policy explains what the portal stores, why, and what you can do about it. We wrote it with the EU General Data Protection Regulation (GDPR) in mind.

Who is responsible

The controller of the personal data described here is Oleh Kopiika, FOP, registration number 3192315692, Ruska Poliyana st. Druzbu 23, Ukraine. Privacy questions and requests: hello@vishot.ai. We answer within 30 days.

What stays on your PC

The plugin and the studio server run locally. Your scripts, lore, the scene JSON the plugin makes, generated audio and your Unreal project do not leave your computer, unless you switch a role (for example the final voice or the director model) to a cloud model, or attach a scene to a case yourself. For a cloud role, only the request for that role is sent, through the portal, to the provider you chose.

The web studio is different: it runs in your browser, and the layouts, scenes and reference images you save there are kept in your account on the portal (see below).

What the portal stores

• Account: email address, password hash (or the Google account link if you sign in with Google), role, language.
• Profile: handle, display name, studio, bio, avatar and links you add.
• Cases: the cases you create, their text, frames, tags, numbers, video links and, if you attach it, the scene JSON. A case is public only after you consent to publication and a moderator approves it.
• Devices: for each device you connect with the plugin: a device id, the computer name, the operating system and its version, the name and total video memory of the first graphics card, the Unreal Engine version, and the list of models available on it (name, source, format, quantization, size; never paths, model files or your projects). Device tokens can be revoked at any time.
• Model sets: your choice of model for each task, synced between the portal and the plugin.
• Web studio: layouts, scenes, their version history, thumbnails and the reference images you upload. Reference images are private and shown only to you through short-lived links. They go to a video provider only as part of a generation that you, or an agent you connected, start.
• Connected agents (MCP): the AI assistants you authorize and the personal keys you create for scripts: the app name, the permissions you granted, an optional monthly spending limit and when they were used. We store only a hash of each token or key, never the key itself, and a personal key that has not been used for 180 days is revoked automatically. An agent you connect receives the data it reads on your behalf under its provider's own terms; you can revoke it at any time in My account › AI agents.
• Provider keys: API keys for cloud providers, if you choose to store them on the portal. They are encrypted at rest and never sent to the plugin. You can instead keep a key only locally in the plugin, and the portal will never see it.
• Usage log: for requests that go through the portal proxy: time, role, model, token or character counts and estimated cost. Not the content of the request. Requests sent through the proxy pass through our servers to reach the provider; we do not store their content.
• Billing: when you buy a plan or a credit pack, the payment provider collects your payment details, billing address and tax information. We receive from it your plan, its status, amounts and a customer id, never your full card number.
• Plan credit ledger: records of credit added, spent and refunded, shown in your account.
• Requests: plan requests and plugin access requests, with the note you add, and when we answered them.
• Video and image jobs through the platform: for cloud video or image generation, the prompt and the reference frames you send are passed to the provider to run the job and are not stored by us, except reference images you saved in the web studio, which stay in your account. For a video job we keep a job record (model, status, length, cost, the provider's job id). A finished image is returned to the plugin in the same request and is not stored by us. A finished video is copied to our file storage, and the plugin gets a private link to it for 24 hours. As soon as the plugin confirms the download, we delete the file; anything left over is deleted automatically within 3 days.
• Subscriptions and messages: your email if you subscribe to our news, with when you confirmed it and the consent text you agreed to, and the messages you send through the contact or pilot forms.
• Technical data: IP addresses are used briefly for rate limiting to protect the forms and the API.

Plugin and the portal

The plugin sends nothing to the portal before you sign in. When you sign in, it sends the computer name as the device name. After that it sends your device token with every request, and when you press Sync it registers the device with the details listed above under Devices and syncs your model sets (provider, model and cloud setting per role; never keys, local paths or addresses). While you are signed in it checks the "Install on PC" queue and reports install progress, and it sends a role's request to the portal only for the roles you switched to the cloud.

The plugin does not send usage statistics today. If it starts to, the portal will accept anonymous generation statistics only from a connected device and only if you turned them on in your account settings. They contain the model, the role, whether it ran locally or in the cloud, the duration, the number of automatic fix rounds, whether it worked and the plugin version. They are stored without your user or device id. You can turn them off at any time.

The portal also has a public update check that needs no account. A request to it carries no account data.

Why we process it (legal bases)

• To provide the account, the portal and the plugin connection (performance of a contract).
• To take payments and keep billing records (performance of a contract and legal obligation).
• To publish cases you submitted, with your explicit consent, which you can withdraw by unpublishing or deleting the case.
• To send launch news, news about Vishot's own model and occasional development (devlog) updates, as the form you used says, if you subscribed and confirmed your address (consent).
• To collect generation statistics if you turned them on (consent).
• To keep the service secure and prevent abuse (legitimate interest).

Who else sees it

These processors handle data on our behalf:

When online payment opens, we will name the payment provider in this table before the first payment.

When you use your own key, your request goes to that provider under your own agreement with them. When you use platform keys, we send the request to the provider on your behalf under our agreement. Providers may keep requests for a limited time for abuse monitoring under their own policies.

Some services receive data from you directly, under their own terms, and are not our processors: Google, if you sign in with Google; YouTube or Vimeo, when you press Play on a case video; Hugging Face, when the plugin downloads a model to your computer (it sees your IP address and the download request); and the AI agents you connect over MCP, which receive what they read on your behalf.

Published cases and author pages are visible to everyone. We do not sell personal data and do not use advertising trackers.

International transfers

We are established in Ukraine, which the European Commission has not recognized as providing adequate protection. Your data is stored with processors in the EU (Supabase, Ireland; Cloudflare R2, EU jurisdiction) and accessed by us from Ukraine to run the service. Some processors are US companies; we rely on the EU–US Data Privacy Framework or the EU Standard Contractual Clauses in their data processing agreements.

How long we keep it

Account data is kept while the account exists. When you delete the account, your profile, cases and their frames, devices, model sets, keys, usage log, plan and credit history, studio layouts, scenes and reference images, connected agents, your news subscription and the messages sent from your account email are deleted, except what we must keep by law. Invoices and tax records of your payments are kept for as long as tax law requires. Finished cloud videos are deleted from our storage once the plugin downloads them, and within 3 days at the latest. Rate-limit records are deleted within a day.

Messages from the contact and pilot forms are kept for 24 months after we receive them. Addresses for our news are kept until you unsubscribe; after that we keep only a suppression record so we do not email you again. Addresses not confirmed within 30 days of the confirmation email are deleted. You can unsubscribe with the link in every email.

Cookies

We use only the cookies needed to keep you signed in and to remember your language and theme: the sign-in session cookies (their names start with sb-), which end after 30 days without use, and lang and theme, which are kept for a year. During sign-in, password reset and account deletion, and when you confirm or cancel a news subscription, we also set short-lived cookies that last at most an hour: vishot_auth_pending holds the address a sign-in or confirmation email went to, so the next page can show it; vishot_recovery holds the id of the account a password reset link signed in, so only that account can set the new password; vishot_done, kept for ten minutes, only says that your news confirmation or unsubscribe went through, so the page can say so; account_deleted holds the deleted address and plan for the page that confirms the deletion. When you go from the sign-in page to the password reset form, the address you typed is passed in this tab's session storage and removed once the form reads it. We do not use advertising or analytics cookies. The web studio keeps objects you copy in your browser's local storage, so you can paste them into another layout; this stays in your browser. Embedded videos from YouTube or Vimeo load only after you press Play. From then on, that video service may set its own cookies.

Your rights

You can access, correct, export and delete your data. Data export and account deletion are available in the account settings. You can also object to processing, ask us to restrict it, withdraw consent, and complain to your local data protection authority. If you are in Ukraine, you also have rights under Article 8 of the Law of Ukraine "On Personal Data Protection" and can complain to the Ukrainian Parliament Commissioner for Human Rights.

Changes

If we change this policy in a meaningful way, we will say so on the site and, for account holders, by email.