1Who we are and what this policy covers#
Morsel Labs LLC ("Morsel", "we", "us" or "our"), 30 N Gould St, Ste R, Sheridan, WY 82801, United States, is responsible for the personal data described in this policy. Under the EU and UK General Data Protection Regulation ("GDPR") we are the controller of that data.
This policy covers Morsel Wallet for iOS, Android (including the Google Play and Solana dApp Store versions) and Chrome (the "App"), our websites at morselwallet.app and its subdomains (including Morsel Chats on web.morselwallet.app and Morsel Pay's payment and checkout pages), the Morsel connect kit, and the infrastructure we operate for them, such as our API, RPC, relay and notification services at api.morselwallet.app, rpc.morselwallet.app and wss.morselwallet.app (together, the "Services"). It does not cover dApps, websites, protocols or other services run by others, even if you reach them through the App. They have their own privacy policies. Our Third-party services page lists the main ones.
Words like "Services" have the same meaning as in our Terms of Service.
2What we never collect#
- Your recovery phrase, private keys and wallet password. They are created and stored on your device, encrypted, and are not sent to us. (If you created a cloud account in an earlier version of the App, an encrypted backup of your wallets is stored with us until that service is retired. We cannot decrypt it; see Section 3.14.)
- The content of your chats. Messages, photos, videos, voice messages and files are encrypted on your device before they are sent. We only ever handle the encrypted form. (The exception is when you report a wallet and choose to share its recent messages with us; see Section 3.6.)
- Your voice, in a form we can hear. Voice search uses your device's or browser's speech recognition, and Morsel never receives that audio. Voice and video messages reach us only end-to-end encrypted, and transcribing one happens on your phone.
- Your name, email address or phone number to use the App. There is no sign-up. You only give us contact details if you contact support, or if you choose to use Bills & bank transfers, where you enter your name and email for the payout partner's identity check (see Section 3.22).
- Precise location, your contacts or your photo library. The App does not ask for these permissions. Photos and videos you choose to send in a chat are end-to-end encrypted, and a bill photo you take for Bills & bank transfers is read for that request only and not stored.
- Advertising identifiers. The App contains no advertising or cross-app tracking software, and does not use your device's advertising ID.
3What we collect and why#
3.1Wallet addresses and blockchain data#
Wallet addresses and transactions on Cookie Chain, Solana and the other networks the App supports (such as Fogo, X1, Sonic SVM and Solayer) are public. Anyone can see them, and nobody, including us, can delete them from a blockchain.
To show you your balances, tokens, positions, collectibles, prices and activity, the App sends the public addresses of the wallets in it, and of any wallet you choose to view, to Morsel Infrastructure and to the blockchain data providers listed on our Third-party services page. When you swap, bridge, stake, send, place a limit order or use another feature, the App also sends the details needed to quote and build that transaction, such as the tokens, amounts and network. Our servers relay the transactions you sign to the network.
We use this data to provide the features you ask for. We keep cached copies of public blockchain data, such as balances and transaction history, to make the App fast.
Some of these requests go to other services. To show your DeFi positions, our servers send your wallet address to the protocols involved, such as Raydium, Meteora and Kamino. To show prices, the App asks CoinGecko for the prices of the tokens you hold, which tells CoinGecko which tokens they are (but not your wallet address) and your IP address. Solana balances and transactions go through our Solana data provider, Helius.
We also keep some records tied to wallet addresses so the App works well: an index of activity for Cookie Chain wallets that use the App, and records of bridge transfers and stake accounts made through it. These describe public blockchain activity.
3.2Technical data and server logs#
When the App or our websites talk to our servers, our hosting provider's network and our servers receive your IP address. We use it to keep the Services secure and to prevent abuse, for example by limiting how many requests one IP address can make in a short time. Those counters expire within an hour.
Our servers also log each request they handle: the time, the address requested, the response and how long it took. The address requested can include details from the request itself, such as a wallet address or a search term. We use these logs to run the Services, investigate problems and keep them secure. Our hosting provider also keeps network logs for its own operation and security.
3.3Usage data and crash reports#
Usage data is off until you turn it on. The App asks you once, and you can change your answer at any time in Settings, Usage data. In Firefox, the browser also asks for your permission. If you leave it off, the App sends none of what this section describes, except a crash report you choose to send yourself.
What is sent when usage data is on. The App sends anonymous events to Morsel's own servers, never to an analytics or advertising company:
- Which screens and features you use, for example that you opened the App, viewed a screen, added a wallet (and how: created, imported, from a hardware wallet or passkey, or watch-only), unlocked the App and how long that took, changed a setting, or opened or connected a dApp from our list of known apps (any other dApp is recorded only as "other").
- How actions go: whether a send, swap, bridge or other transaction worked or failed, at which step, on which network, the kind of error, and a rough dollar range. Never the amount, the tokens' addresses, your address, the recipient or the transaction's signature.
- Errors: what kind of error happened and in which part of the App. Never the error's message or details.
- Crashes and freezes of the iPhone and Android apps: the type of crash or freeze, the places in the App's code where it happened (code offsets and method names), the version and build of the App, your operating system version and your device model (for example "iPhone15,2"). Never what was on screen, the error's message, memory addresses or any device identifier.
Each event carries a random identifier that the App creates when you turn usage data on. It is not your wallet address and not a device or advertising identifier, and you can replace it with a new one in Settings, Usage data. Events also carry a random session identifier kept only in memory, your platform, the App version and your language. Event times are rounded to the hour. Our servers check every event against a fixed list of allowed fields and drop anything else, including anything that looks like an address, a signature or an amount.
Our servers do not log these requests or store your IP address with them. Your IP address is used only to limit how many requests a device can make, in a counter that expires within an hour.
Turning it off. When you turn usage data off, the App tells our servers, which delete the events linked to your identifier, and the identifier itself. Crash reports waiting on your device are then deleted without being sent.
A crash report you choose to send. If the App stops with an error, its crash screen offers a Send report button. Pressing it sends one report, even if usage data is off: the type of error, its message and where in the App's code it happened. Before it leaves your device, the App removes anything that looks like a wallet address, key, recovery phrase, email address, IP address, link or long number. This report carries no identifier.
Separately, Apple and Google may give us crash statistics for the App through their developer tools if you allowed sharing with app developers in your device's settings. They never include your wallets.
3.4Notifications#
If you allow notifications, the App registers your device with our notification service. It sends:
- a push token from Apple or Google, which lets us address notifications to your device;
- a random identifier the App creates for your device;
- the wallet addresses you have used on that device;
- your platform, app version, language, time zone, the networks you use and the currency you display;
- the notification types you have turned on and their settings; and
- a signature from your wallet proving you control the address.
We keep the push token linked to the wallets it was registered for, with your platform and the notification features your App supports, for 90 days after the App last registers it. We also keep your notification settings and any price alerts you create for each wallet. We use this data to send the notifications you choose, for example when you receive a payment, when a swap, bridge, limit order or recurring send completes, when a price alert triggers, when a perps order fills or a position nears liquidation, when a stock you hold moves (if you turn on Stocks notifications) or when a chat message arrives; to send them in your language and currency; and to avoid sending market and promotional notifications at night in your time zone. We may also send service messages about the App. The App shows your recent notifications in an in-app list, which we keep for up to 90 days.
To notify you about incoming payments on Solana, we add your Solana wallet address to the list of addresses our Solana data provider, Helius, watches for us.
Promotional notifications, such as offers and news about new features, are sent only if you opt in. They are off until you do, and you can turn them off at any time in Settings, Notifications.
Notifications are delivered through Google's Firebase Cloud Messaging and, on iPhone, Apple Push Notification service. Chat notifications for conversations you have accepted carry the message in encrypted form: your device decrypts it to show a preview, and you can turn previews off with "Show message text" in Settings, Notifications. Notifications about new message requests show a shortened version of the sender's wallet address.
If you use Live Activities for a position on iOS, the App sends the wallet, network, token and entry amounts of that position, a code derived from your push token, and Live Activity tokens from Apple, so we can update it on your lock screen. We delete a Live Activity session an hour after it ends, and keep the token that lets us start one for up to 90 days.
3.5Swaps, limit orders, recurring sends, bridging and staking#
These features run on public blockchains and smart contracts, so most of the data involved becomes public when you use them. In addition:
- Quotes and transactions. To quote a swap or bridge or build a transaction, the App sends your wallet address, the tokens and the amounts to Morsel Infrastructure, which passes them to the venues that provide quotes and build transactions, such as CookieBox and CookieScan on Cookie Chain, and Jupiter and Raptor (by Solana Tracker) on Solana. The App contacts Jupiter directly for token search and Solana limit orders. Signed Solana swaps may also be sent through Jito to reach validators faster.
- Recurring sends. We keep a record of each recurring send you set up (your address, the recipient, the amount, the schedule and its payments) so our executor can carry it out and the App can show its history.
- Tracking completion. When you place a limit order, bridge, send a private payment or trade perps, the App may ask us to watch for its completion so we can notify you. We keep that request until the transfer completes or expires. For perps, see Section 3.16.
3.6Chats#
Chats are end-to-end encrypted between wallets, with keys derived from each wallet's own keys. To deliver them, our servers store:
- the encrypted messages and reactions, with messages padded to standard sizes so their length reveals little;
- encrypted media: photos, videos (including round video messages), voice messages and files you send, each encrypted on your device with its own key, which travels only inside the end-to-end encrypted message. We store the encrypted file, padded to a standard size class, with its size, a checksum of the encrypted bytes, which wallet uploaded it and which messages include it. We never receive the key, the file's name or its type;
- metadata we can see: the wallet addresses in each conversation, when each message was sent, whether a conversation is a request, accepted or blocked, how far each side has read, unread counts, and markers for messages that were unsent; and
- settings you choose, such as disappearing-message timers, where offered.
We keep chat history so it can follow your recovery phrase to a new device. It stays until it is deleted. Where offered in the App, you can delete messages for yourself, delete a chat, turn on disappearing messages and erase your chat data. Erasing your chat data deletes the messages you sent and received, your conversations and the reports you made or that were made about you. Deleting a chat for yourself does not delete the other person's copy.
Photos, videos and voice messages. Before a photo is sent, the App draws it again as a new image, which removes its metadata, such as the location and camera details. Location data is removed from videos before they are sent. Video and voice messages use the camera and microphone only while you record. Encrypted files are stored with our hosting provider, and the App uploads and downloads them directly from its storage, which sees your IP address. A file is deleted with the messages that include it: at once when you unsend it or erase your chat data, and otherwise when the messages are deleted or expire. Uploads that are never sent are deleted after 24 hours.
Transcribing voice messages. Transcribe turns a voice message into text using only your phone's on-device speech recognition (on iPhone, and on Android 13 or later). The audio and the text never leave your phone, and the App never falls back to an online recognizer: where your phone cannot recognize speech on the device, Transcribe is not shown. On Android, the system asks for the microphone permission because its recognizer requires it, but nothing is recorded: the recognizer is given the message's own audio. The text is kept encrypted in the App's chat storage on your phone.
Reports. If you report a wallet, we receive your wallet address, the reported wallet's address, the reason you choose and identifiers of its most recent messages to you. If you choose to, you can also include the text of those messages (up to its last five), which your device decrypts and sends to us with the report. Nothing else from the conversation leaves your device. Reporting also blocks the other wallet. We use reports to keep chats safe, for example by limiting a wallet's access to chats.
GIFs. When you search for a GIF, the App sends your search words to our servers, which fetch results from GIPHY. GIPHY receives the search words from our servers, not from your device, and our request logs record them. GIF images themselves load directly from GIPHY's servers, which see your IP address.
The App also keeps a copy of your chats on your device, encrypted with a key derived from your wallet, so they open quickly.
3.7Private Route#
To carry out a Private Route payment, we keep an order record with the recipient's address, the amount and fee, the refund address you chose, the one-time deposit address, the transactions involved and the order's status. We use it only to deliver, refund and account for your payment, and to meet our legal obligations. We delete the record once the payment has been delivered or refunded and the deposit address has been emptied, at least an hour after the order completes and normally within a few hours. An order that needs a person to resolve it is kept until it is resolved. We also keep a small integrity marker for each order so records cannot be tampered with; once the order is finished, the marker no longer identifies it. The deposits and payouts themselves are public on Cookie Chain.
3.8dApp browser, connect kit and WalletConnect#
- Browsing history, bookmarks and connected sites stay on your device.
- Phishing checks run on your device against a list the App downloads from us. We do not receive the sites you visit for this.
- Site icons. To show the icon of a site you visit or that is listed in the App, the App may request it from Google's or DuckDuckGo's favicon services, or from the site itself, which tells that service the site's domain and your IP address.
- Search. If you type something in the browser's address bar that is not a web address, the App sends it to Google Search.
- Transaction previews. To simulate a transaction before you sign it, the App sends the transaction to Morsel Infrastructure. It does not send the address of the site that asked for it.
- Reporting a site. If you report a site, we receive its domain, the reason and any message you add.
- Connect kit. When you connect to a dApp by scanning a Morsel QR code, the dApp and the App exchange messages through our relay. The messages are end-to-end encrypted. The relay forwards them without reading them, keeps each session only in memory, drops it after 24 hours without activity, and does not store messages. Our request logs record the session's random identifier.
- WalletConnect. If you connect to a dApp through WalletConnect, messages pass through WalletConnect's relay network, operated by Reown.
3.9Voice search#
When you use voice search, the App asks your device to turn speech into text: Apple's speech recognition on iOS and Google's on Android. Voice search is not part of the Chrome extension. These providers may process the audio on their servers under their own privacy policies. The App matches the text to screens on your device. Morsel does not receive the audio or the text, unless you then search for something, in which case the search works like typed search. Voice search needs your permission to use the microphone, and you can turn that off in your device settings.
3.10Images and media#
Token logos, collectible images and other media come from many sources, such as IPFS and Arweave gateways and project websites. To protect your privacy and speed things up, the App loads many of them through our image proxy, so the source sees our server instead of you. Some images, GIFs and logos load directly from their host or a content delivery network, which then sees your IP address.
3.11Support#
If you contact support, through the form on support.morselwallet.app or by email, we receive your name, email address, the subject and message, any images you attach, and your IP address, which we use to limit how many requests can be sent. Attachments are stored as you upload them, including any information embedded in the file, such as the location in a photo's metadata, so remove anything you do not want to share first. We use this to answer you and keep a record of the request. We send email through our email providers. Only Morsel team members who handle support can see tickets.
3.12Our websites#
Our websites do not use analytics, advertising or tracking tools, and they do not set cookies. Our hosting provider receives your IP address and request details to serve the pages. Some pages load fonts or images from other servers, which then see your IP address. If you vote on whether a help article was useful, we record only the article and your vote, and use your IP address briefly to limit repeat votes.
3.13Rewards#
If you claim a reward such as the Morsel Genesis Pass, we record the wallet address that claimed it and the IP address it was claimed from, to enforce limits such as one claim per person.
3.14Legacy cloud accounts#
Earlier versions of the App offered an optional cloud account and backup. We are retiring it. New accounts cannot be created, and updated versions of the App stop uploading backups and sign out of cloud accounts.
If you created a cloud account, we still hold, until the retirement is complete, your email address, the sign-in method you used (email and password, Google or Apple, with any password stored only as a secure hash), a list of your signed-in devices with when each was last seen, your token watchlist, and encrypted backups of your wallets and App preferences. The backups were encrypted on your device with your wallet password before upload, and we cannot decrypt them. We will delete these accounts and backups at the end of a notice period. To have yours deleted sooner, contact legal@morselwallet.app.
Your wallets do not depend on the cloud backup: your recovery phrase restores them in the App at any time.
3.15Buying crypto#
Buy opens Onramper, an independent service that connects you with payment providers. When you press Buy, the App sends your wallet address and the network to Morsel Infrastructure, which returns a signed link so that the purchase arrives in your wallet. The link opens Onramper's page, which receives your wallet address and network and your IP address. The amount, your payment details and any identity checks happen on Onramper's page and with the provider you choose, under their own terms and privacy policies. Morsel does not receive your card details or identity documents.
3.16Perps#
Perps (perpetual futures) are traded on independent venues: Jupiter Perps, Pacifica and Phoenix, all on Solana. When you use them, the App connects to the venue you choose directly, not through Morsel. The venue receives:
- your wallet address, to show your account, positions, orders and history;
- the orders you sign, such as the market, side, size, leverage, limit price and take-profit or stop-loss, and the deposits and withdrawals you make;
- the setup the venue needs the first time, such as registering your account or a signed sign-in, and, on Pacifica, your approval of Morsel's builder code; and
- your IP address, as any website does. The App also asks each venue's own region check whether it serves your location. The answer is used on your device and is not sent to Morsel.
On Pacifica and Phoenix, an order can carry a builder fee paid to Morsel, shown on the order before you sign. The fee is part of the order, so the venue, and the blockchain where the order settles, can see that the order came through Morsel. Jupiter Perps orders carry no Morsel fee.
After a trade, the App asks our servers to watch the position or order so we can notify you about fills, take-profit and stop-loss closes, liquidation warnings and liquidations, and, on iPhone, update a Live Activity. Our servers then read that wallet's positions and orders from the venue, using your public wallet address. We keep the watch, with the venue, market, side and order or position reference, until the position and its orders are gone (and at least five minutes after your last trade), and at most 30 days.
Each venue handles your data under its own terms and privacy policy, and its own rules decide where it can be used.
3.17Tokenized stocks#
Tokenized stocks are tokens issued by third parties: xStocks (by Backed), Backpack Securities, Ondo Global Markets and PreStocks. Morsel does not issue them. The App shows a list of them from our servers, built from Jupiter's token list, and buying or selling one is a Solana swap like any other (Section 3.5): the App sends your wallet address, the tokens and the amount to Morsel Infrastructure, which gets the quote and builds the transaction through Jupiter and the other Solana swap venues. The swap itself is public on the blockchain. The issuers do not receive data from Morsel. If you deal with an issuer directly, its own terms and privacy policy apply.
3.18Private balances#
Where available, you can keep a private balance on Solana using Solana Privacy Rings, a protocol shared with other wallets such as Solflare. The App reaches it through our API, which passes requests to our Solana data provider, Helius.
- What is hidden. Your private balance, the amounts you send and receive privately, and which tokens you hold privately. On the blockchain these are encrypted.
- What stays public. Turning on a private balance publishes your private balance keys (public keys only) in an on-chain record, so anyone can see that your address uses private balances. Who pays whom, and when, is public. Every deposit and withdrawal is public, with its amount and your address. A payment from your private balance to someone who does not use private balances is an ordinary public payment, and the App warns you before you send one.
- Your keys and balance stay on your device. The keys are derived on your device from your wallet's own key, and kept only in memory while your wallet is unlocked. Your private balance is decrypted only on your device. Morsel and Helius never receive these keys or your decrypted balance.
- Proofs. Each private send or withdrawal needs a cryptographic proof. Today the proof is made by Helius's prover, which runs in a secure enclave, and the App reaches it through our API. Before sending anything, the App checks the enclave's attestation against a signed policy, and it encrypts each request to that enclave, so our servers and Helius's operators see only encrypted data. The enclave itself processes the amounts and records the proof needs, but never your viewing key or your wallet key, so it cannot spend your funds or read your balance. The App downloads that signed policy, which is public, from a content delivery network (Amazon CloudFront), which sees your IP address.
- What our servers and Helius see. To read your private balance, the App asks for encrypted records using public identifiers, so our servers and Helius see those identifiers, transaction signatures, your wallet address (which our servers use only to limit requests and do not pass to Helius) and your IP address. Our logs for these requests record only the route, method, status and timing, not their content or your address.
3.19Morsel Pay#
Morsel Pay lets businesses and people take payments in crypto, through payment links, checkout pages and subscriptions. Payments go straight from your wallet to the person or business you pay; Morsel never holds the funds. To record and announce payments, Morsel Pay keeps:
- for each payment: the business paid, your wallet address, the token, the amount, any fee, the transaction's signature and the checkout or payment link it came from;
- for a checkout: what the business set up (the amount, the token, a description) and, if the business provided one, your email address; once paid, your wallet address and the transaction;
- for a subscription you set up from a payment link: its terms (the token, amount, how often and how many payments), your wallet address, and which recurring payment (a Solana plan or a Cookie Chain standing order) pays it, which the App reports to Morsel Pay with your wallet's signature, along with the record of each payment made and whether you or the business cancelled it.
The business you pay can see these records in its Morsel Pay dashboard and receive them through its own systems. It handles them under its own privacy policy. Payment records, subscription records and purchase history are kept as the business's record of what was paid. A checkout that expires unpaid is deleted after 90 days. Payments are also public on the blockchain.
3.20Morsel Learn#
Morsel Learn offers short courses from partners, with rewards such as a token per lesson passed, a collectible, Momo points or a partner perk. When you use it, the App sends your wallet address and platform, and our servers keep, per wallet, the lessons you viewed and passed, each graded attempt (the option you chose for each question), and the rewards paid, with their transactions.
To stop one device or person claiming rewards for many wallets, the App creates a random install identifier, kept on your device, and sends it with your answers. Our servers keep only a hash of it, and a hash of your IP address. These identifiers are used only for Learn's limits. The App does not send a device attestation token.
Rewards are paid on the blockchain from the course's own wallet, so they are public. If a course's reward is a partner perk, such as MomoSwap Premium, we send your wallet address to that partner so it can grant it. We keep Learn records for as long as the course's limits and records need them, and delete them on request where we do not have to keep them.
3.21Linked devices and Morsel Chats on the web#
You can link a browser to your phone, at web.morselwallet.app, to read and send your chats there. Linking starts on your phone, in Settings, Linked devices. The browser makes its own device keys, and your phone signs a certificate for them and sends the browser your chat keys, encrypted end to end. Your recovery phrase and wallet key never leave your phone.
- While linking, for up to 5 minutes, our servers keep the browser's public keys, its IP address, its user agent and the website it was opened from, so your phone can show you which browser you are linking.
- For each linked browser, we keep its public keys, the certificate your wallet signed (valid for up to 30 days, then renewed), a name for it (such as "Chrome on macOS"), when it was last used and, where we can work it out, the approximate city and country of its IP address. We delete the record 90 days after it expires or is unlinked.
- Messages sent from a linked browser are marked on our servers with the device that sent them. The other side of the chat does not receive this.
- Unlinking. When you unlink a browser, your wallet signs a statement that it is no longer trusted. We keep that statement, and other chat users' apps can read it so they stop trusting that browser.
The browser keeps your chat keys and chats in its own storage, encrypted. The web chat client sends no usage data.
3.22Bills & bank transfers#
Where available, the App lets you pay a bank account (IBAN) or a bill with your crypto. This is an optional service: the bank payment itself is made by our payout partner, Bridge, and you enter the details yourself.
- Identity check. The first time, you enter your full name and email address. The App sends them through our servers to Bridge, which runs its identity verification on its own page. Any documents you provide there go to Bridge, not Morsel. We keep only whether your wallet has started or passed verification and Bridge's identifier for you, not your name, email or documents.
- Payees. For each bank account you pay, you enter the account holder's name and the IBAN. Our servers pass them to Bridge, and keep the name you gave, the bank's name, a masked IBAN (for example GR16 •••• 0695) and a keyed hash of the IBAN to recognize the same account next time. We do not keep the full IBAN.
- Payments. For each payment we keep your wallet address, the payee, the amount in euros, the reference and note, the due date, Bridge's transfer and the crypto transaction that paid for it.
- Bill photos. If you take a photo of a bill, the App removes its metadata on your device, then sends it to our servers, which ask Anthropic's Claude, an AI service working for Morsel, to read the payee, IBAN, amount, reference and due date. The photo is used for that request only and is not stored. You check and confirm every field before anything is paid.
Bridge handles your data under its own terms and privacy policy.
3.23Travel eSIMs#
Where available, you can buy a travel data plan (eSIM) with crypto. The eSIM is provided by Airalo. We keep an order record with your wallet address, the plan and its destination country, the price, the payment's transaction, Airalo's order, and the eSIM's identifier (ICCID) and activation code, which only your wallet's signed requests can read. Our servers order the plan from Airalo with a Morsel order number, and ask Airalo how much data is left when you check. Airalo does not receive your wallet address, name or email from us.
3.24The Chrome extension#
The Chrome extension is the wallet: it holds, sends, receives, swaps, bridges and stakes tokens and collectibles, and connects to websites. Chats, notifications, Private Mode, private balances on Solana Privacy Rings, rewards, voice search, the DeFi tab (including perps and tokenized stocks), Bills & bank transfers, travel eSIMs and WalletConnect are in the phone app only, so the sections of this policy about them do not apply to the extension. Everything else in this policy does, and the following is specific to it:
- Websites you visit. The extension places a small script on the pages you open so that sites can find the wallet and send it requests, which you then approve or reject. It does not read the content of those pages, and it does not collect or send your browsing history. Your list of connected sites stays on your device.
- Clipboard. The extension reads your clipboard only when you press a Paste button, and only to fill in that field. What it reads is not sent to us or to anyone else.
- Stored data. Your encrypted wallet, your settings and your connected sites are kept in your browser's extension storage. Removing the extension deletes them, so keep your recovery phrase safe.
The use of information received through the extension adheres to the Chrome Web Store User Data Policy, including its Limited Use requirements. We use this data only to provide and improve the wallet's single purpose. We do not sell it, use it for advertising or to determine creditworthiness, or let people read it, except with your agreement, for security, or where the law requires it.
4Legal bases (EEA and UK)#
If you are in the European Economic Area or the United Kingdom, we rely on these legal bases:
| Purpose | Data | Legal basis |
|---|---|---|
| Providing the App's features (balances, activity, swaps, bridging, staking, buying crypto, recurring sends, Private Route, chats and chat media, linked devices, perps watches, private balances, Morsel Pay, Morsel Learn, Bills & bank transfers, travel eSIMs, connect relay) | Wallet addresses, transaction details, encrypted messages, media and chat metadata, linked device records, order, payment and subscription records, Learn progress; for Bills & bank transfers, the name, email and bank details you enter | Performance of a contract with you (Art. 6(1)(b)) |
| Sending the notifications you turn on | Push token, device identifier, wallet addresses, settings, time zone, language | Your consent, given through your device's notification permission and the App's settings (Art. 6(1)(a)), and performance of a contract (Art. 6(1)(b)) |
| Promotional notifications | Push token, settings | Your consent (Art. 6(1)(a)), which you can withdraw at any time |
| Security, abuse prevention and keeping the Services running | IP addresses, server logs, rate-limit data | Our legitimate interests in operating safe and reliable services (Art. 6(1)(f)) |
| Improving the App and fixing bugs | Usage data and crash reports, when you turn usage data on; a crash report you choose to send | Your consent (Art. 6(1)(a)), which you can withdraw at any time in Settings, Usage data |
| Reviewing chat reports | Report details and, with your consent, recent messages | Your consent for the messages you share (Art. 6(1)(a)), and our legitimate interests in keeping chats safe (Art. 6(1)(f)) |
| Answering support requests | Name, email, message, attachments | Performance of a contract or steps you ask for (Art. 6(1)(b)), and our legitimate interests (Art. 6(1)(f)) |
| Rewards and their limits, including Morsel Learn | Wallet address, IP address; for Learn, hashes of the install identifier and IP address | Our legitimate interests in preventing abuse of free rewards (Art. 6(1)(f)) |
| Legacy cloud accounts and backups, until they are deleted | Email, sign-in details, device list, encrypted backups | Performance of a contract with you (Art. 6(1)(b)) |
| Complying with sanctions and other laws, and responding to lawful requests | Any of the above, as needed | Legal obligation (Art. 6(1)(c)) and our legitimate interests (Art. 6(1)(f)) |
Where we rely on legitimate interests, you can object, as described in Section 10.
5How we share data#
We do not sell personal data, and we do not share it with advertisers or data brokers. We share it only as follows:
- Service providers that process data for us under contract, such as our hosting, email and notification providers. They may use it only to provide their services to us.
- Third parties you choose to interact with, such as blockchains, swap venues, bridges, validators, dApps and the other side of a chat or payment. They receive what is needed to carry out what you ask, and handle it under their own policies.
- Data providers that the App or our servers query for blockchain data, prices, token information and media. They see the addresses, tokens or content requested and, when contacted directly by the App, your IP address.
- Legal and safety. We may disclose data if we believe in good faith it is required by law, regulation or legal process, or needed to protect the rights, property or safety of Morsel, our users or others, including to prevent fraud or comply with sanctions.
- Business transfers. If Morsel is involved in a merger, acquisition, financing or sale of assets, data may transfer to the new owner under this policy.
Our Third-party services page lists the providers involved, what each does and what data it handles. The providers of the features in Sections 3.16 to 3.23 are also named in those sections.
6International transfers#
Morsel is based in the United States, and our providers process data in the United States, the European Union and other countries. These countries may have different data protection laws from yours. When we transfer personal data from the EEA, the UK or Switzerland to a country without an adequacy decision, we use safeguards recognized by law, such as the European Commission's Standard Contractual Clauses and the UK's International Data Transfer Addendum, or rely on a provider's certification under the EU-US Data Privacy Framework where it has one.
7How long we keep data#
We keep personal data only as long as we need it for the purposes in this policy, then delete or anonymize it.
| Data | How long we keep it |
|---|---|
| Recovery phrase, private keys, wallet password | Never received |
| Server request logs | Kept by our hosting provider for a limited period, up to 30 days |
| Rate-limit counters | Up to one hour |
| Usage data | Up to 90 days, after which we keep only totals that cannot identify anyone. Deleted at once when you turn usage data off |
| Crash and freeze reports from usage data | Up to 30 days, or until you turn usage data off |
| A crash report you choose to send | Up to 90 days |
| Push token and the wallets it is registered for | 90 days after the App last registers it, or until you turn notifications off for that wallet or the token stops working, if sooner |
| Notification settings and price alerts | While you use notifications for that wallet; delete an alert in the App at any time, or ask us to delete your settings |
| Notification list in the App | Up to 90 days (the most recent 50) |
| Completion watches for transfers | Until the transfer completes, and at most 3 hours (bridges and private payments) to 30 days (limit orders) |
| Live Activities | Session data until an hour after the Live Activity ends; the token that starts one, up to 90 days |
| Solana addresses on the payment watch list | While the address is registered for notifications; addresses can remain on the list after that, and we remove them on request |
| Encrypted chat media (photos, videos, voice messages, files) | Deleted with the messages that include them; uploads never sent, after 24 hours |
| Voice message transcripts | Never received; kept encrypted on your phone |
| Encrypted chat messages, reactions and chat metadata | Until they are deleted. Where offered in the App: messages set to disappear are deleted when their timer runs out, erasing your chat data deletes them at once, and the markers left by deleted or unsent messages are purged within 30 days |
| Chat reports | As long as needed to review and act on them, unless erased with your chat data |
| Linked device records | While linking, up to 5 minutes; a linked browser's record until 90 days after it expires or is unlinked; signed unlink statements are kept |
| Connect relay sessions | In memory only: 5 minutes if the dApp and the App never pair, then until the session has been idle for 24 hours |
| Private Route order records | Deleted at least an hour after the order completes and normally within a few hours; orders that need a person to resolve them are kept until resolved |
| Recurring send records | While the order exists, and afterward as the record of its payments |
| Perps watches | Until the position and its orders are gone, and at most 30 days |
| Private balance keys and decrypted balances | Never received; kept on your device, in memory only while your wallet is unlocked |
| Morsel Pay payment and subscription records | Kept as the business's record of what was paid; checkouts that expire unpaid, 90 days |
| Morsel Learn progress, attempts, rewards and hashed identifiers | As long as the course's limits and records need them; deleted on request where we do not have to keep them |
| Bills & bank transfers records (verification status, payees, payments) | As long as needed to provide the service and keep payment records, or as the law requires |
| Bill photos | Not stored; used only for the request |
| Travel eSIM orders | As long as you may use the eSIM, and afterward as the record of the purchase |
| Support requests and attachments | As long as needed to help you and keep a record of our support; we delete them on request unless we must keep them |
| Reward claims (wallet and IP address) | As long as the reward's limits apply |
| Cached and indexed public blockchain data | Refreshed or discarded as the data changes |
| Legacy cloud account and backups | Deleted at the end of the retirement notice period, or sooner on request |
We may keep data longer where the law requires it, or to establish or defend legal claims.
8Security#
We protect personal data with measures appropriate to the risk, including encryption in transit, encryption of your wallet data on your device, end-to-end encryption of chats and of the connect relay, access controls on our systems, and data minimization. No system is perfectly secure, and keeping your device and recovery phrase safe is up to you. If you find a vulnerability, please report it as described on our Security page.
9Your choices#
- Notifications: choose which notifications you get, including promotional ones, in Settings, Notifications, or turn them off in your device settings.
- Message previews: turn off "Show message text" to stop the App from keeping chat keys for notification previews.
- Chats: where offered in the App, delete messages for yourself, delete chats, set disappearing messages, block wallets and erase your chat data.
- Permissions: allow or revoke access to the camera, microphone, speech recognition, notifications and biometrics in your device settings.
- Linked devices: see and unlink your linked browsers in Settings, Linked devices.
- Optional services: perps, tokenized stocks, private balances, Morsel Learn, Bills & bank transfers and travel eSIMs are used only if you choose to use them.
- Remove a wallet: removing a wallet deletes it from your device, but not from the blockchain. To stop its notifications straight away, turn them off before you remove it; otherwise its registration expires within 90 days. Removing every wallet from the App unregisters the device.
10Your rights#
Depending on where you live, you may have the right to access the personal data we hold about you, correct it, delete it, restrict or object to our use of it, receive a copy in a portable format, and withdraw consent at any time (without affecting what we did before you withdrew it).
To exercise a right, email legal@morselwallet.app. Because we do not have accounts, we usually know you only by a wallet address, so we may ask you to prove you control that address, for example by signing a short message we give you. We never need your recovery phrase or private key to do this. We will respond within the time the law requires, normally within one month.
Some data cannot be changed or deleted: anything recorded on a public blockchain is permanent, and data held by third parties you used is governed by their policies.
If you are in the EEA or the UK and are not satisfied with our response, you can complain to your local data protection authority, such as the authority in your EU member state or the UK Information Commissioner's Office.
11United States privacy rights#
If you live in California or another US state with a consumer privacy law, you have additional rights.
Categories of personal information. In the last 12 months we have collected:
| Category | Examples | Source | Purpose | Disclosed to |
|---|---|---|---|---|
| Identifiers | Wallet addresses, IP address, push token, random device identifier; a random usage-data identifier if you turn usage data on; a hash of Morsel Learn's install identifier; name and email if you contact support or start Bills & bank transfers | You and your device | Providing the Services, notifications, security, support, preventing reward abuse | Service providers; third parties you interact with, such as Bridge for Bills & bank transfers |
| Commercial information | Records of transactions made through features we operate, such as Private Route, recurring sends, Morsel Pay payments and subscriptions, bank payments and eSIM orders | You and public blockchains | Providing the Services | Service providers; the business you pay through Morsel Pay |
| Financial information | Payee names, bank names and masked IBANs for Bills & bank transfers (the full IBAN is passed to Bridge and not kept) | You | Bills & bank transfers | Bridge |
| Internet or network activity | Server logs; usage data and crash reports if you turn usage data on; Morsel Learn progress; linked browsers' user agent and last use | Your device | Security, reliability, improving the App and fixing bugs, providing the Services | Service providers (hosting) |
| Communications | Chat metadata; encrypted chat media we cannot read; recent messages you choose to include in a report | You | Delivering chats; reviewing reports | Service providers |
| Customer records | Name, email and messages in support requests | You | Support | Service providers |
| Sensitive personal information | Sign-in details of legacy cloud accounts; message text you choose to include in a chat report | You | Legacy accounts; reviewing reports | Service providers |
We do not collect precise geolocation, biometric information (Face ID and fingerprint checks happen on your device, and we never receive them), or audio we can hear (voice and video messages reach us only end-to-end encrypted, and transcription happens on your phone). Your time zone and IP address may indicate your general location, and a linked browser's record can include the approximate city and country of its IP address.
No sale or sharing. We do not sell personal information, and we do not "share" it for cross-context behavioral advertising, as those terms are defined in the California Consumer Privacy Act. We have not done so in the last 12 months, and we have no actual knowledge of selling or sharing the personal information of anyone under 16. We do not use or disclose sensitive personal information for purposes that would give you a right to limit it. Because we do not sell or share, there is nothing to opt out of, and we treat Global Privacy Control signals accordingly.
Your rights. You may ask to know what personal information we collect, use and disclose, and ask us to delete or correct it. Email legal@morselwallet.app. You may use an authorized agent, who must show us your written permission. We will verify requests as described in Section 10, and we will not discriminate against you for exercising your rights. If we decline your request, you may appeal by replying to our decision, and if you are still not satisfied, you may contact your state attorney general.
12Children#
The Services are not for anyone under 18, and we do not knowingly collect personal data from children. If you believe a child has given us personal data, contact legal@morselwallet.app and we will delete it.
13Changes to this policy#
We may update this policy from time to time. We will change the "Last updated" date at the top and, for material changes, tell you in the App or on our website before they take effect.
14Contact#
Morsel Labs LLC
30 N Gould St, Ste R
Sheridan, WY 82801
United States
Privacy questions and requests: legal@morselwallet.app
Help with the App: support@morselwallet.app