Privacy policy / Version 2.0.0
Stay Unseen 2.0.0 — Your data.
Clearly explained.
Local privacy controls, optional Pro activation, and useful tools. Here is what each part stores and when it connects to a service.
Overview
Stay Unseen’s social-platform privacy protections run in your browser. Pro licensing communicates with Stay Unseen’s API at api.stayunseenapp.com. The dashboard and public Status page also request published compatibility information from that API.
The extension does not send your social messages, usernames, passwords, social-media authentication cookies, viewed Stories, WhatsApp messages, Threads conversations, Facebook/Messenger content, TikTok viewing history or downloaded media contents to Stay Unseen servers. Supported-site tools can use page data and your existing signed-in session to communicate directly with the social platform.
This policy covers Stay Unseen 2.0.0, the All-in-One Social Suite, and this website. Local processing, licensing, compatibility requests and third-party services are explained separately below.
How page data is used
On Instagram, Facebook, Messenger, WhatsApp Web and Threads, content scripts, page-level hooks and browser network controls identify and suppress supported read-receipt, story/status-view and typing signals. They can inspect request contents in memory, including chat-related fields, to distinguish these signals from normal messages and page loading. TikTok support provides download and follow-status tools; it does not hide profile visits or read receipts.
Mark Seen uses identifiers for the open conversation and the platform’s read action to request a receipt when you choose. Follow-status tools read relationship data for the profile you open. Download tools locate media in the page, player or data supplied by the platform. These operations can inspect account identifiers and accessible session/anti-forgery values locally; the extension does not ask you to submit social passwords to Stay Unseen.
Focus Mode changes page visibility on supported Instagram, Facebook and Threads feed/reel routes. Screen Privacy blurs and locks supported pages on Instagram, Facebook, Messenger, WhatsApp Web and Threads. Neither records your screen or uploads screenshots. The Ghost Pill provides local quick controls and shares preferences between supported tabs in the same browser profile.
Data stored in your browser
Stay Unseen uses local browser extension storage, not browser sync, for these records. Local does not mean that records contain no sensitive information: request endpoints and media URLs can contain platform identifiers.
| Data | Purpose and retention |
|---|---|
| Preferences | Feature switches, saved chat exceptions where present, unread-marker settings, Ghost Pill visibility, pause deadlines, Focus Mode, Screen Privacy and queue preferences remain until changed or extension data is removed. |
| Activity counters and times | Blocked-signal and download totals, installation time, recent activity and charts. Hourly buckets are pruned on writes to the last 24 hours; daily history keeps up to seven recorded days. Counters and timestamps are not uploaded to Stay Unseen. |
| Diagnostics | Up to 20 recent block records, up to 250 diagnostic log entries and up to 60 module-probe entries per stored list. These can include endpoints, site identifiers, feature names, timestamps, build versions and decision metadata. They are local diagnostics, not a general browsing-history collection. |
| Tool results | Recent download, Mark Seen and follow-check outcomes, timestamps, errors and limited technical diagnostics are replaced as tools run. |
| Download Queue | Media URLs, filenames, platform, creation time, browser download IDs, status and errors. Completed/cancelled URLs are removed; failed URLs remain available for retry until their entries are cleared or age out of the bounded history. Saved files and browser download history are separate. |
| Licensing information | A random installation identifier, including for Free users. Pro activation additionally stores a signed entitlement, opaque device identifier, refresh credential and licensing state so access can be checked locally and renewed. The entered purchase key is not saved in extension storage. |
The current extension does not retain raw request-body or WebSocket-frame captures; an upgrade cleanup clears the old capture stores. Diagnostic summaries omit raw message-body captures. The production dashboard omits the technical diagnostics drawer. There is no automatic diagnostic-report upload; you choose what information to share when contacting support.
Live Telemetry means local activity and diagnostics. It is not a server analytics feed. Reset counters clears activity totals, recent blocks and chart history, but does not clear every diagnostic record, your preferences, licence or download queue.
Pro licensing and API requests
Free Instagram, Facebook and Messenger privacy controls do not require a purchase or a Stay Unseen account. Pro uses Stay Unseen’s Cloudflare-hosted API. The extension contacts this API for licensing; it does not contact Gumroad directly for normal activation or renewal.
| Operation | Information sent to the API |
|---|---|
| Activation | The licence key you enter and the random installation identifier. |
| Entitlement refresh | The stored signed entitlement, installation identifier and refresh credential when available. |
| Release this device | The signed entitlement and installation identifier. The device/licence references are contained in the entitlement; the client does not send a separate hardware identifier. |
| Legacy licence migration, when available | The previous signed entitlement and installation identifier, followed by the original purchase key when requested. |
The installation identifier is randomly generated, not derived from hardware or a social account. The server binds an entitlement to that installation and manages up to three active browser installations per licence. Separate browsers or profiles count separately, even on the same computer.
Ordinary Pro feature checks verify the saved entitlement locally. Renewal is attempted about daily and when needed at startup or near expiry; it is not a request for every feature use. Access entitlements expire, while a longer-lived refresh credential can obtain a replacement. Offline access lasts only while the saved entitlement remains valid. Refunds, revocation and relevant provider changes can prevent renewal; they do not imply an instantaneous update to every offline browser.
The backend also provides an authenticated licence-status route accepting an entitlement and installation identifier. The current extension does not call that route in its normal dashboard workflow. It is separate from the public compatibility endpoint below.
Licensing requests do not include social activity, media URLs, download history, feature counters or local runtime-health evidence. See the activation guide for setup and device release.
Payments
Current Pro purchases use Gumroad. Gumroad handles checkout, customer email, billing and payment information under its own terms. The Stay Unseen website and extension do not provide a payment-card form or receive full card details through the licensing implementation.
During activation, the Worker sends Gumroad the licence key and product reference to verify the purchase. Later checks can use a purchase or subscription reference instead of the key. Gumroad’s responses and callbacks may include customer and transaction information; the Worker uses the purchase identifiers, product/tier and entitlement-related state to establish or update access. It does not copy the full provider response or customer email into the current D1 licensing records.
The backend supports Gumroad sale, refund, dispute, dispute-won, cancellation, subscription-updated, subscription-ended and subscription-restarted notifications. A recognized notification triggers a provider check before updating entitlement. Support for subscription events does not mean the currently advertised one-time Pro offer is a subscription.
Cloudflare and server records
api.stayunseenapp.com runs on a Cloudflare Worker and uses Cloudflare D1. This API is separate from website hosting: loading a website page is not a licence activation.
The licensing database stores a keyed hash of the licence key, provider/purchase/subscription references where applicable, product, plan, entitlement state and creation/update/access-expiry information. A keyed hash is a one-way lookup value protected by a server-held secret; the raw licence key is processed during verification but is not written to D1. Older records using an unkeyed hash can be upgraded when the key is presented again.
Installation records store a hash of the installation identifier, an opaque device reference, status and activation/last-contact/release/revocation times. Refresh credentials are stored server-side as keyed hashes with issue, expiry, use and revocation metadata. Legacy records can include migration and provider-instance references.
Provider-event records contain the provider, event reference/type, receipt/processing times and a hash of the payload, not the full callback body. Separate compatibility records hold public platform/feature status, verification dates and tested extension versions.
Cloudflare processes ordinary request information such as IP addresses, headers and request times. The Worker also stores IP-address-based rate-limit buckets, request counts and time windows in D1 to limit abuse of licensing and webhook routes. Operational error and reconciliation logs may be produced. These service records are separate from the extension’s local Live Telemetry.
Compatibility and local feature health
The public Status page and extension dashboard request GET /v1/status/features to read published compatibility records. These requests omit credentials and referrer information and carry no licence token, installation identifier, messages, social-account data, counters or local health evidence. The API still receives ordinary connection information, including the caller’s IP address.
Public Working means compatibility was manually verified for the recorded extension version and date, subject to the status system’s freshness checks. It is not live monitoring of each user’s browser.
Local runtime health is evaluated inside the extension. It checks settings, entitlement, pause state, supported tabs, content-script responses, build versions, page-hook acknowledgements and required network/background components. The dashboard displays the result beside features; hovering, focusing or clicking a health badge explains the signals. Working, Ready, Degraded, Offline, Disabled, Pro and Checking describe local state. A nearby Verified date comes from the separate public compatibility record.
These local probes and their results are not sent to the compatibility service. A healthy component check is not an end-to-end test of what another account sees.
Downloads and profile checks
Instagram/Facebook media tools and the TikTok video downloader retrieve available media directly from the social platform or its content-delivery servers, using browser requests and download APIs or an in-page save. Downloaded media does not pass through Stay Unseen servers. The queue and its media links are stored locally.
The platform/CDN receives normal request information, including your IP address and, where needed, platform referrer or existing session context. Some tools make additional requests to the platform for selected media or profile information. These requests are distinct from licensing traffic.
Follow-status badges cover Instagram, Threads and TikTok. Instagram and TikTok can request profile/relationship information directly from that site using your signed-in session. Threads reads native profile data already available to the page. Relationship caches remain in the page/browser; no follower database or list of viewed profiles is uploaded to Stay Unseen.
These controls do not make you anonymous to the websites you use. The social platforms and their media providers apply their own privacy policies.
Browser permissions
| Permission or access | Purpose |
|---|---|
| storage | Preferences, counters, diagnostics, queue state and local licensing information. |
| alarms | Timed protection pauses, queue maintenance, entitlement renewal and expiry checks. |
| scripting | Install privacy hooks and on-page tools on supported sites, including page-level scripts where needed. |
| declarativeNetRequest (Chrome/Edge) | Block matching privacy signals and set the request context needed for supported TikTok downloads. |
| webRequest and webRequestBlocking (Firefox) | Inspect and block matching privacy signals using Firefox’s request APIs. |
| downloads | Save media, name files, monitor downloads started by the extension, and manage queued retries/cancellations. |
| Supported-site and media-host access | Run tools on Instagram, Facebook, Messenger, WhatsApp Web, Threads (.com/.net) and TikTok, and retrieve media from listed Meta/TikTok delivery hosts. |
| api.stayunseenapp.com access | Activate, refresh, release or migrate Pro licensing and request public compatibility information. |
Firefox also declares authentication information for licensing data sent to the API; this is not a request to submit social-account passwords. The production Chrome, Edge and Firefox manifests do not request the separate tabs permission. The extension uses permitted tab APIs and supported-site access to find relevant open tabs, probe local health and open its dashboard. Host permissions let the extension read and change supported pages; they do not grant unrestricted access to every website.
Website, cookies and support
This website’s code includes no analytics service, marketing pixels, tracking cookies, newsletter signup or contact-submission form. It does not use localStorage or sessionStorage. Interactive previews keep temporary state in page memory and do not connect to your installed extension or social accounts. The Status page makes the public API request described above. After an extension update, Stay Unseen may also open this website’s changelog in a background tab.
Google Fonts supplies the website fonts and receives ordinary connection information. Images, scripts and video files are served with the site. Video files are requested when you choose to play; posters load with the page. The tutorial links to YouTube but does not embed its player.
Browser-store, checkout, YouTube and creator links open third-party services when selected. Those providers and the website host process normal web requests under their own policies. This policy describes the website code; hosting-provider logs are separate from site analytics.
If you email support, your email address and the information you choose to send are processed to respond to your request. No automatic social-content or diagnostic upload is attached by the extension. Avoid including private conversations or credentials in a support message.
Data retention
Local retention and clearing controls are described above and below. Removing extension data does not delete downloaded files, browser download history, payment-provider records or server-side licensing records.
Licence, installation, refresh-credential and provider-event records support entitlement, device limits and purchase-state reconciliation. The current implementation does not automatically delete these records after a fixed period. A credential’s expiry or revocation prevents its use; it is not a database-deletion deadline. Releasing an installation changes its state and revokes its refresh credentials rather than erasing its record.
Rate-limit cleanup targets buckets older than 24 hours during occasional request processing. This is not a guarantee of deletion exactly at 24 hours. Public compatibility records remain until updated or removed. No fixed retention period for infrastructure logs, backups or support correspondence is established by the application code; contact us about information you have provided.
Security
The 2.0.0 licence-check improvements run locally. They add no new data collection, browser permissions or external services.
Licensing and compatibility requests use HTTPS. Pro entitlements are signed and checked for the installation and expiry. The server stores keyed licence/refresh hashes rather than reusable raw values in D1. These measures reduce exposure; they are not a guarantee against every security incident. Treat your purchase key and local activation credentials as private.
What Stay Unseen does not do
- Use extension analytics, advertising trackers or automatic crash-report uploads.
- Send social messages, social-account credentials, viewed profiles or downloaded files to Stay Unseen servers.
- Sell personal data or use your social activity for advertising.
- Require a Stay Unseen account for Free privacy controls.
Your controls and data removal
- Choose features: switch features off, pause protection, hide the Ghost Pill or disable the extension in your browser.
- Reset counters: clears activity counters, recent blocks, chart history and download totals. Other settings, licensing and diagnostics can remain.
- Clear the queue: cancel unwanted pending items, then use Clear finished to remove completed, cancelled and failed entries. Saved files and browser download history are managed separately.
- Release Pro: Release this device contacts the API. After a successful release, the dashboard removes the local entitlement, device identifier, refresh credential and licensing state. The installation identifier remains. This frees a Stay Unseen installation slot; it does not cancel or refund a purchase.
- Remove extension data: uninstall Stay Unseen or use your browser’s extension-data controls where available. Delete downloaded files separately if desired.
Release your Pro installation before uninstalling or clearing data. Local removal alone does not release a server-side slot or delete Gumroad’s purchase records. If you cannot access the old installation, or want to ask about server-side information or support correspondence, contact support.
Children
Stay Unseen is not directed at children under 13. We do not knowingly collect personal information from children. If you believe a child has provided personal information to us, contact the address below.
Changes to this policy
We update this policy when features or data practices change. The date above identifies this revision, which documents the current 2.0.0 licensing, compatibility, local-health and social-tool data flows.
Contact
Stay Unseen is an independent project. For privacy questions, support or a request about information you have provided, email [email protected].
Affiliation
Stay Unseen is not affiliated with or endorsed by Meta, Instagram, Facebook, Messenger, WhatsApp, Threads, TikTok, Google, Microsoft or Mozilla. Product names and marks belong to their respective owners.