Stackr is a local-first Chrome extension. Your core library stays in your browser by default. Data leaves your device only when you choose an optional feature such as analytics, sign-in, sync, or public sharing, or when Stackr requests page metadata and icons for a URL you save. Stackr does not sell personal data or use it for advertising.
1. Data Stackr accesses and why
- Tabs and page URLs: Display, focus, close, and save open tabs, and retrieve titles and icons for links you choose to save.
- Bookmarks: Browse, import, and manage Chrome bookmarks when you use bookmark features.
- History: Search browser history and show recent sites inside Stackr.
- Storage: Save your library, settings, preferences, and local metadata.
- Identity: Authenticate with Google when you choose to sign in.
- Website access: Request metadata and icons from websites for URLs you ask Stackr to process.
2. Local storage
By default, Stackr stores workspaces, stacks, saved links, notes, settings, preferences, and local metadata in Chrome storage on your device. An account or cloud service is not required for core features.
Open-tab information and browser-history results are not uploaded as part of sync unless you explicitly save a page as a Stackr link. The Stackr website may store your appearance preference in browser local storage.
3. Optional analytics
Analytics are off by default. If you enable them, Stackr sends product events to PostHog EU. Events can include a random installation identifier, your account user ID when signed in, authentication state, features used, application surfaces opened, activation milestones, and success or error states.
Analytics do not include saved-link URLs, bookmark contents, browser-history contents, notes, or open-tab contents. Stackr does not use autocapture or session recording. You can disable analytics at any time in settings.
4. Optional account, sync, and public sharing
If you sign in, Google and Supabase process authentication and Stackr receives account information such as your user ID and email address. If you enable sync, Stackr uploads the information needed to synchronize your library, including workspaces, stacks, saved links, notes, settings, sync metadata, and device metadata.
If you publish a stack, Supabase stores a read-only snapshot containing that stack title, description, saved-link titles, URLs, notes, favicons, and item order. Publishing one stack does not expose your other stacks, workspaces, account information, browser history, or open tabs.
5. External requests and service providers
When resolving a link you ask Stackr to process, Stackr may request the page and its favicon directly. These requests omit cookies and referrer information, but the destination can receive the requested URL, your IP address, and ordinary network information.
Stackr uses Google Chrome for browser permissions and local extension storage, Google for optional authentication, Supabase for optional authentication, sync, and sharing, and PostHog for optional analytics. Data is disclosed only as needed to provide features you choose, comply with law, or protect users and the service. Stackr does not sell personal data.
6. Retention, deletion, and your choices
- Local data remains in Chrome until you delete it, clear the extension storage, or uninstall Stackr.
- You can use Stackr without an account and leave sync disabled.
- You can disable analytics to stop new analytics events.
- You can export or restore a local backup.
- You can unpublish an individual public stack.
- You can contact Stackr to request access to or deletion of remotely stored account, sync, or sharing data.
7. Security and children privacy
Stackr limits remote processing by keeping its core library local by default and using remote services only for features that require them. No method of storage or transmission can guarantee absolute security.
Stackr is not directed to children under 13, and we do not knowingly collect personal information from children under 13. Contact us if you believe a child has provided personal information through Stackr.
8. Policy changes and contact
We may update this policy when Stackr features or data practices change. The dates at the top of this page show when the policy became effective and was most recently reviewed. Material changes will be communicated through the website, extension, or another appropriate channel.
Contact hi@stackr.space with privacy questions, requests, or concerns.