tabplate — Privacy first
Updated: 17 October 2026. Applies to the local Chrome extension distributed with this file.
Your data is not a product. We don’t sell your data. We don’t store it on our servers.
What stays on your device
Your local profile name and avatar, boards, groups, links, notes, tasks, uploaded icons, preferences, trash and automatic snapshots are stored locally in this browser profile. The application uses IndexedDB, browser-local storage and a local icon cache limited to 256 entries and 8 MiB of cached response data. Backup history has its own 40 MiB target with a newest-copy exception; current data, the previous recovery record and damaged records are separate. These are component budgets, not a hard limit on the browser profile. Large-state validation runs in a temporary local worker; no processing service is contacted. Separate display-only startup snapshots of the last board and global Favorites are kept locally to show them before repository verification finishes. Each model snapshot is limited to 512 KiB and 320 preview items, and each matching display tree to 512 KiB and 48 link previews; they are valid for up to one day. The open section is remembered in per-tab session storage. These snapshots never replace the database or repair damaged data. It does not use Chrome Sync, account-based cloud storage or a tabplate data server. Exported backups and diagnostics are files saved at your request; tabplate does not upload them. Standard diagnostics contain technical metadata and counts, not your saved URLs, titles, notes or profile. Recovery backups contain your full saved content and should be shared only deliberately. The browser profile, device backups and files you export remain under your control.
No advertising or tracking
tabplate includes no analytics SDK, ad tracker, advertising identifier, telemetry endpoint, account system or data-sale integration. We do not sell, rent or share your saved content or browsing history for advertising.
Magic and browser access
History and open-tab permissions are optional. Opening the onboarding offer does not request access or read history. Starting a history or tab feature asks Chrome for permission if needed. When an empty board is visible and history access was already granted, Lucky checks recent frequent sites locally to decide whether it can run. This check is bounded to 5,000 history results and 24 ranked sites, is throttled for 30 seconds, and retains only an availability count in tab memory. It does not import sites until you click Lucky. Lucky uses a 90-day window and the same Chrome frequency metric as Magic; eligibility requires six different sites with a visitCount of at least two. Chrome visitCount can include older visits to a recently visited page; it is not an exact count of visits within the window. Magic runs locally using domains, titles and local rules; it does not call an AI service or send history to a server. From history, it saves selected root site addresses with neutral site labels and the resulting groups. Private page paths, queries and raw history records are not saved in tabplate. Open-tab imports and links you add may retain their full URLs and titles locally.
The optional right-side tab panel mirrors web tabs from the same browser window only. After you explicitly grant tab access, it updates from Chrome tab events while this tabplate page is visible; it does not poll. When the page becomes hidden, tab listeners and temporary tab metadata are released. This mirror is not written to the database or startup snapshots. Dragging a tab into a group saves that selected URL and title locally and keeps the original browser tab open. Icons in this panel mirror Chrome’s local favicon store or bounded in-memory image data provided by Chrome for an open tab, without direct website requests. Favicon addresses and image data stay in the visible page’s temporary mirror and are not stored with imported links. This browser-tab mirror is independent of the icon display preference for saved links.
Icons and network connections
Website icon fetching is off by default, including when upgrading older preferences that predate this choice. Browser-provided favicons, built-in icons and uploaded images remain available. Chrome’s own favicon handling is a browser feature; this policy describes tabplate’s application code, not Chrome’s independent services or settings.
If you explicitly enable “Fetch icons from websites,” Chrome asks for optional website access. tabplate can then request the root `/favicon.ico`, root page metadata, web-app manifest icons, conventional icon paths, and discovered icon/logo files from saved sites and their asset servers. Those servers can see normal connection information, including your IP address and the requested asset address. Requests omit credentials/cookies and referrers. Private paths and query strings from your saved page URLs are not sent to discover an icon. Asset URLs returned by a website can have their own paths or parameters.
Turning the option off blocks further icon-fetch work, aborts in-flight application fetches, clears the local fetched-icon cache, and asks Chrome to remove optional website access. A request already received by a server cannot be undone. No background history listener or site-monitoring content script runs.
Clicking a saved link opens the destination in your browser. Its own privacy policy and your browser settings then apply.
Control and transparency
You can export boards or workspaces, remove items, manage local snapshots and trash, disable automatic icons, and revoke history/tab access through tabplate or Chrome’s extension controls. Removing an item may leave it in local trash and snapshots until those are cleared or expire. Clearing extension data does not erase backup files you saved separately.
The included source describes the shipped behavior. This statement covers tabplate’s own application code. Chrome, your operating system, destination websites and optional icon servers have their own privacy behavior.
Chrome API references: optional permissions, browser favicons.
Chrome Web Store Limited Use
Tabplate uses information obtained through Chrome and Google APIs in accordance with the Chrome Web Store User Data Policy, including its Limited Use requirements. This information is used only for the disclosed organization, tab-saving and local icon features. It is not sold, used for advertising, or used to assess creditworthiness.
Contact
For privacy and support requests: support@tabplate.com.
About this website
This landing page has no analytics, advertising scripts, account forms or tracking cookies in its application code. Its host may process standard request information to serve and secure the website. A private preview may require the hosting provider’s sign-in. The extension and this website are separate: visiting this page does not give it access to your tabs or history.
Contact
For support or privacy questions, email support@tabplate.com. You can also check the help section.
If you contact us by email, your address and the information you choose to send are handled by email providers so we can reply. Please avoid sending passwords or unredacted backup files.
Read the privacy and permissions guide · Back up and export your content