Your content stays local
Privacy, in plain language.
ClipCompare is provided by Роман Куренок.
Comparisons and local storage
Screenshots, notes, source addresses, comparison details and templates are stored in your browser’s local database. ClipCompare does not upload that content, use OCR or AI to extract it, or sync it to an account. Capture starts only when you choose it and covers a selected area of the visible page.
Delete individual comparisons or clear the library in the app. Unplaced captured snippets are stored separately: remove those separately too. Browser storage clearing or uninstalling the extension can remove local data. Keep private backups of important work.
Files you export or share
PNG, PDF, clipboard images and Studio image/PDF ZIP exports flatten redactions. Review the result before sharing. Private editable backups can retain original unredacted images and source addresses. Template files contain design settings rather than comparison evidence. Files you download or send are outside the browser library; delete them separately where stored.
Extension usage analytics
ClipCompare uses Google Analytics through a Cloudflare relay to understand feature use and improve the product. Events contain only a fixed action name, app version, channel, time and random event/session identifiers. A session identifier changes after 30 minutes without activity. There is no persistent installation identifier or measurement of returning users. These session-linked events are not a claim of irreversible anonymity.
Events exclude screenshots, text, source addresses, comparison names and content. The relay does not explicitly forward your IP address to Google. Network providers still process connection metadata, which can include network addresses, to deliver HTTPS requests. Analytics is not used for advertising or ad personalisation.
Usage analytics is on by default. Open Privacy in the extension and uncheck the usage statistics option to turn it off. You can change this choice at any time.
Turning analytics off clears unsent events and the current session and stops subsequent collection. It cannot retract events already received by Google. The local retry queue holds at most 100 events for up to 24 hours, with at most eight delivery attempts; retries and expiry checks happen while active or on next use, with no timed cleanup while inactive.
Retention and local diagnostics
The configured Google Analytics user/event-level retention period is 14 months. This setting does not cover standard aggregated reports. It is not a promise of permanent storage.
Separate local diagnostics keep up to 1,000 fixed-action records. New writes prune records older than 30 days; there is no timed cleanup while the app is inactive. These local records are not bulk uploaded.
This website and external links
This information site has no forms, analytics scripts or third-party scripts. Visiting it still requires your hosting provider to process normal connection metadata. Browser-store links and email links open services with their own privacy practices.
Privacy questions
Contact quietartifact@proton.me. Do not include private comparison content unless you choose to share it.