Vaultline

> privacy

We collect nothing

Vaultline has no account system, no backend server, and no database. There is nowhere for it to collect your data, and it doesn't. Here is exactly what happens to everything.

No cookies, no tracking

Vaultline sets no cookies of its own and includes no analytics, pixels, or tracking scripts. That is also why there is no cookie consent banner — there is nothing to consent to. The site is served as static files; any cookie would come only from the hosting/CDN layer, never from Vaultline.

What stays in your browser

The trading rules you write are stored in your browser's localStorage, keyed by your wallet address, so you can back them up and prove later what you committed to. This plaintext never leaves your device. Only its keccak256 hash is sent onchain. Clear your browser storage and it is gone.

What is public onchain

A public blockchain is public by nature. Your wallet address, staked amount, current streak, violation count, and the hash of your rules are visible to anyone on Monad. The shareable /v/<address>page just reads that public state — it exposes nothing that isn't already onchain. Do not put anything you need to keep private into a commitment.

Your wallet

Connecting your wallet shares your public address with the page so it can read your commitment. Transactions are signed in your wallet and go directly to the Monad RPC. Vaultline never sees, requests, or stores your private key.

Hosting

The app is a static site. The host may keep standard request logs (IP, timestamp) as part of serving any website, subject to their own policy — Vaultline itself writes no logs and runs no server-side code that could.

This reflects the code as deployed; the source is open if you want to verify it. Terms & Risk →