Scope and purpose

This policy applies to the d3t security Chrome extension. Its single purpose is to provide user-controlled privacy and security features: Facebook phishing detection, website blocking, tracking-parameter removal, GPC/DNT signals, right-click restoration, and privacy controls for Facebook, Instagram, and Zalo.

Data handled

Depending on the features you enable or actively use, the extension may handle:

• Browsing activity: URLs, domains, and query parameters for phishing detection, website blocking, or tracking cleanup.
• Website content: indicators of fake login forms, right-click restrictions, and suggested-post page structure.
• Facebook Friends data: your Facebook user ID and friends' names, IDs, profile URLs, and avatars.
• Authentication information: the Facebook c_user cookie and session token needed to send Friends requests directly to Facebook. Cookie and token contents are not stored.
• Communications data: seen/typing payloads are inspected temporarily in memory to block those signals when enabled. Message content is not stored.
• Preferences: toggle states, blocklists, exclusion lists, and local technical diagnostic metadata.

How data is used

Data is used only to provide features shown in the extension UI and enabled by the user. Facebook Friends requests travel directly from your browser to Facebook. d3t security does not create accounts, advertising profiles, behavioral analytics, or telemetry.

Storage and retention

• Friends data and diagnostic metadata are stored in chrome.storage.local on your device until you clear the cache or uninstall the extension.
• Preferences are stored in chrome.storage.sync and may be synchronized by Chrome through your Google Account according to Chrome Sync settings. The developer cannot access that synchronization system.
• Session tokens, seen/typing payloads, and website content are processed temporarily and are not stored by the extension.

Sharing and transfers

We do not sell, rent, share, or transmit user data to d3t security servers or advertising services. VirusTotal, Google Safe Browsing, and reporting forms open only when you click them; the extension does not automatically submit URLs to those services. Facebook receives Friends requests you initiate using your existing signed-in session.

The support page displays bank QR codes and USDT addresses. Transactions occur in your wallet or banking app; the extension does not receive or store transaction data.

Why permissions are used

storage

Stores preferences, blocklists, and Friends cache.

tabs, scripting

Opens security tools, updates blocked pages, and runs user-requested actions.

declarativeNetRequest

Blocks trackers/sites, removes tracking parameters, and applies GPC/DNT.

webRequest

Recognizes Facebook Friends request templates on a specific Facebook endpoint.

contextMenus

Provides abuse reporting, link scanning, and domain blocking.

sidePanel

Displays quick privacy controls.

cookies (optional)

Requested only when you refresh Friends to identify the signed-in Facebook account.

Website access

Required for phishing detection, website blocking, tracking cleanup, GPC, and right-click features on visited pages.

Your choices

You can disable individual features, deny cookie access, clear the Friends cache, edit blocklists/exclusions, export a configuration backup, or uninstall the extension. Synced preference data can also be managed through Chrome Sync settings.

Children's privacy

d3t security is not directed to children and does not knowingly collect children's personal information.

Policy changes

If data-handling practices change, this policy and Chrome Web Store disclosures will be updated before or with the related release. Material changes will be clearly disclosed in the extension or listing.

Contact

For privacy questions or requests, email mjew781@gmail.com.