Privacy Policy
Last updated:
This Privacy Policy explains what information fake-email.pro collects, how it is used and who it is shared with. It covers the website https://fake-email.pro, the public API at api.fake-email.pro and the Fake Email browser extension for Chrome (together, the “Services”).
fake-email.pro is a disposable email service: it gives you a temporary address that only receives email. If you do not agree with this Policy, please do not use the Services.
1. Who is responsible for your data
The Services are operated by Danil Suiagin, an individual entrepreneur registered in Georgia under identification number 304690886 (“we”, “us”). We are the data controller for the information described here. Contact: support@fake-email.pro.
2. Information we collect
2.1. Using the service without an account
You can use the website without registering. When you open a page with an inbox, we create an anonymous guest record (an internal id, the plan and the time of the last activity) and set a session cookie that links your browser to it. A guest record holds no name and no email address of yours. If you clear the cookie, you lose access to the guest mailboxes.
2.2. Signing in with Google
An account is created by signing in with Google; there are no passwords and no other sign-in methods. We request the scopes openid, email and profile and read the following from the ID token Google returns:
- your Google account identifier (
sub) – to recognise your account when you sign in again; - your email address (only if Google reports it as verified) – shown in your account settings and used to recognise you when you write to support and, if you buy a paid plan, passed to Paddle to create your customer record (section 6);
- your name and the address of your profile picture – shown in the interface.
The name, email and picture are overwritten with what Google sends each time you sign in. We do not store Google access or refresh tokens, and we make no other calls to Google APIs on your behalf: we cannot read your Gmail, contacts, files or any other Google data.
Our use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. We use Google user data only to provide the sign-in and account features described above. We do not sell it, do not use it for advertising, do not use it to train AI models, and do not transfer it to anyone except as needed to provide these features, to comply with the law, or as part of a business transfer with notice to you.
2.3. Mailboxes and messages
- Mailbox addresses you create (random or chosen by you), when they were created, when they expire and whether they were deleted.
- Incoming messages sent to those addresses: the sender, subject, text, attachments and the original message file, with a trace header that records the sending mail server's IP address. We do not control what senders put into a message; it may contain personal data about you or other people.
- Delivery records: for every message, the time, the mailbox and account it went to, the plan, the sender's address and domain, the receiving domain and the size. They are used for statistics and abuse prevention and do not contain the message itself.
Messages are processed automatically to display them: we parse them and look for verification codes and confirmation links to show next to the message. We do not open the links, and we do not use message content for advertising or profiling. The service cannot send email.
2.4. API keys
If you create an API key, we store its name and description, its expiry date, the time it was last used, and a hash of the key with its last four characters. The full key is shown once and is not stored.
2.5. Technical data, IP addresses and rate limits
Every request carries your IP address. We use it to limit how often requests and guest sessions can come from one address and, through Cloudflare, to tell which country you are visiting from (see section 5); it appears in error and rate-limit entries of our server logs. We keep no log of page views. Our API servers log each request as its route, result, duration and the internal id of the account or API key, without the IP address. Our mail servers log each delivered message (the recipient mailbox address, the Message-ID, a hash and the size of the message) and rejected messages (the domains of the sender and the recipients).
2.6. Cookies and browser storage
| Name | Purpose | Lifetime |
|---|---|---|
session_id, ext_session_id | Keep you signed in on the website and in the extension (as a guest or with an account). Not readable by scripts; on the server we keep only a hash of each. | One year from the last activity |
oauth_flow | Protects the Google sign-in while it is in progress. | Up to 10 minutes |
| Interface preferences | The selected mailbox and the light or dark theme (cookies); the countdown of the 10-minute mail page (local storage). | Cookies – up to one year; local storage – until you clear it |
analytics_consent | Remembers whether you accepted or declined analytics cookies, where we ask. | Six months |
_ga, _ga_* | Google Analytics, see section 5. Where we ask for consent, set only after you accept. | Up to two years |
Cloudflare, which stands in front of the website, may set its own strictly necessary security cookies.
2.7. The Chrome extension
The extension works with the same account and the same servers as the website; everything in this Policy about mailboxes and messages applies to it. In addition:
- Stored locally in your browser (
chrome.storage.local): your active mailbox addresses, your autofill settings (including the sites where you switched it off and the address of the current tab, to check it against them) and a few counters of its own. This data stays on your device and is removed with the extension. - The extension's session is a cookie of its own,
ext_session_id, set for fake-email.pro and not readable by scripts. It stays in your browser after the extension is removed, until it expires or you clear the site's cookies. - Access to all websites is needed for autofill: the extension looks for an email field on the page you are on and offers to insert your temporary address into it. It does not collect or send us the pages you visit, their addresses, your browsing history, or anything you type into forms.
- The extension talks only to fake-email.pro. It contains no analytics and no advertising code. After installation and removal it opens a page of our website; the removal page embeds a Google Form you may ignore.
We do not sell data obtained through the extension, do not use or transfer it for purposes unrelated to the extension's single purpose (temporary email addresses and autofill), and do not use it to determine creditworthiness or for lending.
2.8. When you contact us
If you write to us by email or fill in a feedback form (Google Forms), we receive what you send and your email address if you provide it, and use it to answer you.
3. How we use information, and on what legal grounds
- To provide the Services you ask for – create mailboxes, receive and show messages, keep you signed in, apply the limits of your plan, manage API keys and paid plans (performance of a contract).
- To keep the Services secure and available – rate limiting, logs, abuse and spam prevention, backups, debugging – and to answer your requests (our legitimate interests).
- To understand in aggregate how the website is used (section 5): with your consent in the countries where we ask for it, and in our legitimate interests elsewhere.
- To comply with the law and enforce our terms (legal obligation and legitimate interests).
We do not show advertising, do not send newsletters, and do not sell personal information.
4. Who we share information with
We share information only with the service providers that help us run the Services, each for its own task:
| Provider | What for | What it receives |
|---|---|---|
| Cloudflare, Inc. | Network proxy and protection in front of the website and the API, cookie-less traffic statistics (Cloudflare Web Analytics), forwarding of our support mailbox | Your IP address and requests as they pass through; email you send to our support address. Email sent to your temporary addresses does not pass through Cloudflare. |
| Google LLC / Google Ireland Limited | Sign-in with Google, Google Analytics 4, feedback forms | What you agree to at sign-in; usage data described in section 5; what you enter into a form |
| netcup GmbH (Germany) | The servers on which the Services, the database and the message storage run | All data of the Services, stored on servers we manage |
| DigitalOcean, LLC (Spaces, Frankfurt, Germany) | Off-site backups | Backups of the database and of stored messages, encrypted by us before upload |
| Paddle.com Market Limited | Payments for paid plans, as Merchant of Record | See section 6 |
We may also disclose information when the law requires it or to protect the rights, property or safety of the Services, our users or the public, and to a successor if the Services are transferred to another owner; in that case this page will say so before the transfer. We may publish aggregated statistics that identify nobody.
5. Analytics
The website uses Google Analytics 4. It is loaded after the page has finished loading and records page views (the page address and title, the referring page), a few product events such as creating a mailbox or clicking the sign-in button, and standard device and browser data, including an approximate location derived from your IP address. It sets the cookies _ga and _ga_*. We do not send Google Analytics your mailbox addresses, messages, name or email address.
If you visit from the European Economic Area, the United Kingdom or Switzerland, Google Analytics does not load and sets no cookies until you accept it in the cookie banner. Your choice is remembered for six months; you can change it at any time with “Cookie settings” at the bottom of every page, and if you decline, Google Analytics cookies already in your browser are removed. Which country you are visiting from is determined from your IP address by Cloudflare and is not stored; a visitor whose country cannot be determined is not asked.
Elsewhere Google Analytics runs without a banner. Wherever you are, you can opt out by installing the Google Analytics Opt-out Browser Add-on, by blocking cookies for this site in your browser settings, or with a content blocker. The service works the same without analytics. How Google handles this data is described in Google's Privacy Policy.
We also use Cloudflare Web Analytics, which counts visits without cookies and without identifying visitors.
6. Payments
Paid plans are sold through Paddle (Paddle.com Market Limited and its affiliates), which acts as the Merchant of Record. When you buy a plan, we pass Paddle the email address of your account, and Paddle collects your country and billing address and your payment details. We never receive or store your card number or other payment details. From Paddle we receive what is needed to activate and manage your plan: the status of the purchase or subscription, your email address and country, and Paddle's identifiers of the customer and the transaction. Paddle processes your data as an independent controller under Paddle's Privacy Policy.
While the PRO plan is free during the open beta, no payment data is collected at all.
7. How long we keep information
| Data | Kept for |
|---|---|
| A mailbox | Receives email for up to 24 hours unless you extend it; then it stops receiving |
| Messages and attachments of a mailbox created on the website or in the extension | Currently 1 day from receipt on the Anonymous plan, 7 days on Authorized, 30 days on PRO (see Pricing); then deleted automatically. Deleted earlier if you delete the message or the mailbox, or when your storage is full and older messages make room for new ones. |
| Messages of a mailbox created through the API | Deleted together with the mailbox, 24 hours after it was created |
| Copies of messages our parser could not read | 30 days, whatever the plan and even if you delete the message; used only to fix the parser |
| The address of an expired or deleted mailbox | Kept, without messages, so that the same address is never given to anyone else |
| Account (Google identifier, email, name, picture), API keys | Until you ask us to delete the account; a key – until you revoke it |
| Guest record (an internal id, the plan, the time of the last activity) | Kept; it holds nothing that identifies you |
| Sessions | One year from the last activity, or until you sign out |
| Delivery records | 12 months |
| Server logs | 30 days |
| Request counters by IP address (rate limits) | About a day |
| Backups | Database backups – 14 days; the backup copy of messages follows the deletions of the live storage with the next nightly run |
8. Your choices and rights
What you can do yourself
- delete any message or mailbox on the website, in the extension or through the API;
- revoke an API key in the settings;
- sign out, which ends the current session; as a guest, clear the site's cookies;
- remove the extension, which deletes what it stored in your browser;
- withdraw the website's access to your Google account at myaccount.google.com/connections.
Deleting your account and data
There is no self-service button for deleting an account yet. To have your account deleted, write to support@fake-email.pro from the email address of the Google account you sign in with. We will delete the account together with its mailboxes, messages, API keys and sessions, and tell you when it is done. Copies in backups disappear as the backups expire. What remains: the bare addresses of your mailboxes, so that they are never given to anyone else, and delivery records and server logs until they expire, which then refer to an account that no longer exists.
European Economic Area, United Kingdom and Switzerland
You have the right to ask whether we hold personal data about you and to access it, to have it corrected or erased, to restrict or object to its processing, to receive it in a portable format, and to withdraw your consent to analytics at any time with “Cookie settings” at the bottom of every page. You also have the right to complain to your local data protection authority, or to the Personal Data Protection Service of Georgia; we would appreciate the chance to resolve your concern first. You are not required to give us any data, but without the session cookie or Google sign-in the features that depend on them do not work. We make no decisions about you by automated means that have legal or similarly significant effects.
California
California residents have the right to know what personal information we collect, use and disclose, to have it deleted or corrected, and not to be discriminated against for exercising these rights. We do not sell personal information and do not share it for cross-context behavioural advertising.
How to make a request
Write to support@fake-email.pro. We answer within 30 days. We may ask you to confirm that the account or mailbox is yours – for an account, by writing from its email address; for a guest mailbox, we can only act while you still have access to it, because nothing else links it to you.
9. International transfers
We are based in Georgia, and our service providers process data in other countries, including the European Union and the United States. Your information may therefore be processed in a country whose data protection laws differ from those of your own. Where the law requires it, transfers rely on the standard contractual clauses or equivalent safeguards offered by the provider.
10. Security
Connections to the website and the API are encrypted, session tokens and API keys are stored only as hashes, and backups are encrypted before they leave our servers. A mailbox is visible only to the session or account that created it. No system is perfectly secure: do not use a disposable inbox for anything you need to keep private or keep for long.
11. Children
The Services are not directed at children under 13, or under 16 in the European Economic Area. We do not knowingly collect personal data from them; if we learn that we have, we will delete it. If you believe a child has given us personal data, write to support@fake-email.pro.
12. Third-party links and services
Websites we link to and the links inside messages you receive are governed by their own privacy policies, not by this one.
13. Changes to this Policy
We update this Policy when the Services change. The current version is always on this page with the date of the last update at the top. If a change is material, we will announce it on the website before it takes effect.
Attribution
Parts of this Policy are adapted from the Creative Commons Privacy Policy by Creative Commons, used under the CC BY 4.0 licence; the text has been changed.