Last updated April 3, 2026
This Privacy Policy explains how EazPay ("Service," "we," "us") collects, uses, and protects information when you use our Telegram-based payment bot. We are committed to data minimization — we collect as little as possible, and most of your financial data lives on-chain, not on our servers.
EazPay is operated by an individual developer based in California, United States.
| Data | Purpose | Storage |
|---|---|---|
| Telegram User ID | Account identification | Server database (PostgreSQL on Railway) |
| Telegram Username, First Name | Display name for payments and @mention lookups | Server database |
| Bcrypt-hashed PIN | Authentication | Server database |
| 2FA code (when active) | Authentication for large transactions (60s TTL) | Server database |
| Anti-phishing code | Shown in every bot message so you can detect impersonation | Server database (plaintext by design — user-facing) |
| Wallet EOA address | Link your account to your on-chain wallet | Server database |
| Wallet EOA private key | Operate the wallet on your behalf (custodial model — see Security) | Server database, encrypted AES-256-GCM. Encryption key stored separately in Railway env. |
| Transaction cache | Display history in the bot; source of truth is always on-chain | Server database |
This data is publicly visible on the Tempo blockchain and is not controlled by us.
Note on private keys. We do store your wallet EOA private key in encrypted form to operate the bot on your behalf — this is part of the custodial model. If you want to take full custody of your key (and have us stop holding it), use /export to receive your key, then email security@eazpay.xyz to request deletion of your encrypted copy. A self-service /deleteaccount command is on our roadmap.
We use collected data solely to:
We do not use your data for advertising, profiling, or behavioral analytics.
We do not sell, rent, or trade your personal information. Period.
We may share data only in these limited circumstances:
To request deletion of your server-side data, contact us (see Section 10).
EazPay relies on the following third-party services, each with their own privacy policies:
| Service | Role | Privacy Policy |
|---|---|---|
| Telegram | Bot platform, messaging | telegram.org/privacy |
| Railway | Server hosting, database | railway.app/legal/privacy |
| Vercel | Website hosting (eazpay.xyz) | vercel.com/legal/privacy-policy |
| Tempo Blockchain | L1 network for transactions | Public blockchain — all data is on-chain and publicly accessible |
We do not control how these services handle your data. We encourage you to review their policies.
The EazPay website (eazpay.xyz) may use:
We do not use third-party advertising cookies or cross-site tracking pixels. The Telegram bot itself does not use cookies.
We implement reasonable security measures to protect your data:
However, no system is 100% secure. We cannot guarantee absolute security of your data.
You have the right to:
Under the California Consumer Privacy Act (CCPA), California residents have additional rights:
To exercise any of these rights, contact us using the information in Section 10. We will respond within 45 days as required by the CCPA.
We do not knowingly collect personal information from individuals under 18.
For privacy-related questions, data requests, or concerns:
We may update this Privacy Policy from time to time. Material changes will be communicated via the EazPay Telegram bot or channel. Continued use of the Service after changes constitutes acceptance of the updated policy.
By using EazPay, you acknowledge that you have read and understood this Privacy Policy.