Privacy policy

OPEN COOKIE

Effective Date: July 25, 2026

1. Scope

This Privacy Policy describes how the OpenCookie Android application handles information. It applies to the mobile app (com.opencookie.app). This website (open-cookie.pages.dev) is a separate static site; visiting it may load fonts from Google Fonts as described in your browser's network activity.

2. Information We Do Not Collect

OpenCookie does not require you to create an account with us and does not ask for personal information such as your name, email address, or phone number. Based on the current application code and dependencies:

  • We do not operate analytics SDKs (such as Firebase Analytics or Google Analytics).
  • We do not operate crash-reporting services (such as Firebase Crashlytics or Sentry).
  • We do not operate a proprietary backend server that receives user profiles or activity from the app.
  • We do not collect advertising identifiers for tracking.

3. Non-Custodial Design

OpenCookie is a non-custodial application. This means:

  • We do not store or have access to your private keys.
  • We never ask for, store, or receive your seed phrase (recovery phrase).
  • All digital assets remain in your control within Seed Vault on Seeker

4. Data Stored Locally on Your Device

The app uses Android DataStore (preferences) to persist session and connectivity state on your device. This may include:

  • Your connected wallet public address
  • Wallet authorization token and cluster metadata from Mobile Wallet Adapter
  • Your selected Solana cluster (devnet or mainnet-beta)
  • Pending transaction records (signature, action type, timestamps) for recovery after app restarts
  • Your preferred network fee priority setting
  • Last-known working RPC endpoint per cluster

This data stays on your device unless you clear app storage or use the in-app disconnect/log out flow, which removes wallet session data.

5. Data That Leaves Your Device

OpenCookie communicates directly with the Solana network and Seed Vault on Seeker. Data that leaves your device includes:

  • Solana RPC requests: The app sends JSON-RPC requests to public Solana RPC endpoints (such as api.mainnet-beta.solana.com or configured alternatives). These requests include your wallet public key when querying accounts, balances, blockhashes, and transaction status. RPC providers may log IP addresses and request metadata under their own policies.
  • Signed transactions: When you approve an action, the signed transaction is submitted to the Solana network and becomes public blockchain data.
  • Mobile Wallet Adapter: Transaction payloads and authorization requests are passed to Seed Vault through the Solana Mobile Wallet Adapter protocol. OpenCookie does not receive your private keys through this process

The app does not send wallet addresses or activity to an OpenCookie-operated server.

6. Blockchain Data

Blockchain transactions are public by nature. When you use OpenCookie, your wallet address, on-chain profile data (total opens, daily count), and transaction history may be visible through Solana block explorers and other third-party services. This data is recorded on the Solana blockchain and cannot be deleted or modified by OpenCookie after confirmation.

7. Solana Mobile Wallet Adapter

OpenCookie uses the Solana Mobile Wallet Adapter (MWA) protocol. On Seeker, signing happens inside Seed Vault — the device's native wallet. OpenCookie only requests permission to submit transaction payloads for your review and signature

8. Third-Party Services

OpenCookie relies on third-party infrastructure that operates independently:

  • Seed Vault on Seeker — the device's built-in wallet used for connection and transaction signing on Seeker devices
  • Solana RPC providers — used to read chain state and submit transactions.
  • The Solana blockchain — a public distributed ledger.

We recommend reviewing the privacy practices of any third-party services you interact with through the app.

9. Device Permissions

OpenCookie uses standard Android network connectivity to reach Solana RPC endpoints and communicate with your wallet. The app observes network availability to show offline state and refresh data when connectivity returns. No location, contacts, camera, or microphone access is required for core functionality.

10. Changes To This Policy

This Privacy Policy may be updated from time to time. Changes will be reflected on this page with an updated effective date. We encourage users to periodically review this page for the latest information.

11. Contact Information

If you have any questions about this Privacy Policy, please contact us:

Send email