This website hosts a custom port of BassoonTracker, a JavaScript-based music tracker application. We highly respect your digital privacy. This policy outlines how data is handled when you use this version of the tracker.
This port is designed to minimize data footprint. Virtually all application processing occurs entirely inside your local web browser. We do not run automated trackers, analytics scripts, or data-monetization schemes on this site.
Key Principle: Your music files, hardware settings, and audio configurations remain locally on your machine and under your complete control.
The application relies on your browser's local storage to save your workspace preferences. This information does not leave your device unless you manually authorize a cloud synchronization feature.
| Data Item | Purpose | Duration |
|---|---|---|
bassoonTrackerSettings |
Application preferences, MIDI configurations, layout options, and Dropbox token visibility states. | Until browser data is cleared |
| Music Tracks & Modules | MOD and XM audio projects created or uploaded by the user. | Until manually deleted |
| Audio Samples | Sound assets used to compose music modules. | Until manually deleted |
| Playlist Data | Your saved lists of tracker modules and personal favorites. | Until manually deleted |
| Recent Files | Shortcuts referencing local files recently opened in the session. | Until browser data is cleared |
This data is sandboxed locally within your individual browser instance and is never automatically transmitted to any backend database owned by this site.
This port includes optional integration with Dropbox to allow you to back up and sync your music projects directly to the cloud. This behavior is entirely opt-in.
/BassoonTracker.__dbat to remember your session.Important Note: File storage on Dropbox is bound by their specific platform infrastructure. Please consult the Dropbox Privacy Policy for information regarding how they secure their cloud storage.
The site stores a non-sensitive identifier under the key bassoonDropboxClientId within your local storage. This purely helps direct the browser application to communicate with the correct OAuth endpoint upon login requests.
The tracker application itself does not monitor behavior, drop tracking cookies, or build user profiles. However, users should be aware of the following basic web functionalities:
If you choose to stream or pull classic music modules directly from external web resources (like ModArchive or Modules.pl), your browser connects directly to those third-party services. Those connections are subject to the privacy terms of those external domains.
The code architecture powering this application runs transparently in the browser environment. Users can inspect the client-side JavaScript assets directly through native web browser tools to confirm exactly how data is handled.
Because you own your workspace data, managing it is completely straightforward:
You can instantly wipe all local preferences, custom tracking lists, and stored tracks by clearing your web browser’s cache and site cookies or deleting site storage via your browser's built-in developer options.
To disconnect the app from your storage account, disconnect "BassoonTracker" inside your Dropbox Connected Apps panel and manually clear out the local __dbat string value from your browser storage settings.
Because data storage is decentralized, your workspace protection rests on standard web safety hygiene: maintaining the security of your physical machine from malware, running a secure modern web browser, and connecting via a secure, encrypted HTTPS link.
While this is a personal, non-commercial portfolio web asset, its client-side design inherently mirrors strong modern privacy frameworks:
To explore the baseline source framework or report structural application questions, you can reach out via the following open hubs: