ViewSieveViewSieve · 2026-10-10
ViewSieve is provided by AbnerWater, an individual developer. This policy covers the extension, website and support channels, updated September 28, 2026. Contact abnerwater@outlook.com for privacy requests. On-device processing is included in this disclosure; keeping data local does not mean that no data is handled.
On individually authorized YouTube, Instagram and TikTok pages, ViewSieve uses available titles, descriptions, tags, content links, reliable author IDs or profile URLs, platform ad and AI labels, and media state to filter content. Current supported-page URLs, content identities, navigation clicks or keys, scrolling and visibility are used locally for matching, intentional-view protection, correct navigation, metering and diagnostics. It does not read the Chrome history database, build a cross-site browsing profile, log continuous click, keystroke or pointer trails, read private messages or comment bodies, or fetch hidden details. Matching runs on your device.
Keywords, blocked and allowlisted authors, platform preferences, language and recovery snapshots are stored locally. Successful daily cleanup counts, content deduplication digests, success times and relevant rule identifiers enforce allowances. Digests are not page text but remain content-related local data, not uploaded anonymous analytics. Metering rolls over on the next valid local-day access and does not sync across devices. Permission state, pause, the global switch and an entitlement cache also stay local. The extension does not upload page analytics or perform advertising tracking.
Max users may opt in; configuration sync is off by default. After consent, platform settings, layout, keywords and author lists are shared through Chrome storage.sync and may reveal preferences. Google handles delivery under Chrome and account sync settings. The same account and extension ID are required across devices; the configuration budget is 80 KiB. Page text, daily usage and payment entitlements are not product configuration sync data. Rules and author lists are never sent to ExtPay or Stripe.
Google Privacy Policy ↗Turning sync off stops sharing from this device and retains local and shared copies. Deleting the shared copy requires separate confirmation. Other devices pause when they receive the deletion marker and retain local settings. Offline delivery cannot be confirmed; a device that has not received the marker can write old data back. Conflicts require your choice rather than silent replacement. Deleting product configuration does not delete ExtPay login records.
ExtPay and Stripe handle checkout and login recovery using the payment email, chosen plan, payment and subscription status, amount, interval and dates. The bundled ExtPay SDK stores a payment access token, installation date and server user record, which may include email and subscription state. It prefers Chrome sync storage, falling back to local storage if unavailable. This SDK behavior is separate from Max configuration sync and supports restoring payment login. The background verifies access over HTTPS; extension pages receive only limited plan information. ViewSieve does not read card numbers, CVCs, passwords or complete payment forms; sensitive card data is handled on hosted Stripe pages. Access is checked at startup, after payment, on refresh and hourly. Rules, author lists, page content and cleanup usage are not sent to payment services.
ExtensionPay service and data information ↗When you use hosted checkout or subscription management, ExtPay and Stripe handle email, transaction data, billing address and request data such as IP address, device and approximate region under their policies, for checkout, taxes, login recovery, fraud prevention and security. ViewSieve does not request GPS or Chrome geolocation permission and does not use location for filtering or advertising. Payment services retain or delete records under their policies and applicable financial requirements.
Stripe Privacy Policy ↗Storage supports local data, SDK login and consented configuration sync. Scripting runs packaged scripts only on authorized sites. Alarms maintain pause expiry, subscription checks and configuration sync. Debugger is limited to mouse input on a confirmed available native Skip Ad button on an active, focused, authorized YouTube watch page, then detaches on completion, cancellation or timeout. It is not used to record network traffic. User-triggered page diagnostics show limited status, without page text, rules, account information or payment credentials, and are not automatically uploaded.
GitHub provides the static website and official Issues service. This website uses Google Analytics only after visitor consent as described below, with no ad pixels, payment SDK or product account system; demos run only in memory. GitHub handles request data such as IP addresses. When you submit an issue, your GitHub username, report and attachments are public. The extension does not attach page content or configuration automatically. Never post rule exports, personal accounts, login links, tokens or payment details. Send billing, privacy and security requests privately to abnerwater@outlook.com; Outlook.com hosts support email, used to address your request. The extension cannot access your mailbox or chats.
GitHub Privacy Statement ↗Only after you select Allow analytics does the website load Google Analytics (G-NXCGRMZMZX) to measure visits, sources and demo, plan, install and support clicks. Enhanced measurement can also record website interactions such as scrolling, outbound links, downloads and form interactions. Before a choice or after rejection, no GA script loads and no analytics request goes to Google. Google handles browser identifiers in analytics cookies, page paths, referring sites, restricted UTM campaign codes, page language, click types and interaction metadata such as destination links and form identifiers, plus technical request data such as IP address, browser, device and approximate region. This is not completely anonymous data. We do not enable Google Signals, ad personalization or remarketing, or send extension rules, author lists, filtered content, demo words, email or payment details. A website click is not a successful installation or purchase. Do not put personal information into campaign codes.
How Google uses information from partner sites ↗Allow/reject preferences last 180 days in this browser and are shared by the English and Chinese website. Analytics remains off if the preference cannot be saved. Website-specific GA cookies with the viewsieve prefix last up to 180 days without renewal on every visit. Google server-side data follows the actual retention settings of this GA property; deleting local data does not delete historical server records. Open Analytics preferences in any page footer to withdraw: tracking stops, website analytics cookies are cleared and the page reloads. Earlier activity is not replayed. Website analytics is separate from the extension, ExtPay subscription identity and Chrome configuration sync. Contact support for server-side access or deletion requests; identifying records after browser identifiers are deleted may be limited.
Rules and settings remain until you change them, clear extension data or uninstall; local recovery snapshots can retain earlier rules. Media and navigation state serve the current session; daily deduplication records are replaced at the next valid day rollover. SDK login/cache and Chrome shared copies can be restored after reinstallation: uninstalling does not delete cloud copies or cancel a subscription. You can revoke site access, pause filtering, separately delete shared configuration and cancel renewal in the hosted portal. Email support for access, correction or deletion of payment or support records, sharing only what the request needs. You can edit or close a public issue; closing it does not erase the public record. Contact GitHub for removing attachments or other retained copies. Legally required transaction records may not be immediately erasable.
ViewSieve complies with the Chrome Web Store User Data Policy, including Limited Use requirements. Extension data serves requested cleanup, preference recovery, subscriptions and support. Consented website visit data serves the analytics purposes described above. It is not sold or used for personalized advertising, creditworthiness or lending, and is transferred only to necessary service providers or for permitted legal, security or other policy-allowed reasons. We do not manually inspect local browsing content; support handles only information you choose to provide for the request or other policy-permitted cases. Service requests use HTTPS; no system is claimed to be perfectly secure. Material changes will update this policy.