Privacy Policy
IN SHORT
Bazooka processes account, wallet, trading and security data. We hold encrypted wallet keys on our server. Service providers process data for the functions below. Blockchain transactions and published token media are public.
1. Who is responsible
The operator of Bazooka ("we", "us") is the data controller for Bazooka at bazooka.trade and app.bazooka.trade. Send privacy requests to support@bazooka.trade.
2. Data that we collect
- Accounts: email address, username, Privy identity ID, verified sign-in methods, terms acceptance date, sign-in records, account status and security settings. Bazooka does not store a login password, TOTP secret or passkey.
- Google sign-in: when you use it through Privy, your Google account identifier and email address from signed identity data. We request identity, email and profile permissions, not access to your Gmail or Drive contents.
- Wallets and activity: wallet addresses, private keys encrypted at rest with a server-held key, balances, tasks, trades, transaction records, fees, settings, labels, folders and tracked addresses.
- Optional features, when available and used: referrals use codes, account relationships, rewards, payout addresses and IP-based abuse checks. Auto-Trade uses strategy settings, Paper sessions, positions, pending operations, recovery records and share snapshots. These descriptions do not mean all features are currently enabled.
- Security and contact: IP addresses, browser information, request and audit records; the email addresses, notes and request IP addresses of earlier waitlist requests; and support messages and attachments you send.
Privy provides email-code and Google sign-in. Bazooka verifies signed identity data and uses its own sessions. There is no separate Bazooka second factor at sign-in. For protected actions, a one-use code sent to your existing verified email opens a ten-minute confirmation window.
3. Why we use it
- To provide accounts, wallets, transactions and the features you use.
- To process fees and rewards, settle transactions and recover funds.
- To prevent abuse, protect accounts and investigate errors.
- To answer support requests and send account verification, sign-in, sensitive-action confirmation, invitation and recovery emails.
- To meet applicable legal obligations.
Where the GDPR applies, the legal bases are performance of our contract for the service you request, legitimate interests in security and reliable operation, and applicable legal obligations.
4. Public and shared data
Addresses and transactions on supported public blockchains, including Solana, Robinhood Chain, Elysium and HyperEVM, are visible to others. We cannot erase them. Launching a Solana token publishes its image and metadata through Filebase to IPFS. Launching an Elysium token sends its image and metadata to the upload service of the selected launchpad, or stores them on the blockchain. Other parties can keep copies. We cannot reliably recall or delete published IPFS content or content that a launchpad publishes.
An Auto-Trade share code lets other signed-in users preview and import strategy settings, including tracked addresses, labels and configured amounts. Imports remain independent. Referral pages show aggregate account counts, volume and rewards, not referred account names.
5. Providers and international transfers
Providers process data for these functions:
- Cloudflare: DNS, web proxy, Turnstile bot checks, traffic measurements and email routing. It processes request data, such as IP addresses, and forwarded email.
- Hetzner: hosts the public app and its database in Germany.
- Resend: sends account emails and processes recipient addresses and message contents.
- Privy: provides email-code and Google sign-in. It processes login and account details, IP addresses, device information and sign-in events. Its login SDK sends authentication analytics events. It does not receive Bazooka wallet private keys. We do not use it to create, hold or sign with app wallets.
- Google: provides optional Google sign-in through Privy. Gmail also stores and processes support correspondence forwarded through Cloudflare.
- Telegram: processes your profile information and messages when you contact us on Telegram.
- Helius, Jupiter and other blockchain, swap and market-data providers: receive relevant wallet addresses, token identifiers, quote requests and transactions. Auto-Trade's separate market-data service receives public mint or address queries.
- Alchemy and other Elysium and HyperEVM providers, and Hyperliquid: receive relevant wallet addresses, token identifiers, price and quote requests and transactions.
- Elysium launchpads (Kleos, Boxa, Montra, ElysPump): receive the image and metadata of a token that you launch through them, and publish them.
- Filebase: stores and publishes token images and metadata on IPFS.
Providers can process data outside your country, including in the United States. Data protection laws can differ. Their own privacy terms also apply. Contact us with questions about transfers that affect your data.
6. Cookies and browser storage
Bazooka and Privy use cookies and browser storage for sign-in. The app uses essential session and CSRF cookies, plus short-lived pending-sign-up and status-message cookies. A referral link can set the bz_ref cookie for up to 30 days. Browser storage also keeps interface preferences, layouts and wallet selections.
Cloudflare can set security cookies and process traffic data. It injects a Web Analytics beacon into some pages. The landing page currently blocks scripts, including that beacon. Clearing cookies and browser storage can sign you out and reset preferences.
7. How long we keep data
Account records generally remain while your account exists. Deletion does not erase every related record:
- Unsettled operations and retained funds can prevent account deletion.
- Referral codes, relationships, IP-based fraud-review records and payout attempts can remain. Rewards held by other accounts can retain references to your activity.
- Records and service-controlled recovery keys needed for unsettled payments, late deposits or refunds can remain.
- Recovery audit records and retired identity IDs remain after account deletion. They record admin decisions and prevent access through a replaced identity.
- Logs, support mail, earlier waitlist entries and backup copies can remain after account deletion. Deployment backups require separate removal; account deletion does not erase them.
- Public chain data, published IPFS content and other users' imported strategy copies remain outside account deletion.
Retention also depends on unresolved support or security issues and applicable legal obligations. There is no single deletion period.
8. Your rights
Where applicable law, including the GDPR, gives you these rights, you can request access, correction, erasure, restriction of processing and data portability. You can object to processing and complain to a data protection authority. Where processing relies on consent, you can withdraw it.
Send requests to support@bazooka.trade, preferably from your account email. We may need to verify your identity. Rights have legal limits; public blockchain and independently held copies cannot be erased by us.
The public app has no wallet-key export. Use withdrawal and recovery controls to move funds out. For account closure, see the Terms of Use, section 11. Account closure and a privacy request are not the same process.
9. Children
Bazooka is for adults aged 18 or older. It is not intended for children. Contact us if a child has supplied personal data.
10. Changes
We can update this policy. This page shows the effective date of the current version. Check it for changes.
11. Contact
Privacy and support: support@bazooka.trade. See our Contact page for other enquiries.