Privacy Policy
Paymid — paymid.com.br · Version of 2026-11-17 · Contact: contact@aufwassen.com
Paymid is commission-protection software for middlemen. It records a commission agreement, enforces a payment order — commission first, service second — and keeps the proof record. Paymid never receives, holds or moves the parties’ money: payments happen directly between buyer, middleman and seller, on rails they choose.
What we collect
Account data. When a middleman creates an account: name, email address and password. Passwords are stored only as salted scrypt hashes — never in plain text.
Bridge data. What the middleman enters to create a bridge: the buyer’s and seller’s names and email addresses, a description and value of the deal, the commission, the payment rails and destinations the parties will use, and — in blind-deal mode — the seller’s contact. The seller’s contact is stored encrypted (AES-256-GCM) and is revealed to the buyer only after the commission is confirmed.
Contracts. If the middleman uploads or pastes a commission contract so Paymid can extract the deal terms, the contract text or file is stored with the bridge it created, linked by a SHA-256 hash.
Acceptance record. When a buyer accepts the commission agreement on a bridge page, we record the acceptance together with the timestamp, the IP address and the browser’s user agent. This record is the proof the product exists to keep.
Payment confirmations. The parties declare payments on the bridge page and may attach the confirmation reference of the rail they used (for example a transfer reference or a Bitcoin transaction ID). Paymid does not process the payments and never sees full card numbers, bank credentials or wallet keys.
Connector data. When Paymid is used through an AI connector (Claude, ChatGPT or another MCP client), we store the OAuth tokens that keep the connection working. Tool calls carry the same bridge data described above, provided by the signed-in user in the conversation.
Technical data. Server logs needed to operate and secure the service.
How we use it
To operate the payment sequence, keep the tamper-evident bridge record (an append-only, hash-chained event log), show each party what the flow requires of them, provide support and protect the service against abuse. We do not sell personal data, and we do not use bridge data for advertising or profiling.
Who sees what
The parties of a bridge see the information the flow requires: in standard mode the parties are identified from the start; in blind-deal mode the seller’s contact stays sealed until the commission is confirmed. We use a hosting provider (Render) to run the service. Payments run on the parties’ own rails (for example Stripe, PayPal, Pix or Bitcoin processors), under those providers’ own policies. We may disclose data if the law requires it.
Retention
Account data is kept while the account exists. Bridge records are the proof of an introduction and are kept so the parties can rely on them; if you ask us to delete your account, records that another party relies on as proof may be kept in minimized form. Contact us to ask what we hold about you, to correct it, or to request deletion where it applies.
Cookies
One session cookie (paymid_session, HttpOnly) keeps a signed-in middleman signed in. No third-party trackers, no advertising cookies.
Security
Sealed contacts are encrypted at rest, passwords are hashed, and the event record is hash-chained so later edits are detectable. No system is perfect; if you believe your data was exposed, contact us immediately.
Changes
If this policy changes materially, the new version will be published on this page with its date.
