App privacy notice

Windows public beta · Version 0.1.19

Verzugo Studio is supplied by Verzugo Systems Inc. Questions about this notice or data you send to us may be addressed to support@verzugo.com.

Files and saved work

Studio processes the files and workflows you choose on your computer. It saves workflows, preferences, connection settings and working data in your selected workspace, application data folders, local cache and WebView storage. Saved credentials can also be stored in Windows Credential Manager as described below. Exporting or publishing results writes to the destination you choose. Keep separate copies of important source files and results.

Uninstalling the application is not a request to erase your saved work. The installer is designed to retain workflows and application data; the published release notes must describe the behavior verified for this beta. Delete work and application data separately when you intend to remove them, after preserving anything you need.

Assistant access

When you connect a compatible assistant to Studio through MCP, the local Studio companion exchanges requests and results with your assistant client through standard input and output. You select the folder containing your saved workflows. The assistant can receive tool descriptions, workflow structure, selected workflow configuration, validation results, proposed changes and execution status.

Workflow changes are enabled by default, and sample sharing is off by default. When workflow changes are enabled, the assistant can save new workflow files in the selected folder; it does not overwrite existing files. If you enable sample sharing, the assistant can also receive bounded samples of result rows and JSON discovery results. Studio removes recognized credential fields and sensitive connection values from workflow responses. Source data and sample rows can themselves contain sensitive information, so check what you permit the assistant to access and share.

Running a workflow test or JSON discovery requires separate approval in Studio for the exact folder and any requested read-only network origins. That approval lasts until Studio closes. Assistant tests use local workspace files and the approved read-only network requests; database connections and external outputs are unavailable to these tests. Tests create local working files and results in the selected workspace, and assistant setup preferences are saved locally.

Your assistant client may send the responses it receives to its chosen AI service. That client or service controls its own processing and retention. Review its terms and privacy notice before connecting it or enabling sample sharing.

Changing Studio's assistant setup selections does not change or revoke permissions for a running companion. Save the updated configuration in your assistant client and stop and restart its Studio companion to apply the change. Native workflow-test approval is separate and ends when Studio closes.

Connections and downloads

When you use a database connection, authentication and queries communicate with the server or service you select. The operator of that server or service controls its processing and retention. Review its terms and use only data and accounts you are entitled to access. Saved connection settings can include server names, account names and other identifying information. A remember-sign-in option can retain authentication state where supported by the selected driver.

When you save an Oracle connection, Studio stores the password in Windows Credential Manager under the VerzugoStudio.Oracle service and stores an opaque reference in the connection profile. Snowflake's Remember sign-in option asks its driver to store temporary sign-in credentials. Removing an Oracle connection attempts to remove its saved credential; uninstalling Studio does not by itself remove saved connections or guarantee removal of Credential Manager entries.

When you open Help → Check for Updates or choose Check in the Application Updates window, Studio requests update information from verzugo.com. Studio does not check for application updates automatically at startup. If you choose Download, Studio can download available update files from verzugo.com and save them in the local application update cache. The update hosting service can receive normal connection details, such as your IP address, request time and the update file requested. These requests do not send your source files, workflows or saved connection credentials.

Choosing a database driver download or a database driver update check contacts the driver distributor. These driver operations contact dbc-cdn.columnar.tech. Network services receive the information needed to serve the request, such as your IP address, request time and client identification. Other network-enabled workflow features contact the services configured for that workflow.

Download, API Request and Web Scraper contact the HTTP(S) endpoints configured in the workflow. Depending on configuration, they can send URLs, query values, headers, request bodies and row values used to form per-row URLs. Returned content and limited response metadata may be stored in Studio's local cache.

Windows Setup includes Microsoft's x64 Evergreen Standalone installer to provision the shared WebView2 Runtime when it is missing. Microsoft manages that runtime and its subsequent updates under Microsoft's terms.

Studio's interface uses Microsoft Edge WebView2, which includes Microsoft Defender SmartScreen. WebView2 collects and sends diagnostic and SmartScreen information to Microsoft, and its crash reporting can send crash dumps to Microsoft. Microsoft's Privacy Statement and SmartScreen privacy information describe Microsoft's handling of that information. Windows diagnostic-data preferences govern optional diagnostics; Microsoft also collects required diagnostics. See Microsoft's WebView2 data and privacy documentation.

Diagnostics and support

Studio automatically stores the latest interface error locally in its WebView storage. It can include a timestamp, error text, stack and component details, and the app URL. Startup timing stays local and is written to a report file only when a startup-report path is configured. The reviewed first-party code does not automatically send these records to Verzugo Systems Inc.

Application diagnostics can contain file paths, connection identifiers, configuration details and error messages. Installer logs can contain installation paths and package-operation details. Review any logs before sharing. Do not send passwords, tokens, confidential source data or personal information that is unnecessary to reproduce a problem. A small synthetic example is preferred.

If you contact support@verzugo.com, the information you send is available to Verzugo Systems Inc. and the service providers used to receive and handle that correspondence. We use it to investigate and respond to your request. Ask us at that address about information you have provided or to request its deletion, subject to any applicable retention requirement.