Vaccination and health safety follow the law and the public-health guidance — never a blanket Kayanin rule.

The policy

Seven sections, in plain language.

1. 01

   What this policy covers — and what it does not

   Kayanin is a three-sided trust platform, not a workplace. Kayanin does not employ Workers and does not control independent employers' workplaces. The platform surfaces a trust signal; the workplace — wherever it sits — is run by the engaging party (Employer or Agency intermediary).

   This policy is intentionally general. It does not invent mandates. It does not collect medical details. It does not make compliance claims Kayanin cannot verify. It states how any vaccination, testing, disclosure, accommodation, or health-safety requirement on the platform is framed — by what authority, on what basis, and at whose cost.

2. 02

   Any requirement follows applicable law and public-health guidance

   Any vaccination, testing, disclosure, accommodation, or health-safety requirement on Kayanin follows applicable laws and public-health guidance, based on the person's location, role, and work setting.

   The framing has three parts that always travel together:

   • The authority — the requirement is set by the law of the relevant jurisdiction or by the public-health authority of that jurisdiction, not by Kayanin.
   • The basis — the requirement is keyed to one or more of the three drivers below (location, role, work setting). A requirement not keyed to a driver is not a Kayanin requirement.
   • The cost — the cost of compliance sits where the relevant law places it. Kayanin does not set the cost; Kayanin does not collect the cost; Kayanin does not police the cost. Kayanin does not charge Workers for any feature on the core flow (see /scam-prevention).

   Where the law (or the public-health authority of the relevant jurisdiction) requires vaccination, testing, accommodation, or disclosure, the requirement applies at the workplace — not at Kayanin. Kayanin is the trust layer, not the workplace.

3. 03

   Location-based drivers

   A health-safety requirement can be set by the law or the public-health authority of the country, the region, the municipality, or — for cross-border remote roles — the host country the role is performed from. The same Worker performing the same role from two different locations may be subject to two different requirement sets, and the binding set is the one in force where the Worker is on a given day.

   • Country-level rules — national vaccination requirements, national testing regimes, national disclosure obligations, where they exist.
   • Region- and municipality-level rules — local lockdowns, local mask rules, local public-health emergency declarations, where they exist.
   • Cross-border remote roles — for a Worker in one country working for an Employer or Agency in another, the host-country rule (the country the work is performed from) is the controlling rule for the Worker; the engaging party's location drives the engaging party's obligations.
   • Travel-linked requirements — entry, transit, and return vaccination / testing rules set by the destination jurisdiction, where the role involves cross-border travel.

   Kayanin does not maintain a jurisdictional matrix because Kayanin cannot be the authority for any jurisdiction. The Worker and the engaging party look up the applicable rule themselves; Kayanin surfaces the trust signal so two peers can decide whether the basis for a conversation exists.

4. 04

   Role-based and work-setting drivers

   Some roles carry health-safety requirements that other roles do not — because the role puts the Worker, the customer, or the public into a higher-risk contact pattern. The drivers below are illustrative, not exhaustive.

   • Client-site roles — roles that place the Worker on a third-party site (a hospital ward, a care home, a school, a manufacturing line) where the third party's rules, including any health-safety rules, apply on top of the public-law baseline.
   • Healthcare-adjacent roles — roles that interact with patients, residents, samples, or regulated health data, where the healthcare operator's credentialing and the public-health authority's rules apply.
   • Regulated-industry roles — roles in food handling, pharmaceuticals, laboratories, or other regulated environments where the regulator's health-safety regime applies.
   • In-person service roles — roles where the Worker is in sustained in-person contact with the public (childcare, personal care, hospitality front-of-house) where the relevant public-health guidance applies.

   A role description on the listing is the place to surface any health-safety requirement that flows from the role or the work setting. The Worker and the engaging party read the requirement at the listing, not on the platform.

5. 05

   Reasonable accommodation

   Where a Worker cannot meet a vaccination, testing, disclosure, or other health-safety requirement because of a disability, a sincerely held religious belief, a pregnancy, a documented medical contraindication, or another protected ground, reasonable accommodation is the path forward. The accommodation is not a Kayanin issue; it is a workplace issue.

   The accommodation process runs between the Worker and the engaging party (Employer or Agency intermediary), under the law of the Worker's location. Kayanin's role is to keep the trust signal aligned with the public-registry cross-reference on /methodology — not to mediate the accommodation.

   Three principles travel with every accommodation request, regardless of where it is raised:

   • Interactive process — accommodation is a dialogue, not a one-sided demand. The Worker explains the constraint; the engaging party proposes a workable alternative; the two sides iterate until the constraint is met or until accommodation cannot be made.
   • Non-retaliation — a Worker who requests accommodation, or who cannot meet a requirement on a protected ground, is not penalised on the platform. The Worker Trust score is not moved by an accommodation request; the addressing is at the workplace, not on the platform.
   • Non-discriminatory enforcement — the accommodation is offered to every Worker in the same situation, against the same criteria. The criteria are the law of the relevant jurisdiction, not a Kayanin-side preference.

   Kayanin does not mediate accommodation. The path runs between the Worker and the engaging party; the path runs under the law of the relevant jurisdiction; the path runs without penalty on the trust layer.

6. 06

   What Kayanin does not do

   Kayanin operates the trust layer; it does not operate any workplace. Several things Kayanin deliberately does not do, to keep that boundary intact:

   • Kayanin does not collect medical details — no vaccination status, no test results, no diagnosis, no prescription data, no disability disclosure. The platform has no place to enter or surface any of these.
   • Kayanin does not impose blanket mandates — no platform-wide "must be vaccinated" rule, no platform-wide testing requirement, no platform-wide disclosure rule. Any such rule is set at the workplace, under the relevant law.
   • Kayanin does not make compliance claims it cannot verify — no "your listing is compliant with [jurisdiction]" check, no "all Workers meet [requirement]" attestation. The platform cannot make claims about compliance it cannot inspect.
   • Kayanin does not substitute for public-health advice — this page is not a substitute for advice from a qualified health professional, an occupational-health practitioner, or the public-health authority of the relevant jurisdiction. Where those sources conflict with this page, those sources win.
   • Kayanin does not charge Workers for compliance — the Worker side of the platform stays free of charge for any feature on the core flow (see /scam-prevention). A cost of compliance that falls on the Worker by operation of law remains the Worker's cost; Kayanin is not the channel for it.

   The boundary is non-negotiable: Kayanin is the trust layer, not the workplace. Any feature on the platform that looks like a workplace feature is a bug to flag, not a feature to ship.

7. 07

   Review, changes, and contact

   We update this page when the framing above changes — for example, when a public-health authority issues a new cross-border telework rule, when a new category of role moves to on-site default, or when the boundary between trust layer and workplace is re-stated against a new scam pattern that uses health as a vector.

   The "Last updated" date at the top of this page is the source of truth for the current revision. Material changes are also announced on the home page.

   Questions about this policy go to the contact address on /contact. Questions about a specific vaccination / testing / disclosure / accommodation / health-safety requirement go to the engaging party (Employer or Agency intermediary), the public-health authority of the relevant jurisdiction, a qualified health professional, or qualified legal counsel in the relevant jurisdiction — not to Kayanin.