Who provides FUSE
FUSE SQL Studio is independent software provided by Anand Vamsi Krishna Vegaraju. For privacy or support questions, email v.anand.vamsi@gmail.com.
FUSE has no usage tracking, advertising, FUSE account system or built-in AI model. It contacts your Oracle Fusion tenant when you choose to prepare, test, query, browse reports or capture catalog snapshots. Connecting to Oracle requires your own authorized Oracle credentials.
Data used by FUSE
The app handles your tenant address, credentials, connection settings, SQL and parameters, saved queries and drafts, enabled query history, results, and files you import, save or export. SQL and results may contain personal or business information. Use authorized non-production environments. Do not include secrets or unnecessary personal data.
FUSE sends your chosen requests to your selected Oracle Fusion HTTPS services. It does not send tenant credentials or results to a FUSE-operated server. Oracle and your organization control processing and retention within your tenant.
Native Windows app storage
The native app uses Windows Credential Manager for saved passwords. Other connection settings, drafts, saved workspace data and enabled history are stored in a local per-user SQLite database without application-level encryption. SQL and export files are saved where you choose and are not encrypted by FUSE. Results normally stay in memory unless you export them or approve a sample for a coding tool.
Other software with sufficient access to your Windows account may be able to read your workspace or files. Folders may be backed up or synchronized by other software. Do not put passwords or tokens in SQL, comments, filenames or feedback.
Windows browser portable storage
The portable stores its workspace in your Windows user profile, not beside the extracted app. Non-password workspace content and SQL files are plain text. Saved passwords use Windows DPAPI for the same Windows user. This differs from the native app's SQLite and Credential Manager storage. Follow the instructions bundled with your version when saving, closing or upgrading. The current portable authorizes the browser through a private, single-use launch file. A localhost session cookie and an additional origin-specific session value in browser storage protect gateway access; they contain no Fusion password. These values are replaced when FUSE restarts. Windows PowerShell secures the launch file before the browser opens. Changing a saved connection’s Fusion URL requires password reentry.
Portable SQL files
In the browser portable, Save writes both a library copy and a real SQL file. The portable retains the file bound to each query across restarts, renames and default-folder changes. For a new query, the default is Documents/FUSE/Queries or the folder selected in Settings. Browse in Save as can choose another destination through the Windows OS dialog; PowerShell must be available and allowed by device policy. Choosing a path alone does not write it, and existing-file replacement requires explicit approval. Draft autosave alone does not write a SQL file. Imports copy files and nested folders without changing the originals; they are not live folder synchronization. Externally edited files are protected from overwrite.
Keep sensitive SQL literals and exports out of folders accessible to external agents. Your chosen folder may also be accessible to other software or cloud-sync services you use.
Snapshots, presets and recovery
The current portable can save catalog exports and parameter profiles locally. Catalog snapshots contain original report or model bytes, paths, checksums and capture details. Investigation documents saved by earlier versions remain on disk and can contain SQL, connection labels and fetched rows. RC30 build 2 does not create or open those documents. These documents and query recovery copies are not encrypted by FUSE and may contain personal or business data.
Saving parameter definitions does not save values. A named preset stores values only when you explicitly save it; presets are not loaded automatically. In the published RC30 portable, single and multi-value parameter inputs are passed separately from SQL and are not written to query history or SQL files. SQL literals you type and values returned in results can still be saved.
Query recovery and local document storage have limits. Older recovery entries may be removed; keep controlled backups of important work. Review snapshots, presets, result exports and any older documents before sharing. Exporting does not redact their contents or make them safe to disclose.
Result analysis and portable Excel export
RC30 analyzes already-fetched results on your device. Sorting, filtering, grouping and statistics do not request additional rows from Oracle. Excel files are generated locally in your browser; results are not sent to a conversion service.
Choose the current view, all fetched rows or selected cells before exporting. The browser controls the download location. Exports can contain personal or business data, are not encrypted by FUSE and are not automatically redacted. Review them before sharing or placing them in synchronized folders.
Queries and support
FUSE contacts your Oracle Fusion environment when you choose to save and test a connection, run SQL, browse reports or capture catalog snapshots. Inspecting a saved snapshot needs no Oracle connection.
FUSE accepts up to 1 MiB of SQL text. Your Oracle environment may allow less. Use an authorised non-production environment. When contacting support, remove credentials, tenant addresses, and business data.
FUSE is not a certified Oracle SQL parser or a sandbox. Custom functions can have side effects under Oracle privileges. Use least-privileged access and authorized non-production environments.
Managing saved data
You can remove connection profiles, clear or disable query history, and choose where SQL files and exports are saved. Drafts and saved workspace data can remain even when history is off. Removing a library item does not necessarily remove saved SQL files, exports, backups or synchronized copies. Manage those files at their saved locations.
Closing or uninstalling FUSE may not erase every saved file or credential. Check removal on your device and back up important SQL before deleting local data.
Portable closing and upgrades
For the browser portable, wait for Workspace saved, close the app window, then close the console. Test that queries, drafts, profiles and the saved password work after relaunch.
To upgrade the portable, save and close the old app and console, extract the new package into a new folder, and keep your existing FUSE data in the Windows user-profile folder. Do not delete that folder. Portable versions share this workspace; run only one at a time. New HCM and FSCM connections use V3. Saving creates missing FUSE files with approved catalog access but does not overwrite existing models. Existing V3 files are not changed automatically. Working connections need no general model migration. Typed parameters may require the separate parameter-report setup; it prepares missing objects under distinct names without overwriting existing models.
Coding tools in published downloads
The local MCP companion provides documented tables, columns and reviewed joins. Optional query creation and read-only execution requests require separate permissions, which start off each session, and your approval for every request inside FUSE. Review the exact SQL and connection before approving a run. The current portable also shows every typed input; approval is bound to those inputs, SQL and connection for one execution.
Counts-only is the default. Optional result samples need both session permission and approval for each run and connection. Samples can reach the coding tool's provider and are not automatically redacted. Limits are 100 rows, 100 columns and 64 KiB, with five-minute expiry. Cells may be shortened. Share only data you are allowed to disclose, with any required permission from the people it concerns. Prefer synthetic data.
You can disable permissions and clear available samples. Expiry, clearing and revocation stop later access through FUSE. They cannot recall copies already received by a tool or provider. Stored credentials, saved queries, drafts and query history are not exposed through the companion. SQL and inputs submitted by your coding tool are already visible to that tool and subject to its provider policy. Use placeholders, not secrets.
FUSE has no embedded chat, built-in model or provider connection. These companion limits are not a filesystem sandbox. Your coding agent's separately granted file and command permissions and provider settings remain your responsibility. Do not grant access to FUSE's data, SQL or export folders just to use the companion. Schema context sent to a coding tool may be processed by that tool's provider.
Report tools return local text content, including SQL, XDM, XDO, starter RTF and optional chart definitions. They do not save, upload, run or render reports. Your coding tool saves the files with your permission. Report import, layout editing and rendering in BI Publisher are separate actions.
Coding tools in the October upgrade
The website previews a completed app update that is not yet included in public downloads. These details apply to that upgrade, including the local Apple-silicon build; the published editions above retain their existing behavior.
Connect Codex and Connect Claude Code check the local companion and save only FUSE's entry in the selected client's configuration, with a private backup. Unrelated settings and explicitly disabled entries are preserved. Setup does not contact a model provider, submit SQL or change action permissions. Reopen or reload a running client to load the configuration. Other local stdio MCP clients can use manual setup.
Permission choices persist. Run read-only queries, Read query results and Save to the Query Library start on; Approve automatically starts off. With automatic approval off, review the exact SQL and connection and give separate sharing consent before results are shared. If you enable automatic approval, future requests follow your saved action and sharing permissions. Connection names can be visible to the tool; credentials and tenant addresses are not returned by that tool.
Shared results are limited to 200 rows, 100 columns and 128 KiB, expire after five minutes, and may contain shortened cells. They are not automatically redacted and can reach your coding tool and its provider. Disabling sharing or execution, clearing shared results, or closing FUSE revokes later access through FUSE. These actions cannot recall copies already received. Your coding tool's separate file and command permissions still apply.
Query inputs and import in the upgrade
The upgrade validates typed inputs and inserts them as Oracle literals before sending the statement. Parameterized history keeps the template with placeholders. Oracle receives the values in the executed statement; SQL, presets and exported data still need appropriate protection.
Earlier-work import copies supported saved work into the current workspace while keeping existing items and the source workspace. It can include queries, folders and connection settings. Native vault passwords require re-entry. Close the source edition before importing and review the imported connections before use.
This website and downloads
This site has no sign-up form, advertising tracker or product analytics script. The hosting provider may process ordinary request information needed to deliver and protect the site. Portable ZIP, EXE, and MSI downloads come from GitHub. Microsoft handles acquisition and delivery through the Microsoft Store. These services apply their own privacy policies.
Support and feedback
If you contact support, your message and attachments are processed through the support email service to answer your request. Send reproduction steps and sanitized errors. Do not send credentials, usernames, tenant URLs, sensitive SQL, personal or business data, or raw logs. Contact the support email above with questions about information you have supplied.
Independent software
FUSE is independent software, not affiliated with, endorsed, sponsored or certified by Oracle, and grants no Oracle license. Oracle is a registered trademark of Oracle and/or its affiliates. Use only authorized non-production environments and read the bundled notices.
FUSE is available from the Microsoft Store and as a portable ZIP, EXE, or MSI. See the download page for all options. macOS downloads are not available.
The direct ZIP, EXE, and MSI downloads are unsigned. If Windows or your organization blocks them, ask your administrator. Do not disable protections.
Changes to this notice
The date above shows when this notice was last updated. Material changes to data use or sharing require an updated notice and any consent needed before that use.