Privacy Policy
Last updated: June 2026
1. Scope
This Privacy Policy describes how Mybucks.online ("we", "us", or "our") handles information when you use:
mybucks.online — the marketing and information website (the "Landing Site")
app.mybucks.online — the browser-based wallet application (the "Wallet App")
docs.mybucks.online — project documentation
Together, these are referred to as the "Service" or "Services".
This policy does not apply to p2p.gifts or other third-party websites, even when they link to or integrate with Mybucks.online. p2p.gifts has its own Terms of Use and Privacy Policy.
2. Privacy by Design
Mybucks.online is a digital cash envelope built on a seedless, disposable, browser-based wallet framework. The Wallet App does not require registration, accounts, or email addresses. Passphrases, PINs, and private keys are not stored on our servers and are not transmitted to Mybucks.online infrastructure during normal wallet use.
Key generation, signing, and credential handling occur entirely in your browser. When you close or refresh the tab, wallet secrets are cleared from the application's memory. We do not operate a backend database of user wallets or credentials.
3. Information We Do Not Collect
In the Wallet App, we do not:
Require or store your name, email, phone number, or government ID
Store your passphrase, PIN, private keys, or seed material on our servers
Log wallet credentials or transaction signing inputs on Mybucks.online servers
Track in-app wallet activity for analytics or advertising
There is no account system and no server-side user profile.
4. Information Processed in Your Browser
When you use the Wallet App, the following stays on your device unless you choose to share it (for example, by sending a gifting link to someone else):
Passphrase and PIN inputs
Derived private keys and wallet addresses
Transaction data you choose to sign and broadcast
You are responsible for protecting this information on your device, including browser history, clipboard contents, and shared links.
5. Transfer via URL (Gifting Links)
The Wallet App and related tools can generate URLs that encode wallet credentials so a recipient can access a wallet without installing software.
Credential data is placed in the URL hash fragment (
#wallet=...). Hash fragments are handled by the browser and are not sent to web servers in HTTP requests.Anyone who obtains the full URL can decode the credentials and access the wallet.
URLs may be stored in browser history, bookmarks, sync services, or messaging apps you use to share them.
See also: Transfer via URL and Terms of Use — Section 3.4.
6. Third-Party Services (Wallet App)
The Wallet App runs in your browser and may connect directly from your browser to third-party providers for blockchain and market data. These requests are initiated by your device, not routed through Mybucks.online servers.
Examples include:
Infura (and similar RPC endpoints)
Read chain state, broadcast signed transactions
Public wallet address, signed transaction payloads, RPC queries
Moralis
Token balances and (when enabled) transfer history
Public wallet address, chain ID, token contract addresses
TronGrid
TRON network access
Public wallet address, TRON-related RPC queries
Blockchain explorers
Links opened by you
Depends on the explorer; usually via standard web navigation
Google Fonts
Typography
Standard font CDN requests
TrustedSite (optional badge)
Trust / security badge display
Standard third-party script requests
We do not control how these providers collect, use, or retain data. Their practices are governed by their own privacy policies. You should review those policies if you have concerns about third-party processing.
Important: Third parties receive your public wallet address and network-related query data. They do not receive your passphrase or PIN from Mybucks.online, because we never send those to our own servers.
Optional token history (VITE_ENABLE_TOKEN_HISTORY) uses Moralis from the browser when enabled in a given deployment.
7. Local Storage (Wallet App)
The Wallet App may store non-sensitive preferences in your browser's local storage — for example, light/dark theme choice. This does not include passphrases, PINs, or private keys.
8. Landing Site Analytics
The Landing Site (mybucks.online) may use Google Tag Manager for aggregated website analytics (such as page views and referral sources). This analytics is intended for the marketing site only, not for in-wallet activity inside app.mybucks.online.
The Wallet App is configured with noindex directives and is designed without first-party analytics or advertising trackers in the wallet interface.
Analytics on the Landing Site may involve cookies or similar technologies managed by Google. You can manage preferences through your browser settings and, where applicable, Google's opt-out tools.
9. Hosting and Infrastructure
The Services are hosted on third-party platforms (for example, Netlify for the Landing Site and GitHub Pages for the Wallet App and documentation). Those platforms may process standard web server logs (such as IP address, user agent, and requested URL path).
Because wallet credentials in gifting links use URL hash fragments, those fragments are not included in typical server access logs for page loads.
Static site hosting does not give Mybucks.online access to your wallet secrets.
10. Documentation Site
docs.mybucks.online serves static documentation. It does not provide wallet functionality and is not intended to collect personal information beyond ordinary web hosting logs from the hosting provider.
11. Open Source
Mybucks.online is open-source software. Anyone may review, fork, or self-host the code. If you use a copy hosted by someone other than Mybucks.online, that operator's privacy practices may differ from this policy.
12. Security
We apply browser-level protections (including Content Security Policy) to limit which third-party domains the Wallet App may contact. No method of electronic storage or transmission is completely secure. You are responsible for securing your device, browser, and credentials.
See: Security Notice, Browser-Level Protection.
13. Children
The Service is not directed at children under 13 (or the minimum age required in your jurisdiction). We do not knowingly collect personal information from children.
14. Your Rights
Depending on where you live, you may have rights to access, correct, delete, or restrict processing of personal information held by a data controller.
Because the Wallet App does not maintain user accounts or store credentials on our servers, we generally cannot identify or delete wallet data on your behalf — that data exists only in your browser or on public blockchains. For Landing Site analytics, you may use browser controls and applicable vendor opt-out mechanisms.
To exercise rights or ask questions, contact us using the details below.
15. International Users
The Service may be accessed from many countries. Third-party providers (RPC, analytics, hosting) may process data in jurisdictions outside your own. By using the Service, you understand that such transfers may occur.
16. Changes to This Policy
We may update this Privacy Policy from time to time. The "Last updated" date at the top will be revised when changes are published. Continued use of the Service after updates constitutes acceptance of the revised policy where permitted by law.
Material changes may also be reflected in project documentation or release notes.
17. Contact
Questions about this Privacy Policy:
Email: contact@mybucks.online
Website: https://mybucks.online
Documentation: https://docs.mybucks.online
18. Related Documents
Summary: Mybucks.online is a digital cash envelope designed so wallet secrets stay in your browser. We do not operate a custodial backend or user account database. The Wallet App may call third-party blockchain APIs with your public address; the Landing Site may use analytics. You are responsible for credentials, shared links, and device security.
Last updated