What this interface sees, and what it keeps

This notice covers callhouse.finance (this site) and app.callhouse.finance (the dapp). It is written from the code, not from a template: each statement below names the file it was checked against, and the source is listed in the header comment of this page. It does not cover your wallet, the chain, or any third-party site linked from here.

What we process

On callhouse.finance

• Nothing beyond the HTTP request itself. This site sets no cookie, writes nothing to your browser's storage, runs no analytics, has no form and loads no third-party script. Its dependencies are Next.js and React and nothing else.
• The server that answers the request is a Railway service. Railway records standard HTTP logs for it: your IP address, user agent, the path requested and the time. See Retention below.

On app.callhouse.finance

• Your wallet address, once you connect. It is public chain data. The dapp reads your balance, your shares and your claimable USDG straight from the chain, in the browser. Today no request from the dapp carries your address to a server of ours, and there is no account to attach it to.
• Browser storage. The wallet library (wagmi) keeps, in your browser's localStorage under keys beginning wagmi., which connector you last used, the addresses and chain it was connected to, and a flag recording that you disconnected. This is what lets the page reconnect on your next visit. Nothing else is stored, no cookie is set by us, and clearing site data removes all of it.
• The HTTP request. Every page and one server route (/api/overcall/listings) is answered by a Railway service, which records the same standard HTTP logs as the site: IP address, user agent, path, time.

Where it goes

Each of these is a separate organisation with its own privacy terms. By name:

• RPC providers. The dapp reads the chain from your browser, so your browser talks directly to rpc.mainnet.chain.robinhood.com (Robinhood) and, as a fallback, robinhood-rpc.publicnode.com (PublicNode). They see your IP address and every call the page makes, which includes your wallet address as call data once connected. We do not proxy those requests and cannot see them.
• The Callhouse indexer. A history service we run. It stores wallet addresses, share balances and USDG amounts derived from public on-chain events, and nothing that is not already on the chain. The dapp asks it for vault history and listings; it does not ask it for your position today, although the indexer has an endpoint keyed by address and the dapp contains an unused function that would call it. If that is ever wired up, the address will appear in the indexer's request log (which records method, path, status and timing, not IP) and the host it runs on may keep a connection log holding your IP beside it. This notice changes in the same commit.
• Overcall. The cycle page asks our server for the vault's open listings, and our server asks overcall.finance. What is forwarded is the vault's own address, a fixed status and limit and, when asked, the market symbol — all compiled into the route, none taken from your request. Your IP address and your wallet address are not forwarded; Overcall sees a request from our server. The route is read-only.
• Railway. Hosts both domains and the HTTP logs described above.
• The explorer. Links to Blockscout open in a new tab. Following one is a visit to their site under their terms.
• Your wallet. Whatever your wallet extension sends to its own vendor is governed by that vendor, not by this notice.

What we do not do

• No cookies, on either domain.
• No analytics, no tracking pixel, no session replay, no third-party script.
• No accounts, no sign-up, no email list, no know-your-customer process.
• No selling or sharing of anything for advertising. There is nothing to sell.
• No server-side record of which wallet visited which page. No dapp URL contains a wallet address, so Railway's logs hold your IP and the path, not your address.
• No request that would put an IP address and a wallet address on the same line of a log we control — today. The one endpoint we run that takes an address in its path (the indexer's account route, above) is not called by the dapp. If that changes, this bullet goes and the indexer bullet says what is logged.

Legal bases

Where the GDPR or the UK GDPR applies, the basis for the processing described above is the legitimate interest in operating and securing the interface (Article 6(1)(f)) — the HTTP logs exist to keep the service running and to investigate abuse. We do not rely on consent because there is nothing to consent to: no cookies, no analytics, no marketing. Wallet addresses and balances are public chain data that the indexer republishes, not data you handed us.

Your rights

If you are in the EU, the EEA or the UK, the GDPR and the UK GDPR give you rights over personal data about you. In plain words, you can:

• ask what personal data is held about you and get a copy;
• ask for it to be corrected if it is wrong;
• ask for it to be deleted, where there is no reason to keep it;
• ask for processing to be restricted, or object to it;
• receive it in a portable form where it was provided by you;
• complain to your data-protection authority.

Two honest limits. First, a wallet address and its transactions are on a public chain that nobody can edit; the rights above apply to what we hold, and we cannot delete a block. Second, the only personal data we hold ourselves is in Railway's HTTP logs and the indexer's address table, so most requests will be answered by describing exactly that.

Controller: not yet designated. No legal person has yet been named as the controller for the processing described here, and whether an EU or UK representative is required has not been decided. This line will name them when that is done.

Retention

• HTTP logs are retained by Railway for as long as Railway retains them. We have not configured a retention period of our own, longer or shorter, and we do not export the logs anywhere.
• The indexer keeps address-level figures for as long as the chain does, because it is a replay of the chain. Dropping and rebuilding it reproduces the same rows.
• Browser storage written by the wallet library lasts until you clear it. We cannot clear it for you.

Security

Both domains are served over TLS. There are no accounts, passwords or stored credentials on either domain, so there is no credential store to breach; the main protection for your data is that we collect almost none of it.

International transfers

The providers named above — Railway, the RPC providers, Overcall and the explorer — may process data in countries other than yours, including outside the EU and the UK. We have not put transfer safeguards of our own in place beyond what those providers publish; the only data that reaches them is what this page describes.

Children

Neither domain is directed at anyone under 18, and we do not knowingly process data about anyone under 18. The terms require users to be adults.

Changes to this notice

This notice is versioned with the Terms of Use. The version in force is v2-2026-09-13. A change is a new version and a new date, published on this page; there is no other notice.

Contact

Requests about personal data go to privacy@callhouse.finance. The terms are at /terms, the perimeter at /legal, and the dapp this notice describes is at app.callhouse.finance.