Chuyển tới nội dung chính
Tìm Sản Phẩm Win · mới mỗi ngày(mở tab mới)Game treo LIVE TikTokĐi Bar Online, Câu Cá, Chùa Online...

Ai Dễ Ẹc Browser Helper

Privacy Policy

This policy explains how the Ai Dễ Ẹc Browser Helper Chrome extension handles information when connecting supported browser tabs to the Ai Dễ Ẹc desktop application.

  • Effective: August 25, 2026
  • Last updated: August 25, 2026
  • Developer: Ai Dễ Ẹc / Ông Chú MMO

1. Purpose and scope

Ai Dễ Ẹc Browser Helper is a local companion for the Ai Dễ Ẹc desktop application. Its single purpose is to connect supported Google Flow and Grok browser tabs to the desktop app on the same device for workflows that the user explicitly starts.

This policy applies to the Chrome extension. The extension is developed independently and is not made by, sponsored by, or endorsed by Google or xAI.

2. Information handled

The extension may handle the following information only as needed on supported Google Flow and Grok pages:

  • Authentication information: sign-in status, session cookies or headers, access tokens, reCAPTCHA tokens, and a short-lived local bridge session or pairing token.
  • Website and user-generated content: prompts, project or task identifiers, generation request and response bodies, task status, and generated media metadata or results.
  • Limited browsing activity: supported-tab URLs, request URLs, request method or type, tab status, timestamps, user agent, and platform information required for the feature.
  • Local extension state: a random extension instance ID, connection metrics, token count, last-success time, and popup preferences.
The extension does not intentionally collect passwords, payment information, health information, precise location, contacts, or general browsing history outside the supported sites.

3. How information is used

Information is used only to:

  • Pair the extension with the desktop app on the same computer.
  • Confirm that a supported tab and sign-in session are ready.
  • Execute the Google Flow or Grok operation requested by the user.
  • Relay prompts, status, errors, and results between the supported tab and the local desktop app.
  • Recover a broken Google Flow session when the user explicitly confirms clearing labs.google cookies.
  • Maintain security, reliability, and local diagnostics.

4. Where information is sent

  • The local desktop app through the fixed loopback endpoint http://127.0.0.1:18925 on the same device.
  • Google Flow or Grok/xAI first-party serviceswhen necessary to perform an operation the user requests while signed in to their own account.

The extension does not send browsing data to developer advertising or analytics servers. We do not sell, rent, or trade user data, and we do not use it for personalized advertising, lending, or creditworthiness decisions.

5. Browser permissions

The extension requests only the permissions required for its disclosed companion workflow:

PermissionPurpose
cookiesRead supported-provider session state and, only after confirmation, clear Google Flow cookies to recover a broken session.
tabsFind and monitor supported Google Flow and Grok tabs needed for a user-started workflow.
scriptingRun bundled helper code in supported tabs so the local app can perform the requested operation.
webRequestObserve relevant provider requests to obtain task status and the session or request values required by the workflow.
storageKeep the random instance ID, local connection state, metrics, and popup preferences.
alarmsPerform bounded connection and session maintenance while the extension is active.
Host accessOperate only on the disclosed Google Flow and Grok pages and connect to the fixed local loopback endpoint.

6. Storage and retention

  • The random instance ID, local metrics, last-success time, and popup preferences remain in Chrome extension storage until cleared or the extension is removed.
  • A local bridge session value is stored in Chrome session storage and is not intended to survive the browser session.
  • Pairing tokens and active task or capture payloads are held in memory for the active local session.
  • The desktop app may save user-requested project data or media according to the user's app settings.

7. Sharing and human access

Data is shared only with the local desktop app and the supported provider required to deliver the user-requested feature. We do not allow humans to read user data except when the user gives explicit consent for specific support, when required by law, or when necessary to investigate security or abuse.

8. Security

The bridge is bound to loopback. The desktop app validates thechrome-extension:// origin, loopback host and port, extension instance ID, and a random in-memory pairing token. All executable extension code is bundled in the installed package; the extension does not download or evaluate remote code.

No system can guarantee absolute security. We limit access and retention to what is required for the disclosed functionality and update safeguards when material risks are identified.

9. User choices and deletion

Users can stop processing at any time by:

  • Closing the Ai Dễ Ẹc desktop app.
  • Disabling or removing the extension.
  • Signing out of a supported provider.
  • Closing the supported browser tabs.

Removing the extension clears its Chrome-managed local storage. Users can also clear extension data in Chrome and delete saved projects or media through the desktop app. The popup asks for confirmation before clearing labs.google cookies.

10. Children’s privacy

The extension is not directed to children under 13, and we do not knowingly collect personal information from children. If you believe a child has provided information through the extension, contact us so we can review and take appropriate action.

11. Chrome Web Store Limited Use

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

Information is used only to provide or improve the extension's disclosed single purpose. It is not transferred or used for advertising, resale, lending, creditworthiness decisions, or unrelated purposes.

12. Changes to this policy

If our data practices change, we will update this policy, its last-updated date, the Chrome Web Store listing, and any required in-product disclosure before the new practice begins. Material changes may also be communicated through the extension, desktop app, or product page.

13. Contact

For privacy questions, support, or deletion requests: