Privacy
Ponsegle is a wallet-gated video chat product. This page describes what the service handles and what stays on your device.
What we process
- Wallet authentication: the server issues a short text message and a nonce. You sign it with your Ethereum wallet. We verify the ECDSA signature and issue an HTTP-only session cookie. We store the wallet address and session expiry in memory to authorize signaling and TURN config requests.
- Signaling: WebSocket messages relay WebRTC SDP and ICE candidates between peers. We do not record or persist chat content.
- Media: video and audio are exchanged peer-to-peer (WebRTC). We are not in the media path.
- ICE: STUN/TURN credentials may be obtained from Twilio (or equivalent) when configured. That is used only for NAT traversal.
- Rewards: to credit a match we record, against your wallet address, the ticker and amount granted, how long the call lasted, the counterparty's wallet address, and a timestamp. This is what enforces the cooldown and the daily cap; it holds no video, audio, or conversation content. Claims you make are public on Robinhood Chain, as any on-chain transaction is.
What we do not do
- We do not sell or share wallet addresses for marketing.
- We do not store call recordings.
- We do not require registration beyond wallet sign-in.
- We do not link wallet addresses to real-world identity, and we do not ask for it.
Reward tokens
Tokens granted for matches are Robinhood Stock Tokens: tokenised debt securities issued by Robinhood Assets (Jersey) Limited that track a share price. They provide economic exposure to the underlying security but do not grant ownership of it, nor any legal or beneficial rights against its issuer, and confer no shareholder rights. Nothing here is investment advice.
Unclaimed balances are recorded against your wallet address in our database until you claim them. Claiming is a public transaction on Robinhood Chain, and you pay its gas.
Cookies
The session cookie is HTTP-only and scoped to the app. It is required for WebSocket and TURN access after wallet verification.
Contact
Questions about this policy should be directed to the project maintainers of your deployment.