SelectSight / Privacy Policy
Privacy Policy
How SelectSight handles the content you recognize, website visits, and support messages.
Last updated: September 24, 2026 · Release 0.2.0
Local OCR runs on your device without an account. Release 0.2.0 also offers email sign-in, cloud recognition, and subscriptions. Choosing cloud recognition sends selected content to SelectSight and DeepSeek after upload and credit confirmation. Raw images are processed for each recognition request and may remain temporarily in runtime memory; the server does not deliberately write them to its database. Structured results may be cached briefly.
1. Who operates SelectSight
SelectSight is maintained by an independent developer reachable at j.ohnie@outlook.com. This policy covers the browser extension, account and cloud services, public website, and support correspondence.
2. Local recognition
The extension processes visible page elements, images, paused video frames, selected text, and screenshots. A viewport screenshot may contain content outside your final selection; cropping and local OCR take place on your device using bundled models.
When automatic recognition is enabled, hovering over supported images or paused video frames can start local recognition. This does not upload the image. You can pause automatic recognition in the popup. Local OCR remains available without signing in.
Copy commands write recognized text to your clipboard. Manual capture also attempts to copy its result automatically. SelectSight does not read your existing clipboard contents and does not send advertising or usage analytics.
3. Optional cloud recognition, accounts, and payments
When you explicitly choose cloud recognition and confirm the upload and credit cost, the extension sends the prepared selected image or screenshot region, local OCR text and associated recognition information, your browser language, and the requested operation to the SelectSight server. The server sends the content needed for recognition to DeepSeek. Content may include personal information visible in the selected area. Do not submit content you are not entitled to process.
Upload consent is remembered in extension storage. Standard credit-based requests still show a cost confirmation. Merely hovering or signing in does not upload page images. Cloud processing requires an internet connection.
Email sign-in uses Resend to deliver verification codes. We store your email address, verification status, account and device identifiers, device label, authentication records, and free-credit or subscription balances. Email challenges and request IP information support delivery limits and abuse prevention. Codes expire after ten minutes; expiry does not necessarily mean the database record is immediately deleted.
Creem provides subscription checkout and billing management. Payment details entered on its checkout are handled by Creem and its payment providers. SelectSight stores identifiers and subscription, payment-event, and credit records needed to activate access and reconcile billing; it does not receive your full payment-card details.
These providers process information under their own terms and privacy practices. Their retention and processing locations can differ from ours. This policy does not promise zero retention or a particular model-training policy on a provider’s behalf.
4. Storage, retention, and your controls
- Local runtime caches hold screenshots and recognized text while the page or extension worker is active. Closing a panel does not necessarily clear every cache.
- Extension storage holds sign-in tokens, account state, upload consent, tab settings, and pending tasks. Signing out clears account credentials used by the extension; it does not delete your server account or cancel a subscription.
- Raw submitted images are used to process the requested recognition in server memory and are not deliberately written to the server database. Structured recognition results are cached in the database for retry handling, with a one-hour expiry. Cleanup runs on startup and periodically while the service is running, so deletion may occur after expiry. This is not a user-facing recognition history.
- Account, device, verification, billing, credit-ledger, and recognition metadata may remain after result cleanup for account operation, fraud prevention, support, and billing obligations. Signing out or uninstalling does not delete those server records. Hosting logs and backups follow operational retention and may outlast active records.
- You can request account-data deletion by emailing support from your account address. We may verify ownership and retain information required for billing, security, or applicable obligations. Deletion requests do not replace subscription cancellation.
- You can pause recognition, restrict site access in Chrome, sign out, or uninstall. Uninstalling clears extension storage; copied or exported content remains under your control in the clipboard and destination applications. Cancel recurring payments through subscription management or contact support.
5. Website visits and support
The website, API server, and hosting infrastructure receive ordinary request information such as IP address, URL, request time, response status, and browser headers. Operational logs support delivery, troubleshooting, and abuse prevention. Their retention depends on hosting and operational needs.
The public website does not set advertising or analytics cookies. Its screenshots and video show product workflows; viewing them does not upload your images or perform cloud OCR.
Email sent to j.ohnie@outlook.com is handled through Outlook.com and your email provider. We receive the email address, message, and attachments you choose to send and retain correspondence as needed to resolve the issue and meet applicable obligations. Avoid sending passwords, payment-card details, or sensitive screenshots. You may request deletion by email.
6. Sharing and limited use
We do not sell personal data or use recognition content for advertising. Data is used to provide recognition, authentication, billing, support, and service security, and is shared with providers as described above or when necessary to comply with applicable law. We do not use your recognition content to train our own models.
SelectSight’s use of information obtained through Chrome APIs follows the Chrome Web Store User Data Policy, including its Limited Use requirements. External websites, the Chrome Web Store, and applications receiving your copied content have their own policies.
7. Questions and updates
Contact the independent developer at j.ohnie@outlook.com for privacy questions or data requests. We cannot retrieve local-only results from your device. Changes to this policy will be posted with an updated date; material changes will be explained before the affected feature is used.