Salad Watch Privacy Policy

Effective date: October 21, 2026

Developer: vt-studio

Contact: pvdt.tec@gmail.com

About this extension

Salad Watch monitors public GPU earning-rate data from Salad and alerts you when your selected rate exceeds your threshold. It is an independent extension, not affiliated with or endorsed by Salad.

Information stored on your device

The extension stores the following in Chrome's local extension storage: your selected GPU, earnings metric, threshold, check interval, reminder preference, monitoring state, browser-card and sound preferences, the latest public GPU-rate catalog and its fetch time, crossing/reminder history, any pending browser card, and notification/sound test or error results. These values support monitoring, previews, deduplication, and diagnostics. They are not synced through Chrome Sync or sent to the developer.

Monitoring starts paused, although the extension makes an initial public-rate request to populate its preview and GPU list. Starting monitoring enables recurring requests. Manual refresh and saving settings also fetch public rates. Enabled monitoring checks on Chrome startup. The extension does not require an account or collect your Salad login or account earnings.

Network requests and third parties

The extension requests public rate data from https://app-api.salad.com/api/v2/demand-monitor/gpu over HTTPS. The selected GPU and threshold are compared locally and are not submitted in those requests. Requests omit account cookies and credentials. Like other HTTPS requests, they disclose your IP address and ordinary network/request metadata to Salad's infrastructure. That infrastructure's handling of request metadata is governed by Salad's own policies, not this extension's developer.

If you click Open Salad or a desktop notification, Chrome opens https://salad.com/earn/demand. That visit is a separate website interaction subject to Salad's own policies and your browser's usual website settings and cookies.

There are no analytics, advertising, telemetry, remote executable scripts, or developer-operated tracking endpoints in the extension. The alert chime and all code are bundled locally. The developer does not sell user data, transfer it to advertisers or data brokers, use it for unrelated purposes, or use it to determine creditworthiness or for lending purposes.

Optional access to websites

Persistent browser cards are off by default. Enabling them requests optional permission for HTTP/HTTPS sites. When granted, the extension runs a small content script in top-level supported pages to add and remove its own alert card. It checks page visibility to display the card when a tab is visible. Chrome supplies eligible tab identifiers for delivering/injecting the card. The code does not extract website text, form values, passwords, cookies, communications, or browsing history, and it does not record or transmit visited URLs.

Site access is a technically broad browser capability; it is used here for the browser-card feature. The content script can request only the pending alert payload and acknowledge its identifier. Local extension settings and alert history are restricted to trusted extension contexts.

Turning off Persistent browser alerts hides the card and unregisters its script for future pages, but Chrome's granted site permission remains until revoked in the extension's Chrome settings. Desktop notifications, rate monitoring, and the local chime do not require this optional site access.

Notifications and sound

Chrome and the operating system display desktop notifications containing the public GPU label, selected earnings metric, rate, and threshold. An optional browser card shows similar information inside a webpage. Because the card is part of that page's DOM, the host website may be able to observe its displayed text or remove it. Keep this in mind when enabling browser cards on websites you use.

A bundled chime plays in a hidden extension audio document when sound is enabled. No microphone, recording, or audio-upload capability is used. Browser/OS notification delivery, volume, and output settings are controlled by Chrome and your operating system.

Retention, control, and deletion

You can edit settings and pause monitoring from the extension popup. Pausing stops automatic checks; manual refresh/settings changes can still request public data. Pausing does not erase settings, the latest rates, or pending alerts. Clicking a browser card clears that pending card. A newer crossing/reminder can replace it. The latest rate snapshot and diagnostic results replace older ones. Crossing history is retained per GPU/metric/threshold combination to prevent duplicate alerts.

Local data remains until replaced, cleared through Chrome's extension-data controls, or the extension is uninstalled. Revoking optional site access stops browser-card access; uninstalling removes the extension and its local storage through Chrome. The developer has no server copy of your local monitoring settings or history to retrieve or erase.

Contacting support

If you email pvdt.tec@gmail.com, vt-studio receives your email address and whatever message or attachments you choose to send. Those messages are used to answer your request and maintain support correspondence; Gmail/Google handles mail delivery. Do not send passwords or other secrets. You may ask for deletion of support correspondence at that address, subject to applicable retention obligations.

Changes

This policy will be updated when the extension's data practices change. The effective date identifies the current version. Questions about the extension or this policy can be sent to pvdt.tec@gmail.com.