Privacy notice.
Effective: November 15, 2026. SeekMesh is an early-stage project using a working brand. This page describes the current launch implementation, not planned services.
Information collected
Founding registration stores an email address, selected role, creation date and invite/referral code. Resource contributions store a contact email, public display handle, source URL, description, category, and review status. We record legitimate submitted contributions, approved reputation points, pseudonymous member accounts (handle, role, salted password hash, active-session hash, referral metadata), and optional verified public EVM wallet addresses, and public Guild membership and messages. Guild posts and public usernames are visible to other visitors; reports are accessible to moderators. Signed-in users can report a source by source ID, reason and optional details; these source reports are not shown publicly. We use limited request metadata for abuse prevention.
Purpose and visibility
We use registration data for founding-network contact and invitations, and contributor data to assess and publish approved source listings. Approved public listings may display the resource, not the contributor's email. Admins can inspect submissions to run reviews. Information is not represented as verified identity.
Storage and third parties
The app uses a server-side SQLite database stored on the configured deployment volume. Your hosting provider may process related infrastructure and network data. Optional AI-powered synthesis, if later configured, sends the search query and public source metadata to the configured model provider, not signup email addresses. The app includes first-party, aggregate-only event counters (page section opened, a source click, and action starts); those counters do not store IP addresses, raw search queries, browser fingerprints, or individual browsing histories. The hosting provider may process network metadata separately. No external advertising analytics SDK is loaded.
Retention and requests
We retain records while needed for operations and review requests for deletion or export. A submitted request requires identity verification before fulfillment. If you choose to link a wallet, a human-readable EIP-191 challenge is signed locally in your wallet. A short-lived single-use challenge and linked address are stored on the server, not your private key. Unlinking requires the account password. Founding registration alone does not establish token rights, payments, or transferable value.