The short version
- We collect what you give us to build CVs and track applications, plus the technical data needed to keep Rolebranch running.
- Your content goes to our AI model providers only for the task you asked for. It is never sold, used for ads or used to train models.
- If you connect an AI app such as ChatGPT or Claude, it reads and changes only what you allow, and never sees your contact details.
- Download everything or delete your account from Settings, at any time.
Controller
The controller responsible for your personal data is:
Oleksandr BurdaJülicher Str. 1244141 DortmundGermanyEmail: privacy@rolebranch.comRolebranch is the name of the service, not a separate company.
Data we process
| Kind | What it includes |
|---|---|
| Account | Your name and email address. A password, if you set one, stored only as a salted hash we can't read back. Your name and picture from Google or GitHub, and your GitHub username, if you sign in with one of them. From Apple, your name (only the first time) and your email address, which can be a private relay address Apple forwards to you. |
| Your CV and profile | Master CVs and their versions, employment history, education, skills, projects and uploaded CV files. |
| Applications | Job postings, tailored CVs, cover letters, notes, application stages, interview prep and practice answers. |
| Romy | Messages and requests you send to Romy, the files you attach to them, and its answers. On rolebranch.com without signing in, your questions and Romy's answers, tied to your browser by a random id. |
| Credits | Your credit balance and the history of Romy runs. |
| Connectors | The AI apps you connect (such as ChatGPT, Claude or Le Chat), the permissions and monthly Romy credits you allowed each one, and a record of each call it makes: the tool, the time, how long it took, whether it worked and the application or Romy run it touched. Never what the app sent or what it received. |
| Support | Requests you send, any conversation you attach and your replies to our emails about them. When you're signed in, your credit balance and recent Romy runs. Signed out, your email address, confirmed with a code, and the page you wrote from. |
| Technical | IP address, browser and device type, sign-in times, failed password attempts and security logs. A random id for your browser when you use Romy or a form on rolebranch.com without signing in. A technical record of each Romy request, without its content. Usage analytics only with your consent. |
| Free ATS check | The PDF you drop on rolebranch.com/ats-check and what a parser read from it, tied to your browser by its random id; your email if you continue into an account from the result. |
Rolebranch isn't designed for sensitive details, such as health, religion or union membership. Please leave them out of your CV and your messages to Romy.
Why we process it
The legal bases are these: where a purpose is needed to provide the service you asked for, art. 6(1)(b) GDPR; where we name our legitimate interest, art. 6(1)(f); where we rely on your consent, art. 6(1)(a).
- To create and maintain your account, let you sign in with a link, Google, Apple, GitHub or a password, and let you create, import and manage CVs. This is needed to provide the service you asked for.
- To tailor CVs, prepare cover letters, manage applications and prepare interviews with Romy. Also needed to provide the service.
- To let an AI app you connect read and change your Rolebranch data when you ask it to, within the permissions you gave it on the Allow page. Needed to provide the service you asked for. We record each call so you can see it under Connectors and so we can stop misuse; see AI apps you connect.
- To answer your support requests. A request holds your email, your message and, if you choose, the Romy conversation. When you're signed in it also includes your credit balance and recent Romy runs, so we can see what happened. When you write without signing in, we first email a six-digit code to your address; the request reaches us only once you enter it, and one you don't confirm is deleted when its code expires, after 30 minutes. If the address belongs to a Rolebranch account, the request joins that account. Answering our emails about a request adds your reply to it. Requests you send signed out are kept for 2 years after they're closed.
- To email you about your own account: a welcome when you sign up and, after a while away, at most three reminders about your applications and credits until you come back. For this we keep the date you last used Rolebranch, until your account is deleted. This is our legitimate interest in helping you use the service you signed up for. You can object any time: every reminder has a link that stops them in one click, and Settings › Notifications turns them off.
- To email you news and tips from Rolebranch, at most twice a month, in your email language, but only if you said yes: by ticking the box on the welcome step after sign-up (nothing is pre-ticked) or by turning news on in Settings › Notifications. This is your consent, which you can withdraw at any time. We keep when and where you said yes or no and the wording you saw, so we can show it; which news each address got and when, so nobody gets the same email twice; and whether you came back to Rolebranch within seven days of one. You can stop news any time, free and as easily as it started: every news email has a link that unsubscribes you in one click, your inbox's own unsubscribe button does the same, and Settings › Notifications turns news off. An address that bounces or marks news as spam gets no more of it.
- To answer questions you ask Romy on rolebranch.com without signing in. This is needed to give you the answer you asked for.
- To run the free ATS check you ask for on rolebranch.com. The file is read once and kept with its result for 30 minutes, then deleted, unless you continue into an account from the result: then it becomes that account's import. Needed to give you the result you asked for.
- To keep Rolebranch secure and prevent abuse: limits on how often one browser or network can use Romy and the forms, and how often an address or network can try a password, a bot check before a form sends email or Romy starts, and a check that a new password hasn't appeared in a known data breach (only the first five characters of a one-way fingerprint of it leave Rolebranch, never the password). This is our legitimate interest.
- To keep Romy fast, reliable and affordable. For each Romy request we record which job ran, the AI model, how long it took, its size in tokens, its cost and any error. The record carries a pseudonym instead of your account, isn't linked to analytics, and never holds what you sent or what Romy answered. This is our legitimate interest, and you can object to it.
- To learn which features help, from analytics you allowed. This is your consent, and you can withdraw it.
We make no decision about you by automated means that has legal or similarly significant effects (art. 22 GDPR). The CV score and the match score are hints for you alone; no employer sees them, and nothing is applied without your review.
AI processing
When you use an AI feature, we send the relevant parts of your profile, CV, job posting or request to our AI model providers (Anthropic, OpenAI or Google, through Vercel AI Gateway), only to produce the result you asked for. The result comes back to your account. We don't use your content to train AI models.
Files you attach to a message to Romy (PDF, Word, text or images) go to the AI model provider with that message, so Romy can read them. When you turn on web search in Romy's chat and approve a search, Romy searches the web with Perplexity, through Vercel AI Gateway. Perplexity receives only the search terms Romy writes, never your CV or your files. When you paste a link, Rolebranch reads that public page from our servers, so the website sees our request, not your browser.
To see how well Romy works, our monitoring provider in the EU receives a technical record of each request: the job, the model, timings, token counts, cost and errors, under a pseudonym. It never receives your CV, your messages or Romy's answers.
AI-generated content may contain errors. Review it before you use it in an application. More about AI and your data.
AI apps you connect
You can connect Rolebranch to an AI app you use, such as ChatGPT, Claude, Le Chat or another app that works with MCP. You choose the app, you sign in to Rolebranch to allow it, and you choose what it may do: read your master CVs and applications, add and update applications, ask Romy for a tailored CV, cover letter or interview preparation (using the credits you allowed), and suggest changes to a CV for you to review.
- What the app receives. Only what it asks for to answer you, within those permissions: for example a master CV, an application with its posting and notes, or Romy's result. Contact details on your CVs and your recruiters' contact details are never sent to an app.
- Who handles it there. The app's provider (for example OpenAI for ChatGPT, or Anthropic for Claude) receives that data because you asked your app to fetch it. The provider handles it under its own privacy policy and your settings there; it is not our service provider. What you send from the app to Rolebranch, such as a job posting or notes, is handled under this policy.
- What it can't do. An app can't apply to jobs or contact anyone for you, delete anything, accept Romy's drafts or change your account settings. Drafts and suggested changes wait for you in Rolebranch.
- What we record. For each call: the tool, the time, how long it took, the outcome and the application or Romy run it touched. Never the arguments or the results. You see these under Connectors.
- Stopping it. Disconnect an app under Connectors at any time; it loses access at once. What the app already received stays in that app until you delete it there.
Service providers
We use a small number of service providers for hosting, the database, sign-in, email, bot protection, AI processing and web search. Each one receives only what its job needs, and each is named here with where it is based. We don't sell personal data or share it for advertising.
| Type of provider | What it does | What it receives |
|---|---|---|
| Hosting and file storage (Vercel, in Frankfurt, EU) | Runs the site and app and stores files you upload | Everything in transit, uploaded files |
| Database (Neon, in Frankfurt, EU) | Stores your account and content | Your account and content |
| AI model providers (Anthropic, OpenAI and Google, all in the United States, through Vercel AI Gateway) | Power Romy: Claude for tailoring and help answers, GPT and Gemini for the other tasks and as fallbacks | Only the content a task needs, including files you attach for Romy, never to train their models |
| Web search (Perplexity, United States, through Vercel AI Gateway) | Searches the web for Romy when you turn on web search and approve a search | The search terms Romy writes, never your CV or your files |
| Email (Resend, in Ireland, EU) | Sends sign-in links, address confirmations, password emails, request codes, support replies, the welcome email, reminders and news, and receives your replies to our emails | Email address and the message |
| Bot protection (Cloudflare Turnstile, on Cloudflare's global network) | Checks that a person, not a bot, sends a form or starts Romy on rolebranch.com. It sets no tracking cookies | Your IP address and your browser's technical details, for that check only |
| Product analytics (PostHog, EU cloud) | Shows which features help | Usage events, only with your consent |
| Page and performance analytics (Vercel Web Analytics and Speed Insights) | Counts page visits and measures how fast pages load. It sets no cookies | The page address without its query, your browser and device type, and load times, only with your consent |
| AI request monitoring (PostHog, EU cloud) | Shows how fast and reliably Romy answers, and what each request costs | A technical record of each Romy request under a pseudonym, never its content |
| Error monitoring (Sentry, EU) | Tells us when something breaks | Technical details of the error |
| Breached password check (Have I Been Pwned) | Tells us whether a new password has appeared in a known data breach | The first five characters of a one-way fingerprint of the password, never the password or who you are |
| Sign-in providers (Google, Apple and GitHub, United States) | Google, Apple or GitHub sign-in, only if you choose it | Your sign-in request. They send us your name and email, Google and GitHub your picture, and GitHub your username |
Your account, content and files are stored in the EU. Some providers are companies based outside the EU, or process data outside it (the AI model providers, the web search provider and sign-in providers in the United States, and Cloudflare's global network); those transfers rely on the EU Standard Contractual Clauses or the EU–US Data Privacy Framework. Questions about any of them go to privacy@rolebranch.com.
How long we keep it
- Account and document data: while your account is active, or as long as needed to provide the service.
- Files you attach to a message to Romy: as long as that conversation exists. A file you upload but never send is deleted after 24 hours.
- When you delete your account, we delete your data, except anything the law requires us to keep.
- Download archives: 24 hours, then the link stops working and the file is removed.
- Analytics, Romy request records and error reports: up to 12 months.
- Support requests and attached conversations: 2 years after the request is closed. Conversations with Romy on rolebranch.com without signing in: 30 days after their last message.
- Connectors: an app's connection, while your account exists or until you remove it; the record of each call, 90 days.
- Free ATS check: the file and its result, 30 minutes, then deleted; a file you carried into an account is that account's upload.
- Backups: deleted data leaves our database backups within 7 days.
- News: your yes or no, and which news you got, while your account exists.
Your rights
Depending on the law that applies, you have these rights:
- Access and download
Settings › Export sends you a ZIP with all your data. The link works for 24 hours.
- Correct
Edit your profile and content in the app, or ask us to fix what you can't.
- Delete
Settings › Delete account. Confirm with your email; files go first, then records. It can't be undone.
- Restrict or object
Ask us to limit or stop some processing, such as analytics or the records of your Romy requests.
- Object to news
You can object to news at any time, free and without giving a reason, and we then stop at once: the link in any news email, your inbox's unsubscribe button or Settings › Notifications.
- Withdraw consent
Change your cookie choice at any time from the footer, or in the app under Settings › Account › Your data. Disconnect an AI app under Connectors.
- Complain
You can complain to a data protection authority, such as the one where you live. The one responsible for Rolebranch is the Landesbeauftragte für Datenschutz und Informationsfreiheit Nordrhein-Westfalen (LDI NRW), ldi.nrw.de.
Cookies
We use a few cookies to keep you signed in, remember your settings and tie a conversation with Romy on rolebranch.com to your browser. Analytics cookies are set only if you allow them. There are no advertising cookies. The cookie policy lists every one and how to change your choice.
| Name | Purpose | Type | Kept for |
|---|---|---|---|
__Secure-rolebranch.session_token | Keeps you signed in | Essential | Until you sign out, up to 7 days |
__Secure-rolebranch.state | Protects a Google, Apple or GitHub sign-in while it runs | Essential | 5 minutes |
rolebranch.signed-in | Tells rolebranch.com you're signed in to the app, so its header offers Open Rolebranch. It holds nothing about you | Set when you sign in | Until you sign out, up to 7 days |
rolebranch.sign-in-email | Remembers the address you asked a sign-in link for, so an expired link can send a new one | Essential | Until you sign in, up to 7 days |
rolebranch.last-sign-in | Remembers how you last signed in (Google, Apple, GitHub, a link or a password), so the sign-in page can mark it. It says nothing about who you are | Set when you sign in | 180 days |
rolebranch.visitor | Ties a conversation with Romy, and the limits on Romy and the forms, to your browser when you're not signed in. A random id that says nothing about who you are | Essential | 30 days |
rolebranch.locale | Remembers the language you read Rolebranch in | Essential | 1 year |
cf_* | Cloudflare's check that a person, not a bot, sends a form or starts Romy on rolebranch.com. Set only while that check runs; it tracks nothing | Essential | Up to 30 minutes |
rolebranch.tz | Shows times in your time zone | Essential | 1 year |
rolebranch.consent | Remembers your analytics choice | Essential | 1 year |
rolebranch.appearance | Remembers light or dark mode | Set when you change it | 1 year |
rolebranch.sidebar | Remembers whether the sidebar is open | Set when you change it | 1 year |
rolebranch.help | Remembers where Romy's help button sits in the app and whether her window is open | Set when you change it | 1 year |
rolebranch.romy | Remembers where Romy's button sits on rolebranch.com | Set when you move it | 1 year |
rolebranch.name-skipped | Remembers that you skipped adding your name, until you next sign in | Set when you skip it | 30 days |
ph_* | Product analytics: which features are used | Only with your consent | Up to 1 year |
__Secure-rolebranch.session_tokenKeeps you signed inEssential · Until you sign out, up to 7 days__Secure-rolebranch.stateProtects a Google, Apple or GitHub sign-in while it runsEssential · 5 minutesrolebranch.signed-inTells rolebranch.com you're signed in to the app, so its header offers Open Rolebranch. It holds nothing about youSet when you sign in · Until you sign out, up to 7 daysrolebranch.sign-in-emailRemembers the address you asked a sign-in link for, so an expired link can send a new oneEssential · Until you sign in, up to 7 daysrolebranch.last-sign-inRemembers how you last signed in (Google, Apple, GitHub, a link or a password), so the sign-in page can mark it. It says nothing about who you areSet when you sign in · 180 daysrolebranch.visitorTies a conversation with Romy, and the limits on Romy and the forms, to your browser when you're not signed in. A random id that says nothing about who you areEssential · 30 daysrolebranch.localeRemembers the language you read Rolebranch inEssential · 1 yearcf_*Cloudflare's check that a person, not a bot, sends a form or starts Romy on rolebranch.com. Set only while that check runs; it tracks nothingEssential · Up to 30 minutesrolebranch.tzShows times in your time zoneEssential · 1 yearrolebranch.consentRemembers your analytics choiceEssential · 1 yearrolebranch.appearanceRemembers light or dark modeSet when you change it · 1 yearrolebranch.sidebarRemembers whether the sidebar is openSet when you change it · 1 yearrolebranch.helpRemembers where Romy's help button sits in the app and whether her window is openSet when you change it · 1 yearrolebranch.romyRemembers where Romy's button sits on rolebranch.comSet when you move it · 1 yearrolebranch.name-skippedRemembers that you skipped adding your name, until you next sign inSet when you skip it · 30 daysph_*Product analytics: which features are usedOnly with your consent · Up to 1 year
Age
Rolebranch is for people aged 18 and over. We don't knowingly collect data from anyone younger.
Contact and changes
For privacy requests, write to privacy@rolebranch.com. We post changes to this policy here and email you about important ones before they apply.