Legal
Privacy Policy
Effective and last updated: August 6, 2026
VRadical Studio is a desktop application that processes media primarily on your computer. It does not use advertising trackers or sell personal information. Data is sent to an external service only when a feature requires that service, such as a publishing destination or an update check.
1. Scope and contact
This Privacy Policy explains how VRadical Studio ("Studio", "we", "us", or "our") handles information when you use the VRadical Studio desktop application, its documentation website, and its optional online integrations.
For privacy questions, requests, or complaints, contact cheloute.vr@gmail.com.
2. Information handled by Studio
| Category | Examples | Purpose |
|---|---|---|
| Media and project data | Videos, photos, audio, timelines, thumbnails, subtitles, export settings, camera metadata, camera serial numbers, and calibration data. | Import, process, calibrate, preview, export, stream, and publish the content you select. |
| Local application data | Preferences, calibration and Mod profiles, LUTs, caches, export profiles, and diagnostic output. | Preserve your settings, avoid repeated processing, and operate Studio. |
| Account and authorization data | OAuth access and refresh tokens, channel identifiers and names, service usernames, session tokens, and credentials for optional publishing or update services. | Connect to a service you choose, keep you signed in, upload content, or retrieve authorized updates. |
| Publishing metadata | Title, description, tags, category, privacy status, language, scheduling information, recording date, location, thumbnail, and subtitles. | Create and configure a publication at your direction. |
| Support information | Your email, messages, diagnostics, screenshots, sample media, camera model, serial number, operating system, and GPU information when you choose to provide them. | Respond to support requests and diagnose problems. |
Studio does not intentionally collect payment-card information, advertising identifiers, address books, or precise location unless you explicitly enter location metadata for a publication.
3. Local processing and storage
Media processing, project editing, calibration, and export normally occur on your device. Studio does not upload your source media to us merely because you import or process it.
Application data is stored in Studio's application-data folders, native application preferences, project locations you select, and operating-system credential facilities where a feature uses them. Local data remains until Studio removes it as part of its normal cache lifecycle or you delete it. Uninstalling Studio may not remove all settings, calibration files, caches, projects, or credential entries.
4. Google and YouTube data
If you connect a Google account, Studio opens Google's authorization flow and requests the permissions displayed on Google's consent screen. Studio uses the YouTube Data API only to identify the YouTube channel available to the signed-in user and to upload and configure videos that the user explicitly chooses to publish.
The information handled for this integration may include OAuth tokens, YouTube channel identifiers and names, the exported video, and the publication metadata you enter. Studio communicates directly with Google's OAuth and YouTube API endpoints. We do not receive a separate copy of this Google user data on our own server through the normal desktop publishing flow.
OAuth tokens are retained locally so Studio can perform authorized requests and refresh an expired access token. They remain until you disconnect or reset the integration, delete the relevant local application data, or revoke access from your Google Account.
VRadical Studio's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
You may revoke Studio's Google access at any time from your Google Account connections. Content already uploaded to YouTube must be managed or deleted through YouTube.
5. Other external services
Optional features may communicate with services such as YouTube, DeoVR, JillVR, a user-configured VRadical server, GitHub for authorized software updates, or the official Topaz authentication service. When you use one of these features, Studio sends the data required to perform the action you requested. The receiving service processes that data under its own terms and privacy policy.
The documentation website is hosted by GitHub Pages. We do not add analytics, advertising trackers, or marketing cookies to it. GitHub may process technical request information, such as IP addresses and browser information, as described in GitHub's Privacy Statement.
6. When information is shared
We do not sell personal information. Information may be disclosed only:
- to a destination or service you explicitly choose to use;
- to service providers that support the requested function, subject to their applicable terms;
- when you intentionally provide information for support;
- when reasonably necessary to protect users, enforce legal rights, prevent abuse, or comply with law; or
- as part of a business transfer, with appropriate notice and safeguards where required.
7. Retention and deletion
Local media, projects, profiles, settings, caches, and authorization data are retained according to the feature involved and remain under your control on your device. You can remove local files, clear or reset Studio settings, disconnect supported services, and revoke third-party authorization.
Support correspondence and files you voluntarily send may be retained for as long as reasonably necessary to resolve the request, maintain a record of the resolution, protect legal rights, and meet legal obligations. You may request deletion by contacting us, subject to information we must retain by law or for legitimate legal purposes.
8. Security
Studio uses encrypted HTTPS connections for supported online services and keeps authorization data on the user's device. No system is completely secure. Protect your operating-system account, do not share authorization codes or diagnostic files containing sensitive paths or identifiers, and revoke access if you suspect compromise.
9. Your choices and rights
Depending on where you live, you may have rights to access, correct, delete, restrict, or object to processing of personal information we control, and to receive a portable copy. You may also have the right to complain to your local data-protection authority.
Most Studio data is stored locally and can be accessed or deleted directly by you. For information we control outside your device, submit a request to cheloute.vr@gmail.com. We may need to verify your identity before completing a request.
10. Children
Studio is not directed to children under 13 or the minimum age required to consent to data processing in their country. We do not knowingly collect children's personal information. Third-party account services may impose their own age requirements.
11. International processing
External providers selected by you may process information in countries other than your own. Their privacy policies describe their transfer mechanisms and safeguards. Local-only Studio processing remains on the device and storage locations you control.
12. Changes to this policy
We may update this policy when Studio's features, integrations, or legal obligations change. The current version and effective date will always be published on this page. Material changes will be highlighted through an appropriate product or website notice when required.