This Privacy notice describes information Ember may collect through the V2 website, install request flow, partner flow, devnet package distribution, wallet registration, subscription records, and future cover records.
Effective June 19, 2026
This draft Privacy notice covers the public website, install request form, partner request form, devnet package requests, future wallet registration, future subscription records, future cover decisions, and future claim intake for Ember Cover.
The current website collects access and partner request information. Future paid flows may collect additional wallet, subscription, billing, eligibility, compliance, and claim information as described below.
If you request access, submit a partner request, or contact Ember, Ember may collect your email address, name, organization, role, website, wallet/dApp context, message, and any other information you choose to provide.
If you later submit a claim, Ember may ask for transaction details, wallet addresses, loss descriptions, supporting screenshots or exports, and other information needed to assess eligibility and validate the claim.
Do not submit seed phrases, private keys, recovery phrases, passwords, or other secrets through this website, access form, partner form, or claim process.
Future cover flows may use wallet public keys, signed challenges, wallet-registration records, wallet-control proofs, Solana Subscription Plan records, plan PDAs, subscription PDAs, cover decisions, transaction evidence, landed transaction records, covered transaction counts, cap usage, and claims materials.
Onchain Solana data is public by design. Ember may use linked public records to support eligibility checks, fraud controls, cover decisions, claims review, and billing operations.
Future integrations may process transaction hashes, program IDs, account addresses, token accounts, asset metadata, simulation output, signature payloads, signed-message records, timestamps, terms versions, and cover status records.
Ember may process IP address, approximate location, wallet network, jurisdictional signals, sanctions-screening signals, and other eligibility information where needed to determine whether access, subscription, payment, or claim processing is available.
Eligibility data may be used to comply with sanctions, anti-fraud, anti-abuse, export-control, consumer-protection, and other legal or operational requirements.
The current access form does not collect payment information. The planned paid flow may use Solana Subscription Plans, USDC, approved puller records, onchain collection records, and payment confirmation records.
If Ember later supports Solana Pay one-time payments, card payments, fiat payments, or third-party payment processors, payment data may be collected directly by those providers and used to complete billing, invoices, fraud checks, refunds, chargebacks, and support.
Ember may store subscription status, tier, billing period, payment confirmation, plan PDA, subscription PDA, wallet registration, cap usage, cancellation status, failed collection status, and revoke status.
For claim processing, Ember may collect information needed to verify the covered transaction, covered loss, wallet control, payout address, claim timeliness, fraud risk, sanctions eligibility, and any required identity or compliance checks.
Failure to provide requested claim or compliance information may delay, reduce, or prevent a claim review or payout, subject to final binding terms.
Ember uses information to respond to access requests, evaluate partner interest, prioritize integrations, operate the cover service, register accounts and wallets, produce cover decisions, maintain evidence records, process claims, manage billing, detect fraud, improve security, and comply with law.
Ember may use aggregate or de-identified information to understand product usage, improve coverage rules, monitor service reliability, and develop partner integrations.
Ember does not sell access request information.
Ember may share information with service providers that help operate hosting, email delivery, security, analytics, wallet integrations, payment processing, claim management, compliance screening, customer support, and infrastructure.
Service providers are expected to process information only for the services they provide to Ember, subject to applicable contractual, legal, and security obligations.
Ember may disclose information where needed to comply with law, enforce terms, prevent fraud or abuse, protect users or the service, respond to legal process, or complete a business transaction such as financing, merger, acquisition, or asset transfer.
Ember may retain access requests, partner requests, account records, wallet registration records, cover decisions, billing records, fraud-control records, and claims materials for product operations, legal compliance, audit, dispute handling, and abuse prevention.
Deregistering a wallet can end future cover for that wallet, but it does not delete prior cover, billing, fraud-control, compliance, or claims evidence that Ember needs to preserve.
Depending on your location, you may have rights to request access, correction, deletion, portability, restriction, or objection. These rights may be limited where Ember must retain records for legal, security, fraud-prevention, claims, or billing reasons.
Privacy questions can be sent to ember_insurance@proton.me.
Ember