TabsPack
Cookie notice
There are none. This site sets no cookies of any kind, and the TabsPack extension sets none either. That is why you were not asked to agree to anything on the way in.
This website
Every page here is static HTML. There is no cookie, no local storage, no session storage, no fingerprinting, no pixel, no beacon and no tag manager. Nothing is loaded from another server: no font service, no analytics, no video embed, no comment widget, no social button, no consent platform. Everything the page needs is served from this site.
One small script runs, and it opens and closes the menu on a narrow screen. You can turn JavaScript off entirely and every page, every link and all of the content still work.
Consent banners exist because sites place things that legally require consent. This one does not place anything, so there is nothing to consent to and a banner would be theatre.
Server logs
This site is hosted on GitHub Pages. Like any web server, GitHub processes the request in order to answer it: your IP address, the page you asked for, your browser's user agent and the time. That is the ordinary operation of a web server rather than tracking, we do not receive any of it, and it is covered by GitHub's privacy statement.
The extension
TabsPack sets no cookie and reads no cookie. It cannot: it injects no content script into any page,
and it does not request the cookies permission, so the browser does not expose that
interface to it at all.
It stores two things locally, in your browser's own extension storage: your settings, and any snapshots you save. Those are not cookies, they are never sent anywhere, and they exist only on the machine where you made them. Uninstalling removes them.
An export never contains cookies. Not the ones belonging to the tabs you export, not session tokens, not authorization headers. A TabsPack file cannot be used to sign in as you anywhere, and that is written into the format specification as a requirement.
If that ever changes
It would appear here and in the privacy policy in the same release, with a new date, and a proper consent mechanism would come with it rather than a note at the bottom of a page. We have no plans for it.
Contact
Questions to support@palworks.ai, or see the contact page.