UnifyBrowse
Sign inOpen account
Imprint · Privacy

What
we know,
and don’t.

Last updated
August 19, 2026

Plain
language

UnifyBrowse is built and maintained by a small independent studio. This page explains what data is collected, how it’s used, and how it’s handled across the website and the browser extensions. In plain language.

§01Philosophy

The approach is simple: charge for premium software features, and nothing else. Your personal data is never sold to third parties. Extensions are designed to operate locally on your device whenever possible.

Cloud sync exists only for features that genuinely need it, and you have to opt into them. The default is local. The default is anonymous.

§02Information collected

When you use the website or open an account, the following may be collected:

  • Account informationEmail address and basic profile details required for authentication.
  • Billing detailsIf you purchase a Pro plan — whether a one-time lifetime payment or a recurring subscription — payment processing is handled by Lemon Squeezy, our Merchant of Record. Full card numbers are never seen or stored by us — Lemon Squeezy handles the entire payment flow, recurring billing, and tax compliance.
  • Support requestsIf you contact support from within an extension, we receive the message you write and — only if you choose to provide it — a reply email address, used solely to respond to you.
  • Contact formIf you use the website contact form, we store your name, email, subject, and message so we can reply. Submissions are protected by anti-spam verification and used only to respond to you.
  • Anonymous analyticsPer-extension event names, anonymous instance IDs, timestamps. No personally identifiable information.
§03Per-extension specifics02 entries

Each extension requests only the permissions it genuinely needs. Below is a per-extension breakdown.

01

Cairn#

· Permissions

storage: Stores Cairn settings and reading progress locally. unlimitedStorage: Lets the local IndexedDB library grow beyond the browser’s default quota. contextMenus: Provides right-click actions to save pages, selected text, images, and links. activeTab: Reads the current tab only after the user explicitly triggers a save action. scripting: Injects the metadata and article extractor into the active tab only when the user saves it.

· Data handling

Saved items, article HTML, highlights, notes, tags, collections, and reading progress remain on the user’s device. Cairn does not upload this library content to UnifyBrowse.

02

TradeDesk#

· Permissions

storage: Persists your settings, license/entitlement state, and app preferences locally (chrome.storage.local) so they survive browser restarts. Trade data, screenshots, and calculator history live separately in the browser's local IndexedDB — not sent to any server.

contextMenus: Adds right-click menu items to open the Risk Calculator, create a Journal entry, or start a chart screenshot directly from the TradingView page, without needing the toolbar panel open first.

activeTab: Grants temporary access to capture a screenshot of the current TradingView tab when the user clicks to capture a chart image for a journal entry — active only for the click that grants it, per Chrome's activeTab model.

alarms: Uses the Chrome alarms API to periodically check (every 5 minutes) the Pro economic calendar feed for upcoming high- or medium-impact news events, so TradeDesk can notify users ahead of time even when the side panel isn't open. A Manifest V3 service worker can't reliably use setInterval, so alarms are the only way to keep this background check running. Only runs for Pro users who have opted in to Economic Calendar Alerts in Settings (off by default).

notifications: Shows a desktop notification a user-configured number of minutes before a high- or medium-impact economic event for the currency/symbol the user is tracking, if they've opted in to Economic Calendar Alerts (Settings → Economic calendar alerts, off by default). Clicking the notification opens TradingView and jumps to the calendar tab. This is an opt-in Pro feature — no notification is ever shown unless the user explicitly enables it.

Host permission ://.tradingview.com/*: Required to inject the TradeDesk panel into TradingView chart pages — the extension's only content-script target.

Host permission https://td.unifybrowse.com/*: TradeDesk's own license backend, called from the background service worker to activate/validate Lemon Squeezy licenses and fetch the Pro economic calendar. First-party UnifyBrowse infrastructure.

Host permission https://analytics.unifybrowse.com/*: TradeDesk's own anonymous product-analytics ingest, called from the background service worker. First-party UnifyBrowse infrastructure; no trade data is ever included.

Host permission https://unifybrowse.com/*: The marketing site — used for the install/update/uninstall lifecycle pages and the "What's New" changelog link.

· Data handling

TradeDesk does not sell or share user data. No trade data, screenshots, prices, symbols, or notes ever leave the device — they are stored locally in IndexedDB and only ever included in a CSV/JSON export the user explicitly triggers. Anonymous, non-identifying product-usage events (e.g. onboarding completed, a panel opened) are sent to UnifyBrowse's own analytics endpoint, keyed to a random per-install ID, not an account. Activating a Pro license sends only the license key and that per-install ID to the license backend to confirm the plan — never trade data.

§04Third-party services

UnifyBrowse relies on a small set of vetted providers to operate. Each handles only what they need to:

  • Lemon SqueezyPayment processing, tax handling, and license-key management. Operates as Merchant of Record for purchases. See lemonsqueezy.com/privacy.
  • SupabaseDatabase and authentication. Stores account credentials, license records, and anonymous analytics.
  • Hosting (Vercel / Cloudflare)Serves the website and forwards extension API traffic.

Personal data is never sold or shared with advertisers. Data is retained only for as long as your account is active, and is deleted within 30 days of account closure.

§05Data protection
  • All data transmitted uses HTTPS encryption.
  • Database access is restricted by Row-Level Security policies; the studio cannot read your private data outside its specific feature scope.
  • Authentication is handled with industry-standard JWTs.
§06Your rights

You can access, modify, or permanently delete your personal data at any time. The dashboard offers a single button that removes your account and any associated cloud data. Local extension storage can be cleared from your browser’s extension panel.

§07Changes to this policy

This policy is updated when the extensions, the studio, or legal requirements change in a meaningful way. The current version is always posted here with a “last updated” date, and significant changes are announced through in-extension notifications — we don’t email you, because we don’t collect your email.

Questions? Write to the studio — we answer everything.