Privacy Policy for BrowseLog
📊 BrowseLog
Chrome Extension
Privacy Policy
Effective Date: March 15, 2025 |
Version 1.0.0
|
🔒 Privacy Commitment |
|
|
|
BrowseLog is
designed with privacy as its foundation. Your browsing data never |
|
leaves your
device. We collect nothing, store nothing remotely, and share nothing |
|
with anyone.
This policy explains exactly what the extension does — and does not do. |
1.
Overview
BrowseLog ('the
Extension', 'we', 'our') is a free, open-source Chrome browser extension that
allows users to view and export their local Chrome browsing history to an Excel
(.xlsx) file. This Privacy Policy describes our practices regarding data
access, usage, and protection.
This policy applies to the
BrowseLog Chrome Extension distributed through the Chrome Web Store.
2.
Data We Access
2.1 Browsing History
The Extension reads the
following data from Chrome's local history API, solely when you initiate a
Preview or Export action:
•
Page titles of visited websites
•
URLs (web addresses) of visited pages
•
Date and time of each visit
•
Visit count per URL (how many times a page was visited)
This data is accessed
locally from your device only. It is never transmitted to any server, database,
or third party.
2.2 User Preferences (Storage)
The Extension may store
the following preferences locally in Chrome storage to improve your experience:
•
Your selected date range (e.g., 'Last 7 Days')
•
Your keyword filter text
These preferences are
stored only on your local device using Chrome's storage API. They contain no
browsing history or personal information.
2.3 Data We Do NOT Access
BrowseLog does not access,
collect, read, or process any of the following:
|
Data Type |
Example |
Collected? |
|
Personal Identity |
Name, email, address, age |
No |
|
Health Information |
Medical records, symptoms |
No |
|
Financial Data |
Payment info, transactions |
No |
|
Authentication Data |
Passwords, credentials, PINs |
No |
|
Communications |
Emails, messages, chat |
No |
|
Location Data |
GPS, IP address, region |
No |
|
User Activity |
Clicks, keystrokes, scroll |
No |
|
Website Content |
Text, images, videos, audio |
No |
|
Cookies / Sessions |
Login sessions, tracking IDs |
No |
3.
How We Use Your Data
All data accessed by the
Extension is used exclusively for the following purpose:
•
Displaying a preview table of your browsing history
within the Extension popup
•
Generating an Excel (.xlsx) file saved directly to your
local Downloads folder
•
Calculating summary statistics (total visits, unique
sites, days active)
The Extension processes
your history data in-memory within your browser. Once the popup is closed or
the export is complete, no data is retained by the Extension.
|
✅ Data Flow Summary |
|
|
|
Chrome History
API →
Extension Memory → Excel File (local Downloads folder) |
|
|
|
At no point
does data travel outside your device. |
4.
Data Sharing and Disclosure
We do not share, sell,
rent, trade, or otherwise disclose your data to any third party under any
circumstances. Specifically:
•
No analytics or telemetry services are used
•
No advertising networks receive any data
•
No cloud storage or remote servers are involved
•
No third-party APIs or SDKs are integrated
•
No data is shared with the extension developer or
Anthropic
5.
Chrome Permissions Explained
The Extension requests the
following Chrome permissions. Each permission is the minimum required to
provide the stated functionality:
|
Permission |
Why It Is
Required |
Data Sent
Externally? |
|
history |
Read local browsing history
to display and export it |
No — local only |
|
storage |
Save your UI preferences
(date range, filter text) locally |
No — local only |
|
downloads |
Save the generated .xlsx
file to your Downloads folder |
No — local only |
6.
Data Retention
BrowseLog does not retain
any browsing history data. Specifically:
•
Browsing history is accessed only while the Extension
popup is open
•
All history data is held in-memory and discarded when
the popup closes
•
The exported Excel file is saved to your device; the
Extension holds no copy
•
UI preferences stored via Chrome storage can be cleared
at any time by removing the Extension
7.
Security
Because BrowseLog operates
entirely locally and transmits no data externally, the primary security
considerations are:
•
The exported Excel file is saved to your local machine
and subject to your device's own file system security
•
The Extension runs in Chrome's sandboxed extension
environment, limiting its access to only the declared permissions
•
No network connections are made by the Extension
8.
Children's Privacy
BrowseLog does not
knowingly collect any personal information from children under the age of 13
(or the applicable age of digital consent in your jurisdiction). The Extension
does not collect any personal data from any user of any age.
9.
Your Rights and Controls
Since BrowseLog does not
collect or store any personal data, there is no personal data held by the
developer that would be subject to access, correction, or deletion requests.
You retain full control over:
•
Your browsing history (managed within Chrome Settings
> History)
•
The exported Excel files (saved to your local device)
•
Extension preferences (cleared by uninstalling the
Extension)
10. Changes to This Policy
We may update this Privacy
Policy from time to time. When we do, the updated policy will be published on
the Chrome Web Store listing and the effective date at the top of this document
will be revised. Continued use of the Extension after such changes constitutes
your acceptance of the updated policy.
11. Contact
If you have any questions,
concerns, or requests regarding this Privacy Policy or the Extension's data
practices, please contact us through the Chrome Web Store support page for
BrowseLog.
|
📌 Summary |
|
|
|
BrowseLog
reads your local Chrome history only when you ask it to. |
|
Nothing is
sent anywhere. Nothing is stored remotely. You are always in control. |
|
|
|
This extension
was built to serve you — not to collect data about you. |
Comments
Post a Comment