Skip to content

Instantly share code, notes, and snippets.

@guzus
Last active August 9, 2026 17:52
Show Gist options
  • Select an option

  • Save guzus/6655365ddf152087a467d3bae27c717c to your computer and use it in GitHub Desktop.

Select an option

Save guzus/6655365ddf152087a467d3bae27c717c to your computer and use it in GitHub Desktop.

Cookiee — Privacy Policy

Last updated: August 10, 2026

Overview

Cookiee is a browser extension for managing cookies. Cookiee has no developer-controlled data collection server, analytics service, advertising SDK, or account system. Cookie management happens locally in Chrome.

Cookiee also offers an optional Agent Sync feature for local development. Agent Sync runs only after the user explicitly starts it. It temporarily sends cookies for the page selected by the user to a token-protected bridge on the same computer at a loopback address such as 127.0.0.1. Cookiee does not send those cookies to Cookiee servers.

Data Handling

Cookie values can include authentication information. Cookiee reads them only to perform actions requested by the user, such as viewing, editing, importing, exporting, deleting, or temporarily syncing cookies.

During Agent Sync:

  • The dedicated Agent Sync tab shows the selected source page, localhost bridge address, update interval, and expiry.
  • Cookie values are sent only to the displayed loopback bridge after the user starts pairing.
  • The setup prompt contains temporary bridge code and a bearer token, not cookie values.
  • Cookie values are not stored in Chrome extension storage, written to disk, logged, or sent to Cookiee infrastructure.
  • The bundled bridge keeps its latest snapshot in memory and rejects access after the temporary grant expires. Stopping the session stops future updates and attempts to revoke the bridge snapshot.

Cookiee does not sell user data, use it for purposes unrelated to the extension's functionality, or use it for creditworthiness or lending.

Permissions

  • cookies: Reads, creates, edits, and deletes cookies for user-requested cookie management. During Agent Sync, it reads the cookies Chrome would send to the selected page.
  • activeTab and tabs: Identifies the page where the user opened Cookiee, opens or focuses the Agent Sync tab, and verifies that an active sync session still refers to the same source tab and site. Cookiee does not collect browsing history.
  • host_permissions (<all_urls>): Allows Cookiee to manage cookies on the website where the user invokes it.
  • storage: Stores temporary Agent Sync configuration and status, including the localhost bridge address, temporary bearer token, selected origin, interval, and expiry. Cookie values are not stored here.
  • alarms: Runs user-enabled Agent Sync updates while a temporary session is active and clears the schedule when the session stops or expires.

Local Storage and Services

Cookiee does not operate remote servers or databases. Standard cookie management stays within Chrome. Agent Sync communicates only with the user-controlled local bridge shown in the interface and only after explicit user action.

Contact

For questions about this policy, open an issue at https://github.com/guzus/cookiee.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment