About Everiot
Everiot is a fast, server-rendered imageboard for open discussion, board communities, and lightweight media sharing.
Contact
Questions, feedback, moderation concerns, and privacy requests can be sent to [email protected].
Privacy Policy
We only store the minimum information needed to run Everiot, keep communities safe, prevent abuse, and respond to support or privacy requests.
Emergency browser-fingerprint correlation is off by default and may be manually armed only for active attack or lockdown incidents. Everiot runs the open-source FingerprintJS library locally, converts its short-lived visitor value to a keyed server hash, never stores the raw value, restricts access to moderation staff, and removes the evidence within 30 days. The signal is advisory and is never used by itself to challenge, hold, block, or ban someone.
For abuse investigation, public submissions also produce short-lived keyed hashes of a limited browser-header tuple and, when a trusted Cloudflare edge is configured, a limited TLS/connection tuple. Everiot does not store the raw User-Agent, Client Hints, TLS fingerprints, cookies, authorization, referrer, header order, encoding preferences, or request body in this evidence. The hashes expire within 30 days, graph connections expire within 14 days, are visible only to specially authorized moderators, and currently have no risk weight or enforcement authority.
To classify potentially unsafe content, Everiot may send reported posts, posts held for an administrator-approved reason, or—when an administrator enables a wider scope—future public post text and public image-preview URLs to the external OpenAI Moderation API. Text and image previews are screened separately. We do not include profile, session, IP, user-agent, report-author, report, or moderation-case identifiers. OpenAI fetches image previews from the same public URL visitors can access. If administrators separately enable held-post automation, a high-confidence result for an allowed hold reason may release or reject only that screened revision; stale, uncertain, or failed checks remain held. Everiot keeps normalized screening evidence for up to 30 days; action-linked category, model, and policy evidence may remain with the longer-lived moderation case and audit record.
Reported content and moderation context may also be sent to the separately configured external LLModerator provider. The request includes the report category and reason, whether a reporter is present, board, reported text, media presence and type, the accused account's age, public-post and active-ban counts, case summary, site rules, and normalized OpenAI category evidence. It omits direct profile, session, and IP identifiers as well as internal report, post, thread, and case identifiers. LLModerator normally supplies narrative triage. If administrators separately enable held-post automation, only an exact versioned structured decision may release or reject the current held revision; free-form output, stale or uncertain results, unsupported hold reasons, and provider disagreement remain held. LLModerator cannot create bans or remove other content. Provider use is controlled by administrators and can remain disabled.