Pre-launch · First corridor: US→India

Employment records require clear purpose, access, and custody.

Sekai’s product does not yet collect candidate or employer information. These are the trust requirements that must be met before it does.

No certification, completed control, uptime, data-residency, or legal-compliance claim is made here.

Before collection

Explain why the information is needed.

People should know the purpose, what is optional, who may use the information, and how long it may be retained.

01
Purpose and consent
Connect every request to a real role or employment need and make role-specific sharing understandable.
02
Minimum necessary data
Collect only what the current step needs rather than building an indefinite profile by default.
03
Third-party disclosure
Name the providers, purpose, access, location, retention, and accountable owner before use.

During use

Employer, candidate, worker, operator, partner, and support roles need permissions that match their responsibility.

01
Role-based access
Give people only the information they need for the work they own.
02
Correction and review
Provide a human path to question, correct, or update important information.
03
Audit and incident ownership
Record sensitive access and changes, then define detection, containment, communication, and recovery.

At transition or closure

New purposes, owners, access, lawful retention, deletion limits, and offboarding steps should be explicit.

01
Candidate-to-worker transition
Explain which information moves, why, who can see it, and what new obligations apply.
02
Retention by record type
Candidate, interview, contract, payroll, support, and audit records may need different schedules.
03
Deletion and lawful exceptions
Make correction, withdrawal, deletion requests, identity checks, and required retention understandable.

Questions

Does this website collect role or candidate data?

No local form is used. Calendly and Tally collect only what a visitor chooses to submit under those services’ own privacy practices.

Does Sekai have security certifications?

No certification or completed-control claim is represented on this pre-launch site.

Can people request correction or deletion?

Correction and deletion are product principles. The final workflow and lawful retention exceptions must be defined before live data collection.

Start a conversation

Email launch@getsekai.com. We will separate the principle, current fact, and work still required.