1. Overview
This Privacy Policy explains how Crumb — Private Cookie Manager (“Crumb,” “the extension,” “we,” or “us”) handles information when you install and use the extension. Crumb is designed to provide browser-cookie management while minimizing data collection.
2. Information Crumb accesses
To provide its core functionality, Crumb can access browser cookies and the domain of the active browser tab. This allows the extension to display, inspect, search, protect, delete, back up, restore, and automatically clean cookies according to instructions and rules configured by the user.
3. Information we collect
We do not collect, receive, transmit, or store your browser cookies, browsing history, website content, authentication information, personal communications, financial information, health information, location, or user activity on external servers.
Crumb does not use analytics, telemetry, crash-reporting services, advertising networks, tracking pixels, or third-party data-collection services.
4. Local storage
Crumb uses Chrome’s local extension storage to save settings required for the extension to work. This may include theme preferences, site cleanup rules, protected cookie names, local activity history, and other configuration choices.
This information remains in your browser profile and is not transmitted to us. You can remove it by using Crumb’s reset controls or uninstalling the extension.
5. Cookie backups
Crumb allows you to create and restore cookie backup files. Backup files are created locally and are saved only when you explicitly request an export. Sensitive cookie values are excluded by default unless you deliberately choose to include them.
You are responsible for securely storing any exported backup that contains cookie values, since such values may include active authentication sessions.
6. Permissions
Crumb requests the following Chrome permissions:
- Cookies: to read, display, modify, back up, restore, and delete browser cookies at your request.
- Storage: to save preferences, rules, protected cookie names, and local history.
- Tabs: to identify the active website and support current-site and tab-close cookie management.
- Alarms: to run optional scheduled cleanup rules.
- Host permissions: to manage cookies for websites across the browser. Chrome requires matching host permissions before an extension can access a website’s cookies.
7. Data sharing and sale
We do not sell, rent, share, or transfer user data to third parties. We do not use user data for advertising, profiling, creditworthiness, lending, or any purpose unrelated to Crumb’s single purpose as a browser-cookie manager.
8. Remote code and external services
Crumb does not execute remotely hosted JavaScript or WebAssembly. The executable code needed by the extension is packaged with the extension. Crumb does not require an account, cloud service, or external API to provide its functionality.
9. Children’s privacy
Crumb is a general-purpose browser utility and is not directed toward children. Because Crumb does not collect personal data, it does not knowingly collect personal information from children.
10. Security
Crumb is designed to minimize risk by keeping processing local and hiding cookie values by default. However, no software can guarantee complete security. Users should handle exported cookie values carefully and avoid sharing files that may contain authentication sessions.
11. Changes to this policy
We may update this policy when Crumb’s functionality or legal obligations change. The effective date at the top of this page will be updated when revisions are published. Material changes will be reflected on this page before or alongside a relevant extension update.
12. Contact
Questions about Crumb or this Privacy Policy can be sent to husseinakl22@gmail.com.