How BuzzBit X collects, uses, shares and protects personal data.
Version: 2.1 | Effective: October 11, 2026 | Last Updated: November 18, 2026
BuzzBit X Ltd. (“BuzzBit X”, “we”) operates buzzbitx.com, api.buzzbitx.com, the BuzzBit X mobile app and the BuzzBit X Chrome extension.
Giving us data is voluntary, but without the data marked * we cannot open or run an account.
2.1 Account*: name, email, password hash (or your Google or Apple sign-in identity), business name and type, time zone and language. When you sign up with your email address, a record that you accepted the Terms, with the date, your IP address and your browser’s user agent. Your choice about marketing email from us.
2.2 Billing*: plan and invoices. Card numbers are entered on Cardcom’s payment pages; we store only a payment token and the card’s last four digits. If Shopify bills you, Shopify holds your payment details.
2.3 Usage and device: the requests you make to our servers (which show the features you use), IP address, browser and device type, error reports (through Sentry) and support messages. If you turn on notifications, a push-notification token for your device or browser.
2.4 Connected stores and tools: when you connect a store or tool (for example Shopify), we import the orders, products, customers, bookings, payments and invoices that the integration describes on its connect screen.
2.5 Meta Platform Data (Facebook, Instagram, WhatsApp): your Meta user ID, name and email; the Pages and Instagram business accounts you manage and their access tokens (encrypted); Messenger and Instagram direct messages and comments sent to your Pages and accounts; your WhatsApp Business account, phone numbers and message content; and webhook events. To disconnect, use Account → Integrations, or remove the BuzzBit X app in your Facebook settings; we then stop receiving new data. To delete Meta data: remove the BuzzBit X app in your Facebook settings (Settings & privacy → Settings → Apps and websites), which sends us a request to delete the data we hold about your Facebook account; you can follow its status at /data-deletion-status. You can also delete your whole account from the Privacy Center in your account, or email support@buzzbitx.com.
2.6 Google user data: with your permission, Gmail messages and labels, Calendar events, the Sheets you choose, Google Ads accounts and metrics, and your Google profile for sign-in. See section 6.
2.7 TikTok Platform Data: when you connect a TikTok account, we receive only the data needed for the Direct Post feature:
open_id and display nickname, used to identify which TikTok account a post will be published to.creator_info/query endpoint (privacy options, interaction settings, maximum video duration). These are read live before each post and are not kept long-term.publish_id returned by TikTok and, once the post is live, its publicly_available_post_id, so you can see which BuzzBit X post became which TikTok video.The video and photo files you upload are sent to TikTok unmodified. We do not add watermarks, overlays or branding to your content.
2.8 Chrome extension: the extension stores your BuzzBit X session, reads the page you are on only when you use it or give it broader site access, and sends data to api.buzzbitx.com. If you choose to connect a model running on your own computer, it can also send page text to that local model.
2.9 BuzzCall video calls: audio and video go directly between participants (WebRTC). When a direct connection is not possible, they are relayed through Cloudflare’s TURN service. We do not record calls.
2.10 AI clients you connect (MCP and OAuth): see section 8.
2.11 Your own AI provider key: if you add one, the key (stored encrypted) and the AI steps you configure with it. See section 7.
2.12 Voice: if you use a voice feature, the audio you record or the text you ask to hear. See section 7.
We do not sell personal data. We share it only as follows.
(a) Sub-processors that host or run the service for us:
| Provider | What it does for us | Location |
|---|---|---|
| Supabase | Database hosting | Frankfurt, Germany |
| Render | API servers and background jobs | Frankfurt, Germany |
| Vercel | Hosting and delivery of the web app | Global network |
| Upstash | Job queues and cache (Redis) | Cloud hosting |
| Resend | Sending email | United States |
| Sentry | Error reports from the web app and API | United States / EU |
| Cardcom | Card payments and invoices | Israel |
| Cloudflare | Relaying BuzzCall audio and video when a direct connection fails (TURN) | Global network |
| Google (Firebase Cloud Messaging) | Delivering push notifications to the mobile app | United States / global |
| Expo | Delivering push notifications to the mobile app | United States |
| Web push services of your browser’s maker (for example Google, Mozilla, Apple, Microsoft) | Delivering browser notifications, if you turn them on | Set by your browser |
| Slack | Internal alerts to our team about the service, which can include a merchant’s name or email | United States |
| Speech provider (only when voice features are enabled) | Turning speech into text and text into speech for voice features (section 7) | The provider’s region; named here when voice features are enabled |
| Tracing provider (only when tracing is enabled) | Performance traces of API requests, which can include request paths and workspace identifiers | The provider’s region; named here when tracing is enabled |
We will update this list before we start using a new sub-processor, and the “Last Updated” date above will change.
(b) Sign-in providers you choose: Google and Apple receive what is needed to sign you in when you use “Sign in with Google” or “Sign in with Apple”.
(c) Third parties our web pages load: our web app loads Facebook’s JavaScript SDK from Meta and its typefaces from Google Fonts, so Meta and Google receive your IP address and browser information when you visit. See the Cookie Policy.
(d) The platforms you connect, which receive what the integration needs (for example recipient numbers and message content to Meta, or a post to TikTok). If you installed BuzzBit X from the Shopify App Store, Shopify also bills you.
(e) AI you bring yourself: your AI client when you connect it through MCP, and the AI provider whose key you add for AI steps. They act for you under your own terms with them and are not our sub-processors.
(f) Authorities, when the law requires; and (g) a successor in a merger or sale, with notice to you.
We use Meta data only to provide the features you turn on, keep it under the Meta Platform Terms, do not sell it, and do not use it to build profiles beyond what you ask for. Deletion: see 2.5.
We access Google data only for the feature you connected: reading and sending Gmail from your inbox view, showing and creating Calendar events for bookings, reading and writing the Sheets you choose, and reporting Google Ads performance. When you disconnect a Google integration we stop accessing your Google account; data already imported into your workspace (for example calendar events attached to bookings) stays there until you delete it or delete your account.
BuzzBit X’s use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. We never use Google data for advertising, never let staff read it except at your explicit request for support, for security, or where the law requires, and never use it to train AI models. Google data reaches an AI provider only if you configure an AI step with your own key, or let your own AI client request it, for a feature you use.
Apart from voice features (below), BuzzBit X does not run an AI model of its own for you and does not use a platform AI key on your behalf. We do not use your data or your customers’ data to train, fine-tune or improve any AI or machine-learning model, and we do not let anyone do so on our behalf. AI reaches your data in two ways, both chosen and controlled by you:
In both cases the provider is your own processor, or an independent service you engage, under your terms with it; it is not a BuzzBit X sub-processor. What it keeps, and whether it may train on the data, depend on those terms. We store your key encrypted and use it only for the steps you configure. You can remove the key or disconnect the client at any time.
Voice features are the exception. Speech-to-text and text-to-speech run on a speech provider that BuzzBit X configures, not on your key. When you use a voice feature, the audio or text is sent to that provider only to be converted. That provider is our sub-processor (section 4). When no speech provider is configured, voice features are unavailable.
API keys you create for BuzzBit X are stored as bcrypt hashes. OAuth tokens are stored as SHA-256 hashes; access tokens expire after 1 hour and refresh tokens after 30 days, with rotation. Each token is bound to one workspace and to the scopes (read, write, execute) you approved.
Tool-call records. We keep a record of each tool call an AI client makes: the time, the tool, the workspace, the token or key used, the outcome, and the call’s inputs and results, which can include content such as a search term or the text of a draft the client created. These records stay in your workspace for as long as it exists and are deleted with it. We do not currently delete them on a schedule.
We send the connected client only the response to its call. The client’s provider (for example Anthropic for Claude) acts for you under your own terms with it and is responsible for what it keeps.
To revoke access: for an AI client connected with OAuth, go to Settings → Connected apps; for an API key, go to Account → Integrations → Claude → Manage, on the Keys tab. A client can also revoke its own token through POST /oauth/revoke.
| Data | How long |
|---|---|
| Account and workspace data, including Customer Data | Until you delete it or ask us to delete your account. After you confirm an account-deletion request, deletion is carried out 30 days later; financial records are kept in anonymised form where tax law requires. |
| Messages and conversations (email, Messenger, Instagram, WhatsApp) | Until you delete them or your account. We do not currently delete them on a schedule. |
| Records of AI tool calls (section 8) | Until your account is deleted. We do not currently delete them on a schedule. |
| Website visit events collected from your store | 30 days once processed, and no more than 90 days |
| Email delivery events (opens, clicks, bounces) | 180 days |
| Records of completed automation runs | 180 days |
| Automation trigger events | 90 days |
| Webhook payloads we receive, and records of webhooks we send | 30 days |
| Logs and error reports at our hosting and error-monitoring providers | For those providers’ own retention periods |
| Backups | Data deleted from our database can remain in our database provider’s backups until those backups expire. |
We use TLS for data in transit; AES-256-GCM encryption for stored third-party access tokens and API keys; hashing for passwords (bcrypt) and for the API keys and OAuth tokens you create for BuzzBit X; encryption at rest by our database provider; workspace isolation on every query; role-based access for team members; and signature verification of inbound webhooks from Meta, Shopify and Stripe. Our database provider keeps backups. No system is perfectly secure; please report issues to security@buzzbitx.com.
Our API and database run in Frankfurt, Germany (Render and Supabase). Our job queues and cache run on Upstash. The web app is served through Vercel’s global network. Email is sent through Resend (United States) and error reports go to Sentry. Transfers out of Israel rely on the adequacy of the destination or on the recipient’s contractual undertakings under the Privacy Protection (Transfer of Data to Databases Abroad) Regulations 5761-2001. Transfers of EU personal data to the United States rely on the EU-US Data Privacy Framework where the provider is certified, and otherwise on Standard Contractual Clauses.
Under sections 13–14 of the PPL you may see the data we hold about you and ask us to correct or delete it. Under the GDPR you also have rights to erasure, restriction, portability and objection, and to complain to your supervisory authority. You can export your data or request deletion of your account from the Privacy Center in your account, or email support@buzzbitx.com. We answer within 30 days and may verify your identity. Israeli residents may also complain to the Privacy Protection Authority (gov.il).
Our web app uses only the cookies and browser storage it needs to work, and no analytics or advertising cookies. It does load Facebook’s SDK and Google Fonts. The Cookie Policy explains what that means.
The service is for businesses and not for anyone under 18.
We notify the Privacy Protection Authority of a serious security incident as the Data Security Regulations require, notify affected merchants without undue delay and in any case within 72 hours of becoming aware of it, and support merchants with their own notifications.
For material changes we will email account owners at least 30 days in advance, and the version and dates at the top of this page will change.
What it is. BuzzBit X for Chrome is a side panel that connects your browser to your BuzzBit X workspace. It works only while you are signed in to your BuzzBit X account.
Permissions and why.
| Permission | What for |
|---|---|
storage, unlimitedStorage | Your settings, sign-in, and the on-device data described below. |
sidePanel | The panel itself. |
activeTab, tabs, scripting | Reading, screenshotting or acting on a tab when you ask. Opening, switching or closing tabs for a task you started. |
alarms | Refreshing your sign-in, and re-checking pages you chose to watch. |
identity | Signing in with BuzzBit X (OAuth). No Google account data is requested. |
contextMenus | The “Ask BuzzBit X about…” and “Save this ad to BuzzBit X” right-click items. |
| Access to api.buzzbitx.com | Required. |
| Access to all websites, and to a local AI app on your computer (Ollama / LM Studio) | Optional. Chrome asks for it through its own dialog, only when you turn on a feature that needs it. You can revoke it in Chrome at any time. |
What is sent, and where. The extension sends your data only to BuzzBit X (api.buzzbitx.com) and, if you connect one, to a local AI app on your own computer. BuzzBit X receives:
For watched pages, the extension also loads the page itself directly from its website, about every six hours, without your cookies, to see whether it changed.
If you use your own Claude (Anthropic) key, BuzzBit X passes your messages, and the page content involved, to Anthropic to generate the answer. The key is stored encrypted on BuzzBit X’s servers, not in the extension. With a local AI app, chat and file indexing stay on your computer.
The BuzzBit X web app. buzzbitx.com, and no other site, can ask the extension whether it is installed. While the panel is open in the same workspace, buzzbitx.com can also ask it to run a browser step. Each step runs under the panel’s permissions: anything that needs confirmation asks you in the panel. The result (for example page text or a small screenshot) is returned to your BuzzBit X web session. No sign-in token passes between the web app and the extension.
What stays on your device.
Pages the extension does not read. A fixed list of sign-in, payment, bank, crypto-exchange and password-manager sites, and incognito tabs. On other pages that contain password, card or one-time-code fields, it records only the page’s address and title, and it never types into those fields.
Retention and deletion. Signing out revokes the extension’s sign-in and deletes its tokens. The rest of the on-device data (history, screenshots, file index, watched pages) remains until you remove the extension, which deletes all of it. Data sent to BuzzBit X is kept with your workspace under the retention terms of this policy.
No selling, no ads, no analytics. We do not sell data from the extension. We do not use it for advertising, or to determine creditworthiness or for lending. The extension contains no analytics or tracking. BuzzBit X for Chrome’s use of information received from the browser adheres to the Chrome Web Store User Data Policy, including the Limited Use requirements.
Contact. support@buzzbitx.com
BuzzBit X Ltd.
Privacy: support@buzzbitx.com
Security: security@buzzbitx.com
Legal: legal@buzzbitx.com