Security and trust
A restrained security model for a verified hiring marketplace.
Jobsupa is built for employers and candidates who need to understand verification, data handling, and access controls before marketplace access expands.
Security overview
Production changes move through the Jobsupa release workflow. Deployment credentials, server-side API keys, and internal service credentials are kept out of the browser bundle.
Data handling principles
Pilot data is scoped to the hiring use case being evaluated: employer contact details, role context, candidate profile signal, and operational data needed to run the pilot.
Access control approach
Employer access starts with review-based onboarding. Candidate access is limited during rollout and can be configured around the pilot's verification requirements.
Pilot review process
Before launch, Jobsupa reviews role data, candidate flow, recruiter access, retention expectations, and any security or procurement questions raised by the employer.
Retention and deletion expectations
Retention expectations are defined during the pilot review. Employers can raise deletion, export, or access requirements before candidate review begins.
ScaleMule relationship
ScaleMule is the underlying production platform used for Jobsupa service APIs and deployment controls; customer-facing Jobsupa pages expose only public configuration.
Pilot review
Reviewed before employer rollout
Jobsupa does not require employers to accept a generic trust story. The first pilot conversation is used to clarify the data and access model.
- Employer and recruiter access needs
- Candidate verification and communication flow
- Role data, profile data, and shortlist handling
- Retention, deletion, export, or procurement requirements