(As of November 2025)

MetaMask Transaction Shield Limited Supplemental Terms of Use

The following supplemental terms of use apply to your subscription to MetaMask Transaction Shield in addition to the Consensys Terms of Use posted at https://consensys.io/terms-of-use/ (the “ToU”). In case of inconsistency between the general and supplemental terms, these supplemental terms shall control. You agree to read all terms and conditions applicable to MetaMask Transaction Shield and that you will comply with them in all respects.

Definitions

“Active MetaMask Transaction Shield Subscription” means a subscription-based protection plan under which the subscriber, upon timely payment of the subscription fee, becomes eligible for the specified services listed under Metamask Transaction Shield (as listed on https://metamask.io/transaction-shield).

“Covered Transaction Protection Event” means any transaction that is not subject to an Exclusion as defined herein where a transaction made in MetaMask during an active MetaMask Transaction Shield subscription in which the MetaMask Transaction Shield Transaction screener fails to detect a transaction that results in a Covered Loss to the subscriber.

“Covered Loss” means a loss where a subscriber loses assets in a confirmed transaction where the user was shown that the transaction where the loss occurred was covered by Metamask Transaction Shield and MetaMask Transaction Shield did not indicate the risk of loss to the subscriber and the transaction wasn’t subject to any Exclusions as defined herein. Subject to the Covered Transaction Cap as defined herein, all Covered Losses will be denominated in mUSD by Consensys in its sole discretion at the time of loss.

“Covered Transaction Cap” means 100 covered transactions per month with an aggregate value of up to $10,000 USD per month.

“Exclusions” mean any of the below scenarios in which the proximate cause of a subscriber loss is any of the following:

The subscriber had their seed phrases or private keys compromised as a result of subscriber behavior.
- Non-exhaustive examples include: phishing, sharing keys, losing keys, improperly storing keys) and/or malware.
The subscriber sustains a purely economic loss.
- Non-exhaustive examples include: the subscriber’s transaction and MetaMask behaved as expected, but the subscriber sustained an economic loss due to the transaction the subscriber undertook. This could include interacting with honeypot or similar token contracts. Economic losses are not covered under MetaMask Transaction Shield.
Losses that are not from the subscriber’s wallet where Metamask is signing. Only transactions exclusively cryptographically signed by MetaMask are Covered Transactions for purposes of a MetaMask Transaction Shield Subscription.
The subscriber incurs a loss due to their MetaMask wallet being tampered with in any way not specifically endorsed by MetaMask.
- Non-exhaustive examples include: the subscriber makes changes to the code or functionality of MetaMask either directly or indirectly.
Losses due to subscriber behavior:
- Non-exhaustive examples include: the subscriber ignored Metamask Transaction Shield scanner results and continued with a transaction despite being advised by MetaMask Transaction Shield that the transaction would not be covered.
Losses whose proximate cause occurred outside an active MetaMask Transaction Shield subscription.
- Non-exhaustive examples include: the subscriber entered into a transaction prior to having an active subscription and the losses that occur as a result of that transaction occur during the subscription period. Examples may include granting permissions to token contracts which are later exploited during a subscription.
Losses occur on an unsupported chain
- The list of MetaMask supported blockchains are listed in ‘Supported Networks’
Hacked Protocols
- E.g. where the protocol or smart contract has a vulnerability and funds are stolen through an exploit.
If in our sole discretion we believe that your use of our Services is in violation of applicable laws or regulations.

“Priority Customer Support” means: that the user will be provided with priority access to technical support. You may seek or receive technical or product support, information, advice, or guidance from us regarding the Offerings, including via third party service provider, chat interface, or email. All support made available or provided by or on behalf of Consensys is believed to be reliable, but we do not make representations or warranties, express or implied, as to its accuracy, its completeness, or the results to be obtained.

“Supported Networks” means the networks found at https://metamask.io/transaction-shield as updated from time to time. In the event of a chain split, MetaMask in its exclusive discretion will determine the chain(s) it supports. In the event a Supported Network is removed, your subscription will remain applicable to that Supported Network only for the remainder of the current Term of your subscription in which the Supported Network became unsupported.

1. MetaMask Transaction Shield. MetaMask Transaction Shield is a subscription membership offering subscribers transaction screening, a warranty on such screening, and priority customer support. MetaMask Transaction Shield subscribers are eligible for transaction protection for Covered Transaction Protection Events where a Covered Loss occurs up to the Covered Transaction Cap.

2. Term and Termination. MetaMask Transaction Shield subscriptions are on a monthly basis or annual basis beginning on the date of subscription. Each “month” of term shall be defined as the period beginning as at the subscription timestamp, ending at the same local time and date in the following month. In cases where a corresponding date does not exist in the following month (e.g., January 31 to February), the warranty period will end on the last day of the next month. Subscriptions renew upon receipt of payment. Consensys reserves the right to terminate your subscription in our sole discretion. If we terminate your subscription, you will receive a prorated refund of your subscription fee (prorated based on the termination date and the date that your billing cycle ends).

3. Conditions Required for Covered Loss. If a subscriber sustains a Covered Loss as defined herein, Consensys will require that the user meet the following list of conditions to be eligible for payment.

The appropriate subscription fees have been paid in full due on or before the start date of the Metamask Transaction Shield subscription.
User submissions must not be fraudulent.
The transaction does not fall within any of the Exclusions.
Your application must be filed with Metamask within 21 days of the transaction which resulted in an alleged Covered Loss.
User to provide certain information as may be required by law to facilitate such payment in its sole discretion, including but not limited to identifying information. Any information provided is subject to our Privacy Notice and Supplemental Privacy Notice. Failure to provide this information within 30 days of written request by Consensys may render a Covered Loss void.

4. No Assignment. Your subscription cannot be transferred or assigned.

5. Not Insurance. Metamask Transaction Shield is not insurance and does not provide reimbursements for many types of losses that insurance is meant to cover. Metamask Transaction Shield does not provide reimbursements for losses due to fortuitous events that are to a substantial extent beyond the control of you and Consensys. For example, Metamask Transaction Shield does not cover losses resulting from a cyber-security attack on Metamask’s systems, the exposure of a cryptographic private key to a third party, or the total loss of a cryptographic private key. To the extent that you require protection beyond Metamask Transaction Shield, we strongly encourage you to purchase an insurance policy that provides coverage for fortuitous events that may result in the loss of funds held in your Metamask account.

6. Release. As a subscriber, as it relates to any Covered Transaction Protection Event, your sole and exclusive remedy with Consensys is payment for the Covered Loss pursuant to your subscription, and you release and forever discharge Consensys all of its employees, agents, successors, assigns, heirs, legal representatives, affiliates, directors and officers from and against any and all actions, claims, suits, demands, payment obligations or other obligations or liabilities of any nature whatsoever, whether known or unknown, which Consensys or any of its employees, agents, successors, assigns, heirs, legal representatives, affiliates, directors and officers have had, now have or may in the future have directly or indirectly arising out of (or in connection with) the Covered Transaction Protection Event.

Supplemental Privacy Notice — MetaMask Transaction Shield

Effective: November 2025

This Supplemental Privacy Notice applies to you only if you participate in the MetaMask Transaction Shield offering. Consensys Software, Inc. is the data controller with regard to the provision of the offering. This Supplemental Privacy Notice sets out important information about the collection and processing of Personal Information that may occur when you engage with the offering. This Supplemental Privacy Notice is incorporated into and forms part of the Consensys Global Privacy Notice.

Defined terms used in the Supplemental Privacy Notice have the same meaning as those defined in the Global Privacy Notice and the MetaMask Transaction Shield Supplemental Terms.

Personal Information We Collect

Location information - when you opt-in to participate in the MetaMask Transaction Shield offering, we temporarily process your IP address to derive your general location information. We do this to determine your eligibility to participate in the MetaMask Transaction Shield offering and to ensure that we are not providing services to regions prohibited by sanctions laws.
Usage information - transaction related information, such as transaction hash, and user event information is processed for the purposes of providing you the offering and the management of claims that you submit for the reimbursement of a Covered Loss. Users who participate in the MetaMask Transaction Shield offering are also opted-in to our analytics data collection feature (also known as MetaMetrics). To learn more about MetaMetrics how to manage relevant settings, please see our relevant support article (here).
Covered Loss information - when you submit a claim for reimbursement of a Covered Loss, you will need to provide information to substantiate your claim. You may also be required to provide information to verify your compliance with the MetaMask Transaction Shield Supplemental Terms. This may include the collection of data required to verify your identity.
Contact information - where you submit a claim for reimbursement of a Covered Loss, you will need to provide your email address so that we can contact you about your claim. You can also choose to share your email when you pay by credit card for the purposes of receiving payment confirmation, invoices and reminders from Stripe (for example, where your card has expired).
Financial information - where you pay by credit card, this data will be collected directly by a third-party provider (Stripe) and it will be used solely for the purpose of fulfilling your purchase request of the MetaMask Transaction Shield subscription.
Other information - we process additional information as necessary to provide the MetaMask Transaction Shield offering. This may include wallet related information, to the extent that you share this information for the purposes of receiving reimbursement for a Covered Loss.

How We Use the Personal Information We Collect

We only process personal information as necessary to provide the MetaMask Transaction Shield Offering. If you are in a region where a legal basis is required for the purposes of processing personal information, we rely on the performance of the contract between you and Consensys Software, Inc. for these purposes.

Who We Share Personal Information With

We may disclose Personal Information about you t service providers where necessary in order to provide the MetaMask Transaction Shield offering. We work with third parties for the purpose of providing the offering such as hosting, maintenance and claim management. These third parties may have access to or process your Personal Information as part of providing those services to us.

In particular, where you choose to pay for the MetaMask Transaction Shield offering by way of credit card, your Personal Information is shared with a third party (Stripe) for the purposes of processing your payment.

Depending on the region, countries or states based on where you reside, you may have certain rights in relation to your Personal Information. For further information, please see section 6 of our Global Privacy Notice, entitled ‘Your Rights’.

To the extent that there is a conflict between the information contained in this Supplemental Notice and the Global Privacy Notice, this Supplemental Notice takes precedence.