1. Purpose
TossTabs is a new-tab browser organization tool. It displays the tabs currently open in the user's browser in a single workspace, grouped by domain. After the user takes an explicit action, TossTabs can save and close ordinary webpage tabs and organize them into a short-term action queue with a 72-hour active window. Users can reopen, switch to, deduplicate, or delete those items.
Reading sources, to-dos, and notes are used only to handle short-term work directly related to those browser tabs. They are not standalone services.
2. Data handled by TossTabs
TossTabs may handle the following data within the user's Chrome profile:
- Open-tab metadata required for tab management, including title, URL, domain, tab ID, window ID, and active state.
- Saved-tab records, including title, URL, category, saved time, expiry time, and completion or dismissal state.
- Public Reading List records, including source name, title, URL, excerpt or summary, category, publication time, and read or dismissal state.
- Public reading-source names and URLs added by the user.
- User-created categories, to-dos, and notes related to short-term browser work.
- Extension preferences, including theme, reading preferences, model gateway URL, model name, and an optional model API key.
- Local operational status, such as the time and result of the most recent capture, cleanup, or reading refresh.
TossTabs does not read the body content of open browser tabs, inject scripts into websites, or intentionally collect a user's name, email address, precise location, health information, financial or payment information, or personal communications.
3. Local storage
Saved tabs, categories, public reading sources and reading records, to-dos, notes, preferences, non-sensitive model settings, and local operational status are stored in chrome.storage.local within the current Chrome profile.
A user-provided model API key is stored only in chrome.storage.session. It is not written permanently to local storage and is cleared when Chrome restarts or when the extension is reloaded or updated.
TossTabs does not operate an account database or developer-controlled synchronization service for this information. Users can remove individual items, clear the extension's data, or uninstall TossTabs to delete locally stored information. Chrome-local extension storage is not a cloud backup and may be lost if the Chrome profile is removed or corrupted.
4. Optional AI connection
AI features are optional. They operate only after the user enters model settings, grants Chrome access to the specific model-gateway origin, and requests or enables the relevant feature.
When the user enables AI organization, TossTabs sends the following data directly to the OpenAI-compatible model gateway selected by the user:
- For saved-tab classification: a limited set of saved-tab identifiers, titles, domains, and URLs.
- For Reading List filtering and summarization: a limited set of public-source candidate data, which may include identifiers, source names, titles, URLs, publication dates, and excerpts.
- The selected model name and, if required, the API key as an authentication credential.
To-dos and notes are not sent to the model gateway. The selected gateway provider processes requests under its own privacy policy and terms. TossTabs' developer does not receive those model requests or responses unless the user independently chooses a gateway operated by the developer; this policy would be updated before TossTabs offered such a service.
5. Public reading sources and network requests
TossTabs can retrieve data from public RSS, Atom, JSON feeds, websites, and public newsletter archives that the user chooses to add. It may also retrieve optional public Follow Builders JSON data from raw.githubusercontent.com. If the fixed public SVPG RSS feed cannot be accessed directly by the extension background process, TossTabs may use api.rss2json.com as a fallback parser for that feed only.
For other public reading sources and user-selected model gateways, TossTabs requests Chrome access only after the user adds or configures a specific origin. Remote sources and model services must use HTTPS. HTTP access is permitted only for a model service running on the user's own device at localhost or 127.0.0.1.
Site icons are loaded through Chrome Manifest V3's local _favicon API and Chrome's local favicon cache. TossTabs does not send tab domains or URLs to a third-party favicon service.
Public-source operators, GitHub, rss2json, and any user-selected model-gateway provider may receive ordinary request metadata and process it under their own privacy policies.
6. Retention and deletion
Unprocessed saved tabs, unread Reading List items, and unfinished to-dos have a 72-hour active window. After they reach the end of that window, TossTabs physically removes them from local extension storage during its cleanup process. Cleanup runs hourly and also runs when the extension or dashboard starts.
Completed, dismissed, or manually deleted items are handled according to the user's action. Notes remain until the user deletes them, clears the extension's data, or uninstalls TossTabs.
7. Sale, advertising, analytics, and human access
TossTabs contains no advertising or analytics SDK. The developer does not sell user data, use it for personalized advertising, use it for credit or lending decisions, or transfer it for purposes unrelated to TossTabs' disclosed single purpose.
Because core browser-work data remains within the user's Chrome profile and optional AI requests go directly to the gateway selected by the user, the developer does not routinely have human access to that data.
8. Security
Remote public sources and user-selected remote model gateways must use HTTPS. Local model gateways may use HTTP only on the user's own device. Users should connect only to providers they trust and should review each provider's security, data-retention, and privacy terms.
9. Chrome Web Store Limited Use
TossTabs' use of information received from Chrome APIs complies with the Chrome Web Store User Data Policy, including the Limited Use requirements. Information obtained through Chrome permissions is used only to provide or improve the extension's disclosed browser-tab organization purpose.
10. Changes to this policy
If TossTabs changes how it handles user data, this policy and the relevant in-product and Chrome Web Store disclosures will be updated before the changed behavior is released. Where required, users will be asked for affirmative consent.
11. Contact
For privacy questions or deletion assistance, email yxxuziva@gmail.com. Because most TossTabs data is stored only in the user's Chrome profile, the developer generally cannot access or delete it remotely. Users can delete individual items in TossTabs, clear the extension's data, or uninstall the extension.