folvraPrivacy & public connections
Know what you share.
Before you connect.
The local Demo does not create a profile, collect email or operate a social backend. A future public follow can still reveal a relationship between wallets.
Practice stays in this page.
Inputs, reviews and labelled practice relationships exist in the open page's memory. There is no analytics service, persistent local storage, profile, email form or backend database in this Demo. Reloading the page or clearing practice removes practice data.
Practice caller addresses are fixed examples, not real user identities. A practice result is not a blockchain transaction, and it is not transmitted to a public network by the practice controls.
Connection is a separate choice.
After you click Connect Wallet, an installed wallet may share the selected public address and network. The website does not ask for a recovery phrase or private key, and connecting alone grants no token allowance or automatic follow.
There is currently no deployed contract configuration. Real relationship reads, estimates and writes are disabled. A future configured version will make requests through wallet/RPC providers under their own policies; this website cannot make those channels private.
A public relationship can persist.
A future onchain follow reveals its caller, target and event history. Counts and current state can be queried or indexed by third parties and correlated with other wallet activity. Unfollowing does not erase the earlier event.
A wallet is not proof of a unique person, verified organization or trusted counterparty. Do not use a public relationship to express a sensitive association unless you accept that visibility.
Original media.
No invented inbox.
The homepage embeds the original mechanical-head video from its supplied CloudFront media host. Loading it sends ordinary web request information, such as network address and browser headers, to that host. Its poster is an extracted original frame; fonts, icons and wallet runtime are served locally.
The project's X address is pending. No support inbox or privacy-processing backend is invented, and another project's social account is not substituted. This page describes the current local Demo, not a claim of deployed privacy infrastructure.