1. Scope and effective date
This Privacy Policy applies to Traceboard version 1.0.0 and to the local data processing performed by the Traceboard Chrome extension. It describes the production behavior of the extension as distributed through its official store listing.
The policy is effective September 4, 2026. References to “Traceboard,” “the extension,” “we,” or “our” in this document refer to the Traceboard extension and its developer. References to “you” refer to the person using the extension in a Chrome or Chromium-based browser profile.
Traceboard is an extension that draws relationships between pages visited in tabs. The extension runs inside your browser profile. It does not require you to register an account or provide a name, email address, password, profile photograph, payment method, or other account credential.
2. Single purpose of Traceboard
Traceboard’s single purpose is to provide a local visual map of tab branches and page navigations so that you can understand and revisit the path of a browsing session. A page can appear as a node, and a navigation or tab opener relationship can appear as a connection between nodes.
The extension uses page addresses and titles because a visual trail would not be useful if every node were anonymous. It uses tab identifiers and opener relationships because those fields let it distinguish a continuation in one tab from a new branch opened from another tab.
Traceboard is not intended to inspect the body of a webpage, classify the subject of a page, profile your interests, create an advertising audience, rank sites, or infer sensitive attributes. Its data model is deliberately narrow and oriented around navigation structure.
The board lets you pan and zoom the graph, fit a large trail to the visible canvas, focus the path leading to one node, pin a useful node, add a short private note, reopen a recorded page, and clear the local trail.
3. Data Traceboard processes
When you browse with Traceboard installed, the extension processes a limited set of browser tab metadata needed to build the trail. Depending on the event, this can include the following fields.
| Data | Why it is used | Where it is kept |
|---|---|---|
| Page URL | Identifies the page represented by a node and lets you reopen that page. | chrome.storage.local |
| Page title | Provides a readable label for the node. | chrome.storage.local |
| Tab identifier | Associates navigation events with the current tab while building the trail. | Local trail record and temporary session map |
| Opener relationship | Connects a newly opened tab to the node from which it was opened. | chrome.storage.session while needed; relationship becomes the stored parent node ID |
| Creation, last-seen, and close timestamps | Orders the trail and distinguishes currently available and closed-tab nodes. | chrome.storage.local |
| Pin state | Remembers nodes you marked as useful. | chrome.storage.local |
| Private note | Stores the short note you voluntarily type into the node inspector. | chrome.storage.local |
Traceboard normalizes a recorded HTTP or HTTPS address by removing its URL fragment before saving a navigation node. Other parts of the URL, including query parameters, can remain because they may identify the page you actually visited. You should therefore treat the saved trail as browsing information and use the clear control when you no longer want it retained.
Traceboard currently caps its stored navigation-node collection at 500 nodes. It also limits retained session metadata to the most recent 50 session records. The visible board shows the latest session and caps its current rendering set to 180 nodes for predictable performance.
4. Information Traceboard does not collect
Traceboard does not inject a content script into ordinary websites and does not read webpage body text, article paragraphs, form field values, passwords, payment details, messages, comments, images, video frames, clipboard contents, microphone input, camera input, downloads, cookies, localStorage belonging to websites, or the contents of browser developer tools.
The extension does not create a user account and therefore does not ask for a legal name, username, email address, postal address, telephone number, date of birth, government identifier, profile biography, or payment information.
Traceboard does not use analytics or telemetry. It does not send feature-use events, crash reports, identifiers, browsing records, notes, or device characteristics to Google Analytics, Firebase Analytics, Segment, Mixpanel, Amplitude, Sentry, an advertising network, or another measurement provider.
Traceboard does not use remote artificial-intelligence services. It does not upload your URLs or notes to an LLM provider, embedding service, recommendation engine, categorization API, or remote search service.
5. Chrome permissions and why they are required
tabs
The tabs permission lets Traceboard receive tab creation, navigation, title, and closure information and inspect the opener relationship supplied by Chrome. This is the core input needed to represent browsing paths.
The permission is not used to read the body of pages. Traceboard does not call chrome.scripting, register a page content script, or execute code inside the websites you visit.
storage
The storage permission allows the extension to save the trail, session timestamps, pin state, and your notes in chrome.storage.local. It also uses chrome.storage.session for a temporary map between live tab IDs and trail node IDs while the browser session is running.
chrome.storage.local is browser-managed extension storage associated with your browser profile. Traceboard does not mirror that storage to a Traceboard cloud account or server.
6. Local storage, retention, and deletion
Trail nodes and their session metadata are stored locally using Chrome’s extension storage API. The extension keeps this information so the map survives closing and reopening the Traceboard board and survives ordinary browser restarts.
Traceboard does not implement automatic cloud retention because it has no cloud storage. Data remains in the browser profile until one of the following occurs: you clear the trail using the built-in control, Chrome removes extension data when the extension is uninstalled or its storage is cleared, the internal node cap removes older nodes as new nodes are created, or you otherwise reset the browser profile.
The board includes a visible “Clear local trail” control. When you confirm that action, Traceboard clears its stored nodes, sessions, and last-activity state from chrome.storage.local. It also removes the temporary live-tab map from chrome.storage.session.
Short notes are attached to individual trail nodes. Deleting the trail deletes those notes with it. Traceboard does not keep a hidden second copy or server backup of deleted notes.
If you uninstall the extension, Chrome normally removes extension-controlled local storage for that extension. Browser behavior and enterprise profile management can vary, so you can use “Clear local trail” before uninstalling if you want to delete the data explicitly from within Traceboard first.
7. Network and remote-code behavior
Traceboard contains no application network client. Its production source does not use fetch, XMLHttpRequest, WebSocket, EventSource, remote JavaScript imports, analytics beacons, tracking pixels, or a Traceboard API endpoint.
All executable JavaScript and CSS used by the extension is packaged with the extension. No executable code is downloaded at runtime. This design is consistent with Chrome Web Store requirements against remotely hosted executable code.
If you double-click a node or use its page link, Chrome can navigate to that recorded website. The resulting website request is a normal browser navigation requested by you, not a data upload to Traceboard. The destination website can of course apply its own privacy policy when you visit it.
The extension UI itself does not load remote fonts, remote images, remote style sheets, advertisements, social widgets, embedded media, or external analytics resources.
8. Controls available to you
You control whether Traceboard remains installed and can remove or disable it at any time through Chrome’s extension management interface. Disabling it stops it from receiving new browser tab events while disabled.
You can inspect the data visually on the Traceboard board. Nodes show the page title, site host, time information, pin status, closed-tab state, and relationships to other nodes.
You can add or remove a pin from a selected node. You can type, edit, or erase a private note. The note input is limited in length and is stored only as part of the local trail.
You can focus a path leading from a selected node back through its parents. This operation is a local view filter only; it does not send the path anywhere or create another copy of the data.
You can use “Clear local trail” to delete the current locally stored Traceboard trail. This is the primary in-product deletion control.
You can also use Chrome’s extension settings to clear extension data or uninstall Traceboard. Those controls are provided by the browser and operate independently from the Traceboard board.
9. Security approach and limitations
Traceboard reduces exposure by avoiding a remote account system and remote database. There is no Traceboard password to steal and no Traceboard server containing your browsing trail.
The extension uses Manifest V3 and packages its executable code locally. It does not contain a production manifest key, signing secret, private certificate, remote loader, debug harness, or external script dependency.
Local-only storage is not the same as encryption. Traceboard does not add its own cryptographic layer on top of Chrome extension storage. Anyone who has sufficient access to your operating-system user profile or browser profile may be able to access local browser data.
You are responsible for the physical and account security of the device and browser profile where Traceboard is installed. Use operating-system login protection and Chrome profile controls appropriate to your environment.
If you use a managed browser, an administrator may be able to apply policies, inspect browser configuration, or manage extensions. Traceboard does not control those administrator capabilities.
11. Children and sensitive use
Traceboard is a general-purpose browser utility and is not designed or marketed specifically for children. It does not knowingly operate a registration flow or collect age information.
Because the trail can contain URLs from any site you visit, it may reflect sensitive browsing activity if you use the browser for sensitive subjects. Traceboard does not attempt to determine whether a URL concerns health, finance, religion, politics, sexuality, employment, or another sensitive topic.
Users who share a device, profile, classroom workstation, family computer, or other environment should consider whether retaining a local browsing trail is appropriate. The clear control can be used whenever the stored trail is no longer wanted.
12. Changes to this policy
This document is written for Traceboard version 1.0.0. Future releases may change features, permissions, or storage behavior. When a change materially affects the way data is processed, the privacy policy should be updated to describe the new production behavior.
A policy update does not silently grant new Chrome permissions. Chrome controls permission declarations through the extension manifest and may show additional permission information when an update requests broader access.
The “effective date” near the top of this policy indicates the date of this version. You can compare that date with the extension version shown in Chrome or on the store listing when reviewing privacy information after an update.
13. Support and privacy contact
For questions about this policy, a suspected privacy issue, or a request for clarification about Traceboard’s behavior, use the developer support or contact method displayed on the official Chrome Web Store listing from which you obtained the extension.
When contacting support about a privacy question, you do not need to send your browsing trail or private notes. Describe the behavior or question in general terms unless you intentionally choose to share a specific example.
Because Traceboard does not maintain user accounts or a server-side browsing database, the developer cannot remotely retrieve or delete a local trail on your behalf. Use the in-product “Clear local trail” control or Chrome’s extension-data controls on the device where the data is stored.