Cover Policy

Definitions

Active Subscription means an Ember Cover subscription that has been accepted through an approved Ember Solana Subscription Plan, paid or collectible where payment is required, and not cancelled, expired, suspended, revoked, or terminated.

Registered Wallet means a wallet public key that has been linked to the subscriber's Ember subscription through an approved registration, wallet-control, or onchain subscription-evidence process.

Covered Transaction means a supported Solana transaction reviewed by Ember before signing, tied to an Active Subscription and Registered Wallet, and displayed or recorded as Covered before the user signs.

Covered Loss means an eligible wallet-drain or malicious-signing loss that results from a Covered Transaction and is not subject to an exclusion, cap limit, fraud hold, or other final terms limitation.

Eligibility

Cover is expected to be available only for supported Solana transactions reviewed by Ember before signing through an approved Ember wallet or partner integration.

The wallet must be registered to the subscriber's active subscription, the subscription must be active at the time of the covered approval, and the transaction must be recorded as Covered before signing.

A transaction is not covered merely because a user requested an install link, visits the website, holds an Ember account, submits a partner request, or signs a transaction through an unsupported wallet or unsupported integration.

Covered risks

V2 cover is focused on wallet-drain and malicious-signing losses that Ember reviewed and backed before signing.

Covered examples include malicious token approvals, drainer signatures, and delegate drains where the later drain remains inside the applicable tail window and evidence requirements.

Covered losses must be directly connected to the covered approval and must be supported by Ember's pre-sign decision record and the onchain transaction evidence.

Exclusions

Compromised keys, leaked seed phrases, shared private keys, poor key storage, phishing that gives an attacker direct key access, malware, device compromise, and unauthorized wallet access are excluded.

Market losses, token price movement, slippage, poor trade execution, low liquidity, economic loss from a transaction that otherwise worked as expected, and speculative losses are excluded.

Protocol exploits, hacked dApps, vulnerable smart contracts, oracle manipulation, validator/network issues, chain outages, unsupported chains, unsupported wallets, unsupported integrations, unsupported transaction types, and losses outside Ember's pre-sign review boundary are excluded.

Losses are excluded where the user ignores an Ember Not Covered, Unsupported, Cover Unavailable, blocked, or similar warning and proceeds anyway.

Losses are excluded where the proximate cause occurred before the subscription became active, after the subscription ended, or outside the active covered transaction record.

Fraudulent, misleading, incomplete, abusive, unlawful, or sanctions-prohibited claims are excluded.

Cover statuses

The public statuses are Covered, Not Covered, Unsupported, and Cover Unavailable.

Internal risk bands are not public cover statuses. If a transaction is covered but requires stronger warnings, it still displays as Covered with the appropriate warning context.

Covered means the transaction is eligible for cover subject to the final Cover Policy, subscription status, caps, exclusions, evidence, and claim approval. Not Covered means Ember reviewed the transaction but will not cover it. Unsupported means Ember does not support the transaction type or context. Cover Unavailable means Ember could not provide a cover decision at that time.

Caps and covered transaction counts

Core provides a $10,000 monthly cover cap and 100 covered transactions. Plus provides a $25,000 monthly cover cap and 150 covered transactions. Max provides a $50,000 monthly cover cap and 250 covered transactions.

Caps and covered transaction counts apply to the subscribed wallet and any additional registered wallet support expressly allowed by final terms.

A single claim cannot exceed the applicable remaining cover cap. Approved claims reduce the remaining monthly cover cap. Covered transaction counts reset according to the billing period or final terms.

Changing wallets or adding additional wallets where allowed does not multiply caps or covered transaction counts.

Conditions for claim review

The claimant must submit the claim within 21 days of the alleged loss unless final binding terms state otherwise.

The transaction must have been recorded as Covered before signing, the subscription must have been active, the wallet must have been registered, and the loss must not fall within an exclusion.

The claimant must provide information Ember reasonably requests to review the claim, verify wallet control, validate transaction evidence, determine payout eligibility, satisfy compliance obligations, and prevent fraud.

Failure to provide requested claim or compliance information within the time requested by Ember may delay or prevent claim approval, subject to final binding terms.

Claim evidence

A claim starts from Ember's pre-sign cover decision, the terms version recorded at the covered approval, and the onchain evidence for what landed.

Relevant evidence may include transaction hash, signature payload, wallet public key, registered account, timestamp, cover status, simulation context, affected assets, post-transaction balances, landed instructions, token authority changes, and any later drain transaction tied to an approved delegate or authority.

Delegate-drain claims require evidence that the original covered approval and later drain remain inside the applicable covered conditions and tail window.

Payout review

A submitted claim is not automatically approved. Ember must review eligibility, exclusions, evidence, cap availability, fraud risk, and compliance requirements before any payout.

If approved, payout amount, payout asset, exchange-rate treatment, timing, and destination wallet will be determined under final binding terms and applicable law.

Until final paid terms are published, this draft does not promise any specific payout rail, processing time, or reimbursement currency.

Not insurance and sole remedy

Unless Ember publishes counsel-approved terms stating otherwise, Ember Cover should be treated as a limited transaction-cover product and not a regulated insurance policy.

The product is not intended to cover every fortuitous event, cyber attack, key compromise, market loss, protocol failure, or loss that traditional insurance might address.

Subject to final binding terms and applicable law, the expected sole remedy for an approved Covered Loss is payment under the Cover Policy up to the applicable cap.

Contact

Cover policy questions can be sent to ember_insurance@proton.me.