מדיניות פרטיות להרחבת Chrome

Privacy Policy — Bar-Tech Click-to-Dial

Date: 15 October 2026 · Version: 0.4.0

The extension lets authorized Bar-Tech PBX users place calls from Chrome or Edge through their assigned extension. This policy describes the 0.4.0 store build.

Data processed

• The email address and password you enter to sign in to the PBX.
• Account and permission information returned by the PBX, including display name, organization, assigned extension and registration status; an access token and session data.
• The telephone number you choose to dial, request identifiers, update times and call state. The extension also receives PBX call events to display active calls, including caller details and numbers present in those events.
• Access permissions for sites you approve, a list of hostnames where you disable phone detection, your language choice and acceptance of the privacy notice.
• Page text and telephone links on approved sites, for local phone detection in the browser; and a number from text you explicitly select through the context menu.

Phone detection skips input fields, password fields, editable areas and payment forms it recognizes. This does not guarantee detection of every sensitive area on a page. Scanning does not send page text to the PBX; a selected number is sent when you request a call. The extension does not use the browser history API or request SIP credentials, AMI secrets or third-party CRM tokens.

Use of data and service connections

Data is used to sign in, check permissions, place calls, display call state and save preferences. Service requests from the store build use HTTPS to https://pbx.bar-t.co.il. A call request includes the destination number and an identifier to prevent duplicate requests, together with authentication and organization data. The extension code contains no advertising or usage analytics component.

The PBX processes the call request and records an audit event containing user, organization and extension identifiers, the request outcome and the last four digits of the destination number. For information about server record retention and service providers for your account, contact Bar-Tech using the details below.

Storage and ending use

• Your password is sent to the login server and is not written to extension storage. The password field in the extension window is cleared when the login operation returns a response.
• The access token, session details and call UI state are held in chrome.storage.session. Signing out removes the session and resets call UI state. A number pending display in the dialer is temporarily held in the same storage and removed when the dialer reads it.
• Login, session refresh and logout requests also use a PBX authentication cookie. Signing out asks the server to invalidate the session and clear that cookie; this depends on the request succeeding.
• Privacy acceptance and language choice are saved in chrome.storage.local. The list of sites where you disable detection is saved in chrome.storage.sync and may synchronize between browsers according to your sync settings. Site access permissions are managed by the browser.

Permissions and your controls

Required permissions are storage for data and preferences, alarms for call timeouts, contextMenus for dialing selected text, activeTab to identify the active site when using the extension window, and scripting to run phone detection on sites you approve.

Access to other HTTP and HTTPS sites is optional and requested separately for a site you approve. You can enable or disable detection on a site, remove site access, sign out, and uninstall the extension through browser settings. Calling is also subject to your PBX user permissions.

Contact

Bar-Tech · office@bartec.co.il · Bar-Tech website

For privacy when visiting this website, see our website privacy policy (Hebrew) and cookie policy (Hebrew).

לקריאת המדיניות בעברית