Security, privacy, upload guidance, and deletion controls
KYBN Trust Center
KYBN is an upload-based HR review and output workspace. It is not your HRIS, payroll system, or system of record. It helps teams review employee exports, generate reporting outputs, and keep support files with clearer traceability.
How KYBN handles uploaded HR files
KYBN starts from uploaded HRIS exports or maintained employee spreadsheets. The workflow is designed so teams can review fields, snapshot logic, missing values, duplicates, changes, and exceptions before outputs are generated.
This is an intentional upload model, not a live HRIS sync. It keeps setup lighter for recurring review workflows and avoids requiring direct system-of-record access for early reporting and follow-up use cases.
Security controls
- HTTPS transport for web and API traffic in production environments.
- Access controls and least-privilege admin workflows.
- Operational logging for generation, checks, support, and lifecycle events.
- Retention and deletion workflows designed for customer-controlled cleanup.
Privacy and model use
Customer-uploaded datasets are processed only as needed to provide the requested workflow. KYBN does not sell customer data, and customer-uploaded datasets are never used to train or fine-tune shared foundation models.
Retention and deletion
KYBN separates uploaded raw files, generated outputs, comparison snapshots, and lifecycle metadata. Deletion means removal from active application storage and product access paths, while retaining minimal lifecycle metadata where needed for traceability.
Data minimization guidance
Upload the fields needed for the workflow, not the entire HRIS database. For most reporting and review workflows, start with the minimum necessary fields and avoid uploading unrelated sensitive data.
Usually appropriate to upload
- Employee ID
- Hire date
- Termination date
- Employee status
- Employment type or worker type
- Department
- Location
- Job title
- Manager
Usually avoid unless needed
- SSN or government ID
- Bank details
- Medical or health data
- Date of birth
- Home address
- Detailed compensation fields
Uploads vs API access
KYBN currently works from uploaded HRIS exports or maintained employee files rather than a public API-first integration model. That makes it a better fit for controlled, repeatable review cycles than for real-time sync or live workflow automation.
If your team needs direct system-to-system sync, continuous refresh, payroll processing, or system-of-record updates, KYBN may not be the right fit.
Vendor review and DPA questions
If your company needs vendor review, DPA information, or security and privacy follow-up before uploading employee data, contact us with the scope of your review. We can help route product, privacy, and deletion questions to the right place.
Trust questions
Is KYBN safe for employee data?
KYBN is designed for intentional HR file review workflows with security, privacy, retention, and deletion controls. Each company should still complete its own vendor and security review before uploading employee data.
Does KYBN require API access to my HRIS?
No. KYBN currently works from uploaded HRIS exports or maintained employee files. That makes it a review and output layer, not a live system integration tool.
What sensitive fields should I avoid uploading?
Avoid uploading fields such as SSN, bank details, health data, DOB, and home address unless the selected workflow explicitly requires them. Start with the minimum necessary fields for the task.
When is KYBN not the right fit?
KYBN is not the right fit if you need real-time HRIS sync, payroll processing, employee self-service, approval workflows, or a system-of-record update path.