Privacy Policy
bePresent
Last updated: March 10, 2026
bePresent is a Chrome extension that blocks distracting social media feeds while you work. This policy explains what data the extension accesses and how it is handled.
Data Collection
bePresent does not collect, transmit, or sell any personal data.
No analytics, telemetry, tracking pixels, or third-party scripts are included.
Data Stored Locally
bePresent stores a small amount of state using the Chrome Storage API
(chrome.storage.sync).
| Data | Purpose |
|---|---|
| Enabled or disabled toggle | Remembers whether blocking is active. |
| Bypass timestamp | Tracks when a temporary bypass expires. |
| Last bypass date | Prevents repeated bypass use within the same day. |
If Chrome Sync is enabled, this state may sync across your Chrome browsers through your Google account. bePresent does not separately receive or process that data.
Network Activity
The extension communicates only with a local service running on localhost on
your own machine to determine whether blocking should be active.
- The local service runs entirely on your device.
- No data is sent to external servers, APIs, advertisers, or analytics providers.
- No browsing history or page content is transmitted by bePresent.
Permissions
| Permission | Why it is needed |
|---|---|
storage |
Saves the on/off state and bypass timing locally. |
tabs |
Updates open tabs when blocking status changes. |
| Host permissions for Instagram, X, and YouTube | Injects the blocking overlay only on supported sites. |
Host Access
bePresent runs content scripts on the following domains:
*.instagram.comto block Reels*.x.comto block the feed*.youtube.comto block Shorts
The extension does not collect or transmit content from those sites. It only injects a visual blocking interface and updates it when your local state changes.
Data Deletion
Uninstalling the extension removes its locally stored data. You can also clear extension data from Chrome's extension management settings.
Changes
This page will be updated if the privacy policy changes.
Contact
For privacy questions, open an issue on the GitHub repository.