1. Service Provider and Contact
FlashMail provides email product listings, purchases using an account balance, order delivery information, and API access. Contact the platform through the support email or Telegram contact listed on this page for product, order, or service questions.
Names such as Hotmail, Outlook, and Gmail identify third-party products or services. This page does not claim that FlashMail is officially authorized by, affiliated with, or partnered with those brands.
2. Products and Conditions
Products follow the current catalog and individual listings. Before purchasing, check the email type, quantity, price, usage period, delivery fields, mail retrieval method, and after-sales coverage. Labels such as short-term or long-term do not mean every product has identical features or permanent availability.
Ask support before ordering when a use or feature is not clearly described. Third-party rules, features, and security controls can change; FlashMail listings do not replace those providers' terms.
3. Platform Accounts and Credentials
Website purchases use your signed-in account and its balance. Protect login passwords, API Keys, and delivered account information. Do not share credentials with unrelated parties or expose keys in public tickets, screenshots, or code repositories.
If you suspect an account or credential leak, stop affected operations and contact the platform. Resetting, replacing, or recovering a credential depends on the account state and supported functionality.
4. Top-Ups, Orders and Delivery
A top-up and a product purchase are separate operations. Check the payment channel, currency, amount, and status; a successful browser redirect does not by itself mean a top-up was credited. Product quantities, applicable discounts, and final charges follow the order confirmation.
After ordering, check the order status and delivery details. If payment status is unclear, your balance changes without a corresponding order, or delivery fails, retain the order information and contact support before submitting again.
5. API Access
Public endpoints follow the /open/* paths, parameters, and response formats in the current API documentation. Authenticated endpoints accept an API Key through the clientKey query parameter; stock queries do not require a key. Website login tokens and public API Keys are not interchangeable.
Purchasing endpoints create real orders and affect balances. Integrators should verify the documentation, handle failures, and protect request URLs containing credentials. Do not use purchasing endpoints as an unconfirmed connectivity test.
6. Acceptable Use
Do not use the service for spam, phishing, fraud, harassment, privacy violations, unauthorized account or data access, or other unlawful activity. Do not use unlawfully obtained devices, network resources, or another person's credentials.
Purchasing a product does not authorize bypassing third-party restrictions or violating their terms. Suspected abuse should be handled using verifiable facts with a contact and appeal channel. A genuine complaint or negative review alone should not be grounds for forfeiting a balance.
7. After-Sales, Disputes and Updates
Read after-sales and refund matters alongside the product listing and the After-Sales and Refund Policy. For a dispute, provide the order number, incident time, and redacted evidence so support can investigate and explain its decision.