For the standard RChilli Resume Parser, RChilli uses its proprietary, internally developed artificial intelligence, natural language processing, and machine-learning parsing engine.
The standard parsing service does not require OpenAI, ChatGPT, Azure OpenAI, public large language models, or other external AI APIs to extract candidate information from resumes.
Under the standard Resume Parser configuration:
- Candidate resume content is not transmitted to an external AI or LLM provider.
- Parsed candidate or applicant information is not sent to a third-party AI service.
- Resume processing is performed to complete the requested parsing transaction.
- Resume content and parsed personally identifiable information are not persistently stored by RChilli after parsing.
RChilli also offers optional LLM-based parsing capabilities for certain use cases or implementations. These optional features may use services such as OpenAI or Azure AI and are separate from the standard Resume Parser workflow.
The optional LLM capability is controlled through the isllmparser configuration setting, which is documented as disabled by default. This means that LLM processing is not automatically applied to every parsing request. It must be specifically enabled and configured for the relevant account, product, or API request.
Where optional LLM processing is enabled, customers may request confirmation regarding:
- Which AI provider and model are being used
- Whether the complete resume or only selected fields are transmitted
- The region where processing takes place
- Whether the provider retains prompts, resume content, or outputs
- Whether customer data is used for model training
- Applicable retention and deletion periods
- Whether enterprise privacy or zero-retention controls are enabled
- Whether the provider is included in RChilli’s subprocessor documentation
- Whether the optional LLM functionality can be disabled
Customers who require account-specific confirmation should contact their RChilli account representative or support@rchilli.com.
Comments
0 comments
Please sign in to leave a comment.