Privacy Policy
Effective 11 September 2026. This policy explains the data Scout uses to operate candidate job discovery, Telegram delivery and recruiter matching.
1. Information Scout stores
Scout stores the career information you provide, including name, email, phone number, current location, master resume text and filename, target roles and locations, remote preference, industries, seniority, company preferences, match threshold, alert settings, job feedback and plan state. When you connect Telegram, Scout also stores the chat identifier and username needed to deliver the service and bind the website setup to your account.
For recruiter matching, Scout also stores recruiter-facing preferences you provide, such as search status, availability, compensation expectations, relocation preferences, work-authorization information, companies you want excluded and whether you have enabled recruiter discovery.
Recruiter mode stores verified work email, workspace information, role briefs, hiring criteria, candidate-match and invitation state, candidate responses and pipeline stage. Recruiter workspaces are isolated by verified account identity; an email domain alone is not an authorization boundary.
Scout records limited first-party website activity for aggregate product analytics. Hosting infrastructure may provide approximate city and country information. Scout does not request GPS location for this purpose and does not publish names, email addresses, phone numbers, Telegram IDs, resume data or precise coordinates in public activity.
2. How Scout uses information
Scout uses candidate data to connect onboarding to Telegram, enforce saved search constraints, rank opportunities, avoid duplicate alerts, learn from explicit feedback, manage plan entitlements and prepare career material you request.
If recruiter discovery is enabled under the current visibility model, verified recruiters can review your professional profile, including your name, career information, resume text and the contact information stored in Scout, when reviewing candidates for their roles. You can turn recruiter discovery off and can exclude specific companies. Profiles that only opted into Scout's earlier anonymous-discovery model are not automatically upgraded to identity-visible recruiter discovery; those candidates must enable the current recruiter-visibility setting first.
Scout does not sell career data or use candidate or recruiter data to build advertising profiles.
3. Resume and AI processing
Your stored master resume remains the factual source of truth for resume tailoring. When an AI-assisted action needs resume context, Scout creates a processing copy and removes obvious email addresses, phone numbers and URLs before sending that copy to the configured Google Gemini service. Contact details remain in Scout and may be restored into the final resume. A target job description may also be processed when needed for matching or tailoring.
Most ingestion, hard eligibility filtering, deduplication and first-pass ranking is performed without an LLM. AI is used selectively for natural-language assistance and requested resume tailoring. Third-party AI processing is also subject to the provider terms applicable to Scout's account.
4. Recruiter discovery and invitations
Recruiters can review only profiles that have enabled the current recruiter-discovery model and have not excluded the recruiter's company. Scout ranks visible candidates independently for each role and may show both recommended matches and a wider role-scoped candidate pool so recruiters can review people directly.
A recruiter can send an invitation after reviewing your profile. Scout attempts Telegram delivery first when available and can use transactional email as a fallback. Your response can be used to organize mutual-interest pipeline stages, but accepting an invitation is not required for an authorized recruiter to view a profile that you have already made recruiter-visible.
5. Telegram, email, referrals and payments
Telegram provides the information required to operate the bot, including chat identifier, username if available, messages, button interactions, payment events and files you explicitly upload. Telegram processes that information under its own terms.
Scout uses Resend for transactional messages such as candidate and recruiter sign-in, invitation fallback email and permitted recruiter outreach. Candidate and recruiter email addresses are not added to advertising lists as part of recruiter mode.
Scout Pro is purchased through Telegram Stars. Scout stores the Telegram payment charge identifier and subscription-expiration information required to grant access and manage renewal. Scout does not receive your card number or app-store payment credentials.
Scout also stores referral attribution and conversion state needed to prevent duplicate rewards. When a referred user upgrades to Scout Pro, the referrer may receive an additional 30 days of Scout Pro. Referral reward state is tied to Scout profiles and does not reveal the referred user's private profile information to the referrer.
6. Storage, security and retention
Production profiles and application state are stored in Redis/Upstash-compatible persistent storage. Scout also stores temporary handoffs, cached job data, deduplication state, delivery counters and recruiter workflow records. Temporary records expire according to their operational purpose; the primary candidate profile remains until it is deleted.
Scout uses Vercel for hosting, Upstash-compatible Redis for persistence, Upstash QStash for scheduled agent execution, Telegram for bot delivery and Stars payments, Resend for transactional email and Google Gemini for selected AI-assisted actions. Credentials are kept server-side in the deployment environment.
Passwordless candidate and recruiter links and website-to-Telegram handoffs are time-limited. Candidate and recruiter sessions use HttpOnly cookies and server-side session state. No internet service can guarantee absolute security, so do not send Scout passwords, government IDs, bank details or unrelated sensitive information.
7. Your controls
You can update your search through My Scout, Scout setup or Telegram settings, replace your master resume, change alerts, manage recruiter-facing preferences and turn recruiter discovery off. You can also exclude specific companies from recruiter visibility. Candidates who previously enabled only anonymous discovery must explicitly enable the current recruiter-visible profile model before their identity and stored profile can appear in recruiter candidate pools.
Delete my data in Telegram Settings removes the primary Scout candidate profile, stored resume, preferences, feedback and associated candidate search state. After deletion the profile is no longer eligible for recruiter matching. Existing recruiter invitation/workflow records may retain limited status, timestamps or pseudonymous identifiers needed for workflow integrity, security and audit purposes, but they no longer resolve to a stored candidate profile in Scout.
Reset web setup only clears the browser's saved onboarding handoff so setup can be restarted; it does not by itself delete a Telegram-linked account.
8. Job sources
Scout retrieves job listings from supported public ATS/job-board sources, employer career pages and approved partner feeds. Scout sends candidates to the canonical job or application URL. A candidate resume is not sent to job sources merely to perform Scout matching.
9. Changes
This policy may change as Scout's features or service providers change. Material changes will be reflected here. Candidate data controls are available from My Scout and the Telegram bot.