Your search data should stay understandable and controllable.
This page describes the current MetaHunt product behaviour: what data is processed, why it is needed, which services receive it, and the controls available to you.
Browsing and job alerts
You can browse vacancies without an account. When you create a Telegram alert, MetaHunt stores the selected filter, an opaque subscription ID, the Telegram chat needed for delivery, delivery state, and the vacancy IDs already sent so later digests do not repeat them.
Use the bot's /list command to review alerts, its unsubscribe button to remove one, or /stop to disable notifications.
CV matching
Your CV text is sent to DeepSeek for structured extraction.
MetaHunt processes the raw text in memory and writes an empty value to its legacy raw-text column. It stores the derived profile needed for matching: role, seniority, experience, English level, and extracted skills.
A Telegram-authenticated account is required before upload. Uploaded profiles are owner-scoped: another account cannot read, rank, edit, or subscribe using your candidate ID. Public demo profiles are synthetic seeded data, not user CVs.
Delete a CV from My account. This removes the account link and its CV-based subscriptions; when you are the final owner, the derived candidate profile and skills are deleted too.
Telegram login and account data
Telegram login provides MetaHunt with your Telegram account ID and, when available, username and first name. They are used to verify the login, create your MetaHunt account, enforce ownership, and deliver requested alerts. MetaHunt does not send raw Telegram identifiers to PostHog analytics.
Retention and deletion
Active account data, CV-derived profiles, subscriptions, and sent-vacancy history are kept while you use those features. Pending alerts that are never linked to Telegram are removed after 48 hours.
You can delete an individual CV or subscription, or permanently delete your account from My account. Account deletion removes the Telegram identity, owned and same-chat subscriptions, notification history, CV ownership, and any derived candidate profile that has no remaining owner. The old session stops authorizing API requests immediately.
Product analytics
MetaHunt uses PostHog's EU endpoint and Vercel Analytics to understand visits, funnel steps, feature usage, and technical performance. Campaign identifiers may be recorded. CV text, filenames, email addresses, raw Telegram identifiers, full alert filters, and vacancy descriptions are not analytics properties.
Candidate IDs in ?cv=links are redacted from PostHog's captured URL and referrer properties.
Account deletion removes MetaHunt's application records but does not itself erase historical pseudonymous events already held by analytics providers. Contact the project owner below for a provider-level analytics deletion request.
Service providers and outbound links
- Vercel serves the web application and performance analytics.
- Railway and PostgreSQL run the API and store application data.
- DeepSeek receives CV text for structured extraction.
- Telegram handles login, bot commands, and alert delivery.
- PostHog EU receives the bounded product events described above.
Clicking an original vacancy opens DOU or Djinni. That site then handles the visit under its own privacy terms.