Affiliate.Careers
Editorial & Data Policy
We openly describe which jobs and fields we collect, what the dataset does not contain, where errors may happen, and how to request a correction or removal.
Service Operator and Public Contacts
- Public name: Affiliate.Careers
- Address: Russia, Saint Petersburg, 25 Mebelnaya Street. The office is located on the first floor of the building.
- Phone: +7 921 569-39-45
- Email: [email protected]
What we collect
- Public job posts from Telegram HR channels covering affiliate, CPA, media buying, iGaming, crypto, and related digital roles.
- Raw message text, source link, publication date, and service flags used for deduplication and validation.
- Extracted fields: role, vertical, company, salary, work format, location, and apply contacts.
What we do not collect
- Candidate resumes, direct messages, private chats, or any data outside public HR posts.
- Internal HR/ATS company data, private dashboards, or any NDA-bound information.
- We do not invent salaries, companies, or contacts when they are absent in the source.
Dataset limitations
- This is a market slice based on public Telegram channels, not a full model of the entire hiring market.
- Some fields are extracted automatically, so errors may happen in roles, verticals, salaries, and company names.
- Duplicates across channels are merged into one canonical card, so publication count and unique jobs count are not the same thing.
- Ukrainian-language vacancies are currently excluded from publication, although raw source messages may still exist in the pipeline layer.
How to verify the data
- Open a job page and compare its text, contacts, and source list against the original Telegram posts.
- Use public JSON, NDJSON, CSV, and RSS feeds to recompute the metrics independently.
- Formulas, indexing thresholds, and limitations are documented on the methodology page.
How to request a correction or removal
If a job page contains an error, outdated contact, or should not be published, contact us via Telegram: @dumay.
Include the page URL, what exactly is wrong, and the original source link if you have it.