SafeBlock privacy policy

Who provides SafeBlock

SafeBlock is published by Jovey. For privacy questions or deletion requests concerning support correspondence, contact Mdthitipong@hotmail.com.

Local filtering

SafeBlock uses Chrome’s request-filtering engine with a bundled list of ad and tracker domains. Filtering does not send browsing activity to Jovey, an external DNS provider, or an ad-blocking server. The extension has no telemetry, account system, analytics SDK, remote scripts, or synchronized storage.

Information handled on your device

When you open SafeBlock, temporary active-tab access lets the popup read the current URL to identify its domain and display Chrome’s page count when available. The full URL, page title, favicon, and count are not saved or transmitted. A website domain is saved as a local exception only when you choose to allow it. Exceptions include that domain’s subdomains.

Optional cookie rejection reads visible page elements and recognized consent-button labels to select explicit rejection or necessary-only choices. Optional YouTube filtering inspects supported player response fields and player elements locally. It does not retain page contents, video history, form input, passwords, or authentication cookies. These features require website access and run only after you enable them.

Optional privacy controls read and change supported Chrome privacy-setting values. They do not read or erase your cookies. First-party cookies and Chrome site exceptions may remain.

Stored information and retention

Chrome stores your feature switches, appearance choice, and explicit website exceptions locally until you change them or remove the extension. Version 1.7 uses Chrome’s native per-page count, which resets on navigation. SafeBlock 1.7 does not create session or lifetime totals. Existing developer-build aggregate totals and their start time may remain on an upgraded installation as clearly labeled historical data; they no longer increase.

No browsing-history log is created. No user data is sold, shared for advertising, transferred for unrelated purposes, or used to determine creditworthiness. The extension sends none of the information described above to Jovey or third parties.

Your controls

Manage domain exceptions in Allowed websites. Release Chrome privacy overrides in Privacy controls. Turn off cookie rejection or YouTube filtering in their respective pages, and manage website permissions in Chrome’s extension settings. Disabling cookie rejection removes shared scripting/site access and may also disable YouTube filtering. Reload affected pages after changes.

Uninstalling SafeBlock removes its extension-local settings and exceptions through Chrome. Historical totals stored by a separate older QuietBlock installation remain with that installation until you remove it. Browser overrides are released when the controlling extension is removed; previously submitted consent choices remain subject to each website’s cookie/storage rules. Clearing a website’s data is handled in Chrome, not by SafeBlock.

Website, downloads, updates, and support

This website’s interactive preview uses sample state in browser session storage. It is separate from the installed extension and cannot read the extension’s settings. SafeBlock pages bundle their fonts and do not include analytics scripts.

Visiting Jovey.co, downloading files, or following external links makes ordinary web requests to the destination and its hosting provider. This site is hosted using GitHub Pages; hosting infrastructure may process standard request information such as IP addresses. Chrome Web Store installation and updates, if the extension is published there, are handled by Google under its policies. These services are separate from SafeBlock’s local filtering.

If you contact support, your email address and the information you choose to send are used to answer your request. Do not send passwords, private browsing history, or sensitive screenshots. You may request deletion of support correspondence using the contact above, subject to applicable retention obligations.

Changes

Changes to functionality or data handling will be reflected here and, where required, in Chrome’s permission prompts. The effective date will change when this policy changes.