Open the live demo

Privacy

Privacy

RelayPay is a hackathon prototype that runs against the PayPal sandbox. No real money moves and no real customer should use it. This page says plainly what it stores and where data goes.

What RelayPay stores

  • The agent's proposals: product, quantity, amount, its reasoning and the tool calls it made.
  • Sealed approval receipts: who approved (a role label such as “cafe-owner”), when, and the SHA-256 fingerprint.
  • PayPal identifiers: order, capture and dispute IDs, and the café's Vault payment token. Never card numbers or PayPal passwords.
  • Dispute drafts, the merchant's decisions, verified PayPal webhook events and an append-only activity ledger.

Data is kept in a Postgres database (or a local file when run on a laptop) on the server that runs RelayPay.

Who RelayPay shares data with

  • PayPal receives orders, the receipt fingerprint as custom_id, captures and dispute evidence, as required to process them.
  • The AI model provider receives the request text, stock levels, catalog prices and, for disputes, the case details and receipt, so the agents can work. It receives no PayPal credentials.
  • Channel3, when enabled, receives a product name to look up market prices.
  • The owner alert channels (Discord, Slack, ntfy.sh, Zapier, or email through Resend), when enabled, receive alert titles, messages and a link back to RelayPay.
  • Hosting (Render, and Neon for the database) stores and serves the app.

In your browser

RelayPay sets no tracking cookies and runs no analytics. It saves one setting in your browser's local storage: whether you chose light or dark mode.

Public receipt pages

Anyone who has a receipt's 64-character hash can open its verification page, which shows the receipt's contents. Share a hash only with people who should see that order.

Questions

Open an issue at github.com/mayurbijarniya/relaypay.

Last updated November 2026.