Kayanin · community guidelines

Last updated · 2026-08-23

The behavioural layer of Kayanin.

What counts as acceptable use on the three-peer platform, the red-line behaviour that is never acceptable (spam, harassment, off-platform-only contact, ID-fishing, payment from a Worker, fake listings, impersonation, score-gaming), the warning → suspension → removal ladder, and the appeal path — the same rules that bind every Worker, Employer, and Agency account.

This copy is a product draft supplied by Kayanin and is pending qualified legal review before launch. It states what Kayanin does and does not do; it is not legal advice.

The guidelines

Eight sections, in plain language.

  1. 01

    Who these guidelines apply to

    Every account on Kayanin — Members (Workers), Employer / Business accounts, and Agency accounts — is bound by these community guidelines. They apply alongside the Terms of Use and the Privacy Policy; together they describe the rules of the three-peer platform.

    Anonymous visitors are not bound by these guidelines but are bound by the underlying laws of their jurisdiction. The platform does not exist outside the law; nothing on this page should be read as authorisation to break it.

  2. 02

    What counts as acceptable

    Most of what happens on the platform is acceptable by default. Acceptable behaviour includes:

    • Posting a real job opening with a real Employer / Business behind it, with pay that matches what the offer letter says.
    • Applying to jobs that match your experience and your stated availability, with truthful profile data and a current resume.
    • Leaving reviews of an Employer or an Agency that reflect what actually happened — including a no-hire outcome if that is the real outcome.
    • Registering an Agency with accurate registration / tax-id and POEA / DMW licence data, and keeping the fields current.
    • Reporting a listing or a contact that you believe violates one of the rules below. The platform reads every report.

  3. 03

    What does not

    The following are never acceptable on Kayanin. The list is illustrative, not exhaustive — anything that materially undermines the trust layer is a candidate for enforcement.

    • Spam — repeated posting of the same listing, repeated messages to a Worker or an Employer who has not opted in, or low-effort contact obviously designed to harvest a reply.
    • Harassment — slurs, threats, doxxing, persistent unwanted contact after a clear "no", or any contact that a reasonable person would describe as intimidation.
    • Off-platform-only contact — listings that refuse to verify on the destination platform ("WhatsApp only", "Telegram only", "no website"). The trust layer cannot verify what it cannot see.
    • ID-fishing — requests for government IDs, selfies holding the ID, or POEA / DMW licence numbers before any conversation has earned that trust. The request is itself the red flag.
    • Payment from a Worker — any fee charged to a Worker for an application, a "placement", a "training" module, a "processing" step, an OWWA clearance, a visa, or a ticket. The boundary is non-negotiable: Kayanin never charges Workers, and any third party on the platform who does is removed.
    • Fake listings — postings that do not correspond to a real role at a real company, or that misrepresent the pay, the location, the contract length, or the duties of the role.
    • Impersonation — pretending to be another person, business, agency, or government entity, or holding yourself out as a POEA / DMW officer. The platform verifies identity at sign-up.
    • Score-gaming — coordinated activity designed to inflate a Worker Trust, an Employer Score, or an Agency Score. Artificial signals are removed and the underlying accounts are reviewed.

    Kayanin is a three-sided platform and the rule applies equally from every side. The full taxonomy of scam signals (and the verify-before-applying checklist) is on /scam-prevention.

  4. 04

    Enforcement ladder

    Moderation happens in three steps. Not every violation reaches step three; the ladder is calibrated so a first-time, low-severity violation can resolve with a warning, while repeated or high-severity violations move to removal without intermediate steps.

    Warning — the first signal that a behaviour has crossed a line. The account keeps its score; a note is attached to the moderation log; the user has 14 days to correct or appeal.

    Suspension — for repeated warnings, or for a single high-severity violation. The account is paused for a fixed period (typically 30 days). Listing visibility is paused; applications already in flight are held in place; the user can appeal in writing.

    Removal — for severe violations or for violations that recur after a suspension. The account is closed, listings are taken down, and the score is reset. The user is told, in writing, what triggered the removal and where to appeal.

  5. 05

    Reporting violation

    Anyone — signed-in or signed-out — can report a violation. The report form lives on the contact page; messages route to the moderation team.

    A useful report includes: the URL of the listing or the profile, the date and time of the contact or the message, and a short note describing the issue. Screenshots are welcome; do not pre-edit the screenshots — moderators need to see the originals.

    Every report is read. The moderation team will reply within a working day to confirm receipt and to give a timeline for review. High-severity reports (active scams, immediate harm) are reviewed before the working-day reply.

  6. 06

    Appeals

    Every warning, suspension, or removal can be appealed. The appeal is a written reply, sent to the contact address below, with the moderation decision ID at the top of the message.

    Appeals are reviewed by a moderator who was not part of the original decision. The appeal window is 30 days from the date of the decision; appeals past the window are considered only with a written explanation of why the delay occurred.

    The appeal decision is final; further appeals on the same incident are not accepted. A new incident can always be appealed on its own merits.

  7. 07

    Cross-references

    The Terms of Use are the contractual layer; the community guidelines are the behavioural layer; the scam-prevention page is the practical layer. They are designed to be read together.

    • Terms of Use — accounts, acceptable use summary, user content, third-party services, disclaimer, limitation of liability.
    • Scam prevention — the eight PH-OFW signals and the verify-before-applying three-step checklist.
    • Methodology — how the trust score that moderation leans on is computed.

  8. 08

    Contact

    Reports, appeals, and questions about moderation go to kayanin@proton.me. The moderation team reads every message; nothing routed to that address is ignored.