This policy covers the NadsX browser extension and the NadsX workspace services it connects to. It is public and does not require an account. The separate website notice describes the public marketing website only. NadsX is independently operated and is not Meta, Facebook, WhatsApp or Google.
Information we handle
| Category | Examples | Purpose |
|---|---|---|
| Account and contact information | NadsX account identifiers, email addresses, Facebook user names and IDs; names and contacts included in records you choose to manage. | Identify the current user and account, provide team access and respond to requests. |
| Authentication information | NadsX session tokens, Facebook access tokens and login context available to the extension on authorized pages. | Verify sessions and access the accounts you are authorized to manage. The extension does not ask you to enter your Facebook password. |
| Advertising and billing information | Account and asset IDs, account status, campaign metrics, spend, balances, billing thresholds, limits and payment-method information returned by Meta, such as card type and masked digits. | Show account statistics, manage advertising assets and generate reports. |
| Leads and managed website content | Selected lead-form answers and contact details; advertising text, images, videos, links, and page or group content you choose to manage. | Synchronize selected records, analyze lead conversion, manage content and download or export requested materials. |
| Feature activity | Feature visits, operation types, task progress, event times and related asset summaries. | Provide usage records, resume enabled tasks, diagnose failures and maintain service reliability. |
| Relevant page and analytics information | The active advertising-page address and account context. Where connected pages trigger analytics, supplied page URLs, titles and a random analytics identifier may be sent. | Recognize the current workspace and measure use of the related product features; see the analytics section. |
| Network and device information | Connected NadsX services may receive IP addresses, browser and operating-system information and security error details. Login audit records include IP and browser information. | Protect sign-in, apply rate limits and investigate service or account issues. This does not imply GPS collection. |
The extension is not designed to collect health records, personal email inboxes, SMS or private chat bodies. It is not a general browsing-history or keystroke recorder. Information contained in forms or content you deliberately manage still needs appropriate authorization, especially if it is sensitive or belongs to another person.
Purpose and when processing occurs
We use information to provide the disclosed advertising-account and asset-management functions: recognizing account context, displaying statistics, exporting reports and materials, synchronizing selected records, and carrying out tasks you initiate or enable. Session checks and enabled background tasks can continue while the browser is running.
Connecting to the NadsX workspace can transmit selected business records and usage summaries to its server. Facebook data requests are made through the extension using the current authorized Facebook session. Installing the extension does not give you permission to access accounts or other people's data that you do not control.
Browser permissions
storage saves preferences, authorization state and task progress. activeTab and scripting recognize the active authorized page and execute packaged page scripts. downloads saves requested reports and materials. alarms wakes enabled background work. declarativeNetRequest applies bundled rules that can adjust specified request and response headers, including content-security-policy headers in some existing compatibility rules.
Host access includes Facebook and its media domains, NadsX service domains and development loopback addresses. The current package also declares compatibility access for gateway.smit.vn, translate.google.com, web.whatsapp.com, messenger.com and web.telegram.org, plus the Google Analytics collection endpoint. A declared domain permission is not by itself evidence that all page content is continuously collected. Chrome's permission controls can restrict access; restricting it may disable affected functions.
Storage, retention and deletion
Preferences, authentication caches, task state and some saved business records are stored in browser storage or IndexedDB. They can remain until cleared, replaced, expired under the relevant feature, or removed by uninstalling the extension. Files you download remain on your device until you delete them.
Records synchronized to NadsX are stored separately on its servers and are not automatically erased when the extension is uninstalled. Login audit records have a default 180-day retention window with scheduled batch cleanup and can be deleted earlier by authorized administrators. Other business records follow the applicable product deletion and retention process; archiving is not necessarily deletion. Legally required records, security records and backup copies may need separate retention and cleanup. Contact us to request review or deletion.
Recipients and service providers
Meta receives the requests necessary to access the Facebook assets you manage. NadsX servers receive information needed for authentication, synchronization, team features and support. Members and administrators may see synchronized records according to the product's account and team permissions.
Hosting, storage and email providers may process information necessary to operate the service. If you use an optional AI-assisted feature, the submitted text or selected materials may be processed by the provider configured for that feature. Google Analytics may receive the analytics information described below. These providers also apply their own policies; we do not describe them as receiving no user data.
Usage measurement and Google Analytics
The current extension includes a page-analytics channel that connected pages can trigger. If a request is received and the channel has not been disabled locally, it can send the supplied page URL, title and a random identifier to Google Analytics. The receiving service also handles network-request information such as IP addresses. Actual triggering depends on the connected page and analytics configuration; it is not a statement that every page is tracked.
Feature usage summaries can also be sent to NadsX for usage records and reliability analysis. Contact us for instructions on disabling the optional analytics channel. Disabling or uninstalling the extension stops subsequent extension requests but does not erase previously synchronized records. This public policy page does not load advertising-account scripts or Google Analytics.
Limited use of information
We do not sell user data or use it as a source for behavioral-advertising profiles, creditworthiness decisions or lending. Processing is limited to the disclosed functions and their necessary operation, security, support and legal purposes. Access by people is limited to authorized product use, assistance you authorize, necessary security investigations or legal obligations.
Information received from Google APIs is used and transferred in accordance with the Chrome Web Store User Data Policy, including its Limited Use requirements. Publishing this statement does not grant additional access to Google or Meta data.
Chrome Web Store · Limited UseSecurity
Production NadsX connections use HTTPS. The server verifies accounts, sessions and permissions; authentication information must not be made public. Browser-local storage is not a promise of hardware-backed encryption and can be exposed if the device or browser profile is compromised.
Do not send passwords, access tokens, verification codes or full payment-card details in support email. No system can guarantee absolute security. If you suspect unauthorized access, revoke affected sessions or permissions and contact us.
Your choices and requests
You can restrict extension site access, disable background work, sign out, revoke sessions, clear local extension data or uninstall the extension. Use the workspace's available view, correction, export and deletion functions for your own records. For server-side access or deletion requests, contact the privacy email below and identify the relevant account without supplying secrets.
We may need to verify identity and authority, especially for team-owned records or leads belonging to other people. Removing local data does not remove server data, and archiving does not necessarily erase it. Applicable legal or security requirements can limit deletion; we will explain relevant limitations when handling a request.
Children and processing locations
NadsX is intended for advertising operators and is not directed at children. If you believe a child has provided personal information, contact us so that we can investigate and take appropriate action.
Information may be processed on your device, NadsX hosting infrastructure and necessary service-provider systems. Locations depend on the service deployment and providers and may involve processing across regions. Contact us for information relevant to the service you use; we do not claim that all information remains in one country.
Changes to this policy
We update this page when relevant data practices or features change and revise the date shown above. Material changes will also be communicated through an appropriate product or listing notice, with additional permission or consent requested where required. The website notice and store disclosures should describe the same actual extension behavior.
Contact and privacy requests
The NadsX operating team handles questions about this policy and requests concerning extension and connected-service data. Email the address below with the relevant account and a description of your request. Do not attach credentials or unnecessary personal information.
coysdsser@gmail.com