← Source Image Finder

Privacy Policy

Last updated: October 23, 2026.

This policy explains what Source Image Finder processes and stores when you scan public webpages, use browser workspaces, create an account, or use a paid plan.

Submitted URLs and scan data

Source Image Finder processes the public webpage or store URLs you submit so it can render pages, discover image assets, check public candidate files, and return scan results. Scan records can contain the submitted URL, discovered public image URLs, image metadata, result classifications, and download selections. The service is designed for public webpages. Do not submit passwords, private-session URLs, confidential URLs, or other secrets.

Scan results remain accessible for up to 24 hours after processing ends. Multiple URLs and Store Catalog results appear in Saved work during that time. Scan Single Page results are temporary and do not appear in Saved work, but their server records follow the same short retention and cleanup schedule. Normal scans do not save full-page screenshots.

Accounts, sign-in, and billing

If you create an account, Source Image Finder stores your email address, a salted scrypt password hash and salt, email-verification status, your plan and credit state, and billing/subscription identifiers and status needed to operate the account. Passwords are not stored in plaintext. Email-verification and password-reset links use short-lived, one-time tokens; Source Image Finder stores only token hashes, not the usable token from the emailed link.

Signed-in sessions use a first-party HttpOnly, SameSite=Lax session cookie with an expiry of up to 30 days. The server stores a one-way SHA-256 hash of each active random session identifier rather than the raw session identifier.

Paid checkout and billing management use Stripe-hosted services. Stripe processes payment-method and billing information. Source Image Finder stores the Stripe customer/subscription identifiers and subscription state needed to manage access, credits, renewals, cancellation, and payment status; it does not store full payment-card numbers in its account records.

Transactional and administrative email is sent through Amazon Simple Email Service (Amazon SES). Source Image Finder sends AWS the recipient address and message content needed to deliver an email. SES delivery events such as send, delivery, bounce, complaint, reject, rendering failure, and delivery delay can be recorded by Source Image Finder for up to 30 days to operate email delivery and sender-reputation safeguards. Those local SES event records can include recipient addresses, SES message identifiers, event type, message tags, and delivery or failure details, but they do not store the email body.

First-party cookies and browser storage

Anonymous visitors can receive a first-party sr_workspace cookie containing a random workspace identifier. It is HttpOnly, SameSite=Lax, and can remain for up to 30 days so the browser can reconnect to anonymous workspace state while that state exists on the server.

Source Image Finder also uses first-party localStorage for scanner/workspace state and preferences such as submitted URLs, selected results, filters, view choices, and download settings. Browser-local data can remain until it is replaced or cleared by the application, or until you clear site data in your browser. Short-lived workflow handoff data can also use sessionStorage.

Server-side workspace and Store Catalog preview state is capped at 24 hours. The anonymous workspace cookie and data in your browser may remain after the corresponding results have been deleted from the server.

Network identifiers and abuse prevention

Like other web services, Source Image Finder receives network request information needed to serve requests and apply security controls. For anonymous catalog-preview allowances and request rate limits, the application stores keyed one-way identifiers derived from the network address together with limited counter/window metadata. The raw network address is not written to those application counter files. Anonymous catalog-preview counters reset daily, and short-window request-limit records are cleaned on a short operational schedule.

Analytics

When Cloudflare Web Analytics is enabled for the production domain, Source Image Finder uses it for aggregate traffic and real-user performance measurement, including Core Web Vitals. Cloudflare Web Analytics does not use cookies or localStorage to identify visitors for analytics and is not used by Source Image Finder for cross-site advertising or behavioral profiling.

Google Analytics 4 operates only on public information and tool pages, with region-based controls. For visitors identified as being in the United States, Google Analytics is enabled by default unless you have opted out; you can opt out below. Visitors identified as being in the European Economic Area, United Kingdom, or Switzerland are asked for permission before the Google tag loads. In other regions, or when the visitor's location cannot be reliably determined, Google Analytics is disabled. Country detection is based on network information provided by Cloudflare and may not always identify your location correctly.

When enabled, Google Analytics uses analytics cookies and receives usage events and technical information, which may include your general location inferred from your network connection and browser/device information. Source Image Finder limits its own analytics events to public page views without URL query strings or fragments; account, admin, and private-workspace pages are excluded. Google Analytics is not used by Source Image Finder for advertising personalization. Google handles data under its Privacy Policy.

Any analytics permission or opt-out choice is stored in your browser's localStorage until you change it or clear site data. You can opt out or withdraw permission using the button below wherever Google Analytics is available. This prevents future Google Analytics collection in this browser, but does not remove events already collected. You can clear site data to remove a stored preference.

Change analytics preference

Operational records and retention

Billing/accounting, security, cost, and host-performance records are retained separately from short-lived scan results when needed to operate and protect the service. Cost and host-performance telemetry defaults to 90 days. Administrator mutation-audit files also default to 90 days. Cost telemetry can include internal job/account identifiers, plan and workflow mode, timing, request/byte counts, result counts, and terminal status; those telemetry records do not contain the submitted target URL or account email address. Host-performance telemetry records server CPU, memory, event-loop, queue, and filesystem measurements and does not contain submitted URLs or account email addresses.

Source Image Finder also keeps privacy-safe aggregate service counters indefinitely so long-term totals and trends are not lost when detailed telemetry expires. These aggregate counters can include successful webpages or catalog products processed, image families found, verified larger-source recoveries, downloads, and byte totals. They do not contain submitted URLs, image URLs, account or email identifiers, IP addresses, job IDs, or other customer-level records. Development and test totals are stored separately from production totals.

Production application logs use structured redaction for submitted target URLs, email addresses, authorization or token values, cookies, secrets, and Stripe secret-style credentials before application log records are written. Account and billing records have separate retention from scan results and are not removed merely because a 24-hour result window expires.

Contact and privacy questions

For privacy or account-data questions or requests, including account deletion requests, use [email protected]. Account deletion is support-assisted at launch. Active billing and processing must be resolved first; eligible local account, access, Saved work, and account-linked operational data are then removed. Some billing, security, dispute, tax, backup, or provider records may follow separate retention requirements. The Contact page describes the monitored support route. Use Terms for service-use rules and Copyright for copyright or takedown notices.