This site is still being built · Live now (Beta)

Privacy at isitphish

Last updated: 2026-11-20 (version 2026-11-20b)

When you check an email

What happens to the email you submit, who can read it and who processes it.

What isitphish stores, and for how long.

When you check an email, isitphish stores a copy of the email you submitted, the links found in it, the screenshots of those links and the result. In what we store, the card, Social Security and bank numbers we can detect are blanked out, and attachments are kept only as their name, type, size and fingerprint (SHA-256), never their contents. An email attached to the email you submit (for example, one forwarded as an attachment) is treated as part of the email you submitted: when we can read it, its text is stored, with the same numbers blanked out, but not the contents of its own attachments. All of it is deleted automatically after 7 days, unless you have a paid seat set to keep checks longer (see "Paid seats: keeping checks longer."). If we find card, Social Security or bank numbers in the email, in its links, or in the addresses or titles of the pages those links lead to, all of it is deleted after 24 hours instead. During the time it is kept, a person at The Cyber Friend may read it (see "Who at The Cyber Friend can read it."). Before the 7 days are up, we may keep a separate copy with personal details removed (see "Improving isitphish."). If you ask for an AI explanation, Anthropic keeps its copy for up to 30 days (see "Who processes it").

ImportantWho at The Cyber Friend can read it.

Assume that a person at The Cyber Friend may read any email you submit and its result. We do not store the contents of attachments, only their names, types, sizes and fingerprints. An email attached to the email you submit (for example, one forwarded as an attachment) is treated as part of the email you submitted: when we can read it, we store its text, but not the contents of its own attachments. Today the owner of The Cyber Friend can open stored submissions while they are kept (up to 7 days, or longer on a paid seat set to keep checks longer), and the copies with personal details removed that we keep for longer (see "Improving isitphish."). For checks kept longer than 7 days, we open them only when you ask us to, to fix a fault that affects your checks, or when the law requires it. We may read them to review results, especially when the checks cannot decide; to improve our checks and our AI; and to look into abuse and security problems. We blank out some numbers automatically, but we can miss them, so remove sensitive details before you submit. isitphish does not offer a human review service. A person reading your email does not mean anyone will reply to you, look at your result again or change it, and there is no response time. For email submitted before 2026-11-08, we do this only to look into abuse and security problems.

ImportantWho can see a result.

Only the browser that ran a check can open its result, its report and its screenshots, using a cookie set for that check (see "Cookies for checks and sign-in."). A check you made while signed in can also be opened from your account, and, on a Team plan, by the plan's Owner and its admins for up to 7 days after it is made. Sharing the link does not let anyone else open it; to share a result, download its report. A check is deleted after 7 days, or after 24 hours if we find card, Social Security or bank numbers, or later on a paid seat set to keep checks longer. People at The Cyber Friend can also see it (see "Who at The Cyber Friend can read it.").

Who processes it.

Cloudflare runs isitphish: the hosting, the storage, the screenshot queue, the isolated browser that opens links, the bot check (Turnstile) and the beta sign-in (Cloudflare Access). Cloudflare also sends our launch and product update emails, and passes on to us any email you send to an isitphish.ai address. If you sign in to the beta with Google, that company handles your sign-in. The AI explanation is offered only when you connect from the United States (including Puerto Rico, Guam, the US Virgin Islands, American Samoa, the Northern Mariana Islands and the US Minor Outlying Islands), Canada, Mexico or the United Kingdom. When you ask for an AI explanation, the parts of the email needed for it are sent to Anthropic, our AI provider. On a check you ask for it with the AI box: a check made with the box unticked asks for no AI explanation. With a paid seat that can run checks you can also press "Re-check with AI" on a check of yours that has no AI explanation, while we still hold its email and within your daily AI credits: the AI may then run on it, and when it runs, the parts of the stored email needed for it are sent to Anthropic in the same way, even if the box was unticked when you made the check. On the free and beta checkers the box always starts unticked, and on the free checker a ticked box asks for the AI only when our rules have not already found the email dangerous, except while a free AI offer of ours is running, when a ticked box asks for the AI on every free check; in both cases within the daily limits. With a paid seat that can run checks, your account has the setting "Start each check with the AI box ticked". The setting itself sends nothing. While it is on for you and you open the check page from the United States (including Puerto Rico, Guam, the US Virgin Islands, American Samoa, the Northern Mariana Islands and the US Minor Outlying Islands), Canada or Mexico, the box starts ticked, and you can untick it on any check to keep that email from the AI. With the setting off, or from anywhere else, the box starts unticked. The setting is off until it is turned on. At the checkout, the AI option starts ticked if you connect from one of those countries and either no choice of yours is on record, or your last recorded choice was "on" at a checkout whose payment page did not open; otherwise it starts as your setting is. What the box shows is recorded as your choice when the payment step starts, and becomes your setting once the payment page opens. It is for your own account only. With such a seat you can change the setting with one click on your account page, or with "Turn it off" on a result, when you connect from one of those countries, unless the owner of your Team plan has turned it off for the team. On a Team plan the owner of the plan can set it for the team, on the same page, from those countries: "off for the team" turns it off for every member, and no member can turn it on while that stands; "on for the team" turns it on for every member whose own last choice was not "off". Each member can still tick or untick the box on any single check. Before we send them, we remove the card numbers, Social Security numbers and bank account numbers we can detect. Other details in the email, such as names and addresses, may still be sent. Anthropic does not use any of it to train its models. Anthropic keeps what we send, and the explanation it returns, for up to 30 days, and may look at it during that time to check for misuse and for security. Anthropic may keep it longer if it is flagged for breaking Anthropic's usage policies, or if the law requires it. If you buy a paid plan, Stripe processes the payment (see "Payments."), and Cloudflare also sends our account emails (see "Customer accounts."). No other company receives the email you submit for checking.

Improving isitphish.

Every day, before the 7-day deletion, an automated job reads the emails we still hold and makes copies of them with personal details removed. The job follows fixed rules and runs inside isitphish; it does not use AI. It removes the names and email addresses of the people the email was sent to, all IP addresses, signatures, phone numbers, street addresses and other personal details its rules find. On results marked Dangerous, the copy keeps the sender's full address as shown in the email (name and email address, including any reply-to or return address); on all other results, it keeps only the domain of those addresses (the part after the @). Other email addresses in it keep only their domain. The copy keeps the phishing signs, such as links, domains and the warning signs we found, but removes the parts of links that could point to the person the email was sent to. It keeps no attachment contents (only each attachment's type, size and fingerprint) and no screenshots. An email attached to the email you submit (for example, one forwarded as an attachment) is treated as part of the email you submitted: when we can read it, its text is copied under the same rules, but not the contents of its own attachments. The removal is automatic and can miss things. We keep these copies for up to 12 months as test and training examples to improve our checks and our own AI, and a person at The Cyber Friend may read them. A copy is not linked to your check, your account or your IP address, and we do not try to find out who is in it. The copies are stored with Cloudflare, which runs isitphish (see "Who processes it."). No other company receives them, and Anthropic does not train on them. We may share phishing signs from them, such as links and domains, with others who fight phishing. The original email is still deleted after 7 days. We leave out emails in which we find card, Social Security or bank numbers, any email you check with "Do not use this email to improve isitphish." ticked, and emails covered by an opt-out sent to privacy@isitphish.ai. To opt out by email, send us the case ID shown with each result (it starts with TCF-). If you are a beta member, you can instead send the email address you sign in with: we then leave out every check you make while signed in that we have not copied yet, including later ones, and we keep a one-way hash of that address on an opt-out list to do this. An opt-out by email reaches only emails we have not copied yet. Once a copy is made, it is not linked to you, so we cannot find it to remove it. This applies only to email submitted on or after 2026-11-08.

Result feedback.

If you use "Is this result wrong?" under a result, or the address printed in its report, we keep what you chose (Legitimate (not a scam), Spam or Phishing / scam), what you typed under "Why?", the case ID, the result it is about, whether the check was free, beta or paid, and the time. Before we store what you typed, we blank out the card, Social Security and bank numbers we can detect, but we can miss them, so do not type sensitive details there. We do not add your IP address, email address or account to it; the form's limits use only a one-way hash of your IP address. For 7 days after you send it, it is also stored with the check's internal ID, so that a person at The Cyber Friend can compare it with the stored check while that is kept. A person at The Cyber Friend may read it to review the result and to improve our checks. It never changes a result automatically, and only feedback that a person has confirmed is exported as a test example. We keep it for up to 12 months. Cloudflare stores it. It is not emailed to anyone, and no other company receives it.

Other people's information.

An email can contain other people's names, addresses or messages. Only submit email you have the right to share. You are responsible for what you submit.

Accounts and paid plans

Sign-in, paid seats, teams, billing and access keys.

Team plans: who can see your checks.

On a Team plan (any plan with more than one seat), the plan's Owner and its admins can open the checks of the people on the team, including the email, its result and its screenshots, for up to 7 days after each check is made. Members and viewers can open only their own checks. The plan's Owner can also search a list of the team's checks by case number, ticket number, member, date or result, for up to 7 days after each check is made; the list shows each check's case number and ticket number, the email address of the person who ran it, when, and its result, never the checked email itself, the full result or the screenshots. To make this search work, we record which team plan each check was made on, and delete that record within a day after the check is deleted. The Owner, the admins and the viewers can see who is on the team and each person's role. Members see their own checks. You can add a ticket number to a check you ran; we store it with the check, show it with that check's result, and delete it with the check. Enter only a ticket number, not names or other personal details. Your organization decides who holds each role; ask your plan's Owner who holds each role. We record role changes, and people added or removed by the Owner or an admin on the team page (who made the change, for whom, when, and the old and new role), and keep that record with your team's account details.

Team invites.

On a Team plan, when the Owner or an admin adds a person to a seat, we email that person an invite with a link that works for 7 days. They join the team only if they accept it, signed in to isitphish with that address. We keep each invite (the address, the role, who sent it, when, a one-way hash of the link, and whether it was accepted, declined, cancelled, ran out, or ended because they joined another team) for 30 days after it is sent, and delete it within a day after that. When someone accepts, we keep a record of the acceptance (the address, the role, who invited them, when, the version of our terms then in force, and the exact words they were shown, with a fingerprint of them) for as long as we keep their account details (see "Customer accounts.") and for 1 year after. Cloudflare sends the invite emails.

Customer accounts.

Paying customers, and people who redeem an access key, sign in to an isitphish account with a one-time code that we email to them. We store no passwords. A code works once and expires after 10 minutes, and we keep only a one-way hash of it. We keep your account email, your account ID, your role on the team (Owner, admin, member or viewer), the name of your Organization if you give one, and the email of each person who holds a seat on your account, while the account exists and for 6 years after it ends. Your account also stores your "Start each check with the AI box ticked" setting and a record of each choice: on or off, the date and time, where it was made (the checkout, your account page or a result page), the version of our Terms stated on the site at that time, and a fingerprint of the text shown with the choice. A choice at the checkout is recorded when the payment step starts, even if the payment page then does not open. If you try the checkout again within 10 minutes and the box and its text are as in your newest record, no second record is written. If you own a Team plan, each choice you make for the team is recorded in the same way, with the plan and your account. We keep these records while your account exists and for 6 years after it ends. If you add your name or a job title to your account, we store them with your other account details and show them only on your account page. You can change or remove them there. If you add a profile photo, we store it with your account and show it only on your account page. You can replace or remove it there. We delete it when you replace or remove it, and within a day after your account ends. When you upload a photo, we remove its EXIF, GPS and text metadata, such as location and camera details. For security, we keep a record of each sign-in (the time and a one-way hash of your IP address) for 90 days. We set one cookie to keep you signed in, one more if you trust a browser (see "Multi-factor sign-in."; signing out does not remove it), and short-lived ones while you sign in (see "Cookies for checks and sign-in."). The cookie that keeps you signed in is not used for advertising or analytics, and it ends after 30 days or when you sign out. We email Owners about their plan: the sign-in codes, what you agreed to when you bought, renewal reminders, price changes, failed payments and cancellations. If your team requires multi-factor sign-in, we may email you a reminder to set it up. We also email you when a second sign-in step is added, removed or reset, when new recovery codes are made, and about a recovery request on your account. These emails have no unsubscribe link, because they are about your account. Cloudflare sends our sign-in codes and these emails; Stripe sends receipts.

Multi-factor sign-in.

If you turn on multi-factor sign-in, we store what we need to check your second step. For an authenticator app, we store its secret key, encrypted. For a passkey, we store its ID, its public key and algorithm, its signature counter, the name you give it, and when it was added and last used; your fingerprint, face or PIN never leaves your device. For recovery codes, we store a one-way hash of each code, the account it belongs to, when the codes were made and whether each has been used. If you tick "Trust this browser for 30 days", we set a cookie on that browser and keep a one-way hash of it for 30 days, so we can skip the second step there; "Forget all" ends them. On a Team plan, the Owner and the admins can see whether you have multi-factor sign-in on and which kind of method you use (never your codes or keys), can reset it (the Owner for admins, members and viewers; the admins for members and viewers; neither for someone who set it up before joining the plan), and can send you a reminder email; only the Owner can require it. When the Owner or an admin resets someone's multi-factor sign-in, we keep a record of who reset it, for whom, on which plan and when (no email address and no code) for 31 days, and if an admin did it, we email the Owner. If the Owner requires it, we keep that rule (the date it starts, who set it and when) until the Owner turns it off or the plan's record is deleted. We delete a method when you remove it or when it is reset, and all of them within a day after your account ends. After a recovery by email or a reset by your plan's Owner or an admin, we keep a note that the account must set up a second step again (and when that changed) until the account ends, and delete it within a day after that. If a plan's Owner, the holder of a Pro plan, or anyone else without a seat on a plan someone else owns asks to recover their account by email, we keep a record of the request (when it was made, opened, cancelled or finished, and by which account) for 31 days, email the account, and, on a Team plan, email its admins a link to cancel it. We record each second-step sign-in like any other sign-in (the time and a one-way hash of your IP address) for 90 days.

Payments.

If you buy a paid plan, Stripe processes the payment for us. You enter your payment details on a Stripe payment page, and Stripe collects them, with your name, email and billing address; they go to Stripe, not to us, and we never receive or store your full card number. We send Stripe your account email, your plan and number of seats, and our account ID for you. From Stripe we keep your Stripe customer ID, your subscription ID, your plan, the number of seats, the billing period, the status of your plan (for example active, past due or cancelled), the dates of the current period, and the amount, date and status of each invoice and refund. When you buy, we also keep a record of what you agreed to: your account email, the plan, the price, the billing period, the number of seats, the exact wording you agreed to and its version, the time, and a one-way hash of your IP address. We keep these billing records and that record while your account exists and for 6 years after it ends, in case of a dispute. Stripe uses your payment details to process payments for us, and also for its own purposes, such as preventing fraud and meeting its legal duties, as its privacy policy explains (https://stripe.com/privacy). Stripe also emails your receipts and shows your card and invoices when you manage billing from your account page.

Beta sign-in.

Private beta members who do not have a paid plan sign in through Cloudflare Access with Google or an emailed one-time code. Paying customers sign in with an isitphish account instead (see "Customer accounts."). We store no passwords. Cloudflare Access handles your sign-in email, and Google handles the sign-in if you choose it. We keep a record that you accepted the Beta Program Terms (your sign-in email, your Cloudflare Access user ID or isitphish account ID, the terms version and a fingerprint of its text, the time, and a one-way hash of your IP address) while you are a member and for 6 years after, in case of a dispute. Beta usage limits use a one-way hash of your email.

Your usage page.

When you check an email while signed in, we keep a list of your checks (the case ID, the time and the verdict, not the email) for up to 7 days, and a count of your checks and AI explanations for up to 13 months, so you can see them on your usage page.

Access keys.

If you redeem an access key, we record which account redeemed it and when, and the date your access ends. We delete the record of the key 13 months after it was redeemed or withdrawn, and the end date 90 days after your access ends. We never store a key itself, only a one-way code of it. To stop guessing, we count failed tries for at most one day, by account and by a one-way hash of your IP address.

Access key invites.

The isitphish team can email an access key to a person. We use that email address only to send that one email and to limit how many invites go to it; it is not added to any list and is not used for marketing. The email contains the key; we do not keep a copy of the email, the address or the key. We keep a record of each invite (the time, which key it carried, whether it was sent, and a one-way code of the address) for 13 months, and a count of invites to that code for one day. Cloudflare sends the email.

Cookies, logs and statistics

The cookies we set, what we count and what our hosting provider logs.

Cookies for checks and sign-in.

When you run a check, we set a cookie, __Host-isp_chk, that lets only your browser open that check's result, report and screenshots. It holds a random value and expires after 8 days. We keep only a one-way hash of it with each check it ran, and delete that with the check. When you ask for a sign-in code or link, we set a cookie, __Host-isp_pre, for 10 minutes, so that the emailed link can finish signing in that browser. We keep a one-way hash of it, with the browser and system name (for example, Chrome on Windows), for those 10 minutes. If your account has a second sign-in step and the browser is not trusted, after the code or link we set a cookie, __Host-isp_mfa, for 10 minutes, so that the browser can finish signing in with the second step, and keep a one-way hash of it for those 10 minutes. If you tick "Trust this browser for 30 days", we set a cookie, __Host-isp_trust, for 30 days (see "Multi-factor sign-in."). These cookies are needed for the service to work and are set wherever you connect from, including the EU and the UK. They are not used for statistics, advertising or anything else.

Logs.

Logs record counts, timings and error codes, never the email text or the links. For security and abuse prevention, our hosting provider (Cloudflare) keeps a short log of each request, including your IP address, browser details and approximate location, for up to 7 days. Our own usage limits use only a one-way hash of your IP address and, for the free checker's daily limit, a one-way hash of the free-check visitor cookie's ID (see "Free check statistics."). From 2026-11-09, wherever this policy says "a one-way hash of your IP address", for an IPv6 address the hash is of the first half of the address (its network part) only, except in the records of what you agreed to (the Beta Program Terms and purchases), which use the whole address; records made before then used the whole address.

Visitor statistics.

We count visits to our information pages (the home page, How it checks, Examples, About, FAQ and Guides) with Cloudflare Web Analytics. It is not used on the checker, the beta, the unsubscribe page or the Privacy and Terms pages. It does not use cookies or track you across sites. On those six pages, your browser sends Cloudflare the page address, the referring site, your browser and device type, and how fast the page loaded. As with any request, Cloudflare sees your IP address and uses it to work out your country. We see only totals, not individual visitors.

Our own visitor and usage counts.

Separately from Cloudflare Web Analytics, isitphish itself counts, each day, how many visitors open each of its web pages, including the checker and the Privacy and Terms pages. To count a visitor only once per page per day, it makes a one-way hash of your IP address, the browser and system name your browser sends (its user agent), the page address and a random value that changes every day (UTC). The random value and the hashes are deleted from our database within minutes after the day ends. Our hosting provider, Cloudflare, keeps restore copies of our database that can still hold them for up to 30 days; after that, a hash can no longer be linked to you. The daily totals we keep hold only each page's address (without anything after a "?", and with any ID in it replaced) and its number of visitors that day. This counting sets no cookie, adds no script to any page and does not store your IP address or your user agent. A page view is not counted when its user agent does not look like a usual browser's, or names a known bot, crawler, link preview or automated tool (such as our own site-check scripts), or when the browser only prefetches the page. A visit whose user agent looks like an ordinary browser's is counted, even when it comes from us. We also count, per day, the checks run (free, paid and beta), new customer accounts, sign-ins to customer accounts and PDF reports downloaded. These are totals only, with no email address and no account or check ID. We keep these daily totals for 400 days, then delete them. Only isitphish's site administrators at The Cyber Friend can see them; customers, including the Owner of a Team plan, cannot.

Free check statistics.

To count how many people use the free checker each day and how many come back, and to apply the free checker's daily limit, isitphish sets the cookie __Host-isp_visitor when you run a free check on the checker page. It holds a random ID, is sent only to isitphish, is not used for advertising or to follow you on other websites, and expires 395 days (about 13 months) after it is set. We store only a one-way hash of that ID with the first and the latest day you ran a free check, and delete it 395 days after your first free check. We use it only to count new and returning free users per day, next to daily totals of free checks, screenshot runs and AI explanations, and to apply the free checker's daily limit: we keep a count of your free checks for each day under a one-way hash of that ID, and delete it after 7 days. If you connect from the European Union, the European Economic Area, the United Kingdom, Switzerland, Gibraltar, Guernsey, Jersey or the Isle of Man, or if we cannot tell where you connect from (Cloudflare works out your country from your IP address), we neither set nor read this cookie, your free check is counted only as a visit we cannot identify, and the daily limit uses only a one-way hash of your IP address, kept for 7 days. Checks made through the beta or through a paid seat's checker do not use this cookie. If you delete the cookie, your next free check is counted as a new user. People at The Cyber Friend see only the daily totals.

Do Not Track.

isitphish sets no advertising cookies. Its only analytics cookie is the free-check visitor cookie (see "Free check statistics."), which also applies the free checker's daily limit and is sent only to isitphish. Neither isitphish nor our visitor statistics track you across other websites, so isitphish does not respond differently to Do Not Track signals.

Mailing list and applications

The launch updates list and partner applications.

Launch updates list.

The launch list is closed to new sign-ups. If you joined it earlier, you stay on it, and we keep your email address, the time you joined, the consent wording you agreed to, and a one-way hash of your IP address, until you unsubscribe or ask us to remove you. We use it only to email you about the isitphish launch and product updates. Every email we send has an unsubscribe link, and you can also ask privacy@isitphish.ai to remove you. Unsubscribing deletes your entry from the list. We never sell the list. Cloudflare, which sends the emails for us, is the only company that receives it.

Partner applications.

If you apply to become a partner, we keep the details you send (company, name, work email, role, seat estimate and message), the time, the consent wording and a one-way hash of your IP address, for 12 months or for as long as you are a partner and 6 years after. Cloudflare stores them. We email a copy to The Cyber Friend's sales mailbox, which Microsoft hosts. We use them only to reply about the partner program. Ask privacy@isitphish.ai to delete them.

About this policy

Who we are, children, and how this page changes.

Who we are.

isitphish is run by The Cyber Friend LLC, 2222 W Grand River Ave Ste A, Okemos, MI 48864.

Children.

isitphish is for adults 18 and older and is not directed to children. If we learn that a child under 13 has given us personal information, we delete it.

Changes to this page.

If we change this page, we post the new version here with its date. We will not use email you have already submitted in a new way without asking you first.

isitphish is a product of The Cyber Friend.