MyLogger Privacy Policy
MyLogger is a Chrome extension for opening, viewing, filtering, searching, and analyzing local log files. This privacy policy explains what data the extension handles, how that data is used, and why the extension requests specific Chrome permissions.
Single Purpose
MyLogger has a single purpose: helping developers open, view, filter, search, and analyze local log files so they can quickly identify relevant log information. All extension features directly support this purpose.
Data Processed By The Extension
MyLogger may process the following data when the user chooses to use related features:
- Local log files selected by the user through the file picker or drag and drop.
- Breakpoint JSON files selected by the user for optional breakpoint log analysis.
- User-entered filter text, search text, tags, and time range selections.
- User configuration, including language, local service URL, common filters, and filter history.
Local Log Files
Local log files are read and processed in the user's browser. Normal log viewing, filtering, searching, marking, context inspection, and saving are performed locally. MyLogger does not proactively upload local log files to third-party servers.
Optional Local Backend Service
MyLogger includes an optional feature called Get Breakpoint Logs. When
the user explicitly uses this feature, the extension sends the selected
breakpoint JSON content to the configured local MyLogger backend service.
The default service URL is http://127.0.0.1:7878/analyze.
This local service is used to extract log filter rules from breakpoint information and local source code. Regular log file content is not sent through this breakpoint feature. The extension does not use this feature to contact third-party servers.
Local Storage
MyLogger uses browser local storage to save user preferences and workflow data, including:
- Selected language.
- Configured local backend service URL.
- Common filters created by the user.
- Recent filter history.
This data is stored locally in the user's browser. Users can back up, restore, edit, delete, or clear related configuration from the extension UI.
Chrome Permissions
clipboardWrite
MyLogger requests clipboardWrite so users can copy selected
log rows from the local log viewer. This is used only when the user
explicitly copies log text from the extension UI. MyLogger does not read
clipboard contents.
downloads
MyLogger requests downloads so users can save filtered log
results, search results, screening results, exported common filters, and
configuration backup files. This permission is used only when the user
explicitly clicks a Save, Export, or Backup button.
Host permissions for localhost and 127.0.0.1
MyLogger requests host permissions for http://localhost/*
and http://127.0.0.1/* so the extension can communicate
with the optional local MyLogger backend service. These permissions are
used only for local service communication initiated by the user.
Data Sharing
MyLogger does not sell user data. MyLogger does not share user data with third-party advertising networks, analytics providers, or data brokers. The extension does not use remote analytics or tracking services.
User Control
Users control which log files and breakpoint JSON files are opened in the extension. Users can clear browser extension data, remove stored filters, edit common filters, delete filter history, or uninstall the extension at any time.
Changes To This Policy
This policy may be updated when MyLogger changes how it handles data or permissions. Updates will be published with the project documentation.
Contact
For questions about this privacy policy, contact the project maintainer through the MyLogger GitHub repository: https://github.com/DingYong4223/MyLogger.