Privacy

• There is no tracking. No analytics script, no advertising tag, no session recording, and nothing about you is sold or shared with anyone for their own purposes.
• Your resume and your records go to an AI model, because reading them is the product. Which parts, for which job, is set out below.
• Postings, scores and alerts are deleted seven days after the posting went up. That is the app's own rule, not a retention policy written afterwards.
• Your card never reaches Roliii. Polar takes the payment and sends back a status.
• One address answers all of it: support@roliii.com.

Roliii is run by an individual established in Cameroon, reachable at support@roliii.com. That is the person answerable for everything on this page the controller, if you are somewhere that uses the word.

Roliii is market-agnostic on purpose, so people use it from everywhere. Where the General Data Protection Regulation applies to you, it applies to this processing, and the rights further down are the ones it gives you rather than a summary of them.

Everything below comes from you, or from something you did in the app. Nothing is bought from a data broker, and nothing is inferred about you from anywhere else on the web.

Your accountwhile the account exists

The email address you signed up with, your name, and your password stored as a hash that cannot be read back. Also the sessions that keep you signed in and the codes behind the confirmation and reset links, which expire after thirty minutes.

Your profilewhile the account exists

The contact details on it, your headline and summary, your skills, how soon you could start, and what you are looking for: titles, work mode, employment type, pay expectation, the responsibility band, industries and locations.

Your recordswhile the account exists

Roles you have held, projects, education, languages and links whatever you entered or accepted from a resume read. These feed the drafts. They are not used to match you to anything.

Your resumeuntil you replace or delete it

The PDF itself, its name, its size and when it landed, plus whatever a read of it proposed while that proposal is waiting for you to accept or discard it. There is one resume per account and no history: replacing the file destroys the old one.

What was matched to you7 days

For each posting scored against your profile: the score out of 100, the five factors behind it, and whether you saved or dismissed the role. Deleted with the posting seven days after it was published, whether or not you ever looked at it.

What you were told7 days

Each alert raised for you, whether you have read it, and whether it went out by email. Pruned on the same seven-day clock, because an alert about a deleted posting is a bell nobody can answer.

Your draftsuntil you delete them

The tailored resume, the cover letter and the screening answers written for a posting, with the log of every instruction you gave and what it changed. Deliberately not deleted with the posting: it is your own writing about a job you may well have applied for.

Your applicationsuntil you delete them

Which postings you told us you applied to, when, and what happened next. Roliii never submits anything, so this exists only because you said so.

Your planwhile the account exists

Which plan you are on, and if you pay the subscription identifier and status Polar sends back, plus the renewal date. No card number, expiry or billing address ever reaches Roliii.

What the models costkept as the spending record

One row per model call made for you: which workload it was, how many tokens it used and what it cost. It is the only thing bounding what an account can spend, so it survives the postings it was about.

When you were last hereone timestamp, overwritten

A single time, rewritten when you open the app. It is what stops a realtime alert interrupting you about a role already on your screen.

Request logsheld by the host, not by Roliii

Serving a page writes the usual line: an IP address, the path asked for, and the browser's user-agent string. Roliii keeps no copy and reads nothing from it. There is no analytics script, no advertising tag and no session recording anywhere on roliii.com.

The seven-day rows are not deleted on request; they are deleted by the sweep that runs every ten minutes, whether anyone asks or not. Roliii is not a job board, and a posting older than a week has already failed the only thing it was for.

To run the thing you signed up forperformance of a contract

The account, the profile, the hunt, the scoring, the drafts, the alerts you asked for, and the plan you chose. Without this data there is no service to provide a hunter with no profile has nothing to hunt for.

To send you emailconsent, withdrawable

Role alerts go out only to candidates who left that channel switched on. Every one of them carries a link that turns it off from the inbox, without signing in. The confirmation and reset emails are not this: they are part of running the account, and they are the only two that go out regardless.

To keep it working and stop it being abusedlegitimate interests

Sessions, the spend ledger, and the limits on how much one account can cost. The interest is keeping the service up for everybody, and it is weighed against a record that says what a model call cost rather than anything about you.

To keep the bookslegal obligation

Payment records, kept for as long as tax law requires wherever the operator and Polar are established.

Five companies, each doing one job under instruction. None of them may use what they receive for anything of their own, and there is no sixth: nothing is sold, and nothing is handed to an advertiser, a data broker, or a recruiter.

Convexthe backend

Holds the database, the resume file, the scheduled sweeps and every function that runs behind a sign-in. Everything in the list above except the request logs lives here. Based in the United States.

Anthropicreading, scoring and writing

Receives your resume when you ask for it to be read, a narrow slice of your profile when a posting is scored, and your records when you ask for a draft. Which slice, in each case, is the next section. Based in the United States.

Googlefinding postings

Runs the search half of discovery. It is sent a job title and a market the question a group of candidates has in common and never a name, an address, a resume or a record. Based in the United States.

Resendevery email

Sends the confirmation link, the reset link and the role alerts. It receives your email address and the contents of the message. Based in the United States.

Polarthe sale

The merchant of record for a paid plan. It takes the payment, holds the card details Roliii never sees, and sends back a subscription status. Based in the United States.

The site itself is served by a hosting provider, which sees the request log described above and nothing from inside your account.

Data is also handed over where the law requires it. If that ever happens you are told, unless telling you is itself against the law.

This is the part most services leave vague, and it is the part worth being exact about. Three workloads send a model something about you, and each sends a different slice.

Reading your resumethe whole document

The PDF is handed to the model as it is, because that is the only way to read a document. It runs once per file, only when you press the button, and what comes back is a proposal you either accept or discard.

Scoring a postingheadline, location, skills, preferences

And nothing else. Not your experience, not your projects, not your education or languages, and not the summary you wrote about yourself. The score is five factors, a career cannot be one of them, and the only version of that rule which can be checked is not sending the career at all.

Writing a draftyour records, and only when you ask

The opposite slice, for the opposite reason: a cover letter with no career behind it is the paragraph nobody reads. This runs when you press a button on one posting, never on a schedule.

Both providers are used through their paid API, whose terms say the content of a call is not used to train their models. Roliii trains nothing of its own on anything, ever.

A model reads each posting against your profile and returns a number out of 100 with five factors behind it. No human looks at it, which is what makes it automated processing, and every score in the app comes with the breakdown so it can be argued with.

It is a decision about a posting, not about you. It does not restrict anything: you set the threshold yourself, you see every match that clears it, and you can apply to whatever you like whatever the number says. Nothing here decides anything with a legal effect on anyone, and nothing is passed to an employer.

Roliii is run from Cameroon and every provider above processes in the United States. Whatever country you are in, your data leaves it.

Where you are in the EEA or the UK, those transfers rest on the standard contractual clauses each provider offers, which are part of the agreement the operator holds with them. A copy of what covers a particular provider can be asked for at the address below.

Most of them are a screen rather than a request. Your profile and every record on it are editable at any time on the profile screen there is no read-only copy of anything the notification schedule is on the settings screen, and every email carries an unsubscribe link.

The rest are a message. You can ask for a copy of everything held about you, for something to be corrected, for the whole account to be deleted, for processing to be restricted, or to object to it. Withdrawing consent to email stops the alerts and changes nothing else.

Deleting the account is not yet a button in the app, and that is a gap rather than a policy. Write to support@roliii.com and everything is deleted within thirty days the account, the profile, the records, the resume file, the drafts and the applications. What is kept afterwards is the payment record the tax rules require, and nothing else.

Requests are answered within thirty days and cost nothing. If you are in the EEA or the UK and the answer is unsatisfactory, you can complain to the data protection authority where you live.

• Passwords are stored as a hash and cannot be read back, by anyone, including the operator.
• Every query for a candidate's own data is reached through that candidate's identity. No function takes an owner as an argument, which is what stops one account reading another by guessing an identifier.
• Traffic is encrypted in transit, and the resume file is reachable only through your own signed-in session.
• Confirmation and reset links expire after thirty minutes, and asking for a reset never reveals whether an address has an account.

None of that makes a breach impossible. If one happens and it puts you at risk, you are told, and so is the relevant authority, inside the deadline that applies.

Roliii is not for anyone under 16 and is not aimed at them. If an account turns out to belong to someone younger it is deleted. Tell us at support@roliii.com if you believe one does.

The date at the top changes when something on this page changes. Where a change affects what is done with data already held, you are told by email before it takes effect rather than after.