SolSub Privacy Policy

Effective date: June 18, 2026

SolSub ("SolSub," "we," "us") is self-custodial software for creating, viewing, and managing subscriptions and allowances built on the Solana Subscriptions & Allowances on-chain program ("the Program"). SolSub includes a mobile app, a web app, and optional hosted services for merchants. This policy explains what each part does with information, and what choices you have.

The short version: We collect no private or personal data. The Program is public and on-chain, and you can use it directly without us. Anything we index about subscriptions and payments is already public on the Solana blockchain — we copy a public ledger, we do not gather anything private. We run no analytics and sell nothing.

1. You Are Not Required to Use Our Infrastructure

The Program lives on the Solana blockchain and is permissionless. Anyone can read it and submit transactions to it directly — through our open-source code, their own tools, or third-party software — without going through SolSub's servers. We run hosted services only for two things the base Program cannot do by itself: (a) a "crank" that submits recurring charges on schedule, because an on-chain program cannot charge itself; and (b) an indexer that filters the shared Program's public activity into a per-merchant history. Both are optional, and both can be self-hosted using our open-source code.

2. We Collect No Private Data

Everything we index about subscriptions and payments — a subscriber's public wallet address, the amount, the token, the transaction signature, the timestamp, and the subscription status — is already public on the Solana blockchain. We copy public ledger data so it can be displayed and searched; we do not create or collect any private data about you. Specifically:

• No analytics or tracking. None of our apps or sites contain analytics, advertising, crash-reporting, or fingerprinting SDKs. We do not collect device identifiers, usage statistics, or location data.
• No email accounts, no passwords. There is no email/password sign-up. Where you sign in, it is a one-time wallet signature (Sign in with Solana).
• No private keys. We never have access to your seed phrase or private keys. All signing happens inside your own wallet; SolSub only requests signatures.
• No selling or sharing. We do not sell your information or share it with advertisers.

The only information we hold that is not already on-chain is operational configuration a merchant gives us themselves — a webhook endpoint URL and a generated signing secret they set up — and a short-lived sign-in token. None of that is personal data we gather about anyone.

3. The Mobile App and On-Device Data

The SolSub mobile app talks to the Solana blockchain directly and keeps no accounts on a server. It stores a small amount of data locally on your device so it can function:

• Wallet session.Your public wallet address, an optional wallet-provided account label, and a Mobile Wallet Adapter authorization token are stored in your device's secure OS keystore (via Expo SecureStore). The token only lets SolSub re-request a session with your wallet app; it cannot move funds. It is deleted when you disconnect your wallet.
• Preferences and cache. Your theme choice (light/dark) and a cached copy of the curated plan registry are stored in local app storage.

All of this stays on your device. Uninstalling the app removes it.

4. The Web App and Optional Hosted Services

The web app has two layers.

(a) Direct, on-device layer. Reading plans and building transactions you sign in your own wallet — creating a plan, subscribing, cancelling, revoking an allowance, or issuing a refund — happens against the blockchain through your browser and wallet. We custody no funds or keys for any of it. To keep you signed in to the dashboard, we set one encrypted, http-only cookie (solsub-session) holding your public wallet address and a sign-in nonce, and we remember your last-used wallet in your browser's local storage. Some clients use a short-lived signed token instead of the cookie. No password is involved.

(b) Optional hosted services (merchant opt-in). A merchant can switch on two server-side features. These run on managed infrastructure (a database provider and a hosting/cron provider we use as processors) and do store data — all of which, except merchant-supplied webhook config, is already public on-chain:

• Auto-collection (the crank).If a merchant enables auto-charge on a plan, we store that plan's on-chain address, the owner (merchant) wallet, the cluster, and a log of charge attempts — the subscriber's public wallet address, amount, token, timestamp, and any failure reason. Our crank then submits the recurring charges the subscriber has already authorized on-chain (see the Terms for how that authorization and its limits work).
• Indexing, event history, and webhooks.To give a merchant a clean history of their plans out of the shared Program's activity, we index on-chain events into a database (subscription created/cancelled/resumed, charge succeeded/failed) keyed by the merchant's plan, including the subscriber's public wallet address, amount, token, signature, and time. Merchants can register webhook endpoints (a URL and a signing secret) to receive these events; we store delivery logs.

What this means for subscribers: if you subscribe to a merchant who has enabled these hosted services, your public wallet address and the on-chain events for that subscription may be stored in our database and shown to that merchant. This is the same data anyone can already read on the blockchain — we are indexing public ledger data, not creating any private record about you. If you interact only with the base Program, or with a merchant who self-hosts, this data does not pass through our servers.

5. Network Services the Apps Contact

To read on-chain data and display useful labels, the apps make network requests to third-party services. Like any internet request, these services can see your IP address and the data you request, and they operate under their own privacy policies:

• Solana RPC providers. The apps query a Solana RPC endpoint (by default Helius, or the Solana public RPC, or an endpoint you configure) to read subscriptions, allowances, and plans on-chain and to submit transactions you have signed. These queries include your public wallet address.
• Token metadata (Helius DAS). When available, the apps fetch token symbols and logos for the tokens used by your subscriptions.
• Curated plan registry. The apps fetch a public, read-only list of curated plans (hosted on GitHub by default). No information about you is sent beyond the standard network request.
• Merchant metadata URLs. Plans can include a metadata link (name, description, logo) controlled by the merchant who created the plan. When a plan is displayed, that URL may be fetched. These servers are controlled by merchants, not by us — they can see your IP address, and we cannot vouch for their privacy practices.

For the optional hosted services in Section 4, we also use a database provider and a hosting/cron provider as processors, and optionally Helius webhooks to receive on-chain events.

6. On-Chain Data Is Public

Your wallet address and the subscriptions, allowances, charges, and transactions associated with it exist on the Solana blockchain, which is a public, permanent ledger. Anyone can view this data, and neither you nor we can delete it. The apps and our indexer read this public data; they do not create any private copy of it about you.

7. Your Choices and Data Deletion

• Disconnect your wallet (mobile) to revoke the session and delete the stored authorization token, or log out (web) to clear your session.
• Uninstall the app to remove all locally stored data (session, preferences, cache).
• Use your own RPC endpoint, the Program directly, or a self-hosted instance if you prefer not to route through our default provider or our hosted services.
• Request deletion of records we control in the hosted services (charge logs, indexed events, webhook configuration) by contacting us. We cannot delete on-chain data, or data a merchant has independently stored.

8. Children

The apps are not directed at children under 13 (or the equivalent minimum age in your jurisdiction), and we do not knowingly collect information from them.

9. Changes to This Policy

If we change this policy, we will update the effective date above and publish the new version at this address. Material changes will be noted in the apps' release notes.

10. Contact

Questions about this policy: @solsub on Telegram