01Scope of this notice
This notice describes TABROOM version 1.0.0, an extension for organizing Chrome tabs into named, locally saved workspaces. It covers the extension interface, its background worker, local records and files the user chooses to export.
TABROOM does not require an account and does not operate a cloud workspace service. Its primary purpose is to save and restore a structure of URLs, windows, pinned tabs and Chrome tab groups.
This policy concerns the extension, not websites opened through it. A restored website may have its own sign-in system, cookies, network requests and privacy notice. Saving a URL does not bring that website under this policy.
02What you choose to save
A workspace is created only when you use Save workspace or import a library. You choose its name and may add a note. You can save selected tabs or all supported tabs in normal browser windows.
Each snapshot records supported web addresses, tab titles, order, pinned status, window labels and group descriptions. Group descriptions include a title, a Chrome color and a collapsed-state flag. The snapshot also has a local identifier, label and timestamp.
Addresses may contain search terms, document identifiers, account-related paths, query parameters or fragments. TABROOM keeps these address components so that restoration and duplicate matching are meaningful. Treat saved libraries as private browsing-related information.
03The permissions requested
The tabs permission allows TABROOM to read titles and URLs of open tabs and to work with tab identifiers. It supports the live browser overview, selection, exact-address duplicate detection, switching to a tab and opening saved addresses.
The tabGroups permission supports reading group metadata and updating groups when you explicitly organize or restore tabs. The sidePanel permission supplies the compact interface beside your current page. The full workspace library is an extension page in a separate tab.
The storage permission is used for the local library and the last restore journal through chrome.storage.local. No host permissions, history permission, cookies permission, content scripts or scripting permission are declared in this build.
04Live browser information
The Live tabs screen obtains the current normal windows and their tab lists from Chrome. The interface uses titles, addresses, IDs, positions, pin states and group associations to show the current arrangement and respond to your commands.
Live information in the interface is not automatically turned into an archive. The extension listens for relevant tab and group changes to refresh the view; it does not maintain a chronological record of every page you visit.
Private windows are excluded by the application. Browser internal pages may appear in the live browser list when Chrome supplies them, but snapshots accept only HTTP and HTTPS addresses without embedded username or password components.
05What a snapshot does not contain
TABROOM does not copy the DOM, page text, form contents, page screenshots, downloaded documents, browsing Back and Forward entries, or the internal state of a web application. It does not read passwords or authentication cookies.
Tab titles and URLs can still reveal personal information even without page contents. A document title, search phrase or private resource path can identify a person or a project. Avoid exporting a library that contains information you should not disclose.
Restoring a snapshot is not restoration of a website login session or an unsent draft. Save your work within the website itself before closing it. TABROOM does not close pre-existing tabs as part of its normal restore operation.
06Organizing tabs in Chrome
Grouping, moving, dragging and switching tabs are actions you initiate in the interface. They change the active browser arrangement, rather than merely editing a visual imitation of the tab strip. A moved tab can leave its former group.
Pinned tabs cannot be grouped by this application. Grouping requires the selected tabs to be in one window; you can move them first. TABROOM checks live identifiers again because a tab may have closed since it was displayed.
These operations do not submit web forms or issue commands inside a website. They can bring a website into view, and that site may then perform its normal foreground behavior. Chrome remains responsible for the actual tab operations.
07Restore choices and duplicate addresses
The restore preview lets you choose a snapshot and select individual entries. You can skip an address already open, focus its existing tab, or deliberately open another copy. Matching uses the complete normalized URL, including its query and fragment.
Newly restored entries are opened in new normal windows corresponding to the saved window structure. The worker opens them sequentially and applies supported pinning and group metadata. Existing tabs are not moved merely to resemble a saved room.
A restore can partially succeed when a tab disappears, Chrome rejects an operation or storage becomes unavailable. An entry may have opened even if a later group update failed. Review the result before retrying; the extension does not promise an all-or-nothing browser rollback.
08The local restore journal
The background worker keeps one restore journal in local storage. It includes a local job ID, time, total entry count, completed entry descriptions, relevant addresses, resulting tab IDs, newly created window IDs and any reported errors.
This journal helps explain a partial or interrupted restore and prevents an unattended retry from silently opening duplicate sets. After interruption, the interface asks you to review and acknowledge the report. Restoration does not automatically resume after a browser restart.
The last completed report can remain until another restore replaces it or you erase the library data. It is not sent to a publisher. The ordinary library export contains rooms and snapshots, not the separate journal.
09Where information is stored
The library and restore journal are stored under this extension in your local Chrome profile using chrome.storage.local. This version does not use chrome.storage.sync and does not provide an extension-operated cross-device synchronization service.
Application limits are forty rooms, twelve snapshots per room, three hundred tabs per snapshot, and a three-megabyte serialized library budget. The restore journal is separate from that library budget. Chrome can impose other storage or device constraints.
These records are not encrypted by TABROOM with a separate user-controlled password. Device encryption, profile protection, browser backups and enterprise settings are outside the extension. Other people with access to an unlocked profile may be able to see your workspaces.
10Network behavior
TABROOM has no analytics endpoint, account server, remote database or remote code loader. The extension interface does not fetch website favicons; it uses locally generated letter marks so that browsing the library does not itself query icon services.
When you restore a URL, Chrome navigates to that website at your request. That navigation can contact the website, follow redirects, use existing browser cookies and load third-party resources selected by the website. This is distinct from sending the library to TABROOM.
Privacy links open an HTML page packaged with the extension. Imported library files are parsed locally. The extension does not request the contents of every saved page merely to validate or display the list.
11Analytics, advertising and external services
This build contains no advertising placement, affiliate-link rewriting, behavioral analytics, usage profiling or crash-report upload integration. It does not calculate a productivity score or sell browsing-related records.
There is no third-party SDK embedded for cloud storage, identity, payment, AI processing or remote typography. Interface assets and executable code are included in the package. System fonts may differ according to the operating system.
Chrome Web Store distribution and Chrome itself are separate services. Their installation, update, security and diagnostic practices are governed by their own settings and notices. TABROOM does not gain access to those services’ account records.
12Exported libraries and recovery files
Export library creates a JSON-based .tabroom file containing your rooms, notes and snapshot records. The data is readable without a password and can expose complete URLs. The file is intended as a personal backup or an intentional transfer.
If a stored library cannot be read normally, the recovery interface can offer the raw local library as a JSON download before resetting it. Such a file may contain private text, old entries or malformed records and should be handled cautiously.
Downloaded files are separate copies. Removing the extension, deleting a room or resetting local storage does not remove copies in Downloads, synced folders, email attachments, external drives or other people’s devices.
13Importing a library
An import is initiated through a file picker. TABROOM does not scan your disk. It reads the selected JSON file, checks the expected format, applies limits, validates web addresses and reconstructs the supported fields.
Imported rooms are added as independent copies with new local identifiers; existing rooms are not silently overwritten. The interface presents the number of rooms before adding them. An invalid or oversized import is rejected instead of replacing the current library.
You are responsible for checking whether an imported file contains links you trust before restoring them. Schema validation is not a promise that every destination is safe, appropriate, available or unchanged since the file was created.
14Retention and version history
Saved rooms do not expire on a timer in this version. Snapshots remain until you delete them or the room, reset the local library, remove the extension’s data, or lose the relevant browser profile storage.
Adding a snapshot retains earlier snapshots until the twelve-version limit is reached. The application does not silently delete the oldest version to make space. You must choose a version to remove or start another room.
Live lists and in-memory selection state are different from saved history. A browser restart or closing the interface can discard that transient state while leaving completed library writes intact. Keep an exported copy when a workspace is important.
15Deletion and your controls
You can delete a particular snapshot while retaining at least one in its room, delete a room and its snapshots, or use the Help panel’s erase control to remove all local room data and restore reports.
Deleting saved records does not close the corresponding websites or remove data held by those websites. It also does not clear Chrome history or cookies because TABROOM does not control those stores.
Uninstalling or clearing extension data is another browser-level control. Managed devices may have organization-specific retention and backup behavior. We cannot promise forensic erasure of storage media or removal from a backup made outside this extension.
16Failures and simultaneous views
Library changes carry a revision number. If another TABROOM view saved first, a stale change is rejected and you are asked to refresh instead of silently replacing the newer library. This is a data-integrity control, not remote synchronization.
Normal save operations wait for Chrome to acknowledge the storage write before reporting success. Quota errors and malformed libraries are reported. A success indicator is not a guarantee against later device failure, profile deletion or external modification.
The worker serializes library mutations and limits restores to one active operation. Abrupt process termination can still leave a partial set of browser tabs, which is why the restore journal and preview remain important.
17Security boundaries
Incoming file values and website titles are treated as text in the interface. Stored URLs are limited to supported web schemes. The extension declares a local-code content security policy and does not expose an externally connectable website API.
These design choices reduce some risks but do not make a Chrome profile a secure vault. A compromised operating system, malicious browser installation, exposed backup or careless export can still reveal a library.
Protect the device and account used to unlock it. Review destinations before restoring unfamiliar libraries. Never place passwords, recovery codes or other secrets into workspace notes simply because the extension stores them locally.
18Children and sensitive uses
TABROOM is a general-purpose organization tool and does not collect age, date of birth or parental information. It is not designed to identify children or provide an age-verification service.
Parents, guardians, schools and organizations should decide whether storing and exporting browsing-related information is suitable for their users. The absence of an extension server does not make every saved address appropriate to share.
Do not treat this tool as an approved record system for regulated, highly confidential or emergency work without your own review. The extension makes no certification about compliance with a particular institutional retention or security requirement.
19Changes to this notice
This notice is specific to the packaged behavior of version 1.0.0 and has an effective date of 8 September 2026. Future releases should update it when their data practices, capabilities or storage formats change.
Additional permissions, a future network service or account synchronization would require a fresh explanation and any browser approval that applies. This notice is not advance consent for undisclosed future collection.
You can inspect the policy packaged with your installed build and review store release information before updating. The present extension does not operate a mailing list or collect an email address to send policy-change announcements.
20Contact and support
The publisher is the developer identified on the verified Chrome Web Store listing for TABROOM. Use the support or developer-contact method displayed on that listing. This package does not contain an invented email address or an in-app support submission endpoint.
For troubleshooting, describe the browser version, operating system, action taken and visible error. Redact private tab titles and addresses before sending a screenshot or example library. A complete personal workspace is rarely needed to explain a problem.
If you voluntarily contact the publisher through another service, that service and the publisher’s support process handle the message separately. This local extension cannot retrieve your library remotely or delete copies already sent to someone else.