Plain-language summary
Visible target
You connect DBOPFS Studio to a specific live tab. That origin remains visible while you work.
Browser processing
File and record inspection, editing, and preview happen locally unless you choose an external destination.
No Studio account
The extension does not require a DBOPFS Studio sign-in, cloud database, analytics profile, or advertising identifier.
Your exports
Downloads, clipboard copies, and print jobs leave OPFS at your direction and are then controlled by your device and chosen destination.
Data DBOPFS Studio accesses
The extension is permitted to run an isolated bridge on HTTP(S) pages. When you connect its workspace to an active tab or inspected page, DBOPFS Studio may access the information needed to provide its interface:
- the connected site's origin;
- OPFS directory names, file names, file metadata, and file contents;
- DBOPFS application IDs, table names, record keys, and record values;
- browser-reported storage usage, quota, and persistence state.
This access supports the DBOPFS dashboard, explorer, editor, previews, imports, application exports, supported record printing, and record-management actions you request.
Collection and transmission
DBOPFS Studio is designed not to transmit inspected OPFS contents, file names, record values, or browsing history to The Wizard Nexus or to an analytics, advertising, or profiling service. Processing occurs in the browser unless you deliberately export, download, print, or copy data to another destination.
The browser, browser extension store, GitHub, operating system, selected printer, synchronization software, or a link you open may process information under its own terms. Those services are outside DBOPFS Studio's control.
Why the extension asks for access
The manifest also declares narrowly scoped web-accessible extension modules needed by that isolated agent. This is a resource-loading declaration, not permission to upload inspected data.
Storage and retention
Site data remains in that site's browser-managed OPFS until the site, user, browser, or operating system changes or removes it. For supported record printing, Studio places one temporary payload in extension session storage; the print page removes it as soon as it reads it, and the browser also discards session storage when the extension is reloaded or restarted. The extension does not create a remote backup or synchronization service.
Exports and downloads remain wherever you save them. Clipboard content is controlled by your operating system and clipboard tools. Print output and spool data are controlled by the browser, operating system, and printer.
Your controls
You can:
- close Studio or the selected site tab;
- review and revoke extension site access in the browser;
- close or uninstall DBOPFS Studio;
- remove exported files and clear clipboard history using device controls; and
- delete individual DBOPFS records in Studio, or clear broader site data using the site or browser storage controls.
Deletion can break the owning application. DBOPFS Studio guards destructive actions, but it cannot recreate deleted data without a backup.
Origin isolation
OPFS is separated by origin and, in some configurations, by additional storage partitioning. DBOPFS Studio does not merge unrelated origins into one live filesystem. It needs a live active or inspected page and the browser-granted access required for that origin.
A DBOPFS application ID separates trusted applications into folders inside an origin. It is not protection against hostile code already running on that same origin. See the origin and trust model.
Children's privacy
DBOPFS Studio is a developer and data-management tool and is not directed to children. The extension is not designed to collect personal information from any user.
Changes and contact
Material changes will be published in this repository and reflected by an updated effective date. For privacy questions, use the contact path published by The Wizard Nexus. Do not include private site data, credentials, or sensitive files in a public issue.
The repository copy of PRIVACY.md is distributed with the source.