Privacy and data use

Public site and attestation checks

This site serves public pages, a registry, and signed attestations. Its browser verification page is prepared but is not public yet. When available, that page will check public records against World Chain and may fetch an attestation from another host. The chosen registry, attestation host, RPC endpoint, and this site's host may receive and log ordinary request data such as IP address and requested URL. The site code has no analytics or third-party page assets.

A published Fiador attestation includes the signing wallet's full address and a hash of its AgentBook human identifier. AgentBook registration is public on World Chain. A disclosed wallet or published hash can be matched to the pseudonymous identifier and other wallets registered to it. The published attestation omits the raw identifier; that does not make the chain data private.

These pages store your light or dark theme choice in your browser. There is no public browser verification form yet.

Owner-only Slack trial

When enabled, the separate Slack app uses the workspace and member IDs supplied with its commands and App Home events to limit who can use a check. Sign in with Slack requests the openid scope to match a private check link to the same workspace member. The app does not request message history. A member lookup for /fiador-whois @member also uses Slack's member information API. Slack's own handling of data is governed by Slack.

/fiador-verify returns a private check link in an ephemeral Slack response. The browser keeps the link's signed state token, not the whole URL, in the tab's session storage across Slack sign-in. The token includes workspace and member IDs and is signed, not encrypted. The browser removes it when a proof callback starts, before the server replies, or on an IDKit error. A failed or expired sign-in flow can leave it there until the tab closes or its storage is cleared. Do not forward the link. The sign-in flow also places short-lived, signed but unencrypted cookies in the browser. They carry workspace and member IDs; the flow cookie lasts at most five minutes and the browser session at most ten minutes. When used, the trial stores opaque flow hashes in its database, and does not store a Slack access token from the sign-in response.

To start a World ID check, the app would create a short-lived private link and a proof request for the selected member. The browser would send the completed proof to the Fiador trial server, which encrypts it in its database before asking World to verify it. World would receive the proof. The app would store a hashed workspace key and keyed account identifiers, the request and its outcome, and, after a confirmed check, a nullifier hash and verification date.

App Home and /fiador-whois send an account's recorded check date through Slack when one exists. Those responses do not identify the human or establish who is using the account now. Slack receives these app views and command responses. The prepared trial admits only its one configured owner account.

Retention and review

The trial code erases the stored encrypted proof after a confirmed account binding, a definitive rejection, or a binding conflict. If the outcome is unclear, it holds the encrypted proof and the account's reservation for operator review rather than asking for another one-time proof. Enrollment intents, nonce rows, proof attempts, and bindings have no automatic deletion schedule, so this page cannot promise a deletion date for them. Expired sign-in flow rows are cleaned separately. General enrollment is still closed while retention and deletion handling are unresolved.

For help, use the support page. The public Fiador issue tracker accepts general questions and bugs. Do not post a private check link, proof, Slack account details, or secret in a public issue. The owner-only trial's operator handles account-specific review privately.