What DialGlide does with your data, in plain language.

Last updated: 8 August 2026 · Applies to the DialGlide Chrome extension

The short version
DialGlide does not ask you for an account, it carries no advertising and no analytics, and it does not send the phone numbers it detects — or anything else from the page — back to us.

1. What DialGlide does

DialGlide looks for phone-number-like text on a web page, and it does that only after you have invoked the extension there or enabled it for that website. It then shows you each number it found, together with a short piece of the text around it, so that you can call it, message it, or copy it.

2. What is handled on your device

To provide its phone-number detection feature, DialGlide processes visible webpage text and phone-related page content, including telephone links, visible form-field values that contain possible phone numbers, relevant labels and attributes, and structured telephone data. Detected phone numbers and short surrounding text snippets may be stored in Chrome’s session storage so the side panel can display the results. This information remains on the user’s device and is not sent to the publisher.

User preferences—including language, default country, click behavior, number-highlighting preference, calling and messaging handlers, the local blocklist, optional custom URL templates, and website origins explicitly enabled by the user—are stored in Chrome’s local storage on the user’s device.

3. What we do not collect

The extension does not create an account and does not ask you for your name or email address.
It does not collect your browsing history.
It does not send detected phone numbers or page snippets to receive-smss.live.
It contains no advertising SDK, no analytics SDK, no tracking pixel, and no code loaded from a remote server.

4. Permissions, and why each one is asked for

activeTab: reads the page only after you have clicked DialGlide or invoked it.
scripting: starts detection on the page you selected, or refreshes it there.
sidePanel: displays what was detected, beside the page.
storage: keeps your settings on your own machine, and keeps the scan results for the length of the browser session and no longer.
contextMenus: adds a right-click action for phone-number text you have selected.
Optional website access: persistent detection is granted for the single website origin you approved, and for no other.

5. Calls, messages and custom dialers

When you choose Call or Message, DialGlide opens a tel:, sms:, sip: or sips: link. What happens after that is decided by your operating system and by whichever calling application you have installed.

If you configure an HTTPS custom dialer template, the number you selected is placed into that URL and is therefore sent to the service you chose — at which point that service’s own privacy policy governs it. DialGlide rejects insecure HTTP templates and permits only HTTPS URLs or supported dialer schemes.

6. How long anything is kept

Scan results live for the browser session and Chrome clears them when that session ends. You can delete your saved preferences, or withdraw a website’s access, from the extension’s settings or from Chrome’s extension controls.

Settings, local blocklist entries, custom handler templates, and enabled website origins remain in local storage until the user resets the extension’s settings, removes the relevant entries or permissions, or uninstalls the extension.

Except for user-initiated actions that open a calling, messaging, or custom dialer service as described above, DialGlide does not transfer detected phone numbers, page snippets, or settings to the publisher or other third parties. We do not sell personal data or use it for advertising, creditworthiness assessment, or any purpose unrelated to the extension’s single purpose.

DialGlide’s use of information received from Google APIs will adhere to the Chrome Web Store User Data Policy, including the Limited Use requirements.

8. Children

DialGlide is a general productivity utility. It is not directed to children under 13.

9. Changes to this policy

If we change this policy in a way that matters, we will update the date at the top of this page, and the store listing where that is appropriate.

10. Contact

Write to us about privacy or anything else at support@receive-smss.live

Last updated: 8 August 2026

Check this rather than trust it

Everything above describes code you can read. DialGlide is published under the MPL-2.0 at github.com/receive-sms-live/dialglide, this same policy is kept under version control as docs/PRIVACY_POLICY.md, and every permission is explained on its own in docs/PERMISSIONS.md. Security reports have their own route in SECURITY.md — and please keep real phone numbers, and anybody else’s page content, out of them.