Privacy Policy – EZ Buffer Content Generator
**Last updated:** February 2025
**Extension:** EZ Buffer Content Generator (Chrome)
**Publisher:** EZmob (or your organization name)
—
## 1. Overview
EZ Buffer Content Generator is a Chrome extension that helps you generate short-form content (e.g. forum posts, email replies, social posts) using AI. You choose options in a side panel and can optionally use text from the current webpage as context. Generated text is shown in the extension only; you copy and paste it where you need it. The extension is intended for internal use (e.g. by EZmob team members or your organization).
—
## 2. Data We Collect and Use
### 2.1 Data you enter in the extension
– **Form inputs:** Content type, audience, tone, helpdesk keywords, blog URLs, custom context, prompt, character limits, and similar options you type or select in the side panel.
– **Optional configuration:** If you use the “Supabase config” section, you may enter a Supabase project URL and anon (public) API key. This is stored only on your device (see “Local storage” below).
### 2.2 Data from web pages (only when you choose it)
– If you click **“Use page context”**, the extension reads text from the **currently active browser tab** (e.g. page title and main content, such as forum posts or comments). This happens only after you click that button. We do not read or access any tab unless you trigger this action.
– That text is used only to fill the “Custom context” field so it can be sent to the content-generation API as part of your request. We do not store it on our servers beyond what your backend (e.g. Supabase) does for processing and logging.
### 2.3 Data we do not collect
– We do not collect your name, email, or other account identifiers unless your organization’s backend does (e.g. for logging). The extension itself does not send such data.
– We do not collect browsing history, bookmarks, or data from tabs you do not explicitly submit via “Use page context.”
– We do not use cookies or similar technologies for tracking, and we do not sell or share your data with advertisers or data brokers.
—
## 3. Where Your Data Is Sent
– All data you submit (form inputs and, if used, page context) is sent over HTTPS to the **content-generation API** configured for the extension. For the default EZmob setup, this is an API hosted on **Supabase** (supabase.co) that your organization controls.
– Only that API (and the services that host it, e.g. Supabase) receives this data. The extension does not send data to any other third-party servers for advertising or analytics.
– Your organization may log requests (e.g. in Supabase or in an event log) for operational, security, or compliance reasons. How long that data is kept is determined by your organization’s policies and backend configuration.
—
## 4. Local Storage
– The extension may store the following **only on your device** (Chrome’s local storage for the extension):
– Optional Supabase project URL and anon API key, if you enter them in the config section and click Save.
– This data is not transmitted to us except as needed to call the API you configured (e.g. Supabase). It is not used for tracking or advertising.
—
## 5. Permissions
We use Chrome permissions only as follows:
– **activeTab:** To read the current tab’s content only when you click “Use page context.”
– **storage:** To save your optional Supabase URL and anon key locally.
– **sidePanel:** To show the extension’s form and generated content in the side panel.
– **Host access (Supabase and all URLs):** To call your Supabase API and to allow the content script to run on pages when you use “Use page context.” We do not send your data to any domain other than the API you configured.
—
## 6. Your Choices
– You can **avoid sending page content** by not clicking “Use page context”; only the form fields you fill in will be sent.
– You can **avoid storing config** by not entering or saving Supabase URL/key in the extension.
– You can **remove the extension** at any time from `chrome://extensions`. That will stop any further data collection by the extension and will remove locally stored config.
—
## 7. Security
– Communication with the API uses HTTPS.
– We do not use the extension to collect passwords or other sensitive credentials beyond the optional anon API key you may store locally. You should only use the anon (public) key, not secret or service keys, in the extension.
—
## 8. Children
The extension is not directed at children. We do not knowingly collect data from children. If you believe a child has used the extension and provided data, please contact us and we will work with your organization to address it.
—
## 9. Changes to This Policy
We may update this privacy policy from time to time. The “Last updated” date at the top will be revised when we do. For distributed builds (e.g. Chrome Web Store), we will comply with applicable store requirements regarding notice of material changes.
—
## 10. Contact
For privacy-related questions about this extension or the data it handles, please contact your organization’s administrator or the publisher (e.g. EZmob) using the contact details provided with the extension or on your organization’s website.
—