Privacy Policy

There are no accounts, no emails, no passwords, no analytics scripts and no advertising trackers on this site. Most of what VaultBags works with is blockchain data, which is public by nature and was never ours to begin with.

Wallet addresses, balances, transactions, claims and locks live on Solana, where anyone can read them forever. VaultBags reads and displays that public record; it cannot edit it and cannot delete it. If you interact with the vault on-chain, that activity is public in the same way every other Solana transaction is.

Connecting a wallet uses Sign-In With Solana: you sign a message, and the server issues a session token valid for 24 hours. It is kept in this site's local storage in your browser, so reloading a page does not ask you to sign again, and it is only ever sent to vaultbags.app. It is not a cookie. It proves you control the wallet and nothing more: it cannot sign or move anything. Disconnecting deletes it from the browser and ends it on the server as well, so a copy of it stops working too; otherwise it expires on its own. When it expires the site asks you to sign in again the next time you act, never on its own. Your private key never leaves your wallet, and no part of the service ever asks for it.

Rate limiting: request IPs are used to throttle abuse, with short-lived counters. Standard server logs exist at the hosting layer, as they do on effectively every website.

Telegram bot: if you link your wallet, the link between your Telegram user ID and your wallet address is stored, along with your notification preferences and a log of which alerts were sent to avoid duplicates. Sending /unlink confirm to the bot, or connecting the wallet at /link and unlinking it there, deletes the link.

AI analyst: your conversations with the analyst are stored keyed to your wallet so your history survives a page reload. You can delete any session from the interface, and deletion removes its messages. Questions asked of the bot with /ask, and questions a wallet pays the agent for, are kept the same way with their answers, keyed to the linked or paying wallet, so a conversation can continue; each keeps at most 25 conversations per wallet and deletes the oldest first.

Public records: claims, governance votes (with the signature that cast them) and raffle entries are published with the wallet that made them, so anyone can check them. A paid call to the agent records the paying wallet and its transaction, which are public on Solana anyway.

Connected apps: if you connect an assistant or another app to your vault, you approve it while signed in with your wallet, and from then on that app knows that wallet's address and can read your own position (what you can claim, what you have claimed and how it has performed, your monthly recap and your badges). It cannot sign, claim or move anything. The server keeps which app is connected to which wallet, the name the app gave and when it connected and last renewed its access, as the record of the access you gave and what the list of your connected apps shows, for as long as the app keeps using it and no longer than 30 days after its last use. You can see each app and end its access, or every app's at once, at /oauth/apps.

Preferences: your theme choice (light or dark) is kept in your own browser's local storage, not on a server.

Your last visit: to show what changed since you were last in My Vault, this browser keeps the time of your last visit and what you had earned and was waiting then, in its local storage, for each wallet you open there. Only that time is sent, without your wallet, to read what the vault did since. Clearing the site's data in your browser deletes it.

The vault diagram on the home page: with a wallet connected, the page reads that wallet's public claim preview from vaultbags.app (the same figures anyone can see for that address, without signing in) when the wallet connects and again after each purchase the vault makes, to say how much more it can claim than when the page first read it. Nothing about those reads is kept.

The service runs on infrastructure providers (hosting, database, connections to the Solana network, price data, the Telegram API for the bot, and a language model provider for the analyst). Most requests to them are made by the VaultBags servers. A payment made to the agent through the standard x402 lane is checked and settled by Coinbase's payment facilitator, which receives the transfer the paying wallet signed; that transfer is public on Solana once it settles. Your browser also talks to a few directly: your wallet, the database provider for the live activity ticker, DexScreener for the embedded price chart, and the hosts of token and profile images (unavatar.io on the launch page). Like any site you visit, they see your IP address and browser. None of them are given anything about you beyond what is necessary to serve the request, and none of it is sold to anyone, because nothing here is for sale.

The VaultBags app for Android and the Solana Seeker works like the site, with these differences.

Signing in: you sign in through your wallet app, and the 24-hour session token is kept in the phone's secure storage, which Android encrypts with a key held by the system, instead of in a browser. Signing out ends it on the server, deletes it from the phone and forgets the wallet authorization the app was keeping. If the server cannot be reached at that moment, the app keeps that ended session's token in the same secure storage for one purpose, finishing the sign-out: it tries again when the app next opens and when the connection returns, and deletes the token as soon as the sign-out is complete. The token stops working on its own 24 hours after it was issued in any case.

Notifications: the app registers the phone for notifications while you are signed in and Android allows the app to post them. On Android 13 and later that is only after you allow it (the app asks when you turn notifications on in its settings). On earlier versions Android allows notifications by default, so the phone is registered when you sign in; you can switch them off for the app in Android's settings. Registering stores the phone's notification token with your wallet address, the platform and the app version, together with your notification preferences and a log of which alerts were sent so none arrives twice. Signing out stops notifications to that phone: its token is marked as signed out and is never sent anything again. At sign-out the app sends that token only when the phone was registered or may have been (Android allows the app to post notifications, or the app was updated from a version that kept no record of it); otherwise it sends nothing. If the server could not be told before the session expired, the app asks Google to delete the phone's notification token instead, which ends delivery to it. Notifications travel through Google's Firebase Cloud Messaging, so Google handles each one on its way to your phone. The app includes Google's Firebase messaging library. From version 0.9.14 the app keeps that library from contacting Google on its own: the phone is registered with Firebase and its notification token is obtained from Google Play services only when the app registers the phone as described here, or when a sign-out sends that token as described above. Earlier versions left the library at its default, which does both the first time the app starts, so a phone that ran one of them is already registered with Firebase. In every version VaultBags receives the token only when the phone is registered as described here, or to end a registration at sign-out.

On the phone: public figures the app last showed are kept in its storage for up to a day, so it opens without waiting. To show what changed since your last visit to My Vault, the app keeps, in its secure storage and for each wallet, the time of that visit and what you had earned and was waiting then; only that time is sent, without your wallet, to read what the vault did since. Signing out keeps it, so the comparison continues when you sign back in; uninstalling the app deletes it. Anything else that needs your sign-in is held in memory only and dropped when you sign out. The app reads the clipboard only when you tap Paste on the Telegram link screen.

The home-screen widget: from version 0.9.17 the app keeps, in its private storage, the address of the wallet it shows (the one you signed in with, or the one it acts for), the last figures the widget read and when a read last failed. If you add the widget, it reads the public claim preview for that address from vaultbags.app, the same figures anyone sees for it before connecting, and, without any address, the share multiplier for SPY and how close the vault's next purchase is. It reads when Android updates it (every 30 minutes) and when you sign in, never more than once a minute. Signing out removes the address and those figures, and the widget then shows that you are signed out; a session that ends while the app is closed is cleared the next time you open it.

Who the app talks to: vaultbags.app, your wallet app, Google Play services for notifications, and, for the checks you start yourself (the reserve balances on the proof screen, a monthly report's on-chain record, the confirmation of a lock you just signed), the public Solana endpoint run by the Solana Foundation, which sees the addresses or transaction being checked. If it does not answer, the same read goes through vaultbags.app. Explorer, X and Telegram links open in your browser or in those apps. The app adds no analytics, advertising or crash-reporting service.

No advertising identifiers, no cross-site tracking, no fingerprinting, no marketing database, no data brokers. There is no email list because there are no emails. If a future feature ever needs to collect something new, this page changes first.

Updates are posted here with a new effective date. Questions and reports via X or Telegram.