Dy Auto Privacy Policy

Effective September 30, 2026 · Last updated October 29, 2026

Dy Auto is a user-controlled browser extension for workflows on public Douyin web pages. It is not an official Douyin product.

Optional lead recognition: Preselected on first use and can be unchecked. A previously saved off choice is preserved, and first-time initialization does not enable it during an already-running task. Preselection does not start automated browsing or messaging. Once a business goal is configured and the option remains enabled, recognition reads already-loaded public comments on the video page you are viewing in the focused tab, without starting an operations task, clicking, scrolling, opening comments or reading all background tabs. Manual browsing batches wait approximately 1.5 seconds after new comments, or are submitted when new comments are present at approximately eight seconds after batch creation, when full, or on a page transition. If you actively start an automated browsing task, the existing flow opens comments and reads successive rounds: 10 rounds per video by default, configurable from 1 to 100, ending after three bottom-of-list rounds without new comments. There is no 2000-comment or three-minute stop per video and no site-wide crawl. Automated browsing batches of up to 2000 comments are submitted when full, approximately every 30 seconds while collection is active, or when the video ends. Manual browsing uses the same 2000-comment batch limit. Uploaded fields include public author identifiers and nicknames, comment text and identifiers, reply relationships, source video identifiers and limited summaries, keywords, business goals and configured customer needs; the recipient is the Dy Auto server. Collection continues after a batch upload without switching videos. Pending batches persist locally. After page closure, network failure or browser worker restart, a once-per-minute check may resume uploading batches belonging to the authorized account while recognition remains enabled; this does not resume browsing actions or messaging. Stopping an operations task does not disable manual recognition. Unchecking stops new reading and new requests for both browsing modes; already-submitted server requests may finish and existing leads remain. Separately enabled video monitoring follows its settings below. Server-local rules and semantic inference identify leads without external AI calls. Batches, recognition results, evidence and contact status are retained for deduplication, quotas and task resumption; contact support to request deletion. Recognition alone does not post comments or send messages, and detected intent is not consent to contact.

Lead contact messages: Recognition only queues leads. Sending requires the user to configure outgoing text and actively start the task, subject to server-side authorization, claim locks and daily quotas. Message templates and outgoing text remain in the browser and are sent to the selected recipient through Douyin, not to the Dy Auto server; the server receives task identifiers and execution results. Ambiguous delivery is not automatically retried. Sending can be paused and does not automatically resume after restart. Trial users can view leads but may open or exclude only the first three eligible customers; the server retains those trial qualifications. Automatic sending requires paid authorization, checked at start and during execution.

Data handled

We process a phone number, extension/user identifier, public Douyin account identifier, authorization token/status, locally stored settings and task records, and public video/profile information only when needed for features the user starts, manual viewing while lead recognition remains enabled, or monitoring previously enabled and saved by the user. Administrators can view upload and recognition records in the admin console; authorized users can read only leads and comment evidence belonging to their current Douyin account, not other accounts' customer lists. Optional AI features send only the necessary prompt and related text to the provider selected by the user. AI API keys are stored locally in the browser.

Lead workspace: identified leads (customer identifier, nickname, intent score, status, comment evidence, source video identifier) are read from the Dy Auto server. Customer notes, tags, manual follow-up stage, follow-up queue, industry templates, cached source-video titles and jump markers are stored only in the current browser and are not uploaded. These local records cannot be restored from the server and may be lost after switching devices, clearing browser data or uninstalling. The workspace's local JSON export contains only manual annotations, monitoring targets, run records, feature flags and business settings. It excludes server-side leads, the follow-up queue, industry templates and title cache; there is no corresponding workspace backup import, so it is not a complete backup. Clearing local records does not delete server-side leads; contact support for server-side data requests.

Video monitoring (optional, off by default): the user must actively enable it and add an enabled video target. Flags, targets and schedules persist locally; after a browser or extension restart, checks may resume according to saved enabled settings. A once-per-minute alarm checks the flag and target due time. Due targets use a 15/30/60-minute schedule, which may be delayed while other tasks are busy. Each run opens a video tab in a separate temporary window without taking focus, reads incremental public comments, submits them to the same server-side recognition flow above, then closes the extension-created window if its page is still on Douyin. Monitoring settings, deduplication indexes and recent run results stay local; uploaded recognition and lead data are stored on the server. Disabling monitoring prevents new runs but does not clear the once-per-minute alarm or immediately cancel an in-progress run, which may finish reading and uploading. Monitoring is independent of the main operations task: stopping that task does not disable monitoring. Monitoring never reads private messages or sends messages.

Use and sharing

After you actively start private-message automation, the extension reads rendered conversation metadata, automatically scrolls the conversation list, opens one-to-one chats, and matches their loaded text. New-message listening uses the start time and first-read baseline to match new incoming messages only, not earlier history or just the last bubble. History mode processes each conversation's fixed range of loaded incoming text in one pass, including older messages previously answered manually or by other tools, without individual selection. It does not load the entire chat history. Chat text is not uploaded to Dy Auto or saved as chat history. Duplicate prevention retains up to 5000 local hashed message/conversation identifiers and timestamps for private messages (500 for the inactive comment module). Comment and specified-account controls are currently hidden.

AI generation and semantic rule matching send only the necessary prompt, target text and 2–40 recent loaded context messages (default 12; up to 1000 characters each) to your chosen AI provider after your consent. Semantic classification selects a configured rule; it does not invent its reply. Private-message AI provider, model, endpoint and API key are configured independently and stored locally. Keys are not sent to Dy Auto. Private-message automation is off by default and never resumes after restart. Authorization/configuration changes, a hidden message tab, draft conflicts, uncertain delivery or AI timeouts stop the task. Random delays, polling intervals and per-run send caps are configurable; there are no repeated confirmation dialogs, and you can stop at any time.

Data is used only for authorization, user-initiated automation and collection, task continuity, records, optional AI replies, security, and support. The extension retrieves versioned CSS selector JSON after authorization to remain compatible with Douyin page changes. That request does not upload Douyin page content or collection results, and the configuration contains no JavaScript, WASM, expressions, or executable commands. We do not sell personal data or use it for personalized advertising.

Optional image replies read your existing Douyin favorite images only after you enable the feature, then send the selected index or a random item in your configured range. Images are not uploaded to Dy Auto or AI providers. Text and images share the per-run send cap; platform restrictions or uncertain delivery stop the task.

Dy Auto's use of user data adheres to the Chrome Web Store User Data Policy, including the Limited Use requirements. Data is used only for user-selected functionality, not advertising, data sales or unrelated profiling.

Task diagnostics: operation stages, selected control-button actions, outcomes, error codes, limited element diagnostics, extension version, task/video identifiers, counts and times are merged and buffered locally, then sent in batches to the Dy Auto server approximately every 30 seconds or at the batch threshold. Failed uploads are retried after connectivity returns. Records belong to the authorized account, are available to administrators for troubleshooting and product improvement, and are retained for 30 days. Diagnostics exclude comment and private-message text, passwords, verification codes and authorization tokens. Ordinary keystrokes and unrelated page clicks are not collected. Existing detailed operation records remain local.

Control and contact

Users can stop tasks, clear local records and settings, or uninstall the extension. To request access, correction, or deletion of server-side account data, email kan831019@gmail.com.