DRIFTBOARD

01. Purpose and scope

This policy explains how Driftboard 1.0.0 handles information when it replaces the browser new-tab page with a spatial map of your currently open tabs. It applies only to the Driftboard extension code included in this release.

Driftboard is designed as a local browser workspace. Its purpose is to visualize tab metadata, let you reposition tab cards, switch to a tab, pin or unpin a tab, and optionally restore an item from the browser's recently closed list.

This policy distinguishes information that is merely read into memory for the current view from information that is written to local extension storage. That distinction is important because the board must temporarily know tab titles and URLs to draw useful cards, but it does not need to upload them anywhere.

02. Plain-language summary

• Open-tab titles, URLs, pinned state, active state, and audible state are read from Chrome so the board can represent the tabs you already have open.
• Spatial positions that you create by dragging, settling, or scattering cards are saved with chrome.storage.local so the layout can survive a reload.
• A small recently-closed list is requested from Chrome Sessions when the board loads so the extension can draw restorable ghost cards.
• No webpage body text, form values, cookies, passwords, page DOM, screenshots, or keystrokes are collected by Driftboard.
• No information is transmitted by Driftboard to the developer or to a third-party service.

If you are comfortable with a local tab organizer knowing the metadata Chrome already exposes for the tabs it manages, Driftboard is intended to keep that processing on your device.

03. Information read from open tabs

When the Driftboard new-tab page is open, the extension calls the Chrome Tabs API for tabs in the current browser window. The response can include a tab identifier, URL, page title, whether the tab is pinned, whether it is active, and whether it is currently audible.

These fields are used to build a card label, determine a grouping domain, render the pinned/current/audio state, and route a user click back to the correct tab. Tab identifiers are treated as transient browser handles and are not deliberately persisted by Driftboard.

A URL can reveal browsing activity. Driftboard therefore treats URLs as local workspace data. The extension does not send URLs off-device, does not add them to an analytics record, and does not create a browsing-history database.

The current implementation filters out its own Driftboard extension page from the spatial node list so the board represents the other tabs you can return to rather than representing itself as a work item.

04. Information read from recently closed sessions

Driftboard requests up to a small number of recently closed session entries through chrome.sessions.getRecentlyClosed. Chrome may return a closed tab title, URL, and a session identifier, or information about a recently closed window.

The extension uses that response to draw dashed “recently closed” ghost cards near the lower edge of the board. A click on a ghost asks Chrome to restore the corresponding session identifier.

Recently closed titles, URLs, and session identifiers are held in the new-tab page memory for the current page lifetime. Driftboard does not write its own durable copy of the recently closed list to chrome.storage.local.

The authoritative recently closed history remains Chrome's own session data. Clearing or changing that browser history is controlled by Chrome, not by Driftboard.

05. Information stored locally

Driftboard persists one category of product state: spatial card positions. The stored object maps a tab URL to an x and y coordinate representing where that URL's card was last placed on the board.

Coordinates are written after user interactions such as dragging a card, pressing Settle, or pressing Scatter. They are rounded numeric values used only to reconstruct a useful spatial layout on the next load.

Because the URL is the position key, the local position object can indirectly reflect sites that have been arranged in Driftboard. This file remains inside Chrome extension local storage and is not uploaded by the extension.

When a later position save occurs, Driftboard writes the current set of mapped tab positions as a whole. A position for a closed tab can remain until a later save replaces the object, until extension data is cleared, or until the extension is uninstalled.

06. What Driftboard does not collect

• No webpage HTML or DOM content.
• No text selected or typed into webpages.
• No form submissions, passwords, payment information, or authentication tokens.
• No cookies, localStorage belonging to websites, or browser cache contents.
• No download history, bookmark collection, contact list, or email account data.
• No device microphone, camera, geolocation, clipboard, or filesystem contents.
• No advertising identifiers or cross-site tracking identifiers.

Driftboard has no content script and declares no host permissions. It therefore does not inject code into arbitrary webpages to inspect page contents.

07. Permissions: tabs

The tabs permission is required because the product's single purpose is to represent and control browser tabs. It is used to query current-window tab metadata, activate a tab when you click its card, and change the pinned state when you double-click a card.

The same permission lets the board react when tabs are created, updated, or removed so cards can stay synchronized with the actual browser window rather than showing stale invented state.

Driftboard does not use the permission as a pretext to transmit tab metadata. All tab handling occurs inside the extension and Chrome API boundary on the device.

08. Permissions: storage

The storage permission gives Driftboard access to Chrome extension storage. Version 1.0.0 uses chrome.storage.local for the positions object described above.

Driftboard does not use chrome.storage.sync, so the extension does not intentionally ask Chrome to synchronize board positions to another signed-in browser profile.

Storage is product state rather than analytics. There is no event stream, user profile, engagement counter, or developer-side database receiving this information.

09. Permissions: sessions

The sessions permission is used only to ask Chrome for a short recently closed list and to restore an entry when you choose a ghost card.

Driftboard does not maintain a second permanent session-history system. The session ID supplied by Chrome is used as a restore handle and is kept in page memory for the current board view.

If the Sessions API is unavailable or returns no usable entries, the board continues to function without recently closed ghosts.

10. No host permissions or content scripts

The manifest for Driftboard 1.0.0 contains no host_permissions field and registers no content scripts. The extension does not request blanket access such as <all_urls>.

A URL visible through the Tabs API is metadata about a tab, not permission to inject into the corresponding webpage. Driftboard uses that distinction deliberately to keep the product narrower.

The visual board is rendered in the extension's own new-tab page using local HTML, CSS, JavaScript, and Canvas code packaged with the extension.

11. Network behavior and remote code

Driftboard 1.0.0 contains no fetch, XMLHttpRequest, WebSocket, beacon, analytics SDK, remote font import, or remote JavaScript loader used by the product.

The extension does not call a developer API and does not require an internet connection for its own interface. Naturally, the webpages represented by your tabs can use their own networks independently of Driftboard.

All executable extension code is packaged locally. Driftboard does not download executable code, evaluate server-supplied scripts, or implement a remote-code update channel outside the Chrome Web Store update mechanism.

12. Analytics, telemetry, and crash reporting

Driftboard does not include product analytics, behavioral telemetry, fingerprinting, session replay, or a developer-operated crash-report collector.

The extension itself does not send interaction counts for Settle, Scatter, Freeze, drag, pin, restore, or tab switching. These interactions remain local browser behavior.

Chrome or the operating system may maintain its own browser diagnostics under their separate policies. That browser-level processing is not controlled by Driftboard and is not data received by the Driftboard developer through this extension.

13. Advertising and sale of data

Driftboard contains no advertisements and no advertising SDK. It does not build interest segments, perform retargeting, or share browsing metadata with ad networks.

The developer does not sell or rent information handled by Driftboard. There is no data broker integration and no monetization path based on tab URLs, titles, session history, or spatial positions.

The extension does not use local board state to influence unrelated advertising displayed by websites.

14. Third parties

Version 1.0.0 does not integrate a third-party cloud processor for extension data. There are therefore no analytics, storage, AI, advertising, or notification vendors receiving Driftboard product data from the extension.

The Chrome APIs used by Driftboard are supplied by the browser platform. Your relationship with Chrome and any websites you open is governed by their own terms and privacy practices.

A restored session opens the same page Chrome restores. Once that page loads, its network and privacy behavior belongs to that site and the browser, not to Driftboard.

15. Retention

Transient tab metadata and recently closed session data normally disappear from Driftboard memory when the new-tab page is closed or reloaded.

Spatial positions persist in chrome.storage.local until a later position save replaces them, Chrome clears the extension's site data, the user removes the extension, or the browser otherwise removes the extension storage area.

Driftboard does not apply a server-side retention period because there is no Driftboard server receiving this information.

16. Deletion and reset

Uninstalling Driftboard through Chrome removes the extension and, under normal Chrome behavior, its local extension storage. Users can also clear extension data through browser controls where available.

Because there is no developer cloud account, there is no separate remote account-deletion request necessary for Driftboard data.

Closing browser tabs or clearing Chrome session history affects the source data available through the Tabs and Sessions APIs, while clearing Driftboard local storage affects saved spatial positions.

17. Security

Driftboard minimizes its attack surface by avoiding remote code, host permissions, content scripts, external libraries, and network transmission of product data.

Local extension storage is protected by the security boundary of the browser profile, but Driftboard does not claim that local browser files are encrypted by the extension itself. Anyone with sufficient access to your browser profile or device may be able to inspect local browser data.

Users should apply normal device protections such as operating-system accounts, screen locks, browser updates, and appropriate profile security.

18. User controls and intentional actions

The board never pins, activates, moves, or restores a tab merely because it is being rendered. Those changes are tied to user interactions: clicking a live card activates it, double-clicking toggles its pinned state, and clicking a ghost asks Chrome to restore it.

Settle and Scatter change only the local card coordinates, not the URLs or contents of your webpages. Freeze pauses the board physics without changing browser tabs.

You can choose not to interact with any card. Simply opening Driftboard reads the current metadata required to draw the board, but tab-modifying actions remain user initiated.

19. Children

Driftboard is a general browser utility and is not designed or marketed specifically for children under 13 or the equivalent minimum age in a user's jurisdiction.

The extension does not knowingly create a developer-side profile for children or anyone else because it has no account system or data collection server.

Parents and guardians should use browser and operating-system controls appropriate to the device and websites a child may access.

20. International transfers

Driftboard does not intentionally transfer extension data across national borders because the extension does not send its product data to a remote service.

Websites open in browser tabs can independently transmit data internationally. That activity is outside Driftboard's code and outside this policy's description of the extension's own processing.

21. Legal requests and disclosure

Because Driftboard does not maintain a developer database of tab metadata or positions, the developer normally has no such extension data to search, export, or disclose in response to a request.

Information that exists solely on a user's device remains subject to the device owner, browser provider, operating system, and applicable law. This policy does not alter lawful obligations those parties may have.

22. Policy changes

This policy may be updated when Driftboard behavior, permissions, storage, or legal requirements materially change. A revised policy should describe the behavior of the corresponding extension version rather than silently expanding collection.

If a future version introduces network transmission, analytics, new permissions, or materially different retention, the policy will be revised to explain those changes before or with that release.

The effective date at the top of this document indicates the policy version applicable to Driftboard 1.0.0.

23. Contact and verification

Questions about this policy should be sent through the developer contact method displayed on the Chrome Web Store listing. Using the Store listing avoids publishing an invented or stale address in this standalone file.

Users and reviewers can verify the stated behavior against the extension package: the manifest lists tabs, storage, and sessions; the new-tab code uses those APIs; and the package contains no declared host permissions or remote runtime dependency.