TonoCard Privacy Policy

Last updated: October 15, 2026 | Effective date: September 12, 2026

Introduction

TonoCard is an integrated hardware and software product for intelligent call answering provided by Longshu (Shenzhen) Artificial Intelligence Co., Ltd. It comprises TonoCard hardware and its companion application (the “App”) and provides automatic call answering, speech understanding, intent recognition, multi-turn conversations, and call summaries. This Policy applies to the TonoCard Overseas Edition App distributed outside mainland China and its companion hardware services. The Overseas Edition uses OpenAI GPT model services for AI calls. The applicable edition is determined by the App distribution package you use, not by the language selected in the interface.

Longshu (Shenzhen) Artificial Intelligence Co., Ltd. (“we,” “us,” or “Longshu AI”) is responsible for the processing described in this Policy and is the data controller where that term is used under applicable law. Our registered address is Room B316, East Building, Lenovo Building, No. 016 Gaoxin South 1st Road, Gaoxinqu Community, Yuehai Subdistrict, Nanshan District, Shenzhen, China. See Section 9 for contact details.

This Policy explains how we collect, use, store, share, and protect your personal information and the rights you have. You can also view the “List of Personal Information Collected” and the “List of Personal Information Shared with Third Parties” under “Settings → About TonoCard” in the App. Key points include:

We explain the information collected for each feature, why and how it is processed, and the effects of declining to provide it. Call records are deleted from cloud systems we manage after successful client retrieval and are then retained only locally on the client. See Sections 1.4 and 2.2.

Optional features such as voice cloning and contact lookup require separate authorization. Feedback audio is not uploaded by default; it is uploaded only after you actively select it and submit the feedback. Declining these optional activities does not affect call answering with the default voice or other features that do not depend on the relevant information.

We do not sell your personal information. To provide AI call answering, speech synthesis, push notifications, and payments, we may provide information to the entrusted processors listed in this Policy to the minimum extent necessary and enter into data processing agreements with them. Before providing sensitive personal information, such as voiceprints, to a third party, we obtain your separate consent unless laws or regulations provide otherwise.

Other than the service processing described in this Policy, we do not proactively obtain additional personal information about you from other third parties. If we need to add a new source, we will explain the source, information types, and purposes and meet applicable notice and consent requirements. Information about other call participants is addressed in Section 1.18.

You can access, copy, correct, or delete your personal information, withdraw consent, manage permissions, and submit complaints or reports through the channels described in this Policy. The product has no separate account system and identifies devices by hardware ID, so it does not offer “account cancellation.” You can stop using the relevant features or withdraw consent and manage or delete data under Section 5. Retention and deletion of information already collected are governed by Section 2.2; uninstalling the App does not itself delete information still processed in our cloud under this Policy.

Sensitive permissions, such as microphone, contacts, camera, location, and notification access, are not enabled by default. They are used only after you expressly consent and within the scope of that consent. Obtaining a permission does not mean that we continuously collect the corresponding information; we process it only as necessary while you use the relevant feature.

For processing based on consent, we begin after you tap “Agree and Continue” or provide the relevant separate consent. See Section 1.16 for other processing grounds. We do not expand your authorization by treating continued use as consent. Policy updates are addressed in Section 6.

1. Information We Collect and Use

When you use TonoCard, we collect and use information that you voluntarily provide or that is generated through your use of the services as follows:

1.1 Device Binding and Activation

The product operates without user accounts and does not require you to register a phone number or email address. When you bind and activate TonoCard hardware, we collect and use the device model, operating system and version, App version, firmware version, Bluetooth address and connection status, and identifiers necessary to identify the device (such as Android ID or OAID on Android, IDFV on iOS, OAID on HarmonyOS, and the hardware serial number, depending on your system). This information supports device identification, activation, and service continuity. It is used to identify your bound device and maintain connectivity and security, and is not used for advertising profiling. If you do not provide this information, you may be unable to complete binding and use the product.

1.2 Service Operation and Security

When you use the App, we collect the device model, operating system, App version, crash logs, diagnostic logs, and operation and service logs (such as connection failures, fault codes, and other technical information) to maintain normal service operation, troubleshoot problems, improve your experience, and protect device and service security. These logs do not contain call audio, call records, summaries, transcripts, or call context. Diagnostic logs are used only for troubleshooting. Logs associated with feedback are periodically cleaned up and deleted after the issue is closed under Sections 1.14 and 2.2. Other diagnostic logs are deleted or anonymized when their troubleshooting purpose is fulfilled. We do not combine statistical data used for analysis with information that can identify you for advertising purposes.

1.3 AI Automatic Call Answering and Conversations

When you use AI automatic call answering, real-time speech understanding, intent recognition, or multi-turn voice conversations, call audio is transmitted to cloud systems we manage and processed using OpenAI GPT model services as necessary to provide these features. Model processing of call audio is used only for real-time inference for the current call. Sections 1.4 and 2.2 explain how call records are temporarily held for delivery, retrieved by the client, and deleted from our cloud. Call audio and the resulting call records may contain sensitive personal information. If you deny microphone permission or do not consent to call audio processing, you will be unable to use AI call answering. This does not affect your use of the phone’s system calling functions or other features.

The Overseas Edition uses OpenAI GPT model services, including GPT Live for real-time speech understanding, conversation generation, and spoken responses. We transmit only the call audio, conversation text, and call context necessary for these features to OpenAI. See Section 4.1.5 for processing purposes and information types, and Section 2.1 for processing locations and international transfers.

1.4 Call Summaries and Call History

When you use call summaries, call history, outcome reviews, or context continuity for subsequent calls, we temporarily process call audio or relevant text supplied by the client as necessary to generate the requested summaries or other inference results. If a subsequent call requires prior context, we use only the necessary historical information supplied by the client for that inference. We do not create a cloud history from that information. Temporary conversation text and context that are not part of a record awaiting retrieval are deleted after inference is complete. We do not write these records to your phone’s system call history. If you do not use the summary or history features, or do not provide the relevant information, you may be unable to view summaries or continue prior context, but basic call connectivity is unaffected.

Call records include call audio, call information such as numbers, times, and titles, and summaries and transcripts generated through inference. Our cloud temporarily processes and retains the necessary data only to complete the current call processing and deliver the records to the client. After the client successfully retrieves the corresponding records, we delete the associated data and copies from our cloud. We do not retain cloud call history, backups, or records for cross-device synchronization. Retrieved records are stored only locally on the client, where you can view, play back, and delete them. Cloud deletion does not affect data already saved on the client. Model processing of call audio is used only for real-time inference for the current call. These rules govern references elsewhere in this Policy to the storage, synchronization, and access of call records. Third-party model services process call data as described in Section 4.1. Audio you actively select and submit with feedback is a separate feedback attachment, subject to Sections 1.14 and 2.2.

1.5 Call Answering Rules and Preferences

When you configure automatic answering rules, handling of specific incoming calls, language, voice, or other preferences, these settings are stored locally in the App and may be synchronized to the hardware and to servers as necessary for consistency across devices. You can change them in Settings at any time. If you do not provide this information, the corresponding personalized rules cannot take effect, but default call answering capabilities, if available, are unaffected.

1.6 Personalized Voice Cloning

Voice cloning is optional. If you choose a personalized voice for AI responses, we obtain your separate, explicit consent before relaying a short audio sample you record through our servers to a third-party voice-cloning provider. Our cloud temporarily relays the sample and does not store cloning audio samples, voiceprint features, or cloned voice models. We do not attach your name, phone number, device identity information, or other user identity details to the cloning sample. The audio and derived features may constitute biometric or other sensitive personal information under applicable law, and we protect them as sensitive information. Omitting identity details does not make the audio anonymous.

The provider uses the sample to create a personalized voice and provide speech synthesis. Sections 2.2 and 4.1.1 describe necessary retention, deletion, and disclosure before submission. The cloned voice is used only for your TonoCard device, not for other users or advertising profiling unrelated to this product. Record only your own voice; do not upload another person’s voice for cloning. You may separately request deletion of the cloned model under Section 5. Declining cloning does not affect call answering with the default voice or other features.

1.7 Contacts

When you separately authorize and use contact lookup or dialing by name on the desktop, we request contacts permission and read only the contact information necessary for that feature. Contact information may include sensitive details about you or other people and is processed only as needed for the feature, as explained in the App. Declining authorization affects only lookup or dialing by name and does not affect the main call answering feature.

1.8 Binding by QR Code

When you scan a QR code on the desktop to complete binding, we request camera permission and recognize the QR code locally. We do not read or upload your photo library. Denying camera permission only prevents binding by QR code; you can still connect through other guided methods, if available.

1.9 Bluetooth Connectivity and Location

When you search for, connect to, or maintain communication with TonoCard hardware, we collect the Bluetooth address, connection status, and firmware version. On Android 11 and earlier, scanning for nearby Bluetooth devices may require location permission. We request it only to meet the system requirements for Bluetooth scanning, not for map navigation or movement profiling, and do not store movement histories. Denying location permission may prevent older Android versions from discovering the device, but does not affect use of a device that is already connected, subject to system restrictions.

1.10 Phone Status

When you use relevant features, we may read phone status to detect whether the phone is engaged in a call and avoid conflicts with device firmware updates or call answering. This information is processed in real time and is not used to create movement or call-status profiles. Denying this permission may disable some conflict-avoidance capabilities, but does not affect your use of the phone’s system calling functions.

1.11 Notifications and Notification Access

We may request notification or overlay permission to display call answering status when a call arrives. On Android systems, we may, with your authorization, monitor incoming-call notifications to identify and answer incoming calls, processing only content relevant to call identification. Denying these permissions may prevent timely display of call answering status on the lock screen or in the background, or prevent incoming-call identification on the relevant system, but does not affect your use of the phone’s system calling functions.

1.12 Push Notifications

To deliver urgent-call and task notifications, we may use push notification services (Umeng Push on Android, Huawei Push on HarmonyOS, and Apple Push on iOS) and collect push tokens and device identifiers necessary for delivery. Push notifications are transactional and are not recommendation notifications based on device profiling. Push SDKs that collect information are not initialized before you consent to this Policy. You can disable notifications in your system notification settings.

1.13 Subscriptions and Payments

When you purchase or renew services related to the product, the Overseas Edition Android App uses Google Play billing, and the iOS App uses Apple in-app purchases. We or the payment service provider process the order and device information necessary to complete the transaction. Refusing to provide information necessary for payment only prevents the relevant purchase and does not affect use during an already activated service period, where applicable.

1.14 Customer Support and Feedback

When you contact us or submit feedback in the App, we may need device information, the App version, a description of the problem, and diagnostic logs you voluntarily attach to verify your association with the device and address your request. Diagnostic logs contain no call data. Audio uploads for feedback are off by default, and call recordings are never attached or uploaded automatically. Our cloud receives an audio attachment only after you actively select it and submit the feedback. Microphone permission or agreement to this Policy does not authorize feedback audio uploads. We use the audio only to investigate and resolve the issue you report. It is a separate feedback attachment, so the call-record deletion rule triggered by client retrieval does not apply to it. After the issue is closed, we periodically clean up and delete its associated feedback data, including the issue description, diagnostic logs, support communications, and any audio attachments you voluntarily uploaded, as described in Section 2.2. You can submit feedback and use other features without uploading audio, although this may limit our ability to investigate an audio-related issue.

1.15 System Permissions

To provide the features described in this Policy, we request each permission separately when you use the relevant feature and explain its purpose at that time. We do not request multiple permissions that can collect personal information all at once on first launch. Denying non-essential permissions does not cause the App to exit. We do not repeatedly display prompts after you decline; where necessary, we guide you to system settings. You can also review and manage granted permissions in system settings.

1.16 Grounds for Processing Personal Information

Processing that requires consent begins only after the relevant consent is obtained, including call audio processing, voice cloning, contact access, and voluntary feedback audio uploads. Where voice cloning involves specially protected data, we obtain the required separate, explicit consent. A device permission does not replace any other consent required by law.

To the extent permitted by applicable law, processing of non-optional information necessary for device binding and activation, providing services you request, and handling payments may be based on entering into or performing our contract with you. Retaining transaction records required by law and responding to lawful authority requests may be based on legal obligations. In emergencies involving life or health, we process information only where legally permitted and necessary.

These grounds do not expand the information, purposes, or retention periods described in this Policy. General troubleshooting or service operation does not bypass legally required consent. Where additional legal conditions apply to particular processing, those conditions must be met first.

1.17 Use Beyond the Authorized Scope

If our use of your personal information goes beyond the purposes you authorized and the scope directly or reasonably related to those purposes, we will notify you again and obtain your express consent before such use.

1.18 Information About Call Participants and Other People

Call audio, text, numbers, and context you provide may concern other call participants. The purposes, recipients, and retention rules in Sections 1.3, 1.4, 2, and 4 also apply to that information. When using recording, transcription, AI call answering, or attachments, you must give participants any notices and obtain any permissions required by applicable law, and avoid providing unrelated information about others. This does not reduce our own duties to provide notice, process information lawfully, and protect privacy rights. Other participants may submit privacy requests under Section 9.

2. Information Storage

2.1 Processing Locations and International Transfers

We are a company established in China. The Overseas Edition uses OpenAI GPT model services, and we and the providers described in Section 4 may process personal information outside your country or region. Provider identities and processing locations are disclosed through the App’s third-party information list or feature notices. The voice-cloning provider and its processing locations are disclosed before you submit a sample under Section 4.1.1. Processing location and retention duration are separate matters; Section 2.2 describes retention and deletion for each data category.

Laws in a destination country may differ from those where you live. Before a restricted international transfer, we will meet applicable requirements and implement the required safeguards, such as an applicable adequacy decision or approved standard contractual clauses. For UK transfers, a recognized UK transfer agreement or addendum will be used where applicable. Where separate consent is required, we obtain it before the transfer. Contact us under Section 9 for information about relevant recipients, locations, and safeguards, or to obtain information about or a copy of the safeguards where entitled by law.

International processing does not change our cloud call-record deletion rules in Sections 1.4 and 2.2. Necessary processing and retention by third-party services are addressed separately in Section 4.1.

2.2 Retention Periods

During normal call processing, our cloud temporarily retains necessary data only for the current processing and delivery to the client. After successful retrieval, our cloud automatically deletes the corresponding call data and copies without a separate deletion request. Retrieved records remain only locally on the client. This automatic deletion is not subject to the general request-handling period and is not extended because a device remains bound. Feedback and voluntarily uploaded audio attachments follow the category-specific rules below.

For other personal information, we retain it only as long as necessary for its purpose and for periods required by law. After a deletion request under Section 5 or 9 and any necessary verification, we delete or anonymize it within fifteen (15) working days, or any shorter period required by applicable law, unless retention is legally required. If a statutory retention period has not ended or a technical impediment legally permits delayed deletion, we limit processing to necessary storage and security protection and delete it when the impediment is removed.

Device binding information and push tokens: retained while the device remains bound; deleted or anonymized within fifteen (15) working days after unbinding or upon your deletion request.

Client-side call data: call records retrieved by the client, including call audio, numbers, times, titles, summaries, transcripts, and local call context, are retained only locally on the client until the day you delete them, or until you go to “Settings → Reset Device,” select “Delete Data,” and confirm the reset. Cloud deletion after client retrieval does not affect this local data. See Section 1.5 for the handling of preferences.

Call audio and call information awaiting retrieval from our cloud: temporarily retained only for the current processing and delivery to the client. After the client successfully retrieves the corresponding records, our cloud deletes the associated audio, call information such as numbers and times, and copies. Model processing of call audio is used only for real-time inference for the current call. Temporary conversation text and context that are not part of a record awaiting retrieval are deleted after inference is complete.

Call summaries, transcripts, and other inference results generated in our cloud: temporarily retained only for delivery to the client. After the client successfully retrieves the corresponding records, our cloud deletes the associated results and copies and retains no cloud call history, backups, or copies for cross-device synchronization.

Voice-cloning samples, voiceprint features, and models: Our cloud only temporarily relays samples and does not store samples, voiceprint features, or models, or attach user identity details to cloning samples. The third-party cloning provider may process and retain necessary samples and models for the period needed to provide the feature; its specific arrangements are disclosed before submission. After you separately delete them or request deletion, we notify that provider to delete them within the period above. Retention by the cloning provider is distinct from storage in cloud systems we manage.

Diagnostic logs and feedback-related data: diagnostic logs are not used for advertising profiling. Logs not associated with feedback are deleted or anonymized when their troubleshooting purpose is fulfilled. Our cloud receives feedback audio only after you actively choose to upload it and submit the feedback. The audio is handled as a separate feedback attachment and used only to investigate and resolve the issue you report. Once a reported issue is closed, we periodically clean up and delete the feedback data associated with it, including the issue description, diagnostic logs, customer support communications, and audio attachments you voluntarily uploaded. You may also request deletion under Section 9.

Other customer support communications and payment orders: communications associated with feedback are cleaned up under the preceding rule. Other customer support communications are retained only as necessary to address the relevant request. Payment orders are retained for the periods necessary to fulfill statutory obligations relating to finance, taxation, anti-money laundering, and similar matters.

If our products or services cease operating, we will notify you through reasonable means such as push notifications or announcements and delete or anonymize your personal information within a reasonable period. In this Policy, “anonymization” means technical processing that makes it impossible to identify the individual concerned and impossible to restore the processed information to its original form. Anonymized information is not personal information.

3. Information Security

We work to protect your information against loss, misuse, alteration, unauthorized access, or disclosure.

We use measures such as encrypted transmission, access controls, and de-identification to provide a reasonable level of security for personal information. We have dedicated management systems, procedures, and organizational arrangements, strictly limit the personnel who can access information, require confidentiality, and conduct audits. For sensitive personal information such as voiceprints, we obtain separate consent, provide information only to the minimum extent necessary, and impose contractual requirements on entrusted processors.

If a security incident such as a personal information breach occurs, we will activate our emergency response plan, contain the incident, and fulfill reporting and notification obligations under the law. Notifications will include basic facts about the incident, possible effects, measures taken, and precautions you can take.

We will make every effort to protect your personal information. However, no security measures are completely infallible, and use of the internet is not always secure.

4. Information Sharing

4.1 How We Provide Information to External Parties

We do not sell your personal information. Without your separate express consent, we do not disclose your personal information publicly or use it for marketing, commercial promotion, or other purposes unrelated to TonoCard services.

We provide service providers only the information needed for specific features and require processing for agreed purposes through data processing arrangements. Overseas Edition AI calls use OpenAI GPT. Optional voice cloning uses the separate provider described in Section 4.1.1. We obtain your separate, explicit consent before providing sensitive voice information to the cloning provider, unless applicable law provides otherwise. Necessary third-party retention and deletion are governed by applicable law, service agreements, and data processing arrangements. Our promise to delete call records after client retrieval applies to cloud systems we manage; it does not mean that all third parties operate with zero data retention.

The entries below describe recipients, purposes, processing methods, and information types by service. Recipient details are also disclosed in the “List of Personal Information Shared with Third Parties” under “Settings → About TonoCard” or in feature notices, covering providers that actually receive personal information. Push and payment services depend on the platform and distribution package; a listed service does not receive your information if it is not used. Components operating locally without transmitting personal information externally are excluded from that sharing list.

4.1.1 Third-Party Voice-Cloning Service Provider

Purpose: Creating a personalized cloned voice and synthesizing responses using that voice when you choose to use voice cloning.

Method: Our servers call its cloud services using encrypted transmission. We do not directly grant it access to all your device permissions through the App. For voice cloning, our cloud only relays an audio sample and does not store the sample, voiceprint features, or model. No user identity information is provided with the audio.

Information types: For voice cloning, we submit only an audio sample, without the user’s name, phone number, or device identity information; the provider processes voiceprint features and models derived from that sample as necessary. For synthesis using the cloned voice, we provide the text to be synthesized and necessary voice data. This involves providing sensitive personal information to a third party.

Provider details and your choice: Before you submit a sample, the feature notice or third-party information list will identify the provider, contact details or privacy-policy link, purposes and methods, information types, processing locations, and retention and deletion arrangements. We obtain separate, explicit consent under Section 1.6. Both disclosure and consent must occur before sample transmission. You may decline cloning and keep using the default voice, use the deletion process in Section 5, or contact us under Section 9. Provider changes are subject to Section 6 notice and consent requirements.

4.1.2 Umeng Tongxin (Beijing) Technology Co., Ltd. (Umeng+ Push, Android)

Purpose and method: Delivering urgent-call and task notifications. The in-App push SDK collects device identifiers and push tokens needed for delivery only after you consent to this Policy. Push SDKs that collect information are not initialized before consent.

Contact: Umeng_Legal@service.umeng.com. Privacy policy: https://www.umeng.com/page/policy .

4.1.3 Huawei Device Co., Ltd. (Huawei Push, HarmonyOS)

Purpose and method: Delivering urgent-call and task notifications through Huawei Push after you consent to this Policy. Information types: Push tokens. Contact: Huawei Consumer Business’s official customer support channels; push privacy information is published by Huawei Developers.

4.1.4 Google and Apple Billing and System Push

Google LLC provides Overseas Edition Android subscription billing. Apple Inc. provides iOS in-app purchases and system push notifications. The relevant app store or system functionality processes transaction credentials, order information, and tokens needed for push delivery; only the applicable service receives the relevant data. The platforms’ privacy policies govern processing for their own payment, security, and legal obligations. We remain responsible for our own processing and processing on our behalf as applicable.

Contact details and privacy policies: Google https://policies.google.com/privacy ; Apple https://www.apple.com/legal/privacy/en-ww/ .

4.1.5 OpenAI GPT Model Services

Purpose: Real-time speech understanding, multi-turn conversation generation, spoken responses for Overseas Edition AI call answering, and requested inference results such as call summaries.

Method and information types: Calling OpenAI GPT model services, including GPT Live for real-time voice processing, over encrypted connections and sending only necessary call audio, conversation text, and context, which may contain sensitive personal information. See Section 2.1 for locations and international transfers.

Retention in OpenAI API services depends on the endpoint, service agreement, and data controls actually enabled. OpenAI’s public documentation describes default abuse-monitoring logs retained for up to 30 days, subject to exceptions such as legal or safety needs; Zero Data Retention requires eligibility and approval. Our deletion of cloud call records does not by itself establish that OpenAI has simultaneously deleted all data or that Zero Data Retention is enabled. Service processing is governed by our service agreement and data processing arrangements with OpenAI.

Contact and rights requests: https://privacy.openai.com/ . Data Processing Addendum: https://openai.com/policies/data-processing-addendum/ . Data controls: https://developers.openai.com/api/docs/guides/your-data . You may also contact us under Section 9 for assistance.

4.2 Embedded Third-Party SDKs

We embed third-party SDKs in the App to enable separate features such as push notifications and payments. We carefully assess the purposes of their use. For more information on the purposes, methods, and scope of personal information processing by SDKs, see the “List of Personal Information Shared with Third Parties.”

4.3 Disclosures Required by Law

Where judicial authorities or administrative regulators lawfully request information through formal legal documents, or laws or regulations otherwise require disclosure, we provide the necessary information in accordance with law after verifying the legality and completeness of the relevant procedures.

4.4 Transfers

If personal information must be transferred due to a merger, division, dissolution, declaration of bankruptcy, or similar circumstances, we will inform you of the recipient’s name and contact details and require the recipient to remain bound by this Policy. If the recipient changes the original purposes or methods of processing, it must obtain your consent again.

5. Your Rights

You can use App controls and the contact channel in Section 9 to access, copy, correct, or delete personal information, withdraw consent, or complain. Depending on applicable law, you may also have rights to portability, restriction, objection, appeal, or requests through an authorized agent. Navigation may vary by system and version; contact us if a request cannot be completed in the App.

5.1 Accessing and Copying Personal Information

Open a call in call history or the relevant history list to view locally stored summaries, transcripts, or recordings, if available. Visit “Settings → About TonoCard” for the “List of Personal Information Collected” and “List of Personal Information Shared with Third Parties.” You may request a copy of information we hold under Section 9; we may verify your association with the device for security. We cannot restore lost local data from cloud records that have been deleted.

5.2 Correcting Personal Information

Edit language, call answering rules, voice, or other editable information in Settings. You may record a new sample to update a cloned voice; to delete an old sample or model, use the separate controls or request process in Section 5.3. Contact us under Section 9 for other information that cannot be edited directly.

5.3 Deleting Personal Information

To delete an individual call record, select the corresponding entry in call history to delete the record stored locally on the client. Our cloud has already deleted the associated call data and copies after the client successfully retrieved that record, as described in Section 2.2.

To clear client-side data, open the App, go to “Settings → Reset Device,” select “Delete Data,” and confirm. Menu labels may vary by system.

To delete voice-cloning data, use the deletion control in voice or voice-cloning settings, or submit a request under Section 9. Our cloud does not store cloning samples, voiceprint features, or models. We notify the third-party provider to delete data it retains as described in Section 2.2. Recording a new sample does not replace an express request to delete an old sample or model.

5.4 Withdrawing Consent

Open this Policy’s page and tap “Withdraw Privacy Policy Consent” at the bottom, or contact us under Section 9. We then stop the relevant consent-based processing and display the consent page again through the App flow. Withdrawal does not affect the lawfulness of earlier processing or processing with an independent lawful basis. Information already provided to third parties is handled under applicable law and agreements; see Section 2.2 for deletion rules. Features depending on withdrawn authorization may become unavailable.

5.5 Managing Features and Permissions

You can disable permissions such as microphone, Bluetooth, contacts, camera, location, and notifications in your phone’s system settings. The corresponding features may become unavailable, while other features remain unaffected.

5.6 Handling Requests and Complaints

Submit a request through “Settings → Complaints and Reports” or email info@tonocard.com. We request only information necessary to verify a request, including device association or an agent’s authorization where appropriate. We generally respond within fifteen (15) working days or any shorter period required by applicable law. If a lawful extension is needed, we explain the reasons and expected timing within the applicable deadline. If a request is denied, we explain why and any applicable appeal process. We do not discriminate against you for lawfully exercising privacy rights.

5.7 Rights Under the Laws Where You Live

If EEA, UK, or Swiss data protection laws apply to our processing, you may, subject to legal conditions, request access, correction, erasure, restriction, or portability, object to certain processing, withdraw consent, and complain to a competent data protection authority. You do not have to complain to us before contacting a regulator.

If US state privacy laws, such as California law, apply to our processing, you may have rights to know what information is collected, used, and disclosed; obtain a copy; correct or delete it; opt out of legally defined sale, sharing, or targeted advertising; and, where applicable, limit sensitive information use, authorize an agent, or appeal a decision. This Policy does not authorize sale of your personal information. Rights depend on applicable law and its exceptions and may be exercised under Section 9. Rights provided by other jurisdictions are also unaffected by this Policy.

6. Changes

We may update this Policy to reflect changes in laws and regulations or adjustments to product features. We will notify you through in-App notices or other means of material changes, including changes to processing purposes, information types, recipients, or your rights. Before expanding or changing processing under the updated Policy, we must obtain your express consent again. We will not treat continued use as consent to the new Policy before you agree to the update.

The App does not require account registration or login. If you do not agree to this Policy, you can exit the App without affecting your use of the phone’s system calling functions or other features.

7. Protection of Minors

The product is intended for adult users and is not directed to children. If you are below the age of majority in your country or region, you should not use the product or submit personal information to us. We do not knowingly collect personal information from children. If a parent or guardian believes that a child has provided personal information to us, please contact us under Section 9 so that we can investigate and promptly delete it in accordance with applicable law.

8 Interpretation and Language Versions

In this Policy, “personal information” means information of any kind recorded electronically or otherwise that relates to an identified or identifiable natural person. Fully anonymized data that cannot be linked to a particular natural person is not personal information.

Identifiers used for device binding and identification, such as Android ID, OAID, and hardware serial numbers, are treated as personal information when they can be linked to a specific device or user. Aggregated statistics that cannot identify an individual are excluded. If we combine non-personal information with personal information, we treat the combined information as personal information for as long as they are used together.

If the general provisions on personal information in the User Service Agreement conflict with this Policy, this Policy prevails. This Policy does not limit your personal information rights under applicable law.

This Overseas Edition Privacy Policy is available in Chinese and English. If they differ, the Chinese text prevails, except where mandatory applicable law requires otherwise regarding language versions or user rights. This interpretation rule does not reduce the protections disclosed in this Policy or limit your statutory rights.

9. Contact Us

We have a team responsible for personal information protection. If you have questions, complaints, or suggestions about this Policy or personal information protection, please contact us as follows:

Company: Longshu (Shenzhen) Artificial Intelligence Co., Ltd.
Email: info@tonocard.com
Address: Room B316, East Building, Lenovo Building, No. 016 Gaoxin South 1st Road, Gaoxinqu Community, Yuehai Subdistrict, Nanshan District, Shenzhen, China

We generally respond within fifteen (15) working days, or within any shorter period required by applicable law. If you are dissatisfied with our response, you may lodge a complaint with the data protection or privacy authority competent under the law applicable to you, including the authority in your place of residence where applicable.