Privacy Policy
This page describes what actually happens to data on Check Gmail Live. It is written from the way the service is built, not from a template, so it is specific — including the parts that are less flattering. If something here is unclear, ask us on Telegram at @tingoma7111.
Summary
- The email addresses you check are processed in memory for the duration of the check and are not written to a database or file on our side. Our application log records that a check happened (time, your IP, how many addresses, which options) — not the addresses themselves.
- Proxies submitted to the Proxy Tester are retained on our server (see below). Do not submit proxies you consider confidential.
- A member account needs only a username and a password. We do not ask for an email address, phone number or name.
- We do not run advertising or analytics trackers. The only third-party requests your browser makes are for Google Fonts and, on your first visit, a country lookup at ipapi.co to preselect a language.
- Payments are made in USDT directly to our wallet; we verify them by reading public blockchain records and store the transaction ID, the sending wallet address, the amount and the network.
1. Email addresses you check
When you start a check, your browser sends the pasted list to our server over HTTPS. The server removes duplicates, keeps the list in memory while the check runs, and streams each result back to your browser over a WebSocket connection. When the check finishes (or you stop it, or you disconnect), the in-memory list and results are discarded. The API (/api/v1/check) works the same way: the list lives in memory until the response is sent.
To perform the check, each address is necessarily presented to Google's systems — in an SMTP handshake with Google's mail servers and, for addresses that accept mail, in a lookup against Google's account-status interface. How Google handles those requests is governed by Google's own policies. No message is ever sent to the address.
Our application log records, per check: a timestamp, your IP address, a random session identifier, the number of addresses, the options you selected (such as Fast Check and Check Deleted) and, when it finishes, how many results fell into each status. It does not record the addresses or the per-address results.
In your browser: the checker saves the text in the input box, your option toggles and your dark-mode preference to localStorage (key gmail-checker-state) so that a page reload does not lose your list. This stays on your device until you clear the box or clear the site's data in your browser. Downloaded TXT/CSV files are generated in your browser, not on our server.
2. Proxy Tester
The Proxy Tester works differently, and you should know this before using it. When you submit a proxy list, the server appends the submitted list to a file on our server, and for every proxy that tests as working it also records the proxy address, the public IP it resolves to, its geolocation and its latency. We use this archive to maintain and de-duplicate our own proxy lists. Submitted proxies may therefore be kept indefinitely and used by us. Do not submit proxies you consider confidential — use the downloadable local checker script offered on that page instead, which runs entirely on your own machine.
Geolocation of a working proxy's public IP is obtained server-side from ip-api.com. The proxy's exit IP is sent to that service; your own IP address is not.
3. Member accounts
Running a check requires a free member account. Registration asks for a username and a password only. We store:
- your username and a bcrypt hash of your password (we cannot read the password itself);
- the date of registration and the IP address used to register; the date and IP address of your last login;
- usage counters per IP address: number of logins, number of checks and total addresses checked;
- your API key, plan and entitlement fields (per-run limit, thread cap, feature flags, Premium expiry, volume top-up total), and any internal notes an administrator adds about the account (for example the reason for a suspension);
- login sessions: a random token, your user ID and username, the creation time and the IP address. Sessions expire after 30 days or when you log out.
The IP-based fields exist to enforce the limits in our Terms — a maximum number of accounts per IP address and detection of an API key being shared across several IP addresses — and for troubleshooting.
4. Cookies and browser storage
| Name | Type | Purpose | Lifetime |
|---|---|---|---|
memberSession | Cookie (HttpOnly, Secure, SameSite=Strict) | Keeps you signed in to your member account. | Browser session; server side up to 30 days |
adminSession | Cookie (HttpOnly, Secure, SameSite=Strict) | Staff only — administration panel. | 24 hours |
lang | localStorage | Remembers the interface language you chose. | Until cleared |
gmail-checker-state | localStorage | Input box text, option toggles, dark mode on the Gmail checker. | Until cleared |
proxy-checker-state | localStorage | Input box text, options, dark mode on the Proxy Tester. | Until cleared |
There are no advertising, analytics or cross-site tracking cookies. localStorage entries never leave your browser; you can remove them at any time through your browser's site-data settings.
5. Language detection
On your first visit, if you have not chosen a language yet, the page asks ipapi.co for the country code of your IP address in order to preselect a language. Your IP address is sent to ipapi.co for that single request; the result is used only to pick a language, and your choice is then stored locally so the request is not repeated.
6. Payments
Premium plans and volume top-ups are paid in USDT on the TRON network (TRC-20) or BNB Smart Chain (BEP-20), sent from your own wallet directly to ours. There is no payment processor and we never see card or bank details. To confirm a payment we read public blockchain records through TronScan / TronGrid (TRON) and public BNB Smart Chain nodes. For every confirmed payment we store: the transaction ID, the sending wallet address, the amount, the network, the plan it activated, the time, and your username. Blockchain transactions are public by design and can be viewed by anyone on a block explorer; we do not add anything to the chain.
7. Server logs and security
Like any web server, ours records requests: IP address, requested URL, timestamp, response status and user-agent string, plus the application events described above (checks started and completed, logins, registrations, payment confirmations, rate-limit hits). We use these logs to keep the service running, to investigate errors and abuse, and to enforce rate limits and IP blocks. They are not used for advertising and are not sold. All traffic to the site is served over HTTPS.
8. Third parties
| Service | What is sent | Why |
|---|---|---|
| Google (mail servers and account-status interface) | The email addresses being checked, from our server | Performing the verification itself |
| Google Fonts | Your browser's request for the Inter font file (your IP) | Page typography |
| ipapi.co | Your IP address, once, on first visit | Preselecting a language |
| ip-api.com | The public IP of a working proxy (server-side) | Geolocation in the Proxy Tester |
| TronScan, TronGrid, BNB Smart Chain nodes | Transaction IDs and our wallet address | Confirming USDT payments |
| Telegram | Whatever you choose to send us there | Support and announcements — governed by Telegram's own policy |
We do not share account data, check lists or logs with anyone else, except where the law requires it.
9. Your choices
- Deleting your account. Message us on Telegram from the account you want removed (or with proof you control it) and we will delete the account record. Payment records tied to a transaction ID are kept for accounting.
- Access and correction. Ask us on Telegram and we will tell you what is stored against your username.
- Local data. Clear the input box, or clear the site's data in your browser, to remove anything stored in localStorage.
- Proxies. If you do not want a proxy list retained, do not submit it to the online tester; use the local script instead.
10. Children
The service is intended for adults managing email lists. It is not directed at children, and we do not knowingly collect data from anyone under 16.
11. Changes
When this policy changes we update the date at the top of the page. Material changes are also announced on our Telegram channel.
12. Contact
Privacy questions and deletion requests: Telegram @tingoma7111. See the Contact page for what to include in your message.