Privacy starts with collecting less.
This policy describes the behavior of the current website prototype and should be reviewed before production deployment.
This draft privacy notice is written for the current Sinkers website prototype. It is not legal advice and should be reviewed and adapted by qualified counsel before the site is deployed as a production service. The prototype does not provide accounts, wallet connections, alert subscriptions, or a live blockchain data service.
What this prototype handles
The website pages are primarily static content. The demo dashboard filters illustrative rows locally, and the simulator calculates hypothetical values in the browser. The prototype does not ask visitors to submit wallet addresses, connect accounts, or provide private keys.
Hosting and operational providers may process technical request data such as IP address, browser information, and server logs under their own terms. The final production deployment should document all providers, purposes, retention periods, and applicable legal bases.
No wallet connection is enabled
This build does not implement WalletConnect or another wallet integration. It does not ask for signatures or token approvals. A visitor should never enter a seed phrase or private key into a monitoring website.
If wallet features are introduced later, the site must explain the specific purpose and permissions, minimize data collection, and provide a safe way to disconnect. A read-only alert experience should not require permission to move assets.
No account preferences are persisted here
The current interface does not save a watchlist or dashboard preferences to a user account. Browser behavior may still involve essential framework or hosting mechanisms. The production policy should inventory any analytics, cookies, and third-party scripts that are actually enabled.
This draft does not promise that every infrastructure provider retains no logs. Review the hosting configuration and provider terms before publishing a final policy.
Explain any future account or alert data
If accounts, saved watchlists, or notifications are added, the project should list the exact fields collected, the reason each is needed, retention periods, and deletion controls. Access should be scoped so users cannot read another person’s private settings.
A Telegram or other notification integration should be opt-in, secure, and removable. No such integration is connected in this build.
Set a real contact route before launch
No privacy contact email or legal entity information has been supplied for this project. This draft therefore does not invent a contact address. A production launch should add a monitored contact route and identify the organization responsible for responding to requests.
See Security & Transparency for current platform limitations. The Terms of Service and Risk Disclosure should be reviewed alongside this policy.
Good questions deserve clear answers.
These notes reflect the current prototype status. For product details, follow the linked guides and their stated limits.
Does Sinkers store my wallet address?
The prototype has no wallet connection and does not ask for a wallet address.
Can I save a watchlist?
No account-backed or persistent watchlist feature is implemented.
Is this final legal advice?
No. This draft must be reviewed by qualified counsel and aligned to the final hosting and data practices.
THE INTELLIGENCE BEHIND EVERY MARKET SIGNAL.
Stay ahead by staying curious. Verify the event, question the interpretation, and keep the limits in view.