Observe
Watch privacy-relevant APIs, third-party requests, storage activity, permissions and other browser behavior as the page runs.
Veilance watches privacy-relevant behavior inside your browser, explains what actually happened, and gives you the choice to contribute useful observations to a shared intelligence network.

Privacy intelligence starts in the browser.
Veilance reports what it can observe and keeps inference separate from fact.
The page created and processed an audio signal in a pattern associated with browser fingerprint construction. AudioContext also has legitimate uses, so Veilance shows the evidence without assuming intent.
A browser can expose a lot about you. The bigger problem is that you normally cannot see when a site is asking for it.
Veilance is not built around collecting browsing history. The first product is local visibility.
Watch privacy-relevant APIs, third-party requests, storage activity, permissions and other browser behavior as the page runs.
Show what happened, why it matters and how confident the detection is. Legitimate API use is not automatically labeled malicious.
If an observation may add value to the network, review a sanitized payload and choose whether to submit it.
The wrong model is "browse the web and earn crypto." That becomes a bot farm immediately. Veilance only rewards uploaded telemetry after it survives validation, deduplication and, when needed, independent corroboration.
If a sanitized report adds useful intelligence to the network, the contributor earns VLNC. Duplicate, replayed, manufactured or low-value submissions earn nothing.
Routine detection should not require sending your page visits to Veilance.
A contribution is a deliberate action, with a report the user can inspect before it leaves the browser.
No routine collection of passwords, form values, auth tokens, cookie values, clipboard contents, screenshots or arbitrary page text.
The telemetry schema and sanitization rules should be documented so users can see exactly what the extension is allowed to transmit.
Validated observations build a historical map of privacy behavior across the web: third-party relationships, fingerprinting techniques, storage behavior, first-seen and last-seen dates, confidence and change history.
That data can support users, researchers, security teams, journalists, browsers and privacy products through Veilance Intelligence and the Veilance API.
VLNC is the Veilance reward and utility token on Solana. Users can choose to upload sanitized telemetry; when a contribution is accepted, reward credit can be settled to the contributor's Solana wallet in VLNC.
Detection does not require a wallet. Uploading telemetry is opt-in. A wallet is only needed if the user wants to receive rewards. VLNC can also be traded independently on Pump.fun; trading is separate from the contributor reward system.
Veilance is available now as an unpacked Chromium extension for Chrome, Edge and Brave. Detection runs locally. Telemetry upload, wallet linking and VLNC payouts are not active in this release.
Clone the repository, then load the cloned directory into your browser.
git clone https://github.com/VeilanceApp/Veilance.git
cd Veilance
Update later with git pull, then reload the extension and any open website tabs.
Open the repository, select Code, choose Download ZIP, and extract the archive.
github.com/VeilanceApp/Veilance ↗Load the extracted Veilance-main directory. Do not select the ZIP itself.
chrome://extensionsedge://extensionsbrave://extensionsmanifest.json.From the Veilance directory, start a local server:
python3 -m http.server 8080py -m http.server 8080Then open http://localhost:8080/test-pages/privacy-demo.html, use the test controls, and review the resulting observations in the Veilance popup.
The current extension lets users inspect and export the sanitized payload locally. No telemetry is sent to Veilance until the validation server is operational and the upload feature is explicitly enabled.