catchlead.

CatchLead

Privacy Policy

How CatchLead handles account information, project data and public conversations.

Last updated: October 31, 2026

Operator: Волошин Олександр Олександрович, an individual. Country: Ukraine.

voloschin2015@gmail.com

Account holders and people whose public posts appear in CatchLead can contact the operator. Do not send passwords, API tokens or identity documents with an initial request.

This site is a static product preview. Sign-in, analysis, search, saved leads and monitoring are unavailable here. The workflows below apply only with an enabled server application. Source platforms operate independently.

The site remembers language and appearance. In the enabled application, Firebase Authentication handles Google or email/password sign-in. Account and project data include user ID, email, name, photo, optional company, settings, website URLs, product descriptions, audiences, phrases, sources and monitors. Firebase handles passwords.

Sources provide post IDs, usernames, text, dates and original links. Manual results stay in page memory until a new search, navigation or reload; saving requires Add lead. Enabled monitors can automatically save accepted leads and notify chosen destinations. Relevance scores use product context and evidence; they do not verify buyers. No automated outreach is implemented.

Firebase Hosting processes technical request data to serve this site. The enabled application uses Firebase Authentication and Firestore. A configured OpenAI-compatible provider receives extracted website content for analysis; TypeSafe receives product context and public-post content for relevance inference. Optional Resend, Telegram, Slack or Discord delivery shares notification content and destination data. Reddit commercial access awaits approval; Threads public search is unconfirmed. Providers describe their own processing in their policies.

Saved records remain until removed or a removal request is handled. Cache reuse expires after 30 days; physical deletion is not guaranteed by that expiry. Historical scans, snapshots, usage records, provider logs and backups may require separate handling. Removing a source or its original post does not automatically erase stored copies.

Contact the operator for access, correction or deletion. Identify the account, project or original post links; authors need no CatchLead account. We may request proportionate proof of control. Do not initially send passwords, tokens or identity documents. The deletion page explains the available actions.

The application uses server-held credentials and authenticated ownership checks. Browser storage also supports sign-in and temporary drafts when enabled. Providers may process data in other countries; no specific region, certification or zero-retention guarantee is asserted. Scores support human review, not conversion probabilities.