The short version
Boost Me Bitch has no user accounts, no analytics, and no tracking. There is no database of users, because there are no users to put in one — everything that identifies you lives in your own browser, your own Nostr identity, or your own Lightning wallet.
If you sign in with Google, we use it as encrypted storage, not as an identity provider. We never receive your name, your email address, or your profile photo.
What we never receive
- Your name, email address, or Google profile photo.
- Your Nostr private key.
- Your PIN.
- Your Lightning wallet credentials.
The Google sign-in requests exactly two scopes: openid and drive.appdata. Neither one grants access to your name or email, and we do not request the scopes that would.
Google sign-in and Google Drive
Signing in with Google is optional. It exists for people who want to use Nostr but have no Nostr key yet. When you use it:
- A Nostr key is generated locally, at random, in your browser. Nothing about it is derived from your Google account.
- That key is encrypted with a key derived from your PIN, which never leaves your device and which we never see or store.
- Only the resulting encrypted blob is uploaded to your Google Drive, into the hidden
appDataFolder— a private space only this app can read. It is not visible in your normal Drive files and counts against no visible storage. - Your Google account ID (the
subclaim) is used only as salt for that encryption. It is held in memory for the duration of sign-in and is never written to disk or transmitted to us.
We cannot decrypt your backup. Neither can Google. Only someone with both your Google account and your PIN can. This also means that if you forget your PIN, that account cannot be recovered by anyone, including us.
Boost Me Bitch's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.
What stays on your device
App settings, favorites, mute lists, your sent-boost log, wallet connection details, and — if you used Google sign-in — your encrypted Nostr key all live in your browser's local storage and IndexedDB. None of it is sent to us. Clearing your browser data for this site removes it.
What is public by design
Nostr is a public protocol. Anything you publish through this app — boost notes, comments, your profile, your follow list, your public mutes — is broadcast to Nostr relays operated by third parties, where it is readable by anyone and may be copied, cached, and rebroadcast indefinitely. Deletion requests exist in Nostr but relays honor them at their own discretion. Treat anything you publish as permanent and public.
Lightning payments go directly from your wallet to the recipient. We do not route, hold, or take a cut of any payment. Boost metadata you choose to send (your typed “from” name, your message) travels with the payment to the recipient.
Servers we do talk to
- Podcast Index — podcast search and feed data is proxied through our server so that API credentials never reach your browser. Those requests carry your search terms and, as with any web request, your IP address.
- Nostr relays, Lightning services, podcast hosts, and artwork hosts — contacted directly by your browser, and each will see your IP address. We do not control these third parties.
- Google — only if you use Google sign-in, and only as described above.
The site is hosted on Vercel, which keeps standard server logs. We do not run analytics, advertising, or third-party tracking scripts.
Deleting your data
- Local data — sign out, or clear site data in your browser. Signing out of a Google-created account erases that key from the browser permanently.
- Your Google Drive backup — in Google Drive, open Settings → Manage apps, find this app, and choose Delete hidden app data. You can also revoke the app entirely at myaccount.google.com/permissions.
- Published Nostr events — cannot be reliably deleted, as described above.
Children
This app is not directed at children under 13, and we do not knowingly collect information from them.
Changes and contact
If this policy changes materially, the date at the top of this page changes with it.
Questions: chad.farrow@gmail.com
