What MorrowTab stores, and where.

1. Who publishes MorrowTab

MorrowTab is published by FixQuotes. You can read about the publisher on the FixQuotes about page (opens in a new tab).

This policy covers the browser extension declared as MorrowTab — Boards, Search & Daily Quotes, a Manifest V3 extension for Chrome and Edge on Chromium 114 or newer, together with this website. MorrowTab is distributed through Microsoft Edge Add-ons (opens in a new tab) and the Chrome Web Store (opens in a new tab). This policy applies to both distributions.

Questions about this policy, and every other kind of support request, go through one route: the FixQuotes contact page for MorrowTab (opens in a new tab). There is no in-extension feedback form and no separate MorrowTab support address.

MorrowTab has no user account. There is nothing to register, nothing to sign in to, and no FixQuotes-side profile associated with your use of the extension.

2. What syncs through your browser

MorrowTab writes its shared data to chrome.storage.sync, the browser's own extension sync area. That data travels through the sync service of the browser profile you are signed into — Google's for Chrome, Microsoft's for Edge. FixQuotes operates no server for it and receives no copy of it.

Schema 2 separates your logical MorrowTab data from the way it is transported. Each browser profile creates a random actor identifier and publishes only its own compressed checkpoint. A checkpoint includes the logical records below plus counters and causal context needed to merge work from online and long-offline computers without one computer replacing another's copy.

The checkpoint is canonical JSON compressed with gzip, base64-encoded and divided into bounded Sync items when necessary. Its envelope declares compressed and uncompressed sizes and a SHA-256 digest; MorrowTab validates the complete item set, sizes, digest and decoded records before using it. This compression saves space. It is not encryption. Exact transport key names are intentionally not part of this policy because they carry no additional user data and may change without changing what is collected.

A normal save submits that profile's new chunks, schema marker and actor pointer in one multi-key browser Sync write. Superseded chunks owned by the same actor are removed after editing becomes idle; a failed cleanup backs off and retries. Another profile's actor checkpoint is never removed by that routine.

Your content materializes into five logical record shapes:

Plugin.meta

One record holding schemaVersion, boardOrder (the order your boards appear in), and a settings object: theme, density, openLinksInNewTab, layout, openSearchInNewTab, orderLinksByUsage, dailyQuoteMode and backgroundMode. These are single shared settings, not per-board ones.

Plugin.board.<id>

One record per board: id, name (the board name you typed), columnOrder, searchEngineIds, and lastSearchEngineId.

Plugin.column.<id>

One record per column: id, title (the column heading you typed), boardId, linkIds, and an optional color holding the accent you picked.

Plugin.link.<id>

One record per saved link: id, title, url, boardId, columnId, an optional newTab for a per-link "opens in" override, an optional autoCloseMinutes set to 5, 10, 15, 30, 60 or 120 only when newTab is true, and an optional clicks integer. The record format also allows an optional description of up to 200 characters, typed into the link editor's single-line Description field. Quick Save never writes a description or inactivity timeout.

About clicks: every left-click and middle-click on a saved link increments that link's usage value, and the new value is included in the synced logical record. This happens whether or not "Order links by most used" is switched on. It is a plain integer — there are no dates or times in the value itself — but schema 2 surrounds changes with pseudonymous actor and logical-counter metadata. The usage value syncs with the rest of your data and is included in an exported backup. "Reset usage" appears while usage ordering is enabled and clears every counter after confirmation.

Plugin.searchEngine.<id>

One record per extra search engine you add: id, name, urlTemplate (the address template containing {query}), boardId, visibleOnAllBoards, and the optional list of boards a search engine is shown on. The permanently-first "Browser default" option is built in and is not a stored record.

How conflicts are represented

Record presence and each top-level field have causal version metadata; shared settings are tracked separately per setting. The metadata consists of the random actor IDs, increasing logical counters and the counters a device had already observed. It contains no hardware serial number, operating system account, wall-clock activity time, IP address, tab history or browsing log.

Causally later changes replace values they observed. Concurrent changes to different records or fields both survive. Concurrent values for the same field remain represented and choose one deterministic result on every computer. A live edit concurrent with a delete is kept; a delete made after observing an edit wins, and an explicit later recreation wins again. Child ownership establishes membership, while board/column/link ordering arrays are only ordering hints, so an older ordering list cannot hide a newer item.

The current schema-2 release validates and automatically upgrades a complete schema-1 MorrowTab graph before publishing its first schema-2 checkpoint. Incomplete or invalid legacy data is unchanged and read-only. A newer-schema marker also makes schema-1 releases refuse writes, although every computer should still be updated to the current release before editing.

What is not in there

The configured autoCloseMinutes value is a setting, not activity history. Logical link records carry no wall-clock timestamp, tab ID, live deadline, visit history or browsing log. The text you type into the search box is never written to sync. Nothing about the pages you visit is written to sync unless you deliberately save that page as a link.

Sync is not end-to-end encrypted

Chrome's extension sync is not end-to-end encrypted, and whatever encryption your browser applies to synced data is your browser's feature, not MorrowTab's. MorrowTab adds no encryption of its own; gzip and base64 only make checkpoints smaller and transportable. Treat board names, column headings, link titles, saved addresses, custom search templates, random actor IDs and logical counters as non-confidential. If something should not sit in your browser profile's sync data, do not save it in MorrowTab.

There is no MorrowTab sync switch

MorrowTab has no in-extension control to turn sync on or off. It follows the sync settings of the browser profile itself. If your browser profile is not syncing extension data, MorrowTab's records simply stay in that profile's storage on that computer; if it is, they travel with the profile. That choice belongs to your browser's own settings, not to MorrowTab.

How much can go in

MorrowTab enforces its own ceilings before every write: at most 500 Sync transport items, 8 KB per item and 100 KB in total, within logical caps of 30 boards, 120 columns (40 per board), 250 links (200 per column) and 80 search engines (20 per board). Checkpoint chunks use a smaller internal target. Exceeding any limit means the write is refused, not truncated.

Zero records can mean a genuinely new profile or Sync that has not hydrated yet. Missing chunks, partial legacy records, corrupt compressed bytes and size/hash mismatches also remain read-only. None of those states is treated as permission to publish the sample board or delete arrived data. A new user can explicitly choose Start with sample board on the welcome page; a returning user can choose Use my synced boards, which writes nothing while Sync catches up.

3. What stays on this computer

Sixteen records live in chrome.storage.local. They belong to one browser profile on one computer. Their local copies do not appear in exported backups and none is written to web localStorage. The schema-2 actor identifier is also included as pseudonymous metadata in the checkpoint that this profile publishes; the other fifteen values are not synced.

• A persistent schema-2 actor identifier — a random installation ID used with logical counters so this profile can own its checkpoint and merge causally. It is not derived from hardware, your browser account or personal information.
• Plugin.localActiveBoardId — which board this computer is currently showing.
• Plugin.localQuickSaveTarget — the board and column Quick Save last saved to, as { boardId, columnId }.
• Plugin.localSearchHistory — the search text you submitted, kept per search engine so it can be offered back as autocomplete. Each entry is normalized and capped at 512 characters, de-duplicated case-insensitively, and limited to 50 entries per engine. There is no time-based expiry; entries for engines you delete are dropped on the next load.
• Plugin.localSearchHistoryEnabled — whether new queries are recorded. It defaults to on, and the "Save search suggestions" toggle in Settings controls it.
• Plugin.localBackgroundImage — a background image you uploaded, downscaled to a 2560 px maximum side and re-encoded as a WebP data URL. The original file is never uploaded anywhere and never enters sync.
• Plugin.localPexelsNatureBackground — the nature photo cached while that feature is enabled, stored as a verified WebP data URL alongside the SHA-256 digest it is re-checked against on every read.
• Plugin.localDailyQuote — the cached quote of the day, so the page can render before any request is made.
• Plugin.localLastGoodSnapshot — a rolling copy of the last cleanly-loaded synced records, kept so a damaged sync state can be recognized.
• Plugin.localPreReplaceSnapshot — a copy of the synced records a backup import replaced, kept so an unwanted import stays reversible.
• Plugin.managedTabs.failClosed — a temporary Boolean safety marker written only if the background worker cannot safely persist or cancel an automatic-close deadline. It contains no tab ID, hostname, URL or timer.
• Plugin.localAutoClosePermissionPrompted — a Boolean remembering that this installation has already offered the optional auto-close permission, so a refusal does not trigger another automatic prompt on later clicks, new tabs or reloads. It contains no tab ID, hostname, URL or browsing history and is not itself a permission grant.
• Plugin.localFaviconCache — up to 128 hostname-keyed icon entries within 256 KiB, containing verified small PNG images and expiry metadata. Successful icons stay fresh for seven days and can be used stale for at most 30 days. Explicit no-icon or blocked results are remembered for 24 hours. Transport failures start with a five-minute retry delay and back off to at most 24 hours, with a shared cooldown to reduce requests during outages.
• Plugin.localFaviconDownloadsEnabled — whether this computer downloads missing or stale website icons. It defaults to on. Turning it off stops new requests without deleting the reusable icon cache.
• Plugin.localCalendarCache — for each calendar feed a calendar board subscribes to, the time it was last downloaded, whether that worked, the last error, and the events for the coming weeks (titles, times, locations and descriptions). It exists only on a computer that has downloaded a feed, and an entry is deleted as soon as no board references that feed any more.
• Plugin.localCalendarView — which calendars you have hidden on a calendar board and whether it shows the agenda, week or month layout. Written only when you change one of them; it contains the hidden calendars' feed addresses and nothing else.

All sixteen are ordinary extension storage values held in plain text inside your browser profile directory. MorrowTab does not encrypt them, and anyone with access to that profile on that computer can read them.

Plugin.managedTabs (session only)

If at least one saved link has an inactivity timeout and MorrowTab opens it, the background worker writes one temporary registry to chrome.storage.session. It is keyed by the managed tab ID; each entry contains that tab's window ID, the original hostname with a leading www. removed, the selected number of minutes, and either the time it entered the background or null while its countdown is stopped. The single alarm name Plugin.managedTabs.autoClose carries no additional data.

This registry exists only so a suspended Manifest V3 worker can safely resume the current browser session. It is not written to Sync or local storage, is not exported, and is cleared when the browser session ends or the extension is reloaded, disabled, removed or updated. MorrowTab does not rebuild it from saved links, so no old tab is closed after a restart.

If the Boolean fail-closed marker is present when a background worker starts, automatic closing stays disabled while the worker removes the session registry and its alarm. Only after both are cleared does it remove the marker and allow newly opened managed tabs. The marker is never synced or exported.

4. Every network request MorrowTab can make

The extension declares three fixed hosts plus one optional, per-site permission that two features use, each for a site you name yourself. The table below is the complete list of requests the code can issue.

Search and local icon fallbacks

Searching. "Browser default" hands your query to the browser itself, which sends it to whichever provider your profile is configured to use. A custom engine is an ordinary navigation to your own template with the query inserted. Either way the search goes straight to the engine, exactly as if you had typed it in the address bar. It never passes through a FixQuotes server: the quote, nature-background and favicon endpoints have nothing to do with search.

Local fallbacks. A working icon bundled inside the extension needs no remote lookup. Otherwise a cached downloaded icon can be used, while the browser's own chrome-extension://…/_favicon/ result or a two-letter badge provides a fallback. Chromium may return a generic globe on a computer that has not seen that site; this does not suppress an eligible download while the setting is enabled.

5. Each permission, and why it is there

MorrowTab runs an automatic content script only on top-level HTTPS Zoom recording pages matching https://*.zoom.us/rec/*. It reads video source addresses and adds a dismissible download overlay that updates as the player loads. Closing it stops watching the player; refresh the recording page to show it again. There is no Zoom context-menu action. Addresses stay on that page and are not saved to Sync. Saving a video uses the Zoom document's normal referrer policy and browser session context. MorrowTab declares no tabs permission. Choosing the Google Maps context-menu item provides the selected text to MorrowTab and sends it to Google as a search in a new tab. Link auto-close uses the optional webNavigation permission to receive navigation events, but the worker considers only tab IDs that MorrowTab itself created and compares only their top-level hostname. It stores no navigation log.

The extension's own Content-Security-Policy is script-src 'self', style-src 'self', object-src 'none', base-uri 'none', with images restricted to the extension itself, data: URLs, fixquotes.com and images.pexels.com. No script is ever loaded or executed from a remote source.

6. What a backup contains

"Export backup" in Settings writes an optional disaster-recovery or point-in-time file named morrowtab-backup-YYYY-MM-DD.json to your own computer through the browser's normal download. It is never uploaded anywhere. It has exactly four top-level fields:

• application — the string "MorrowTab".
• schemaVersion — 2.
• exportedAt — the timestamp of the export.
• records — the materialized logical record set described in section 2: meta and settings, boards, columns, links (including each link's clicks count and configured autoCloseMinutes value), and search engines.

The file is plain text. It is not encrypted and it cannot be password-protected. Anyone who opens it can read your board names, link titles, saved addresses and search templates, so store it the way you would store any other file containing that information.

A backup is not required for normal schema-2 convergence between computers. It deliberately excludes actor IDs, logical clocks, causal alternatives, delete markers, checkpoint compression envelopes and chunks, plus every one of the sixteen device-local records:

• the schema-2 actor identity used by this browser profile;
• the cached calendar feeds and their downloaded events (the feed addresses themselves are part of the synced board and therefore of the backup);
• which calendars are hidden and which calendar layout is shown;
• your saved search suggestions and the "Save search suggestions" preference;
• your uploaded background image, and the cached nature photo — no image bytes are ever exported;
• the cached daily quote;
• the board this computer is showing, and the remembered Quick Save destination;
• both local safety snapshots;
• the managed-tab fail-closed safety marker and the auto-close permission-prompt marker.
• the downloaded favicon cache, including hostname metadata, and its download preference.

The session-only Plugin.managedTabs registry and its live countdowns are also excluded.

Restoring a full backup replaces everything currently synced, after a confirmation. Before it does, the records it is about to replace are copied to Plugin.localPreReplaceSnapshot on that computer, and "Restore pre-import copy…" brings them back. A valid schema-1 MorrowTab backup is fully validated and upgraded to schema 2 during import. Importing a single exported column is different: it adds that column to the current board rather than replacing anything.

Two other files can be produced on request, and both are written locally by the browser, never uploaded: a single-column export, and — from the recovery view — a raw, unrepaired diagnostic snapshot of the synced records. The diagnostic snapshot contains your data verbatim, so treat it as you would a backup if you ever send it anywhere.

7. No analytics, telemetry or trackers

There is no analytics library, no telemetry, no beacon, no WebSocket, no XMLHttpRequest, no EventSource and no third-party script anywhere in the extension. There is no advertising tracker and no advertising identifier. Nothing measures how you use MorrowTab and reports it anywhere.

There is no remote code of any kind: everything MorrowTab runs is shipped inside the extension package and is loaded from it. Apart from the requests listed in section 4, resource loading reads packaged extension files or the browser's native favicon endpoint. Downloaded website icons are normalized image data, never executable code.

The synced board graph is stored by the browser, not uploaded to a MorrowTab account or board database. Website-icon lookup is a separate functional request that discloses an eligible saved hostname to FixQuotes and causes FixQuotes to contact that public website for its icon. It does not send your complete saved address, title, board name or search text.

This website. These pages are static files. They run no analytics, set no cookies, embed no third-party scripts and show no consent banner — which is why you have not been asked to dismiss one. As with any website, the host that serves these pages may keep its own server logs, which is outside MorrowTab's control.

8. Credits and third-party material

Bundled brand icons

MorrowTab ships 49 brand icons covering 63 domains inside the extension package. They are a generated subset of the theSVG Color icon collection (also called The SVG Company Icon Set), distributed as @iconify-json/thesvg-color, collection author thesvg.org, under the MIT license, Copyright © 2025 thesvg.org. The full license text is reproduced in the extension's third-party notices.

The icon data is converted to self-contained SVG files during development. MorrowTab includes no Iconify runtime and never contacts an Iconify API or any other third-party icon service.

Fallback site icons

For a saved link without a working bundled icon, MorrowTab can download a verified small PNG through FixQuotes and cache it on this computer. FixQuotes fetches public website artwork directly, not through a third-party favicon provider. These runtime images are not part of the bundled MIT icon collection. Site names and logos remain the property of their respective owners and their display does not imply endorsement. Native browser icons or initials remain available when no downloaded icon can be obtained.

Quotes

The Quote of the Day comes from FixQuotes (opens in a new tab). A catalog of 150 quotes ships inside the extension, so the quote area renders before — and without — any network access; the daily refresh from the FixQuotes feed then runs at most once per local day unless the quote is set to Off.

Photographs

The switchable daily nature photographs come from Pexels (opens in a new tab). They are downloaded at the moment they are used and are not bundled with the extension. Attribution is required and is shown in the product: MorrowTab rejects the photo metadata unless it carries the exact credit Photo by <photographer> on Pexels pointing at Pexels' own pages. MorrowTab holds no Pexels API key.

Trademarks

Product names and logos are the trademarks of their respective owners. Their inclusion in the bundled icon set does not imply any partnership with, sponsorship by, or endorsement from those companies.

9. Deleting your data

These are the controls MorrowTab actually gives you:

• Clear saved suggestions (Settings) — appears while saving suggestions is on, asks for confirmation, then permanently removes the saved search text from this computer. It does not change whether future searches are recorded.
• Save search suggestions (Settings) — switch it off and existing suggestions are kept but nothing new is recorded.
• Remove image (Settings) — removes the background image you uploaded from this computer.
• Daily Pexels nature (Settings) — switching it off stops all further requests for nature metadata and photos. The separate website-icon setting can still use api.fixquotes.com.
• Download website icons (Settings) — switching it off stops new favicon requests on this computer. Cached icons remain available; the preference and cache do not sync and are excluded from backups.
• Reset usage (Settings) — appears while usage ordering is on and clears every per-link click count after confirmation.
• Auto-close (link editor) — setting a link back to Off removes its synced timeout. Closing the tab, ending the browser session, reloading the extension, or revoking its optional navigation permission removes the corresponding live tracking state. The local permission-prompt marker remains, preventing repeated automatic prompts; choosing Enable auto-close in the notice or saving an enabled timeout explicitly asks again when access is missing.
• Deleting a link, column or board — deleting a column also removes its links, and each deletion leaves a six-second Undo in the toast.
• Import backup… (Settings) — replaces everything currently synced, after confirmation, while keeping a restorable copy of what it replaced on this computer.

Schema 2 represents a deletion with causal metadata so a stale offline checkpoint cannot mistake an intentional deletion for missing data. The marker carries actor/counter context, not a new browsing record. A current causal tombstone can retain the deleted record's former fields, and a profile's pointer may retain one prior checkpoint while the Sync budget permits it. Unreferenced superseded chunks can also remain briefly while idle cleanup is pending, or longer if the browser rejects cleanup until a later retry. Those values are not shown in the board or included in a normal exported backup, but they can remain inside compressed Sync transport data; older profiles can retain them too until they return and publish again. Physical retention inside the browser's sync service is controlled by Google or Microsoft, not FixQuotes.

10. Changes to this policy

This policy describes the current MorrowTab release. If a future release changes what is stored, what is requested, or which permissions are declared, this page will be updated before that release is published, and the effective date at the top will change with it.

Material changes will be summarized on the changelog alongside the release that introduced them, so you can see what changed and when. The version of this policy in force is always the one on this page.

If anything here is unclear, or you believe something on this page does not match what the extension does, please tell us through the FixQuotes contact page for MorrowTab (opens in a new tab).

Effective September 2, 2026