Accounts and tracking
FUSE has no usage tracking, advertising, or FUSE account system. It contacts your Oracle Fusion tenant only when you choose to prepare, test, or run. Connecting to Oracle still requires your own authorized Oracle credentials.
Data used by FUSE
The app handles the tenant address and credentials you enter, the SQL you write, saved workspace data, query results, and files you choose to export.
RC18 browser portable stores workspace data in your Windows user profile, not beside the app. SQL and profile fields are unencrypted. Passwords use account-bound protection whose Windows save-and-restart behavior still needs testing. RC18 was assembled on macOS and awaits Windows 11 testing.
The older RC17 native portable and installer share their own workspace in your Windows user profile. Saved passwords in those native builds use Windows Credential Manager. They do not contain the RC18 updates.
Oracle requests and local files
Tenant requests go only to the Oracle Fusion address you provide, through the relevant BI Publisher service. FUSE does not provide a direct database connection.
Drafts, saved queries, settings, optional history, and result previews stay on the device unless you choose to export or share them.
Managing saved data
You can remove connection profiles, clear or disable query history, and choose where exported files are saved. Before closing RC18, wait for Workspace saved, close the app window, then close the console. Test that queries, drafts, profiles, and the saved password work after relaunch.
Closing RC18's console does not erase saved data. Closing or uninstalling older native builds may also leave saved workspace data and credentials on the device. Back up important SQL before testing. Previously lost RC17 browser-session work cannot be recovered.
Optional schema companion
The local schema companion provides documented tables and columns and reviewed joins. It does not share FUSE credentials, drafts, results, or query execution. Copied schema context should contain metadata and citations, not your SQL or results.
These limits apply to the companion only. They do not control a coding agent's separate file permissions. File access you separately authorize and your provider's settings remain your responsibility. Do not grant the agent access to the FUSE workspace folder just to use schema context.
This website
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. Public preview files come from FUSE-Downloads on GitHub and can be downloaded without an account.
Sending test feedback
Send reproducible issues privately to the person who shared FUSE. Include your Windows build, browser version, package checksum, and steps to reproduce. Share Pass / Fail / Blocked / Not tested and redacted errors. Do not send credentials, usernames, tenant URLs, sensitive SQL, personal or business data, or raw logs.