A quick word on the background: this site is something I built alone in my spare time — I work a day job and only have evenings for code and maintenance. Before writing this I looked at how other disposable-mail sites handle their policies: most are copy-pasted lawyer templates, or basically nothing. I wanted neither. So I wrote down exactly how I use this site and where data really goes, point by point. If anything is unclear, just email me — I will explain every line in plain language, no double-talk.
In one sentence: this site does not make money off your data. No ad networks, no analytics SDKs, no hidden trackers. Data is stored as little as possible and deleted as soon as possible. Every point below is laid out in the open.
1. Email Address
The temporary address generated on the page is a random string plus a domain suffix (e.g. ttcbixob01@qiuyumail.xyz). The string is purely random — it has no connection to you, your phone number, your usual email, your device, your IP, or the time. I deliberately made the generator independent of everything, so that even if the database were ever stolen, nobody could trace an address back to you.
Addresses are stored in Cloudflare KV and D1 (Cloudflare cloud storage services, more below). They expire after 24 hours of inactivity and are auto-renewed when new mail arrives. If you close the page or clear your browser data, the address still exists on the server (otherwise it could not receive mail), but after expiry it gets wiped — and that random string could theoretically be generated for someone else later. So do not treat a temporary address as a permanent one; this applies to every temp-mail service out there.
There are currently 2 domain suffixes to choose from: qiuyumail.xyz and sppdry.kdns.fr. Whichever suffix you pick, as long as the prefix is the same, the inbox is the same — handy for registering on different sites with one address and seeing all codes on a single page.
2. Received Mail
Mail sent to a temporary address is stored on the server and cleared when the address expires — nothing is kept permanently. Mail content is only shown to you in your own browser tab. I do not read it manually (honestly I have no time — thousands of mails a day), it is never analyzed, never sold, and your verification codes are of zero value to me.
Transport is HTTPS-encrypted and storage has basic access controls. But one ugly truth up front: temp-mail addresses are "semi-public" by nature — anyone who knows the address can access that inbox. This is a universal flaw of all temp-mail products, not unique to this site. So never use it for anything truly important: bank verification, payment confirmations, recovery mails for important accounts. If something goes wrong, that risk is yours alone.
One practical note: verification mails from some websites can be delayed — anywhere from a few minutes to over ten minutes is normal — and some sites do not send at all (certain platforms simply never mail overseas addresses). If it does not arrive, wait a bit; if it still does not, regenerate a new address and try again. That is on the sender's side, not this site, and there is nothing I can do about it.
3. Access Logs
To prevent abuse, the server records visitors' IP addresses and browser identifiers (UA). What for? To stop three kinds of people: API flooders, password guessers, and scripted scrapers. During normal use these records only exist as short-term in-memory statistics and are cleared within minutes — not stored, not used to profile you. A temp-mail site has neither the need nor the spare time for that.
Only when a security event triggers does an IP get written to a temporary block list. Examples: 3 consecutive failed admin logins; scripted high-frequency API requests. Such IPs are blocked for the duration set in the admin panel (default 1 hour), but normal users will never hit this — use the site normally and your IP is never recorded.
If you are blocked, the page will tell you. If you think it is a false positive, email me and I will review it manually — genuine mistakes get unblocked. There was once a user flagged for receiving too many codes; he emailed me, I saw it was normal use, unblocked him on the spot and loosened the threshold a bit.
4. Data Storage
Data lives in Cloudflare KV and D1 — cloud storage. Mail data expires after 24 hours by default (auto-renewed on new mail), and stats only keep aggregated totals. Storage has basic access controls, but no cloud service can guarantee 100% safety; in extreme cases (a massive Cloudflare outage, an account breach), data loss is not impossible — so do not put anything important here.
Two more words on location: Cloudflare KV/D1 is distributed storage — data syncs across global data centers and the physical locations are decided by Cloudflare, not me. If you are especially sensitive about which country your data sits in, this site may not be for you. That is the objective reality of cloud services; as an individual developer I cannot afford my own data center.
Speaking from experience: since this site launched, my own mailbox was wiped once by a Cloudflare hiccup (in an early version). Since then I back up all important code locally. So I know firsthand that cloud storage is not absolutely reliable — do not treat this place as a safe.
5. Third-Party Services
The site runs on Cloudflare, involving: CDN (content delivery), DNS resolution, Email Routing (for receiving), KV/D1 storage, and Turnstile (human verification on the admin login). Their data policies follow Cloudflare's official documentation.
Telegram push: if you configure your own bot, mail subjects, senders and codes go to your bound Telegram. Entirely optional — if you do not configure it, nothing happens, and I do not use your Telegram info for anything else.
Sending: mail sent through this site is delivered by a third-party provider (Resend), which necessarily sees recipients and content — that is how every sending service works.
Translation: the on-page translator calls Google Translate, and text is only sent when you tap translate.
Full third-party list: Cloudflare (CDN/DNS/mail routing/storage/human verification), Resend (only when sending), Telegram (only if you configure push), Google Translate (only when you tap translate). No analytics SDKs, no event tracking, no ad networks, no shady "partners". My habit when writing code is to stuff nothing unnecessary into a page — extra code means extra maintenance.
6. Cookies & Local Storage
The site uses browser localStorage for your UI preferences: language (Chinese/English), light/dark theme, and your history of used addresses. All of this stays in your own browser and is never uploaded; clearing browser data wipes it and nothing breaks.
No advertising cookies, no cross-site tracking. Note: Cloudflare's edge may set some basic Cf cookies (load balancing, protection) — that is the platform layer, not something this site sets, and details follow Cloudflare's privacy policy. I cannot turn it off either; it is part of the cost of Cloudflare's free tier.
7. Security Measures
Small tool, but the defenses are in place: hidden admin entry plus human verification plus encrypted tokens; consecutive login failures auto-block the IP; spam floods auto-trigger protection mode on the flooded address (new mail rejected for 1 hour, existing mail kept, the address owner unaffected); captcha against automated API hammering; sending rate limits (2 per address/day, 20 per IP/day); mail content is sanitized before rendering to stop scripts injected via malicious mails; all admin endpoints require an admin token.
These measures cannot stop 100% of attacks — no website can claim that. But at least it is not running naked, and every layer was written and tested by me. Someone once tried to bypass cross-site checks with a malicious Origin header — I fixed it. Someone tried bypassing the script filter with uppercase tag names — fixed too. This tug-of-war will continue, and anything found gets fixed.
8. About Minors
This is a personal learning project; it does not target minors and has no mechanism to collect minors' information. If you are under 18, maybe tell your parents before using it. That said, the site has no payments, top-ups, lotteries or social features — it probably will not interest you anyway.
9. Your Rights
Honestly, the personal data this site holds is minimal: the address, received mail, UI preferences. Want it gone? Simple — stop using the address and it auto-expires in 24 hours. Want it gone immediately? Clear your browser's local storage and never use that address again. Everything is in plain sight: no hidden copies, no bureaucratic deletion-request process — I have no energy for a request/approval system, and none is needed, because the data barely lasts anyway.
If you dispute a ban or rate limit, email me and I will review it manually. False positives are usually lifted; deliberate spam/attacks are not — said upfront.
10. Data Breach Response
If — and I say if — a breach ever happens, say Cloudflare gets compromised or my own backend is broken into, I will do what I can: investigate and patch immediately; post an on-page notice with scope and rough timeline; reset security configs as needed (rotate keys, purge suspicious ban data, reset admin tokens).
Because this site stores very little personal data (basically random addresses and mail content), the real-world harm is limited — but what should be done will be done. Frankly, compared to big companies leaking hundreds of millions of accounts, even if this site's database were dumped, all they would get is a pile of random strings and verification codes — worth about zero. That is one more reason I insist on storing little: the less you store, the less you panic when things go wrong.
11. Policy Updates
This policy may change as features change; updates replace this page directly, no separate email notice (the update date is at the top). Continued use means you accept the updated version.
If this site ever adds a "collect more data" feature (accounts, payments — unlikely, given the site is free and non-profit), I will update this policy explicitly before launching it, never sneakily. Rest assured — I am stubborn that way and do not play word games.
12. Contact
Questions about privacy or data? Email bertuh2@outlook.com. Maintenance is basically just me, so replies may be slow (day job during the day), but every mail gets read — no read-and-ignore. Please briefly state your purpose; ads, promos and bulk mail go straight to the bin — I already get enough spam daily, do not add to it.
One last honest line: a temp mail is meant to be used and tossed — do not expect it to keep anything for you. Use it for a code, block some spam; if you like it, use it more; if not, do not. I will not chase you. Any data concern, just ask.
Read these few lines before using the site. Nothing complicated, all plain truths. Using it means you accept these terms; if not, do not use it — nobody is forcing you. No hidden traps in the fine print, and no "final interpretation right belongs to us" escape clause — the interpretation is mine, but I will interpret it literally, not creatively.
A word on origins: this site started as my personal project to learn Cloudflare Workers, written from scratch and revised across dozens of versions — mail routing, the ban system, security hardening, all polished bit by bit. So it is neither a commercial product nor a big-company service; it is a personal hobby project, running on enthusiasm.
1. Nature of Service
This is a personal learning-and-sharing project, provided free — no paid features, no memberships, no top-ups, no lotteries, no ads. Free means no SLA (service level commitment): no guarantee of always-online, no guarantee mails are never lost, no guarantee speed stays fast, no guarantee it will not be attacked — all plain truths.
If I ever stop maintaining it, it may close without notice and the mails go with it. That is why I keep repeating: never put anything important here. I am not trying to scare you; I am stating the ugly part up front so you do not feel cheated if something happens. To me this site is a free toolbox — use it however you like, but do not expect it to be as reliable as your home safe.
2. What Temp Mail Is For
This is a "use and toss" temporary mailbox. Good for: forum sign-ups, downloading resources, claiming coupons, testing mail features, blocking spam, privacy-sensitive occasions (when you do not want to leave your real email). Bad for: banks, payments, primary social accounts, government accounts — password recovery for those heavily depends on the mailbox; once a temp address expires, recovery becomes a nightmare, and that consequence is yours alone. I cannot take responsibility — and could not afford to.
Addresses expire in 24 hours (auto-renewed on incoming mail); after expiry mails are wiped and the address could theoretically be regenerated for someone else. Do not treat a temporary address as permanent — that is not just this site's rule but common sense across all temp-mail services. Like toilet paper in a public restroom: gone once used, do not expect it to stay.
One more reminder: some websites detect temp-mail domains and refuse registration (especially certain coupon-hunting campaigns). That is not this site being broken — it is the other site's policy. Try a different suffix among our domains, or try again later; sometimes it goes through.
3. Usage Rules
Normal use is free — use it however you want. But do not treat it as production infrastructure: do not send or receive important business mail, do not register accounts that need long-term maintenance, do not put this address into forms you expect to keep receiving from — because the mailbox expires, and after that those mails will not reach you.
If the site suffers abuse (APIs flooded, quotas blown), I may throttle or take it down temporarily for maintenance — for the sake of the majority, not targeting anyone. What counts as reasonable usage? No hard number, honestly — a normal person registering on sites at a normal pace is the reference line. If you generate hundreds of addresses per minute, send dozens of mails per second, or run scripts hammering the site — sorry, that is not "normal use", and the system will stop you automatically.
An experience worth sharing: I once saw someone batch-register on one platform for coupon farming; the flood of verification mails blew through a domain's delivery quota and slowed everyone else's inbox. So rate limiting is not paranoia — people have actually done this.
4. Prohibited Behavior
Explicitly forbidden: using the site to send spam, ad-bombing or phishing mail; illegal uses (fraud, gambling, money laundering, spreading prohibited content); scanning, probing or attacking this site or others' servers; batch-registering then abusing site resources; automated tools making requests far beyond normal usage (my own testing excluded).
Consequences: the address enters temporary protection mode (new mail rejected for 1 hour), attacking source IPs get rejected, and in serious cases I will not rule out cooperating with law enforcement. If put under protection by the system you can appeal at bertuh2@outlook.com with an explanation, and it may be lifted depending on the case — but deliberate spam and attacks generally will not be. Said upfront to save everyone the argument.
One more thing: many people think temp mail is for doing shady things. It is not. 90% of this site's users just register on websites, receive codes and block spam. The occasional spammer gets intercepted within a few mails, and the domain never reaches whitelists. So do not bother trying anything dirty — it will not work, and it leaves nothing worth keeping anyway.
5. Mail Delivery & Sending
Mail sent through this site is delivered by a third-party provider (Resend) — failures, delays and spam-folder landings are all possible. That is the objective reality of email systems, true for every sending service including giants like Gmail and Outlook. Within the limits of the law, this site accepts no liability for such losses.
Incoming mail depends on Cloudflare Email Routing; occasional delays or losses are possible. If a code does not arrive, wait a minute or two, then try regenerating the address. If the mail you are expecting is especially important (e.g. an account activation link), prepare a backup option — do not put all eggs in one basket; that old saying fits everywhere.
Sending has explicit limits (2 per address/day, 20 per IP/day) — anti-abuse measures, not bugs. Recipients can see your temporary address, so do not send anything you would regret — once an email is out, it is out, like water spilled.
6. Service Interruption & Termination
The site may go down or stop for maintenance, faults, attacks, domain expiry, or simply me losing interest — no advance notice promised. If conditions allow, I will try to post a notice on the page beforehand, but no guarantees. When the service stops, all mails and stats go offline with it, and no export is provided — you were not supposed to put anything important here anyway.
If the site is unreachable for a long time, it is probably not about you — check your own network first, try another network or device, then wait. If it is down for days, maybe something really happened; an email asking is fine, and I will reply with an explanation.
Honestly, this site has had a few "almost gone" moments: once the domain nearly expired because I forgot to renew, once the Cloudflare account nearly got flagged by risk control. Every time it was a false alarm, but it reminded me how fragile personal projects are — which is why "no guarantee of permanent operation" sits at the top, not as courtesy but as truth.
7. Intellectual Property & Content
The site itself (interface, code, copy) is written by me, or uses open-source components (under their respective licenses). Content you send or receive through this site belongs to you — I claim no rights over it, and take no responsibility for it: what you send is on you. There is no content moderation here (and there cannot be — thousands of mails a day, physically impossible to review), so illegal content is the sender's own responsibility.
Copying, adapting or republishing the code and copy? The code is yours to take — open-source spirit welcome; I learned standing on others' shoulders too. But do not slap it on another domain and call it your original work, and do not copy the copy verbatim — change it at least, respect the labor. I made the copy this long precisely so that whoever copies it at least reads it once before editing.
8. Disclaimer
The site is provided "as is", without any express or implied warranty. Specifically: no guarantee of uninterrupted service, no guarantee of data safety, no guarantee mails always arrive, no guarantee of zero errors. For any direct or indirect loss from using this site (including but not limited to: failed sign-ups because a code did not arrive, unrecoverable accounts because the address expired, losses from leaked mail), this site assumes no legal liability — but will do its best to help on a moral basis.
In plain human language: this is a free tool I built in my spare time. It saves you trouble and gives you convenience, but you also accept that it may let you down. If something goes wrong, I will help where I can (check whether a mail was delayed, explain why it did not arrive), but do not expect compensation — I cannot afford it; even if the running costs are not high, they all come out of my pocket.
9. Limitation of Liability & Indemnification
To the maximum extent permitted by law, the total liability of this site (and its maintainer) arising from the site is capped at what you actually paid to use it — and since the site is free, what you paid is 0. In other words, the liability cap for any loss is zero, except where the law mandates otherwise (e.g. willful illegality, gross negligence).
You agree: if your violation of these terms or your illegal activities through this site lead to any third-party claims, losses or lawsuits, you bear them yourself and must compensate this site for its resulting losses (including reasonable attorney fees — though I doubt it will ever come to that, since the site sees barely a handful of disputes a year).
One addition: if a dispute really arises, I would rather talk first than litigate. Email me with the facts; if it can be solved, solve it; if not, then discuss further. We are all adults — no need to drag a tiny tool into court.
10. Spam & Abuse
Zero tolerance for spam. Criteria include but are not limited to: mass delivery in a short time, obvious marketing/ad content, forged senders, flooding one address. When security triggers: the flooded address enters 1-hour protection mode (existing mail kept), the attacking source is rejected, and in severe cases the whole site temporarily enters defense mode (global rate limiting).
If you believe your address was falsely put under protection (say, a few normal mails got it temporarily rejected), email an appeal with your address and rough time — I will manually review and lift false positives. I once adjusted the threshold because several normal users got caught — their common trait was very frequent mail (e.g. registering on a dozen sites at once). The threshold has been loosened considerably since; normal use basically will not trigger it.
11. Changes & Governing Law
Terms may be updated; updates replace this page directly, no separate notice (the update date is shown at top). Continued use means acceptance of the current version.
The site is hosted overseas (Cloudflare is global infrastructure), governed by the legal framework of the relevant cloud provider's regions; where your local laws conflict, the stricter side applies. Any term dispute is preferably resolved through friendly negotiation — in plain words, talk it out over email. Lawsuits over a free temp-mail service? The lawyer fees alone would exceed this site's annual running cost.
12. Miscellaneous
Matters not covered here follow "common sense" and "public order and good customs". If any clause is found invalid, the rest remain in force.
Contact for this site: bertuh2@outlook.com. A few words from the heart to close: this site was built in my spare time, for neither money nor fame — just the satisfaction of something I wrote being used by someone. If it works well for you, I am happy; if you have suggestions, bring them; if you find a bug, report it — but please do not insult me. The speed at which I fix bugs depends on how clearly you describe the problem.
Enjoy using it — and remember not to keep anything important here. Use it, toss it, everyone goes home happy.