Privacy Policy

Overview

Shore Wallet is a non-custodial cryptocurrency wallet. We never hold, control, or have access to your private keys or funds. This policy explains what limited information we do collect through our website and app, and how it's used.

What we collect

We do not collect your private keys, seed phrase, wallet passwords, or transaction contents — these are generated and stored entirely on your device and never transmitted to us.

We may collect basic website usage data (pages visited, general location at a country/region level, device and browser type) through standard analytics, for the purpose of understanding site usage and fixing bugs.

If you contact us through the contact form, we receive whatever information you choose to include (name, email address, and your message).

What we don't collect

We do not collect KYC (know-your-customer) information, government ID, or biometric data, since Shore Wallet does not require an account to use.

We do not have access to, and cannot see, your wallet balance, transaction history, or on-chain activity. That information lives on the public blockchain, not on our servers.

Cookies

Our website may use minimal cookies or local storage for basic functionality (such as remembering a filter preference on the blog). We do not use cookies for cross-site advertising tracking.

Third parties

We do not sell personal data to third parties. Limited technical data may be processed by infrastructure providers (such as our hosting provider) strictly to operate the website.

Your rights

Since we collect very little personal data in the first place, most requests can be resolved simply by asking us to delete any contact form message you've sent us. Reach out at support@shorewallet.com with any privacy question or request.

Changes to this policy

We may update this policy as the product changes. Material changes will be reflected with an updated date at the top of this page.

A note on this document

This page is a starting template and has not been reviewed by a lawyer. Before relying on it as your actual, published privacy policy, have it reviewed by a qualified attorney familiar with applicable data protection law (such as GDPR or CCPA) for your actual jurisdictions and user base.