Roleford
Sign inSee your matches

Privacy policy

Last updated

Who is responsible

Roleford is run by Vitalii Maslianok, a sole trader in Ukraine, at 14 Prospekt Martynova, Sofiivska Borshchahivka, Bucha district, Kyiv region, 08156, Ukraine, the controller of the personal data described here. Contact for anything about your data: hello@roleford.com.

What we collect

  • Account and sign-in: name, email address, profile picture link and account id from the sign-in method you use (GitHub, Google, LinkedIn, Microsoft, an email code or a passkey), sign-in sessions with IP address and browser, and your time zone.
  • CV and profile: the CVs and LinkedIn PDFs you upload, their text, and what you enter or edit in your profile, including your preferences for roles, places and pay.
  • Sources you connect: what your public GitHub profile and repositories show about your code, and the public profile stats of the Hugging Face, Stack Overflow, LeetCode or Kaggle handle you give us.
  • Use of Roleford: ratings, matches, applications, the drafts we generate and your edits, the emails you send through Roleford (recipients, content, attachment), hiring-process reports, tokens, achievements and your settings.
  • Analytics: the pages you open, the buttons, links and form controls you use, your browser and device type, errors and where you came from (such as a link's campaign tag). With your consent, also your IP address with an approximate location worked out from it, a random id in a cookie and recordings of your sessions (see Cookies). Whether or not you accept, also records of what you do in your account, such as signing up, rating postings, the job previews and public job pages you open while signed in, applications, tokens and purchases.
  • Purchases: your plan and a record of each purchase. Paddle collects the payment details; we don't receive your full card details.
  • Technical data: IP address, browser and server logs, used for security, rate limits and Cloudflare Turnstile.
  • How you found us: when a link brought you before you signed up, its campaign tags, its referral code, its ad click id, the name of the site it was on, the first page you opened and when (see Cookies), kept once with your account; and your answer to "Where did you hear about Roleford?", if you give one.

An account needs an email address. Matches need a CV, a LinkedIn PDF or GitHub. Everything else is optional. Please don't include details an employer doesn't need, such as health or religion, in your CV.

Why we use it, and on what basis

  • Consent (GDPR Article 6(1)(a)): analytics cookies and session recordings, and the IP address and approximate location kept with them, only if you accept them. You can withdraw it at any time (see Cookies).
  • Contract (Article 6(1)(b)): to provide the service you ask for, including sign-in, your profile, matches, preparing applications, connecting sources, sending from your mailbox, tokens, plans, service emails and interview reminders. You can turn reminders off in Profile.
  • Legitimate interests (Article 6(1)(f)): to keep Roleford secure and prevent abuse, to suggest contacts, to show your profile to recruiters and hiring companies (see Your profile and recruiters), to research companies' hiring processes, to send the morning email with new matches while you've used Roleford in the last 14 days and other emails that are on until you turn them off (in Profile, or with the unsubscribe link in each email), to learn which channels bring people to Roleford, to measure how Roleford is used: counting visits without cookies, and keeping records of what you do in your account, and to maintain and improve the service.
  • Legal obligation (Article 6(1)(c)): for records we must keep, such as for tax.

Ukrainian law (Law No. 2297-VI) allows processing on the same grounds. Matching ranks postings for you, and our recruiter search ranks candidates for recruiters, who make their own decisions; we don't make decisions with legal or similarly significant effects about you by automated means.

AI. To generate drafts and read CVs, we send your CV text, profile and the posting to our AI provider (currently Anthropic). AI output can be wrong.

Gmail. With Gmail, Roleford asks only for permission to send and can't read your mailbox. Roleford's use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. We keep that permission, encrypted, until you disconnect Gmail in Profile, remove Roleford's access in your Google Account or delete your account. We don't share or sell data from Google APIs, or use it for advertising or to train AI models.

Your profile and recruiters

Recruiters and hiring companies use our recruiter search to find candidates. When you join Roleford, we describe you there with what you write in your profile: your name, headline, where you live, the languages you speak, your current level, notice period, work permit, experience, education, skills, what you are looking for and the profile links you add. Recruiters also see what we learn about you from your public professional profiles, such as your skills, level, employer, location and languages. These include GitHub, LinkedIn, Stack Overflow, Hugging Face, social profiles and personal websites, including pages found through public search engines. We connect those profiles to your Roleford profile through your GitHub account, the profile links you add, or your verified email address when your public GitHub profile shows the same one.

Recruiters can see these details unless you turn on Hide my profile from recruiters in Profile → Privacy. Any recruiter or company using our recruiter search, including your current employer, can see this; to stop it, turn on Hide my profile from recruiters. While you use Roleford, recruiters see that you are open to work; Let recruiters find me only shows you higher in their lists. We don't show them your CV files or their text, your expected salary, the companies you never want to see, the email address of your Roleford account (an address your public GitHub profile shows stays visible, as it is public), your drafts and applications, or payment details.

  • Your CV: when you upload a CV or a LinkedIn PDF, we read its text to suggest details for your profile and to describe you in our recruiter search. Recruiters may see what we read from it; you can change it or tell us it is wrong.
  • What we show you: when we find something about you in your public profiles, we show it to you with its source, such as "from your GitHub" or "from public profiles", and you can add it, change it or tell us it is wrong. When you tell us something is wrong, we stop using it for your matches and in our recruiter search.
  • Contacts: like anyone at a company, you may be suggested to other job seekers as a contact there, using what People we suggest as contacts lists and the experience you give in your profile. Hide my profile from recruiters doesn't change this; to opt out, use the link in any email sent through Roleford or write to hello@roleford.com.
  • Basis and your choice: legitimate interests (Article 6(1)(f)), so that recruiters can find you for work. You can object at any time by turning on Hide my profile from recruiters: our recruiter search then stops using the details you gave us and your use of Roleford as a sign you are open to work; what your public profiles show stays, and what you told us is wrong stays out.
  • Deleting your account removes everything you gave us from our recruiter search, including the link to your Roleford profile and the open-to-work signal. What it shows from your public profiles is not affected.

People we suggest as contacts

This section is for people suggested to job seekers as contacts at a company, whether or not they use Roleford. It is the information GDPR Article 14 requires.

  • What we use: name or username, role and seniority, employer, GitHub account id, links to public profiles, and the email address the person shows on their own GitHub profile.
  • Sources: public GitHub profiles (email, name, links, company and bio); LinkedIn headlines and profile text found through public search engines; public bios on X, Bluesky, Mastodon, personal websites, Stack Overflow and Hugging Face; and, for Roleford users, the experience in their profile.
  • Purpose and basis: to let a job seeker write to someone on the team they are applying to. Basis: legitimate interests (Article 6(1)(f)). Suggestions and emails per address are limited.
  • Recipients: the job seeker shown the suggestion; the AI agent they connected to Roleford, if any, and the company behind it; their mail provider if they email you; our AI provider for drafting follow-ups; and our service providers (see Who receives data). Transfers outside the EU are as described under International transfers.
  • Retention: until the job seeker's application is closed, marked hired or deleted, and, if nobody emailed you, no longer than a fixed period after the suggestion. A hash of the address is kept for a short fixed period to apply the limits. If a job seeker emails you, the email stays in their history until they delete their account. After an opt-out, only a hash of your address is kept.
  • Not informed directly: we don't write to people who are suggested but never emailed, because doing so would mean sending an unsolicited email and would involve a disproportionate effort (Article 14(5)(b)). We publish this information here instead, and every email sent through Roleford links to it.

Opt out or object

Use the link at the end of any email sent through Roleford, or write to hello@roleford.com. We then stop suggesting the address and refuse sends to it. We keep a hash of the address so the opt-out keeps working. You also have the rights under Your rights.

Your AI agents

You can connect an AI agent (such as Claude, Cursor or another app you use) to run your job search on Roleford. Once you allow it, the agent and the company that provides it receive your profile, the jobs matched to you, the jobs you unlock with what they include, your applications, and the people at those companies we suggest writing to. What they do with it is under their own terms and privacy notice; an email the agent sends for you is sent by you, not through Roleford.

We keep each connection, when it was made and last used, and which actions and token spends came from an agent. Disconnect an agent at any time in Profile → Your agents; deleting your account disconnects them all.

Who receives data

  • Service providers that process data for us, currently including Anthropic (AI), Google (email, Google sign-in, Gmail sending), Microsoft (Microsoft sign-in, Outlook sending), Cloudflare (network, security, backups), Hetzner (hosting) and PostHog (product analytics, with data stored in the EU).
  • Paddle.com Market Ltd, which sells our plans and packs as merchant of record under its own privacy notice.
  • The sources you connect, when we read the public profile you name.
  • Recruiters and hiring companies using our recruiter search, as described under Your profile and recruiters.
  • Employers and people you choose to email.
  • The AI agents you connect, and the companies behind them, as described under Your AI agents.
  • Other job seekers, who see accepted hiring-process reports without your name and, if you are suggested as a contact, what People we suggest as contacts describes.
  • Our professional advisers, and authorities where the law requires.
  • Someone who takes over Roleford, if the business is transferred.

International transfers

Our servers are in the EU (Finland). The operator works from Ukraine, which has no EU or UK adequacy decision. Some providers are in the United States or the United Kingdom. For the UK we rely on its EU adequacy decision; for US providers, on the EU-US Data Privacy Framework (and its UK extension) where the provider is certified, otherwise on standard contractual clauses. Recruiters and hiring companies using our recruiter search may be outside the EU and the UK; for them we rely on an adequacy decision where there is one, otherwise on standard contractual clauses. Write to hello@roleford.com for a copy.

How long we keep it

  • Account data: until you delete your account; sign-in sessions until they expire or you sign out.
  • After deletion: a one-way hash of your email and sign-in ids with the rewards already paid, for as long as Roleford offers sign-up rewards; a one-way hash of your account id, so nothing from the deleted account is added back; a short-lived marker that the account was deleted; data the law makes us keep, for the period it sets; data needed for a legal claim, until it is settled or time-barred.
  • Opt-out records: a hash of the address, for as long as Roleford runs or until the person asks us to remove it.
  • Logs and security data: for a fixed rotation period, then deleted automatically; longer only while a specific incident is investigated.
  • Analytics: for a fixed period set in our analytics provider, then deleted automatically, and session recordings for a shorter one. Deleting your account deletes the analytics tied to it.
  • Backups: each is deleted automatically at the end of a fixed rotation; deleted data leaves the backups when the last backup holding it is deleted.
  • Suggested contacts: as described under People we suggest as contacts.

Your rights

Under the GDPR, the UK GDPR and Ukrainian law, you can ask for access to your data and a copy of it, and for its correction, deletion, restriction or portability. Where we rely on consent, you can withdraw it at any time. For analytics cookies, use Cookie settings at the bottom of our public pages, or Profile → Privacy.

Right to object. Where we rely on legitimate interests, you can object at any time on grounds relating to your situation. To object to recruiters seeing what you gave us, turn on Hide my profile from recruiters in Profile → Privacy.

Profile → Privacy has Download my data and Delete my account. For anything else, write to hello@roleford.com. We reply within the time the law requires and may ask you to confirm your identity. You can also complain to a data protection authority: in the EU, where you live or work or where the alleged infringement took place; in the UK, the ICO; in Ukraine, the Ukrainian Parliament Commissioner for Human Rights.

Cookies

Necessary cookies. Roleford sets cookies needed to provide the service: the sign-in session and short-lived security cookies during sign-in and when you connect a mailbox. Cloudflare may set security cookies, including for Turnstile, and Paddle's checkout uses its own cookies under Paddle's policy. These don't need consent.

Where you came from. A cookie, rf_ft, is set when you open Roleford from a link or another site that says where you came from: it holds that link's campaign tags, referral code and ad click id, the name of the site it was on, the first page you opened and when, for 30 days. When you sign in, it is read once and deleted from your browser; it is kept with your account only if you followed it before you signed up. It holds nothing else, isn't shared, and isn't used to follow you on other sites. To refuse it, delete the rf_ft cookie in your browser's settings for roleford.com before you sign up; blocking every cookie of roleford.com also blocks signing in.

The job you opened. A cookie, rf_job, is set when you open a job on one of our public pages before signing in. It holds that job's id and the page you opened it from, for one day, so we can take you to the job after you sign in. It is deleted once you're there. The job and the page are then kept with your account, to show you the job again until you start it or remove it, and to count how many people sign up from each of our job pages.

Signed in. A cookie, rf_in, is set while you use Roleford signed in, for 30 days, and deleted when you sign out. It holds nothing about you. Our public job pages read it so that only a signed-in visit tells us which of them you open.

Analytics cookies and session recordings, with your consent. If you accept them in the cookie banner, our analytics provider, PostHog, keeps a random id in a cookie and in your browser's storage on roleford.com, keeps your IP address and an approximate location worked out from it, and records your sessions: how the pages look and where you click and scroll. Recordings hide everything you type and, inside the app, all the text on the page. Once you sign in, your analytics are linked to your account id, name and email.

Without your consent. If you reject them, or haven't answered, PostHog keeps nothing in your browser except your answer. We still count page views and clicks without cookies. PostHog tells visits apart by a code it computes on its servers from your IP address and browser, which changes every day. It then drops your IP address and doesn't work out where you are. We don't use that code to link your visits to your account. Records of what you do in your account, with your account id, name and email, are kept in our analytics provider either way (see Why we use it).

Privacy signals. If your browser sends Global Privacy Control or Do Not Track, we treat it as a rejection, whatever you answered before, and don't show the banner. To accept analytics cookies, turn that setting off first.

Changing your mind. Use Cookie settings at the bottom of our public pages, or Profile → Privacy. Rejecting after accepting stops recording at once.

Age

Roleford is only for people aged 18 and over.

Changes

We may update this policy by posting a new version here with a new date. Where the law requires, we'll notify you.