What PooYeet uses
The extension uses public account handles, Account Geography detections, a pseudonymous install identifier, contribution state, operational metrics, selected Feed Hide Rules, entitlement status, and local cache counts to provide browser-side feed control and reliability checks.
If contribution is enabled, confirmed two-letter Account Geography detections may be sent to the shared backend cache. UNKNOWN is not a confirmed country and is not contributed as a confirmed record.
What stays on your device
Personal Overrides remain local-only. Feed Hide Rules and local detections are applied in your browser; the alpha feed action hides matching posts in the page DOM and does not perform native X account actions.
What PooYeet does not collect
PooYeet does not collect tweet text, full browsing history, unrelated URLs, cookies, auth tokens, provider secrets, X credentials, payment-card details, or private location. Account Geography does not assert nationality, residence, identity, or affiliation.
Waitlist email
When you join the waitlist, your email address and available signup attribution — source, UTM source, UTM medium, and UTM campaign — are sent to Resend and added to the PooYeet waitlist segment. Resend processes this information for email-list management.
The site uses a short-lived, one-way network-address hash to enforce an hourly signup limit. The application does not store raw IP addresses in its waitlist database, and the rate-limit record expires.
Controls and support
You can turn contribution off in the extension. Local feed hiding can continue when contribution is off. A Debug Bundle excludes tweet text, full browsing history, unrelated URLs, cookies, auth tokens, provider secrets, install tokens, raw handles, and Personal Override values by default; sensitive fields require explicit support opt-in.
For privacy questions or removal from the waitlist, email info@pooyeet.com.