Cookie Ledger Privacy Policy

Effective date: August 12, 2026

Cookie Ledger is published by Kalen. Questions can be sent to kalen010901@gmail.com.

Summary

Cookie Ledger locally accesses cookies only for a website the user is viewing and has authorized. Cookie data is not uploaded, shared, sold, or stored on a publisher server.

Sensitive browser data

After authorization, the extension can read name, value, domain, path, expiration/session, Secure, HttpOnly, SameSite, and store identifier. Values may contain sensitive identifiers/authentication data. The publisher cannot see them because they are not transmitted.

User-directed operations

Export files can contain sensitive cookie values. Store and share them carefully.

Permissions

No content scripts or DOM access are used.

Storage and network

Cookie records, values, and search text are not copied to chrome.storage.local; only theme/filter preferences are stored. No application network requests, backend, API, analytics, telemetry, advertising, account, or cloud sync exists.

Collection, sale, analytics, and sharing

No publisher-side collection, sale, sharing, advertising use, analytics, tracking, crash reporting, or remote logging occurs.

Limited Use

Chrome API information is used only for current-site cookie debugging. It is not transferred to brokers, used for advertising, used to build profiles, or used for unrelated purposes. Human access does not occur because data is not transmitted.

Retention and control

Cookie data stays in Chrome's cookie store; no separate database is kept. Preferences remain until cleared/uninstalled. Site access can be revoked in Chrome.

Not a privacy/security guarantee

This developer/QA utility does not block trackers, guarantee anonymity, secure accounts, classify malicious cookies, or improve speed.

Children

This technical tool is not directed to children under 13.

Changes

Material changes update this policy and listing before release.

Contact

Kalen
kalen010901@gmail.com