Browser extension privacy — NudeNyang

Effective date: 2026-10-09

NudeNyang operates the browser extension and its connected Companion sharing service. This notice describes their handling of browser content. External websites have their own policies.

Data and purpose
With service permission, selected home feeds and requested YouTube likes/watch history or BOOTH likes are processed for tablet display. Cards may include titles, author/account display names, post text, source/media URLs, images, timestamps, duration, counters and prices. Public posts can contain personal information. Local browser storage keeps preferences, tab identifiers, profile labels and a Companion pairing credential. The extension does not read the full browser history, password store or private-message inbox, or capture the screen or microphone.

Authentication and recipients
Page scripts use the selected website’s login context, page-accessible cookies and headers only for requests to that website. Website cookies and passwords are not exported with cards. Content and local pairing credentials pass through Native Messaging to Companion on the same PC. The extension has no separate advertising or analytics endpoint. Data is not sold or used for targeted advertising or credit decisions.

Sharing and network processing
Starting Browser Connect on the tablet lets other people viewing it see recommendations and selected account lists, which can reveal interests and watch history. Shared tablet controls can select lists from the connected owner’s account. Companion can send selected content URLs, images and ordinary subtitles to the operator’s relay server. Opening media also contacts external websites/media providers. Stopping sharing cannot withdraw copies others have already seen or saved.

Local retention
Browser preferences and pairing remain until changed, reset or removed. Active collection data is held in memory; temporary X reconnection may reuse a same-account home cache for up to ten minutes. Companion bounds each account-list memory cache to 360 items. Separately, recommendation deduplication history retains hashes/timestamps for two hours, up to 720 entries; watch-hiding history defaults to 30 days, selectable as 7/30/90 days, up to 1,024 entries. Expiry is applied during load/use/cleanup, not guaranteed deletion at a precise time while the app is closed.

Server retention and access
Playback access uses a renewable 90-second lease; content references are held for one hour from registration/update. Access expiry is different from deletion. Expired rows are cleaned opportunistically and may remain in the live database. Content URLs/subtitles can remain in operational backups, for which no automatic deletion deadline is currently configured. Error logs may contain IP addresses; no fixed time-based deletion period is configured. The operator can technically access stored data and backups. HTTPS protects transport and is not end-to-end encryption against the operator.

Controls and enquiries
Revoke service permissions, stop sharing, forget the browser connection or remove the extension. Removing the extension does not delete separate Companion/server data or other viewers’ copies. Contact the address below to enquire about or request deletion of stored data; technical and backup limits will be explained. This notice will be updated when data handling changes.

Contact and deletion requests: tkfdlswk234@gmail.com