BYDIFF Privacy Policy
This policy explains the data processed by the BYDIFF extension for Google Chrome, the purposes of processing, local and server storage, Chrome permissions, and user controls.
Snapshots, history and monitoring results are intended to remain on the user's device and are not uploaded to developer cloud storage.
Web Console account, project settings, compact statistics, licensing and limited product telemetry.
Data is not sold or used for personalized advertising or advertising profiling.
1. Scope and developer
This policy applies to the BYDIFF extension for Google Chrome and BYDIFF server functions at bydiff.com. Developer: Yury Barkalov. The product's primary purpose is to discover and compare changes on websites selected by the user.
2. Data processed locally
This data is required for the core monitoring function.
| Category | Examples | Purpose |
|---|---|---|
| Website addresses | domains, URLs, internal links, sitemap.xml, robots.txt | Discovering pages and building the scan list. |
| Page content | Title, Description, H1–H6, Canonical, Robots, text, links, DOM, Schema, images/ALT and supported fields | Creating snapshots and comparing saved states. |
| Technical results | HTTP status, network errors, timestamps, crawl state | Availability diagnostics and scan-state display. |
| Product settings | Language, schedule, notifications, exclusions, projects | Preserving user-selected BYDIFF behavior. |
3. Where working data is stored
- Chrome Storage and browser-local mechanisms: settings, interface state, projects, queues and data needed by the extension.
- User-selected local folder: saved snapshots/archives and related files when that feature is used and the user grants access.
- Retention: depends on mode, settings and user actions. Projects and local history can be removed in BYDIFF; files separately saved to disk may require manual deletion.
Working snapshot content and scan results are not intended to be uploaded to the BYDIFF server as part of licensing or product telemetry.
4. Data sent to the BYDIFF server
The server is used for the BYDIFF account, Web Console, compact-statistics synchronization, plan entitlement and limited product analytics.
| Function | Data sent | Purpose |
|---|---|---|
| Web Console | At registration: email, password hash and the provided name. For projects: root website address, name, mode and schedule. After a completed scan, the extension may send a compact summary: project address, version identifier, status, counts of found/scanned pages, changes and errors, and completion time. HTML, DOM, page text, screenshots, images and archived copies are not included in this summary. | Operating the user console, synchronizing schedules and displaying history without uploading full snapshots. |
| Plan entitlement | Active account session, Trial/PRO plan, Trial/Pro expiry, Installation ID and Scanner Agent version. The current account model does not require a separate license key. | Applying server-side Trial/PRO limits and capabilities, Scanner Agent compatibility and session revocation. |
| Product telemetry | Installation ID, version, PRO mode and limited usage events: extension open, scan start, comparison, history and exclusions open. | Aggregated usage, stability and version-distribution statistics. Telemetry does not include URLs, domains, HTML, page text or SEO scan results. |
| Service messages | Installation ID is used to select the appropriate message audience (PRO or a specific account group). The extension receives only the message title, text, type and display period from the server; IDs of already shown messages are stored locally. | Displaying important service notices and BYDIFF update information. Messages are data and do not contain remotely executable code. |
English BYDIFF / Web Console
English BYDIFF English (email, English pages, English changes/English HTML-English, DOM, English pages, English Web Console.
English Web Console English. English pagesEnglish https://bydiff.com English BYDIFF.
5. Google Chrome permissions
Permissions are used in connection with BYDIFF's stated functions.
| Permission | Use |
|---|---|
| activeTab | Temporary access to the active tab following a user action. |
| scripting | Running page analysis required for monitoring functions. |
| storage / unlimitedStorage | Local storage of settings, state, projects and history needed for comparison. |
| alarms | Scheduling background tasks and recurring checks when Chrome can run them. |
| notifications | Displaying notifications about scan state and product events. |
| favicon | Displaying website icons in the interface. |
| optional_host_permissions http://*/*, https://*/* | Access to HTTP/HTTPS websites selected by the user for monitoring; access is requested for the relevant feature. |
| https://bydiff.com/* | HTTPS communication with licensing, configuration, service-message and limited product telemetry APIs. |
6. Sharing, sale and advertising use
BYDIFF does not sell user data, provide it to advertising networks, or use monitoring data for personalized advertising, credit scoring or advertising profiling. Data may be processed by technical infrastructure required to operate the website/API and hosting, to the extent needed to provide the relevant server functions.
7. User control and deletion
- The user chooses which websites to monitor and can delete a project and local history.
- Schedules, notifications and exclusions can be changed or disabled.
- Website access permissions can be revoked through Chrome controls.
- Uninstalling the extension removes its Chrome Storage data according to Chrome behavior; files separately saved in a selected local folder may remain until manually deleted.
- Questions about server-side Web Console and licensing data can be submitted through the contact channel on the BYDIFF Support page.
8. Security and server-data retention
Communication between the extension and the BYDIFF API uses HTTPS. Session tokens are stored on the server in a protected representation, while full working snapshots are separated from server telemetry and compact Web Console summaries. Service data may be retained as needed for account operation, security and product operation; some aggregated/service statistics are cleaned according to configured retention rules. No storage or transmission method can guarantee absolute security.
9. Children and sensitive information
BYDIFF is a professional website-monitoring tool and is not specifically directed to children. Do not send passwords, API keys, payment data or other secrets through the developer contact channel when they are not required to resolve a request.
10. Policy changes and contact
This policy may be updated when BYDIFF features, permissions or data-processing practices change. The current revision is published on this page. Developer: Yury Barkalov. For privacy, access or server-data deletion questions, use the BYDIFF Support page and the developer contact channel listed there.
11. Chrome Web Store Limited Use
Data is used only for BYDIFF's disclosed features and related operational purposes.
The use of information received through Google Chrome capabilities and browser APIs adheres to the Chrome Web Store User Data Policy, including the Limited Use requirements. Data is not sold, transferred for personalized advertising, or used for purposes unrelated to BYDIFF's disclosed functionality.