What local OCR means
Optical character recognition and image processing run in the extension environment. Image pixels are transient during processing, while search terms and copied text are not persisted.
To avoid repeating completed work, structured OCR results may use a bounded local IndexedDB cache. Cache keys use salted, hashed site scope and image-content digests instead of retaining raw page or image URLs.
Why each Chrome permission is needed
| Permission | Purpose |
|---|---|
| storage | Manage settings, per-site choices, and the bounded local OCR cache. |
| scripting | Register the combined finder only on sites the user has approved. |
| offscreen | Run packaged OCR work inside the extension while it is needed. |
| activeTab | Support a user-invoked toolbar fallback for the current tab. |
| sidePanel | Show the query, combined results, and OCR progress in Chrome’s Side Panel. |
| Optional HTTP/HTTPS host access | Read text and supported images on approved regular webpages and render result highlights. |
Site access is requested only after an explicit user action. Without permission, the extension does not read or inject into the page and Chrome Find remains unchanged.
Re-requesting an original image host
Chrome may display a cross-origin image while preventing direct pixel access. In that case, the extension may re-request only the exact approved HTTP(S) source URL from its original host.
Credentials and referrer are omitted and redirects are rejected. This is not an upload to an external OCR service, and the extension does not invent another URL or request an unapproved host.
Delete cache, local data, and site access
- Use Clear OCR cache in extension Settings to remove structured OCR records.
- Delete all local extension data removes the OCR database, settings, review state, and local cache salt, then creates fresh defaults.
- Site permission is separate. Use Remove all website access or Chrome’s site-access controls to revoke it.
- Uninstalling the extension removes extension-owned local storage through Chrome’s normal extension data lifecycle.
No ads and clear support limits
Version 1 contains no ad SDK, ad UI, ad-network request, user analytics, or remote configuration. User data is not sold or used for interest-based advertising or cross-site tracking.
Incognito mode is unavailable. Chrome pages, PDF Viewer, Canvas, video, WebGL, DRM, and inaccessible frames are unsupported or not guaranteed. Review the Privacy Policy for the complete data-handling statement.