Ding Annotator uses your account and annotation-task data to run workflows you start, create transcripts, save accepted work, and diagnose reports you choose to send. We do not sell personal data or use it for advertising.
01
Scope and operator
This Privacy Policy applies to the Ding Annotator Chrome extension, backend API, and associated administration tools (collectively, the "Service"). In this policy, "we," "us," and "Ding Annotator" refer to the operator of the Service available at annotator.remotten.com.
Ding Annotator is intended for authorized annotation workers and administrators. Your organization may provide additional notices or instructions governing the annotation tasks assigned to you.
02
Information we process
Account and authentication information
We process your username and password when you sign in. Passwords are used for authentication and stored by the backend only as password hashes. The extension stores session information, including an authentication token and request-signing information, in Chrome storage so your session can continue when the side panel or service worker restarts.
Annotation task content
Depending on the workflow, we process source audio, audio URLs, current annotation text, task metadata, generated transcript text, edits, and the final text you accept. Audio may be copied through the backend for processing and uploaded to object storage.
Operational and diagnostic information
We process your username, request timestamps, API routes, response status, workflow state, completed-task count, model token usage, estimated model costs, and error information. The extension may display local workflow logs. Those detailed client logs are sent to the backend only when you open the Report dialog and choose to submit a report.
Active-tab context
When you run a workflow, the extension identifies the active tab so it can operate on the intended DingTalk annotation task. Tab URL and title information may be included in diagnostic context. Ding Annotator does not use browsing activity for advertising or unrelated profiling.
03
How we use information
- Authenticate users and protect API requests.
- Retrieve and run the workflow selected by the user.
- Create true-verbatim transcripts from task audio.
- Compare generated text with the current annotation.
- Store accepted annotation results and count completed tasks.
- Enforce request limits and protect the Service from abuse.
- Investigate failures using reports deliberately submitted by users.
- Maintain, secure, and improve the reliability of the Service.
We use Chrome extension data only to provide and improve the extension's single purpose. Our use of information received from Chrome APIs complies with the Chrome Web Store User Data Policy, including its Limited Use requirements.
04
Service providers and data locations
We use service providers to perform specific parts of the Service:
These providers process information on our behalf under their applicable terms and security controls. Processing may occur in countries other than the country where you work.
06
Storage and retention
We retain account, annotation, request, report, and usage records for as long as reasonably necessary to operate the annotation program, maintain security and audit history, resolve disputes, and meet legal obligations. Temporary audio copies may be removed after processing, while object-storage and annotation records may remain according to the annotation program's retention settings.
When information is deleted, residual copies may remain for a limited period in backups or security records. We may retain de-identified or aggregated information that cannot reasonably be linked to an individual.
07
Your choices and controls
- A workflow runs only after you select it and click Run.
- You can click Stop to end the active workflow.
- You can review and edit proposed transcript text before accepting it.
- A task counts as completed only after you click Accept.
- Client logs are submitted only when you choose Send Report.
- You can remove local extension data by uninstalling the extension.
You may request access, correction, or deletion of account-related information by contacting us. Some information may need to be retained where required for security, contractual, or legal reasons.
08
Security
We use reasonable administrative and technical safeguards, including HTTPS transport, authenticated sessions, password hashing, time-limited request signatures, access controls, and request-rate limits. No storage or transmission method is completely secure, so we cannot guarantee absolute security.
09
Children's privacy
Ding Annotator is a workplace annotation tool and is not directed to children. We do not knowingly collect personal information from children through the Service.
10
Policy changes
We may update this policy to reflect changes to the Service, legal requirements, or our data practices. We will publish the updated policy on this page and revise the effective date above.
11
Contact us
For privacy questions or requests, contact the Ding Annotator team:
[email protected]