Staktekst Privacy Policy
Last updated: 2026-09-07. Applies to Staktekst 3.4.0.
Staktekst is a local-first Chrome extension. It does not include a backend service, analytics, telemetry, advertising SDKs, or cloud sync.
Data Stored Locally
Staktekst stores the following data in the browser profile where the extension is installed:
- notes created in the popup or tab view
- selected text saved as clips
- bookmarked page titles and URLs
- tags and source metadata attached to saved items, including nearby text used to locate clipped passages again
- extension settings, including language, theme, bubble mode, and search engine preferences
- unsaved editing drafts and the original item snapshot used to detect editing conflicts
- retained data from older versions and local migration results, used for recovery
Items are stored in IndexedDB. Settings and search engine configuration are stored in chrome.storage.local.
Drafts are stored in the extension's local browser storage. Saved-item JSON exports do not include drafts or preferences.
How Page Data Is Used
Staktekst processes selected text and the current page's title and URL to provide clipping, bookmarks, search, and tag suggestions. When revisit highlighting is enabled, it reads page text locally to locate passages the user previously saved. Saved clips can include a short surrounding text context to help locate the original passage.
These operations support the extension's visible features. Staktekst does not maintain a separate log of all browsing activity, and it does not send this page data to the developer or use it for analytics or advertising.
Network Activity
Staktekst does not send saved items or settings to a Staktekst server.
The extension can open user-configured search engine URLs with the selected text as the query. Those searches are handled by the destination websites, not by Staktekst.
Search engine icons in the bubble menu come from the browser's local favicon cache (the favicon permission). Staktekst does not fetch icons from external services.
Chrome Permissions
| Permission | Use |
|---|---|
storage |
Save local items, settings, search engines, and change notifications |
contextMenus |
Add right-click actions for saving notes, clips, and bookmarks |
activeTab |
Work with the active page when the user invokes extension actions |
downloads |
Export stack data to a local file |
favicon |
Show search engine icons from the browser's local favicon cache |
Web page content scripts (<all_urls>) |
Show the selection menu, handle page shortcuts, and locate previously saved passages on revisited pages |
Data Removal
Users can clear saved stack items from the extension UI and discard drafts from the draft recovery list. Saving or cancelling an editor also removes that draft. Clearing the saved stack does not erase retained legacy source copies or unsaved drafts. Legacy copies are kept locally to make migration recovery possible. Removing the extension from Chrome also removes extension-local data managed by the browser profile; export a backup before uninstalling if it is needed.
Contact
For questions about this policy, use the developer contact listed on the Staktekst Chrome Web Store page.