Acoro Privacy Policy
This Policy applies to the Acoro Mainland China edition operated by 深圳市灵恪科技有限公司, including its corresponding mobile apps, Web service, system sharing and public sharing. The distribution edition determines the regional policy; the interface language selects its Chinese or English translation. Separate feature-specific rules apply to the features they cover.
Please read this Policy carefully before using Acoro, particularly the provisions on sensitive information, third-party services, international processing, public sharing and account deletion. You may choose whether to provide information for optional features. Refusing an optional permission normally affects only the associated feature.
This Policy explains definitions; collection; processing activities; purposes; cookies and local storage; processing by service providers, sharing, transfers and disclosure; third-party services and permissions; storage and security; your rights; children; changes; and contact details.
1. Definitions
1.1 “We”, “us” and “our” refer to 深圳市灵恪科技有限公司, the developer, operator and personal information processor of Acoro.
1.2 “You” or “user” means a natural person who registers for, signs in to, accesses or uses Acoro.
1.3 “Personal information” means recorded information relating to an identified or identifiable individual, excluding anonymized information. “Sensitive personal information” means information whose disclosure or misuse may harm personal dignity or the safety of a person or property. Applicable laws may provide additional definitions and protections.
1.4 “Current materials” means links, screenshots, images, files or text you provide for a particular question. “Saved sources” means content you expressly choose to save for storage, parsing and indexing.
1.5 “Conversation data” includes questions, messages, attachments, AI responses, references, feedback, processing status and conversation history.
1.6 “Publicly shared data” includes conversation titles, questions, responses, source-processing results and access status that you choose to make accessible through a public link.
2. Information we collect
2.1 Account registration, sign-in and linked identities
The mainland China edition supports mainland Chinese phone numbers and email verification codes. We process the number or email you provide, code-delivery and verification records, account identifiers, sign-in times and necessary security logs for authentication, linking or changing identities and security. Phone numbers use +86; Alibaba Cloud SMS processes the number, template parameters, delivery results and rate-limit information to send codes. Code sign-in requires no separate password.
On supported mobile platforms, you may use Apple or Google sign-in or identity linking. We process authorized identifiers, email, name or avatar and credentials to create or link your account. Our service verifies Apple credentials; Google sign-in uses Firebase Authentication. Web offers the phone/email-code methods enabled for its distribution and does not offer third-party sign-in. Matching email text does not automatically merge different sign-in identities.
2.2 Account information and preferences
When you view or edit your account, we process your user ID, display name, avatar, linked identities, email and language preference. An avatar upload processes the image you select or capture; image access may use short-lived signed URLs. We also store language, appearance and notification preferences to restore your settings.
2.3 Current materials, saved sources and parsing
When you paste or upload links, text, screenshots, images or files, we process the submitted content, file name, type and size, source URL, platform, title, author, publication date and other available metadata, processing status and failure reasons. Submitting materials for a question does not automatically save them to your long-term library. Saving a source is a separate, explicit action for supported source links.
After you choose to save a source, we may process public page content, subtitles, OCR text, screenshots, summaries, semantic segments, vector representations, candidate mentions, structured fields, factual claims, references, timestamps and content versions to build your personal library. The information obtainable depends on the source platform and its restrictions.
2.4 Conversations, responses and source verification
When you ask a question, we process its text, current materials, retrieved personal-library content, language, conversation and message identifiers, responses, structured results, references, feedback and execution status to answer, restore history, show sources and handle retries.
Responses may distinguish information from current materials, your library, web search and AI inference. Necessary content may be processed by contracted model, extraction, OCR, embedding or safety services to generate and verify responses.
2.5 Public conversation sharing
When you choose Share for a conversation, we process a public access token, sharing status, displayed content and necessary access logs. The link preserves the conversation at sharing time; later questions are not added automatically. Anyone holding the link can view the displayed questions, responses, source titles, status, summaries or covers without signing in. Information included in your questions or responses can become public even if it is not labeled as profile information. Review the content before sharing.
2.6 System sharing, camera, photos, files and clipboard
When you actively share text, links or images from another app to Acoro, we receive the content selected in the system share sheet. When you use the camera, photo library or file picker, we access content within the permissions you grant and the actions you take.
In supported signed-in, foreground situations, Acoro can read a clipboard link and show a confirmation prompt. The operating system may first request paste permission or show an access notice. Content versions and stable fingerprints help avoid repeated prompts. Detecting a link does not automatically save it without your confirmation.
2.7 Local caching, offline recovery and realtime events
To support startup, offline use and connection recovery, the app or browser stores sign-in credentials, preferences, cached resource snapshots, pending commands, idempotency keys, creation times, retry states and realtime cursors. Sensitive credentials use secure storage on supported platforms; Web storage is subject to browser limitations.
2.8 Device information, logs and security
For stability, security and troubleshooting, we may process user ID, platform, operating-system or browser information, app version, page, request path, status code, elapsed time, error type, request identifier, network state, IP address, access time and anomalous activity records. Client logs mask potentially sensitive text and do not record request or response bodies, authorization headers, email addresses or public sharing tokens.
2.9 Support, complaints and rights requests
When you contact us, report a problem or objectionable content, or exercise your rights, we process contact details, communications, descriptions, relevant screenshots, necessary account or device details and handling records.
2.10 Push notifications and unread counts
When notifications are enabled on a supported platform, we process account-linked push tokens, push provider, platform, language, app version and notification settings to deliver source-processing results, synchronize unread counts and open the relevant conversation. iOS uses Apple Push Notification service (APNs); Android uses Firebase Cloud Messaging (FCM), which also uses a Firebase installation identifier.
Notifications may include source titles, processing status, conversation or source identifiers and unread counts and pass through the push provider. Your device may show them on the lock screen; manage preview settings as needed. You can turn off reminders in Settings — Notifications or in system settings. The Web version currently does not offer these system push notifications.
2.11 Topic suggestions and interaction feedback
To suggest topics related to your materials, we process saved content or summaries, recent conversation topics, interests, language and suggestion impressions or clicks. Records may include suggestion and source identifiers, position and time. We use them to generate and adjust suggestions and evaluate their quality.
You can type your own question or refresh suggestions. Neither action disables personalized processing. Contact us using the details in this Policy if you have questions or wish to request an explanation or restriction of processing.
2.12 Maps and places: we process place names, addresses, coordinates, viewport and source information that you search for, select, confirm or save to display places and correct markers. Manual selection is not access to your device’s current location; the current map-selection flow does not require device location. Any future feature requiring it will explain the purpose and request permission before access.
3. Main processing activities
| Activity | Information potentially processed | Purpose |
|---|---|---|
| Account and profile | Phone number, email, verification records, third-party identifiers, name, avatar, language and user ID | Sign-in, verification and account management |
| Current materials | Links, text, screenshots, images, files and metadata | Answer a question and generate previews |
| Saved sources | Original content, text, subtitles, OCR, summaries, segments, vectors, claims and evidence | Personal-library retrieval and verification |
| Conversations | Questions, attachments, messages, AI output, references, feedback and status | Responses, history and sources |
| Public sharing | Conversation snapshot, source-processing results, public token and access status | Public snapshots and link validity |
| Local and realtime | Cache, offline commands, idempotency keys, cursors and preferences | Recovery, deduplication and synchronization |
| Logs and security | User ID, platform, version, page, errors, request IDs, IP and access time | Troubleshooting, audit and abuse prevention |
| Notifications | Push and installation identifiers, platform, language, version, content and unread count | Result notifications, badges and navigation |
| Suggestions | Saved summaries, recent topics, interests, impressions and clicks | Topic generation and quality evaluation |
| Maps and places | Search terms, place names, addresses, selected coordinates, viewport and source links | Rendering, search, geocoding and place correction |
4. How we use personal information
4.1 To provide core services: registration, sign-in, identity linking, receiving links and files, parsing, personal libraries, questions and answers, source verification, feedback, public sharing, topic suggestions, notifications, synchronization and offline recovery.
4.2 To protect security and stability: identity verification, session management, detecting abnormal access, preventing fraud and abuse, auditing, troubleshooting, recovery and complaint handling.
4.3 To improve the product: analyzing minimized or de-identified usage, error and performance data to improve retrieval, parsing, responses and interaction. Unless you separately authorize it or law provides otherwise, we will not use private conversations, saved source text, uploads or sensitive personal information to train general-purpose models for an unspecified audience.
4.4 To meet legal obligations, including lawful requests from competent authorities and applicable obligations concerning cybersecurity, data protection, generative AI, children and dispute resolution.
4.5 To communicate verification codes, account-security notices, policy changes, service status, support replies and information directly related to your use of Acoro.
4.6 If we intend to use information for a new purpose not described here and not directly or reasonably related to the original purpose, we will provide notice and obtain consent where required.
5. Cookies, clipboard and similar technologies
5.1 The website may use cookies, Local Storage, IndexedDB or similar technologies for sessions, language, cached resources, offline commands and security. Mobile platforms may use secure storage, an app database, SharedPreferences or UserDefaults for equivalent purposes.
5.2 Disabling or clearing these technologies may sign you out, remove preferences or cached data, prevent recovery of pending commands or make certain features unavailable.
5.3 Clipboard-link detection is limited to the supported signed-in foreground situations and is subject to operating-system permissions and notices. Processed versions or fingerprints prevent duplicate prompts; detection does not automatically create a saved source.
6. Service providers, sharing, transfers and public disclosure
6.1 Processing by service providers
We may engage service providers for authentication, verification messages, cloud computing, databases, object storage, parsing, OCR, embeddings, AI generation, web search, notifications, logs and security. We require processing within necessary limits and under our instructions through contracts, access controls, minimized transmission, security assessment and oversight.
6.2 Sharing
We provide information to other independent processors only where there is a valid legal basis, such as your choice of third-party sign-in, authorized disclosure or a legal obligation. We provide recipient details, purposes, methods and data categories and obtain separate consent where required. Service-provider processing, your public sharing and transfers in corporate transactions are governed by the corresponding provisions below.
We do not sell personal information to unrelated third parties. When a third party independently provides services to you, its own rules apply. Read those rules before authorizing access or following a third-party link.
6.3 Corporate transfers
If a merger, division, acquisition, asset transfer, insolvency or similar transaction involves personal information, we will provide legally required notice of the recipient and contact details and require continued protection under this Policy. Changes to the original purposes or methods require renewed consent where applicable.
6.4 Public disclosure
Except for your active public sharing, separate consent or legal requirements, we do not publicly disclose personal information. Anyone with a share link may access, forward, copy or capture the content. Conversation share links currently have no automatic expiry. Renaming a conversation, deleting shared messages or deleting the conversation invalidates the current link. Invalidation cannot erase copies previously saved by visitors.
7. Third-party services and device permissions
The following list describes the principal external services used by the current client. Availability and processing may vary by version, platform or region. Material changes will be reflected in this Policy or an in-app notice.
| Service | Information potentially processed | Purpose | Provider information |
|---|---|---|---|
| Sign in with Apple (Apple) | Apple identifier, email, name, identity token and authorization state, subject to your authorization and Apple’s response | Mobile sign-in, linking and reauthentication before deletion | https://www.apple.com/legal/privacy/ |
| Google Sign-In (Google) | Google identifier, email, name, avatar, identity token and authorization state, subject to your authorization and Google’s response | Mobile sign-in, linking and reauthentication before deletion | https://policies.google.com/privacy |
| Firebase Authentication (Google) | Identity tokens, email, user agent, IP and authentication information | Google sign-in verification and account security | https://firebase.google.com/support/privacy |
| Alibaba Cloud Simple Log Service (SLS) | User ID, platform, version, page, redacted errors, request IDs and necessary network logs | Diagnostics, audit and stability | https://help.aliyun.com/zh/document_detail/2705225.html |
| Apple Push Notification service (APNs) | Push token, notification title and body, conversation/source IDs, unread count and technical information | iOS result notifications and badges | https://www.apple.com/legal/privacy/ |
| Firebase Cloud Messaging (Google) | Installation ID, push token, notification content, conversation/source IDs and unread count | Android result notifications and badges | https://firebase.google.com/support/privacy |
| Alibaba Cloud Object Storage Service (OSS) | Uploaded avatars, images and files, parsed media and access metadata | File storage and access-controlled retrieval | https://help.aliyun.com/zh/document_detail/2705225.html |
| Alibaba Cloud SMS | Phone number, verification template parameters, delivery status and rate-limit information | Deliver verification codes and verify phone ownership | https://help.aliyun.com/zh/document_detail/2705225.html |
| AMap Open Platform (AMap) | Map viewport, search terms, confirmed place coordinates, network address and device/technical information needed by the SDK, depending on the feature and provider rules | Mainland map rendering, place search, geocoding and manual selection; a separate map authorization is presented before SDK use | https://lbs.amap.com/pages/privacy/ |
Acoro may also use server-side email, extraction, OCR, embedding, model, web-search and safety services. Necessary questions, material excerpts, images, search terms or related metadata may be sent to contracted providers. We restrict purposes and transmission scope; independent disclosure or international processing is subject to applicable notice and authorization requirements.
| Permission or capability | Use | Choice and effect |
|---|---|---|
| Camera | Capture a question attachment or avatar | Optional; other input methods remain available |
| Photos and media | Select images or screenshots | Optional; access is limited to selections or granted scope |
| File picker | Select supported documents | Optional; system picker controls access |
| Clipboard | Detect foreground links and request confirmation | Subject to system controls; manual input remains available |
| System sharing | Receive selected text, links or images from another app | Only when you actively share |
| Network | Authentication, sync, parsing, AI, sharing and update checks | Required for online features; limited cached/offline functions remain |
| Package installation (Android direct-install testing only) | Download a test update from AppHost and request system installation | Only direct-install test builds use this. Google Play/store builds do not request APK-install permission and open the store for updates |
| Notifications (iOS and Android) | Result notifications and unread badges | Optional; manage in app or system settings |
8. Storage and protection
8.1 Storage locations and international processing
As a general rule, personal information collected and generated in mainland China is stored there. If you choose Apple or Google sign-in or enable notifications on a supported platform, identity credentials, push identifiers, notification content and technical information may be processed outside mainland China by Apple, Google or Firebase. Firebase states that Authentication operates from US data centers. Where required, we provide international recipient and contact details, purposes, methods, data categories and rights channels and complete applicable separate consent, impact assessments and other procedures.
8.2 Retention
| Information | Retention or deletion rule |
|---|---|
| Account and identity | Until account deletion or service termination, subject to legal requirements. External identity providers apply their deletion or revocation processes. |
| Current materials and temporary attachments | For the time needed to complete the request, recover failures, provide security and reasonable caching; expressly saved sources follow the saved-source rules. |
| Saved sources, conversations and feedback | Until deletion, account closure or service termination; information needed for disputes, audits or legal duties is restricted for the necessary period. |
| Public sharing | Until invalidation, content deletion, account deletion or service termination. Links have no automatic expiry; renaming a conversation or deleting shared messages or the conversation invalidates the link. |
| Client and service logs | Normally no more than one year, unless law, security audit or dispute handling requires otherwise. |
| Local and offline data | Stored on your device or browser; removed according to account switching, sign-out, deletion, in-app clearing, uninstall and system rules. Sign-out does not immediately remove every preference or temporary file. Use Settings — Storage to clear applicable cache. |
| Push and suggestion records | For the time needed for the feature, synchronization and security. Invalid push tokens are disabled; account-related data follows deletion rules. Providers manage their own installation identifiers. |
If deletion cannot immediately reach backup systems, we isolate and restrict access to the affected information and delete or anonymize it in the backup rotation cycle.
8.3 Security
We use measures such as encryption in transit, access control, authentication, separation of permissions, audit logs, masking of sensitive information, idempotency and replay protection, backups, confidentiality obligations and vendor management. No internet environment is entirely secure. We will respond to security incidents and report to authorities and notify you as required by law.
9. Your rights
9.1 Through available features you may access, copy, correct or supplement account information and language preferences; view, rename or delete saved sources and conversations; provide response feedback; and invalidate share links by renaming a conversation or deleting shared messages or the conversation.
9.2 You may request account deletion in Settings — Account and security — Delete Account. Once accepted, Acoro revokes sessions and public sharing and asynchronously deletes account data and linked identities. Depending on linked identities, mobile apps also attempt to revoke Apple authorization, delete the Firebase authentication user and disconnect Google authorization. A failure in external cleanup does not reverse an accepted Acoro deletion request.
9.3 You may withdraw camera, photo, file, clipboard and notification permissions in operating-system or browser settings; manage reminders in Settings — Notifications; clear cache in Settings — Storage; or clear app data using system controls. Withdrawal does not affect the lawfulness of earlier consent-based processing but may make the relevant feature unavailable.
9.4 Contact us to request access, copying, correction, deletion, restriction, explanations or to make a complaint. We may verify your identity to protect security and will respond within applicable legal deadlines.
9.5 Where permitted by law, we may decline requests that are unjustifiably repetitive or excessive, require disproportionate technical measures, harm others’ rights, involve trade secrets or meet another lawful ground for refusal, explaining our reasons.
10. Children and minors
10.1 Acoro is primarily intended for adults. Minors should use it with a guardian’s consent and guidance. Children under 14 should generally not independently register or provide personal information.
10.2 If we discover that children’s information was collected without verifiable guardian consent where required, we will promptly delete it or otherwise act as required by law. Guardians may contact us to request access, correction or deletion.
10.3 Guardians should carefully assess content, sources, risks and visibility when minors use AI responses or public sharing.
11. Policy changes
11.1 We may update this Policy to reflect laws, regulatory requirements, features or changes in processing purposes or methods. We will not reduce your rights under this Policy without following applicable law.
11.2 For material changes to purposes, data categories, recipients, international transfers, sharing, rights channels or contact details, we will provide prominent notice through the app, email or another appropriate method and obtain renewed consent where required.
12. Contact us
12.1 For questions, suggestions, rights requests or complaints, email service@lincotalk.com, call 400-960-8200 (mainland China service number), or write to 7A, Konka R&D Building, 28 Keji South 12th Road, Nanshan District, Shenzhen, China.
12.2 We respond within applicable legal deadlines after receiving your request and completing necessary identity verification. If you are dissatisfied or believe your rights have been harmed, you may complain to a competent authority or bring proceedings before a court with jurisdiction as permitted by law.
The Chinese and English versions describe the same regional policy and revision. Changing translation does not change the service region, processing practices or consent. Contact us about discrepancies; they do not reduce rights granted by applicable law.