V129 moderation policy

Temporary bans and appeals

This policy describes Frinly's implemented moderation boundaries. Ban enforcement remains off until the operating procedure, retention, and owner review gates are approved.

Human decisions only

Reports and safety signals can begin a review, but they do not create a ban automatically. A moderator must review the available context, choose a listed reason and temporary duration, confirm the decision, and add a written note.

Privacy-minimized evidence

Frinly uses protected server-side browser-session hashes for this workflow. Admin review does not require raw IP addresses, exact location, passwords, government ID, or a durable device fingerprint.

Appeals and revocation

A guest may submit the opaque reference shown with a ban. The appeal enters the moderation queue for a separate human decision. An approved appeal still requires an audited administrator revocation.

Available grounds

Harassment or threats

Sexual or explicit behavior

Suspected minor-safety risk

Scam, spam, or impersonation

Repeated rule or ban evasion

Other reviewed safety issue

Temporary durations

24 hours

7 days

30 days

90 days

Indefinite bans are not available in the current workflow.

Record retention

Pending review

Frinly will not run retention cleanup until explicit windows have owner and legal review, plus a dry-run and audited deletion implementation.

Ban records and protected hashesNot set

Safety reportsNot set

Ban appealsNot set

Admin audit recordsNot set

Cleanup writes: off. Open investigations and active bans are never cleanup candidates.

Emergency correction

Owner review pending

A mistaken ban can be revoked by an administrator with a recorded reason. A broader issue requires public chat to be paused and ban enforcement disabled before recovery review.

1.For one mistaken ban, use Ban Management to revoke the active record with a documented reason.

2.For a broader safety issue, set FRINLY_PUBLIC_CHAT_PAUSED=true and FRINLY_BAN_ENFORCEMENT=false in Render, then redeploy.

3.Confirm the revoke and any pause action in the admin audit log before restoring access.

4.Review related reports and appeals, record the incident outcome, and restore traffic only after the owner signs off.

Required safeguards

Every ban decision requires human review and a written moderator note.

Only the listed temporary durations are available; indefinite bans are not supported.

Appeals enter the moderation queue and never automatically revoke or shorten a ban.

Frinly does not ask for passwords, raw IP addresses, exact location, government ID, or device fingerprints in an appeal.

Ban creation and revocation remain separate audited decisions.

Retention cleanup stays disabled until record windows, legal review, and an accountable owner are configured.

Submit an Appeal View Rules