Privacy Policy

Effective Date
2026-02-18
Updated
2026-08-29

This policy explains what information the Chat2File-DeepSeek browser extension (the "Extension") processes, why it is processed, and whether it stays on this device or is sent elsewhere. The Extension is not an official DeepSeek service.

Conversation Content

When you use the Extension on https://chat.deepseek.com/, it reads conversation content visible on the page (such as text, code, tables, and formulas) for exports you initiate, or for saving to Notebook.

Our servers do not store your conversation data.

Account, Membership, and Payment

Sign-in and registration require your email address. That email is sent to our server at https://deepseek.chat2files.top to send verification codes, create or sign in to an account, and show your membership status and remaining export quota. Verification codes are sent to that email.

The recovery credential used to keep you signed in is stored in the Extension's local storage. Short-lived sign-in credentials stay only in the Extension background's memory. Scripts on the conversation page cannot obtain these credentials and do not access our servers directly.

After a successful export, the Extension confirms quota once with our server. That request includes confirmation for this export (and may include format types). It does not include conversation body text. The count is recorded on the account and is not reset by reinstalling or switching devices.

When you activate membership, order information is sent to our server; you complete payment by scanning a WeChat Pay QR code generated on this device inside the Extension. Amounts and benefits are as shown at the time. WeChat Pay processes collection under its own rules.

Other Data Stored on This Device

The Extension stores the following in the browser's local storage provided for extensions:

  • Export settings and preferences (including UI language, format visibility, and Word / PDF options; Word document creator and similar fields you fill in are written only into files you export)
  • Local export counts (used for in-extension prompts; not reported to our servers)
  • Notebook folders and notes (our servers do not store this content)
  • The email last used to sign in, only for pre-filling the sign-in form; it does not mean you are currently signed in
  • Export records not yet confirmed by the server (without conversation body text)
  • A snapshot of the current pending payment order (including product, amount, and payment code, used to display the QR code; the payment code is not sent to a third-party QR-code website)
  • UI display state such as first-run help and co-creation prompts

PDF preview temporarily stores the data needed for preview on this device so the preview page can read it and download; that entry is deleted after a successful read. If preview is not completed, the entry may remain on this device for a time.

Requests to DeepSeek

Only when you enable "Message time" in batch export does the Extension read existing login credentials already present on the DeepSeek page (read-only) and request current session data from DeepSeek, in order to align message times. The Extension does not create, modify, or delete that credential, and does not write it into the Extension's own storage. If it cannot be read or the request fails, that timed export is aborted. When the option is off, the Extension does not make the above request to DeepSeek.

Third-Party Resources and Outbound Links

When exporting images, the Extension's background page loads formula styles from a third-party CDN (jsDelivr) so formulas display correctly.

Links you click open third-party pages, such as the extension store, feedback entry, or product promotion pages. After you leave, those sites handle the visit under their own policies.

Permission Uses

The Extension requests the following permissions and uses them as described.

  • scriptinginjects the export and Notebook UI on the DeepSeek conversation page, and adjusts code-block display on the page when needed for export so visible content can be exported in full.
  • storagestores the data described in section 3 on this device, as well as credentials used to restore sign-in.
  • debuggerused only to generate PDF. The Extension briefly attaches to the tab used to produce the file, calls the browser's "Print to PDF" capability, then disconnects. During this process the page content on that tab may be briefly replaced; the page is refreshed afterward. This permission is not used to inspect, monitor, or debug your computer.
  • tabsopens the settings page, PDF preview page, and outbound links you click; syncs settings and sign-in state to already-open DeepSeek tabs.
  • offscreenused for page rendering related to image export, so the conversation page is not occupied.

Site access

  • https://chat.deepseek.com/*run the Extension on the conversation page; and, in the circumstances described in section 4, read message times from DeepSeek.
  • https://deepseek.chat2files.top/*account, quota, membership, and payment requests are sent only to this address.

Sharing and Disclosure

We do not sell your personal information. Currently, information leaves your device only in these cases:

  • Account, quota confirmation, and payment order information sent to our servers (see section 2)
  • Requests to DeepSeek when you enable message times (see section 4)
  • CDN access when loading formula styles (see section 5)
  • Visits to the corresponding site after you click an outbound link
  • Payment processing by WeChat Pay when you scan to pay

Retention and Deletion

Data on this device is retained until you delete it, clear extension data, or uninstall the Extension. You can delete individual notes, or uninstall the Extension through the browser to clear data on this device.

Signing out deletes local sign-in credentials and ends the current session. The email used for form pre-fill remains on this device by default.

Security Boundaries

Short-lived sign-in credentials do not enter conversation-page scripts and are not written to local storage. Login credentials on the DeepSeek page are not written to Extension storage. Payment codes used for payment are stored only on this device, to generate the QR code.

We cannot promise absolute security. Do not store highly sensitive information such as plaintext passwords or ID numbers in conversations, notes, or exported files.

Minors

If your jurisdiction imposes additional requirements for minors using online services, please use this Extension under guardian guidance.

Policy Updates

We may update this policy when functionality or compliance requirements change. The updated version takes effect upon publication. Your continued use means you accept the updated policy.

Contact

For privacy-related questions, please contact the maintainer through the contact entry in the settings page or on the extension publishing page.