1. Core Philosophy: Feed Provenance Without Panoptic Tracking
   AdSniffer ("we", "our", or "us") builds tools to empower individual readers to understand commercial intent and synthetic content across social feeds. We believe content verification must never come at the expense of reader surveillance.

The AdSniffer Browser Extension operates on a stateless, minimal-disclosure architecture. We do not inspect your private correspondence, browsing habits, financial credentials, search history, or personal bookmarks.

1. Host Permissions & Data We Inspect
   The extension requests scoped host permissions strictly limited to the domains where our users view social media timelines:

https://x.com/ & https://twitter.com/
https://bsky.app/
https://threads.net/, https://.threads.net/, https://threads.com/, & https://.threads.com/*
What AdSniffer Reads: When a social post enters your browser viewport on these designated platforms, our client script extracts the publicly visible post copy and metadata (e.g., author handle, timestamp, and engagement links).

What AdSniffer Never Reads:AdSniffer does not read direct messages (DMs), login forms, payment fields, private draft entries, or pages outside the specified host matches.

1. How Post Data Is Evaluated & Stored
   Ephemerality & Stateless Inference: Extracted post text is transmitted over TLS to the AdSniffer inference API solely to classify advertising likelihood (Hard Ads, Sponsored, Lead Generation) and synthetic AI perplexity. The inference model processes the text in memory and immediately returns the statistical scoring vector. Post text is discarded and never stored in persistent databases.

Local Client Caching: To conserve your network bandwidth and quota, post identification hashes and badge outputs are cached locally in your browser via chrome.storage.local. This cache remains on your machine and can be cleared at any time by removing the extension or resetting storage.

1. Authentication & Account Data (Google OAuth)
   To disburse and track your detection quota (including the founding 10,000 detection Early Bird allocation), AdSniffer supports authentication via Google OAuth2. When you sign in, we receive:

Your unique Google account identifier and verified email address
Basic profile metadata (display name and profile image URL)
We use this identity strictly to maintain your account ledger, prevent duplicate automated sybil claims, and authenticate API requests. We do not access Google Drive, Gmail, Google Contacts, or any other Google service.

1. Chrome Web Store Limited Use Disclosure
   AdSniffer's use and transfer of information received from Google APIs and Chrome Web Store permissions adhere strictly to the Chrome Web Store Developer Program Policies, including the Limited Use requirements:

We will never transfer or sell user data to third parties, data brokers, or advertisement networks.
We will not use or transfer user data for serving personalized or targeted advertisements.
We will not use or transfer user data to train generalized third-party AI models without explicit user consent.
6. Contact & Data Deletion Inquiries
If you wish to delete your account record, revoke Google OAuth tokens, or ask questions regarding AdSniffer privacy practices, please contact our team at:

extension@adsniffer.app