Privacy, plainly.
Privacy policy · Updated September 30, 2026
Foyer is operated by Hashbot Inc., in Quebec, Canada. This policy describes how we handle information when you use Foyer. For privacy questions or requests, email [email protected].
What Foyer does
Foyer connects Discord accounts and signed, OpenSea-verified and delegated wallet addresses to NFT and token ownership rules chosen by server administrators. It checks holdings, updates Discord roles, and can publish public collection sales in a channel the administrator selects.
Information we handle
- Your Discord identifier, username and display name, sign-in session, and encrypted OAuth access token. Discord provides the servers and permissions needed to authorize dashboard access.
- The wallet addresses you choose to link, their network family, and linking time. For delegated wallets, we also store the linked delegate address, delegation network and registry version, and read the public delegation when checking access. Short-lived signing challenges contain your Discord identifier and username, address, site origin, and nonce. The signature proves control; we do not request seed phrases or private keys. If you choose the OpenSea bio option, we store the selected wallet’s profile username and primary address. We read the public main profile bio to verify an expiring phrase and recheck the public wallet association during role checks. The phrase is linked to your Discord account on our server and is public while you leave it in your bio; it does not contain your Discord identifier. You can remove it after verification. We store the short-lived challenge, but do not store your full bio.
- Server, role, and channel identifiers; configured asset requirements; membership connections; verification outcomes; pending updates; and activity records.
- When a server administrator enables Enforce role, Foyer reads the server member list to identify holders of those roles, including people without a Foyer account. It processes Discord user and role identifiers for this purpose and discards other member profile fields. Only holders needing enforcement enter a temporary work queue; Foyer does not create an account or discover wallets for unverified members.
- Screenshots or text that an administrator submits to draft an import from another bot. Foyer sends them to Anthropic’s Claude API for that request only, keeps the drafted rules in the administrator’s browser until they are imported, and does not store the images. Anthropic does not train on API data. Crop screenshots to the rules list; member names and wallets shown in them are not needed.
- Public sale information, including item metadata, artwork URLs, transaction identifiers, and buyer/seller addresses, for enabled collection feeds.
- Operational request counts, timing, errors, and server identifiers to measure reliability and costs. Hosting and network providers also handle connection information such as IP addresses.
- When billing is enabled, payment-provider customer and subscription identifiers, billing status, renewal dates, and the administrator responsible for billing. Stripe hosts the payment form and handles payment details, billing addresses and tax identifiers used for invoices and tax calculation, and acceptance of the purchase terms. Foyer stores the checkout reference, offer version and agreed price text. It retrieves finalized invoice details from Stripe to provide purchase copies and, when enabled, sends the complete purchase terms by email through AWS. Delivery records retain invoice references, delivery status and a content checksum, not the recipient address or email body. Foyer does not store full card numbers or customer tax identifiers. When the USDC payment option is enabled, MoonPay Commerce hosts the crypto checkout and keeps the payer’s email address for renewal reminders and receipts; Foyer stores the MoonPay subscription reference, the paying wallet address, the network, the amount and the transaction signature (public blockchain data), the paid period and the administrator who paid. Foyer reads the payer’s email from MoonPay only at the moment it sends the purchase terms and does not store it.
How information is used and shared
We use this information to authenticate you, prove wallet control, evaluate the rules you request, deliver and maintain roles, operate sales feeds, prevent abuse, provide support, and administer subscriptions.
If a role is confirmed more than about 20 seconds after you start a check from the verification page, Foyer may send you one Discord direct message saying the role is ready; it sends no other direct messages.
Discord receives role and channel actions. Ownership providers receive public wallet addresses and asset queries: dRPC, Alchemy, OpenSea, UniSat, and configured network RPC services. WalletConnect/Reown is involved when you choose its wallet connection. AWS hosts Foyer in the United States, and Cloudflare handles website traffic. Stripe processes card billing when used, and MoonPay Commerce processes USDC payments when that option is used. These providers operate under their own policies and may process information outside Canada.
Authorized server administrators can see their community’s linked members, shortened wallet addresses, role outcomes, and activity. A public blockchain address can reveal holdings and transaction history; linking it associates it with your Discord account in Foyer. Enabled sales feeds publish public buyer/seller addresses in the chosen Discord channel.
Foyer does not sell wallet links or use Discord messages for advertising. The bot does not request Presence or Message Content access and does not analyze server conversations.
Cookies and browser storage
Foyer uses essential cookies for Discord sign-in and sessions, including a short-lived OAuth state cookie. Wallet providers may use their own storage. The application does not currently include advertising trackers.
Optional role enforcement
When an administrator turns on Enforce role, Foyer removes that role from members who have not verified with Foyer in that server or whose confirmed holdings no longer qualify. A qualifying active rule for the same role keeps access. An incomplete holdings check never removes a role.
While enforcement runs, Foyer keeps a short list of who currently holds the role. Each entry is deleted once it is processed, when enforcement or service stops, or after 24 hours at the latest. Later scans can list a member again while they still hold the role. Deleting your Foyer account clears your queued enforcement work, but an unverified holder can still lose an enforced role. Foyer does not create accounts or look up wallets for people who have not verified.
The activity entry for an unverified holder records the role name and outcome, without their user identifier or profile. Historical encrypted backups follow the retention policy below.
Retention and deletion
Account and wallet links remain while your account is in use. Activity history and aggregate operational measurements currently have no scheduled expiry. Hosting service journals are limited to 14 days. Encrypted backups currently have no automatic expiry; deleting your active account does not immediately erase historical backup copies.
You can export your account and activity or delete your account from account settings. Deletion removes active sessions and linked wallets, removes the account, and replaces your name in historical activity with “Former member.” Discord identifiers required to finish outstanding role removals remain until that work completes. Blockchain records and previously posted Discord messages are not erased by deleting a Foyer account.
Before deleting a billing owner’s account, Foyer cancels future renewal and closes unfinished checkouts. Servers keep the time already paid for. If billing cannot be confirmed, deletion remains pending and can be retried from account settings. Minimal customer, subscription and cancellation references remain for billing administration; financial records remain with Stripe. For access, correction, deletion, billing records, or historical backup questions, email [email protected]. We may need to verify your identity before acting on a request.
Contact and changes
Privacy requests for Foyer are handled by the Founder of Hashbot Inc., Quebec, Canada. Email [email protected] with questions, requests, or complaints. See support options. We will update this page and its effective date when our practices change and provide appropriate notice of material changes.