About

Who operates it

RoleInbox is built and operated by Zirui Li. The processors it relies on — for the database, payments, email and hosting — are listed by name on the privacy page.

Why truth-first

The research that started this product found the same complaint everywhere. Tools that apply for you invent work history, guess screening answers in the applicant’s name, and leave nobody able to see what was actually sent. Volume is easy to sell and easy to measure, and it is not what gets anyone hired.

So the unit we care about is one application worth sending, not a submission counter. An answer is built from career facts you entered and approved. The system does not stop a person lying about themselves; what it stops is a model reading “five years of Kubernetes required” and writing five years of Kubernetes into your name.

That principle is written into the parts of the system that are hardest to change later. An answer contradicting a limit you set can be offered to you but never committed, and the database enforces it. Missing information in a posting stays unknown instead of being rounded to a yes or a no. Every application sent leaves a receipt that can be redacted but not rewritten.

The refusals are the product. A tool that never stops is a tool that has stopped checking.

Who writes this site

Every page and article here is written by Zirui Li, the developer of RoleInbox, against the code and the product decision records the repository keeps. Where a page states what the system does, it names the file or the decision it came from.

Contact

Write to support@roleinbox.com, for data questions too.

How it works · Pricing · Home