Legal & privacy
Privacy Policy
This policy separates two different things: data handled by this website today, and privacy claimed by the proposed PayMoney protocol. No settlement service is live.
Information this website records
Server request logs
Each request produces an access-log entry containing the method, path, user-agent string, referring URL when supplied, requesting IP address, status, latency, and a short visitor pseudonym. The pseudonym is keyed with a secret created at server startup, remains stable for that process, and changes when the server restarts. The Cookies Policy explains that mechanism.
There is no browser session and no cookie identifier. User-agent classification is performed when logs are analyzed rather than stored as additional device or operating-system fields.
Real-user performance measurements
Pages send a first-party batch of standard Web Vitals when the page becomes hidden. These are performance timings used to maintain the site. They do not create an advertising profile or load a third-party analytics script.
Contact form
Submitting the contact form writes the supplied name, email address, and subject to the server log, plus the length of the message. The message body itself is deliberately not logged. There is no contact database, CRM, or automated outbound-email integration.
If you prefer not to place contact details in the application log, use support@paymoney.finance.
Blockchain and transaction data
This website observes none. There is no production PayMoney wallet, settlement API, bank adapter, or transaction-monitoring service connected to it.
Why the website uses this information
- to serve and secure the website
- to diagnose failures and measure page performance
- to understand first-party traffic, including automated crawlers
- to review and reply to messages sent through the contact channel
Storage and retention
Request, performance, and contact metadata live in the server's operational logs. There is no automated expiry and no separate database to purge; retention lasts as long as those logs are kept. A deletion request therefore means locating and deleting applicable log data where legally and operationally possible.
Third parties
The hosting provider necessarily processes traffic delivered to the server. The site loads no third-party analytics, tag manager, advertising system, consent platform, remote font, script, image, or CDN resource. Page assets are served from this origin.
The proposed protocol's privacy boundary
The target architecture keeps bank credentials and plaintext bank records on the payer's device. Three notaries participate in cryptographic sessions but are not meant to receive the disclosed transaction fields. Solvers and aggregators receive opaque action material; Ethereum receives an aggregate proof and vault state transition.
Within the vault, the target hides participants, amounts, destination, offer identity, claim identity, bank transaction identity, and the concrete adapter and rail. It deliberately does not hide:
- public Ethereum deposits and withdrawals
- that an external-evidence-class action occurred in an epoch
- the ordinary fiat transfer from the payer's and recipient's banks
- information that banking law requires those banks to process
This is post-deposit transaction privacy and private proof of fiat payment, not anonymous banking.
Cryptographic boundary
The target vault proof, commitments, account authorization, notary signatures, and aggregator selection use hash-based constructions. The bank's TLS server authentication may still use RSA or elliptic-curve cryptography. A hash-based notary attestation cannot make the bank's classical TLS origin proof post-quantum.
The full assumptions and residual leakage are documented in Security and Trust & risks.
Your rights
Depending on applicable law, you may have rights to access, correct, delete, restrict, or object to processing of personal data. Contact us to make a request. We may need enough information to locate the relevant log entry and verify the request.
Changes and contact
This policy will change before any live protocol service begins collecting a new category of data. Updates appear here with a revised date.
Contact: support@paymoney.finance