BlockParty's Privacy Policy

gistfile1.txt

# BlockParty Privacy Policy

**Last Updated:** October 14th, 2025

## TL;DR

BlockParty processes everything locally on your device. We don't collect, store, or transmit any of your data. Period.

---

## Understanding Chrome's Scary Warning Messages

When you install BlockParty, Chrome shows some alarming permission warnings. Here's the truth about what they mean and why you're seeing them:

### Warning: "Proceed with caution - This extension is not trusted by Enhanced Safe Browsing"

**Why you're seeing this:**
Google's Enhanced Safe Browsing feature only "trusts" extensions from large, established publishers with thousands of users. BlockParty is a small, indie tool built by one person, so Chrome treats it with extra caution.

**What this actually means:**
- This is a reputation/size warning, not a security warning
- Chrome checked our extension thourouhly before publishing to its website and hasn't found anything malicious
- It basically means we're not a huge company with 100k+ users yet

**How to verify we're safe:**
- Check the extension's permissions in Chrome's extension settings
- Read reviews from other users
- Look at our network activity in Chrome DevTools (you'll see we only talk to X/Twitter)

---

### Warning: "Read your browsing history"

**Why you're seeing this:**
Chrome shows this warning for ANY extension that requests the `tabs` permission. The `tabs` permission allows extensions to see and interact with browser tabs.

**What we actually use it for:**
- Finding which tabs have X/Twitter open
- Sending your CSV data from the extension popup to the X/Twitter page
- Detecting if you close or reload an X/Twitter tab during processing

**What we DO NOT do:**
- We DO NOT read your browsing history
- We DO NOT track which websites you visit
- We DO NOT record your browsing activity
- We DO NOT look at any tabs except X.com and twitter.com
- We DO NOT store or transmit information about your tabs
- We DO NOT monitor your web activity in any way

**The technical truth:** We can only see tabs that match our permissions (X.com and twitter.com). Even if we wanted to see your other tabs (we don't), Chrome literally won't let us. 

---

### Warning: "Read and change your data on twitter.com and x.com"

**Why you're seeing this:**
Chrome shows this warning for ANY extension that needs to interact with website content. We need `host_permissions` for x.com and twitter.com to perform the mute/block/unmute/unblock actions you request.

**What we actually use it for:**
- Sending API requests to X/Twitter to mute/unmute/block/unblock accounts
- Reading the responses to know if the action succeeded or failed
- Interacting with X/Twitter's interface on your behalf

**What we DO NOT do:**
- We DO NOT read your tweets
- We DO NOT read your direct messages
- We DO NOT read your followers or following lists (unless you provide them)
- We DO NOT access your password or authentication tokens
- We DO NOT post, like, retweet, or interact with any content
- We DO NOT modify anything except the specific accounts YOU listed in YOUR CSV file
- We DO NOT scrape or collect your X/Twitter data
- We DO NOT send your data to any external servers

**The technical truth:** We only send the bare minimum requests needed to mute/block the accounts you specified. We don't read your timeline, profile, or any other data. You can inspect the network requests in Chrome DevTools to verify this.

---

## What Data We Actually Collect

**None.** Seriously, nothing.

The only thing stored anywhere is:
- **Terms acceptance flag:** A simple `true/false` value in your browser's localStorage indicating you clicked "I Understand" on the welcome screen

Your CSV files, account lists, and processing results exist temporarily in your browser's memory while you're using the extension, then they're gone.

---

## How BlockParty Actually Works

1. You upload a CSV file - it stays on your device
2. The extension reads the file in your browser's memory
3. The extension finds your open X/Twitter tab
4. The extension sends instructions to that tab: "mute @username1, @username2, etc."
5. Your X/Twitter tab makes requests directly to X/Twitter (like you're doing it manually)
6. Results are shown in the extension popup
7. When you close the popup or start a new upload, everything is cleared from memory

**No external servers. No data collection. No tracking. No analytics.**

---

## Third-Party Services

We use exactly ZERO third-party services:
- No analytics (not even Google Analytics)
- No error tracking
- No telemetry
- No advertising networks
- No data brokers
- No cloud services

The only server BlockParty talks to is X/Twitter's, and only because that's literally what the extension does.

---

## Your Legal Rights

Since we don't collect your data, there's nothing to request, delete, export, or manage. Everything stays on your device.

---

## Contact & Support

Questions about privacy or how BlockParty works?

- X/Twitter: [@jojobuilds](https://x.com/jojobuilds)

---

## The Bottom Line

Chrome's permission warnings are designed to be scary because they have to cover the worst-case scenario of what an extension COULD do with those permissions. BlockParty requests:

1. **`tabs` permission** → Chrome warns about "browsing history" (we use it to find your X/Twitter tabs)
2. **`host_permissions` for x.com/twitter.com** → Chrome warns about "reading and changing data" (we use it to perform mute/block actions)
3. **`storage` permission** → To remember you accepted the terms

That's it. There's no tracking, data collection or shady stuff whatsoever. Just a simple tool to help you manage your X/Twitter experience!

---

*Last updated: October 14th, 2025*