Yanovo Privacy Policy

1. Scope and operator

This Policy applies to the Yanovo instant messaging clients and official website, yanovoim.top, provided by ACC工作室 (ACC Studio). For activities in which we decide the purposes and means of processing, ACC工作室 is the personal information handler. Contact: contact@yanovoim.top.

This Policy explains processing related to accounts, chats, audio and video calls, message translation and website access. External websites you choose to open have their own policies. When providers support a Yanovo feature, we still describe the processing here and do not disclaim our responsibilities merely because a third party is involved.

We process information on an applicable lawful basis, such as necessity to provide the Service, legal obligations or consent. Device permissions, reading terms and consent to processing are distinct. Continued use does not replace separate or renewed consent where required.

2. Information, purposes and permissions

Accounts and profiles. Registration, sign-in and account recovery involve the phone number or email you use, account identifiers, password verification information and verification codes. In “Me — Personal Information” you can view and edit supported profile fields, such as nickname, profile picture, gender and region. Identifiers, nicknames and pictures are shown to relevant users in search, contacts, groups and chats; not every profile field is publicly available on the internet.

Messaging. To transmit, display, retrieve and synchronize messages, we process sender and recipient identifiers, conversation and group relationships, message text, photos, audio, video and files you send, and timestamps, delivery, read and withdrawal states. Messages and attachments are stored on the server and relevant clients. Clearing local history does not automatically remove server data or copies saved by others.

Audio and video. Voice messages and calls use the microphone; capture and video calls use the camera. Calls also involve participants, timing, answer and end states, connectivity and information needed for media transport. Media may travel directly between peers or through relay nodes. Voice calls use the proximity sensor for screen control near your ear; this local device interaction is not geographic location collection.

Photos, files and QR codes. Selecting or saving photos, videos and files, and scanning QR codes, uses system pickers or requests photo, file or camera permissions where required by the operating system. Selecting a file does not authorize upload of an entire library. Scanned QR contents identify the relevant user, group or link.

Translation. When you request translation or enable it for a conversation, the client sends account verification, a message identifier and source and target languages to our server. The server obtains the corresponding text you are authorized to access, calls the MyMemory translation API and stores successful translations for later retrieval. You can turn automatic translation off in the relevant conversation’s translation settings. This stops new automatic requests for that conversation but does not itself delete originals, cached translations or information already received by the provider.

Devices, security and logs. The client uses Android ID or iOS IDFV, device model, operating system and app version for device identification, sign-in and compatibility. The server processes IP addresses, request times, API and error or security event information for operations, troubleshooting and abuse prevention. See Section 5 for log retention and Section 3 for push SDK processing.

Notifications and feedback. Push registration identifiers identify devices receiving notifications. You may disable Yanovo notifications in system settings. When you use “Me — Privacy — My Suggestions” or email us, we process the contents and contact details you provide to respond and investigate. Do not include unnecessary passwords, verification codes or others’ personal information.

Website and local storage. Browsing the introductory website does not require registration. The website reads the language parameter in links to select the interface and legal version. Clients use local databases and preferences for conversations, caches and settings. Website access and release lookups generate necessary network requests. Removing a local cache does not delete an account or server data.

Manage camera, microphone, photo and file permissions in your device’s app settings. Refusing a permission affects the feature that needs it, rather than unrelated features. Withdrawal does not invalidate earlier lawful processing or automatically erase uploaded data. Request deletion under Section 4.

3. Providers, third-party processing and cross-border transfers

We use the providers below for push and translation. Their retention periods and further processing differ from the rules for our own service. We do not represent that provider data is retained for only 15 days or that providers never use it to improve their services.

JPush. The provider is Shenzhen Hexun Huagu Information Technology Co., Ltd. and its affiliates. The client integrates the JPush SDK for push registration and notifications, involving registration identifiers, device and app information, network information and push logs. Exact SDK fields depend on platform, version, permissions and configuration; the official policy also describes device identifiers and optional network fields. See the Jiguang Privacy Policy for details and contact channels. A system notification switch controls display; it does not itself erase registration identifiers or stop every SDK network activity.

MyMemory (Translated) translation API. Our server sends the message text and source and target languages to api.mymemory.translated.net. The provider can also receive our server’s request IP address and necessary access logs. This translation request does not send your Yanovo password, sign-in token or entire conversation history. The text itself may contain personal information, so choose what you translate carefully. See MyMemory’s service and privacy terms for its rules and contact channels.

MyMemory’s published terms describe long-term retention of submitted segments and possible service improvement and partner processing. Use of the API should not be understood as a promise of transient processing with no retention or model improvement. Turning translation off does not mean previously received provider data is erased. Contact us for assistance or use the provider’s official channels to exercise relevant rights.

Hong Kong storage and overseas processing. Account data, chats and files on our own service are stored in Hong Kong, China. Translation and push providers and their network nodes may process relevant information elsewhere. For users subject to mainland Chinese personal information rules, provision to Hong Kong or other overseas locations entails applicable cross-border requirements, including recipient, purpose, means, data types and rights information, required separate consent and applicable procedures. This Policy alone does not replace those procedures or authorization.

Agreeing to this Policy is not blanket authorization to disclose all personal information to any third party. New providers or purposes require updated notices and authorization where applicable. Entrusted processing must have defined purposes, scope and safeguards; disclosure to independent handlers or public disclosure is subject to applicable requirements. Disclosures required by competent authorities are limited to the necessary lawful scope.

4. Your rights and how to exercise them

Access, correction and copies. View and edit supported fields in “Me — Personal Information”. Email us to request access or correction for other personal information or to request a usable copy. We will provide a reasonably usable copy within the scope of the request.

Withdrawal of consent. Turn permissions or notifications off in system settings and automatic translation off in conversation settings. Email us to withdraw consent to other consent-based processing. We will explain what processing can stop and any feature effects; refusing unnecessary processing is not a basis for denying every basic feature.

Deletion and account closure. Request closure in “Me — Account Security — Delete Account”. The current operation disables the account and clears its password and certain profile fields; it does not immediately erase all history or attachments. Email specific deletion requests for remaining personal information, messages and files. Following verification, we will delete or anonymize data as required by law and explain the basis and scope of any part not immediately removable. Withdrawing a message, clearing local history and closing an account are distinct operations.

Handling requests. We may perform account or identity checks proportionate to the request to prevent unauthorized access or deletion, without requiring unrelated information. We will respond promptly with the outcome, explain necessary extensions or refusals and provide an appeal channel. Applicable statutory deadlines apply. Additional technical work alone is not a blanket basis for denying statutory rights.

5. Retention, location and security

Account data. Retained as necessary to provide account and communication services. After closure, handling follows Section 4 and legal retention requirements; disabled status does not mean all data has been physically erased.

Chats, files and translations. Chat records and uploaded files currently have no automatic expiry and remain stored; successful translations are cached against the original message. This supports history and communications and is not irrevocable authorization to retain forever. Deletion or anonymization is required when applicable legal deletion conditions are met, the purpose no longer requires the data or a request must lawfully be honored. Recipients’ copies and provider-held data require handling according to their circumstances.

Logs. Operational logs on our own service are normally retained for 15 days. Any longer retention required by law or necessary for a specific security incident or dispute is limited in scope, duration and use. The 15-day rule does not cover chats, files, translations or data processed by third-party SDKs.

Location. Our own service data is located in Hong Kong, China. Section 3 describes third parties and other overseas nodes. We do not represent that all data is stored solely in mainland China.

Security and incidents. We will apply safeguards appropriate to the data and risks, including access control, authentication, transmission protection and permission management, limit unnecessary access and investigate incidents. Personal information incidents are subject to legally required remedial steps, notification and reporting. Network transmission and information systems cannot be guaranteed to be entirely risk-free.

Data that cannot immediately be erased for legal reasons or pending backup cycles must be restricted to necessary storage and security rather than used for arbitrary new purposes.

6. Policy updates

We display an update date on this page. Material changes to the operator, purposes, data types, providers, retention, locations or rights channels will be appropriately notified through the website or client. Required renewed or separate consent will be addressed rather than relying solely on continued use.

Email us to ask about an earlier version or specific changes.

7. Protection of minors

Users under 18 should read this Policy with a guardian’s guidance and obtain consent where legally required. Guardians should help minors share identity, contact, location and other sensitive information carefully.

Processing personal information of children under 14 requires guardian consent and dedicated safeguards: clear and necessary purposes, restricted access and disclosure, and no treatment of general service terms or default switches as guardian consent. Children’s personal information should not be submitted or relevant processing activated before legally required guardian authorization is completed.

Guardians may email us to request access, correction, deletion or withdrawal of consent for a child’s information. Collection without necessary consent requires prompt investigation and lawful cessation, deletion or other protective measures.

8. Contact us

Operator and privacy contact: ACC工作室 (ACC Studio). Email: contact@yanovoim.top. Signed-in users may also send feedback in “Me — Privacy — My Suggestions”. Email remains available if you cannot sign in.

Identify the account, issue and action requested without sending passwords or complete verification codes. You may appeal the outcome through these channels, complain to competent authorities or bring proceedings before a people’s court with lawful jurisdiction.

Appendix: definitions

Personal information is recorded information relating to an identified or identifiable person, excluding anonymized information. Sensitive personal information is information whose leakage or misuse can readily harm dignity or personal or property security, including personal information of children under 14.

A personal information handler decides the purposes and means of processing. Anonymization irreversibly prevents identification; de-identification prevents identification without additional information. An SDK is a software development kit integrated into an app. Erasure, anonymization, disabling an account and clearing a local cache are distinct actions.