Privacy and data handling

Updated: 16 November 2026 (Asia/Taipei). Applies to docsaid.org and its beta preview.

Operator and scope

DOCSAID operates this website. Contact [email protected] about account data, uploaded images, API metadata, public comments or inquiries. This policy describes the current service and its data lifecycle. Software, model weights and datasets have separate licenses linked on the licensing page.

Images, accounts and usage

Uploaded images are used for the requested recognition. After processing, the server does not retain images or recognition results, and uploads are not used for training. Member records include account identifiers, name/email, key-management information without key plaintext, and request metadata such as model/version, file digest, time, status and duration. Guest cookies and network identifiers support quotas and abuse prevention; guest trial records are not linked to member accounts. Submitted comments and inquiries are stored.

Services involved

We use external services for sign-in verification, website delivery and protection, email notifications and website analytics. Each receives data needed for its role: sign-in information, website traffic, submitted comment/inquiry content or public-page measurements. Providers may process data across borders. Before using the service, you may contact [email protected] for details about the providers handling your data.

Retention periods

Routine cleanup removes guest request metadata after 7 days, inquiries after 180 days, inquiry network identifiers after 24 hours and discarded comment drafts after 90 days. Active drafts, member request metadata, key-management records, account-closure records and public comments currently have no automatic expiry; removal can be requested. Reading-statistics identifiers are kept for 2–7 days and abuse-review records for 90 days. Backups are retained for 14 days; deleted data ages out of older copies within that cycle. Operational logs rotate by size, without a fixed retention period. Email copies and provider records need separate handling as part of deletion requests.

Closing your account

In the account menu, open Manage account and choose Delete account. After account closure is processed, we clear the profile name/email and revoke API keys; work already accepted can finish. Published comments remain visible. Private drafts, member request and key-management records, and account-closure records follow the retention policy above. Before closing, delete the comments/drafts you want removed or request assistance by email. Specify any other stored data or provider records you want included in your deletion request.

Data kept in your browser

Login and guest-limit cookies support authentication and quotas. Language and analytics choices are stored in this browser; list positions and non-secret operation identifiers may use tab storage. Demo images/results and unsent inquiry drafts stay in tab memory while navigating and are cleared on reload, tab closure or account change. Use the clear/download/copy controls before leaving. Account-synced comment drafts are stored on the server and follow the separate draft retention rules.

Website analytics

Website analytics is enabled by default on public pages. It measures basic browser, device and engagement information. Private account pages, form input, keys, images, recognition results and URL query parameters are excluded, and advertising features are disabled. You can turn analytics off in the footer to stop collection and clear this site’s analytics cookies. For data already sent, contact us with a data request. Your preference remains until changed or browser storage is cleared.

Data questions and requests

Email [email protected] to request access, correction or deletion, withdraw a choice, or ask about processing and retention. Include the account email or receipt/request ID needed to locate the record; never send an API key or a full identity-document image. We may verify ownership before acting and explain the scope, retained records and provider follow-up.

[email protected] · Contact