Magnet Manager — Privacy & Permissions

Core promise: This extension does not collect your browsing history, does not read any cookies except for 115.com, and does not report data to any third-party analytics service. All magnet processing happens locally in your browser; 115 offline / aria2 push operations are sent directly from your browser, never proxied through our servers.

1. Data we collect

DataPurposeStorageUploaded?
Purchase emailLicense delivery, refund contactOur license server (Cloudflare Worker + D1, deployed at api.magnet.gaoyatang.com)You provide it at purchase
Device ID (browser-generated UUID)License device binding (5-device cap)Local chrome.storage.local, only sent during license checkSent to our license server
License keyPaid user identifierLocal chrome.storage.localSent during license check
aria2 endpoint / token / save dirRPC push configLocal chrome.storage.localNever uploaded
115 offline directory cidMagnet push targetLocal chrome.storage.localNever uploaded
Last 3 extension crash diagnosticsPrompt the user on next popup open to optionally submit anonymous diagnosticsLocal chrome.storage.local, 7-day TTLOnly uploaded after the user clicks "Submit diagnostics"
Last 50 full task logs Detailed log view, troubleshooting, copying magnet / aria2 GIDs Local chrome.storage.local Never uploaded
115 offline task list ("My 115 Files" page) From v0.2.0: an in-extension page that lists every offline task on your 115 account, so you can one-click push to aria2 Fetched live from 115's own API (in your browser context) when you open the page; not persisted locally Never uploaded to our servers (request goes browser → 115 directly)

Task logs may include the full magnet URL, entry source (popup / page button / context menu), per-step status, error messages, aria2 GIDs, and SmartResult JSON; stored only in your local browser. Clear all entries via the "Full log" page (popup → "📋 Full log").

2. What we do NOT collect

3. Per-permission justifications

API permissions

PermissionPurposeWhere called
storagePersist license / config / task historychrome.storage.local in background / popup / options
cookiesOnly reads 115.com domain cookies, used to call 115 offline-download APIs. When the "115 → aria2 relay" feature is enabled, also reads the 115 CDN auth cookie acw_tc and forwards it as an HTTP header to your own configured aria2 endpoint (required for aria2 to fetch files from 115's CDN); never sent to our serverschrome.cookies.get({ url: 'https://115.com', ... }) in background
notificationsNotify on magnet task completion / failurechrome.notifications.create in background
contextMenusAdd "Send to Magnet Manager" right-click menu itemchrome.contextMenus.create in background
alarmsDaily background sync of license state / server timechrome.alarms.create in background, daily interval

Host permissions (granted at install)

OriginPurpose
https://115.com/* + https://*.115.com/*Call 115 offline-download APIs. 115 binds session cookie to issuing IP, so requests must originate from your browser context; the extension calls directly, never through our servers.
https://api.magnet.gaoyatang.com/*Call our license validation / order / refund services. All payment data transmitted over HTTPS + HMAC-signed.
http(s)://localhost/* + http(s)://127.0.0.1/*Local aria2 RPC (default scenario).

Optional host permissions (granted on demand, with browser prompt)

If your aria2 is not on localhost (NAS, Tailscale, reverse proxy, etc.), the extension will prompt the browser permission dialog automatically when you save the endpoint. You can revoke at any time via chrome://extensions/ → "Site access".

Content Script <all_urls>

Content script is injected into all pages, but only does local-only magnet detection (regex scan of page magnet links). It does not send any data to any server. Detected magnet links get a "→ Offline" button injected next to them; the magnet is only sent to background after you click the button. The content script itself makes no outbound network requests or sensitive operations.

4. Third-party services

ServicePurposeData scope
115 Cloud Storage (115.com)Offline downloads / file managementMagnet URL and 115 cookie only, called directly by the extension, never through our servers
Our license API (api.magnet.gaoyatang.com)License validation, orders, refundsPurchase email, license key, device ID
Alipay (landing page redirect only)Purchase paymentOrder amount and ID only, never via this extension
Your configured aria2 RPC endpoint Download task push Default mode ("aria2 only" button / smart-push fallback): magnet URL + save path.
"115 → aria2 relay" mode (opt-in via Settings): 115 HTTPS download URL + filename/subdirectory path + User-Agent + Referer: https://115.com + 115 CDN auth cookie header Cookie: acw_tc=... (without it aria2 cannot pull from 115's CDN).
Target address fully under your control; only enable relay for aria2 endpoints you trust.

5. User-initiated feedback data (since v0.1.3)

When the user clicks the in-extension "Report problem" button to actively submit, the extension uploads sanitized diagnostic data to our license server (api.magnet.gaoyatang.com). Nothing is sent without that click.

What is uploaded:

Never uploaded: cookies / aria2 RPC token / license key / full aria2 endpoint URL / file path passwords / full magnet URLs / local paths, etc. Crash messages and stacks are redacted for URLs, secrets, license/cookie-like values, full magnets, and local paths, then truncated.

Retention: open / triaging tickets up to 180 days; resolved / spam tickets purged after 90 days.

6. Data retention and deletion

7. Contact

Privacy questions, data requests, bug reports:
Email [email protected]
Product home magnet.gaoyatang.com

Last updated: 2026-05-07