运见 YUNVIA
Yunvia Privacy Policy
上海甲木参天科技有限公司 operates Yunvia. This policy describes how the current app handles personal data for accounts, profiles, relationships, daily guidance, reports, readings and AI conversations, and how you can manage that data.
1. Data used for each feature
Account access and security
Email authentication uses your email address and verification code or password. Password credentials in the business database are stored as cryptographic hashes. Codes verify sign-in or account deletion, currently expire after five minutes, and are subject to frequency and failed-attempt limits. We also process login credentials, failed login counts and related timestamps to maintain access and resist unauthorized attempts.
If you choose Google sign-in, we verify the credential and process the authorized Google account identifier, email and available name and profile image. Email sign-in remains an alternative. Yunvia does not ask for your Google password.
Birth profiles, charts and daily guidance
Profile information includes a nickname, sex, birth date and time, time zone, selected or entered birthplace, place identifier, coordinates and true-solar-time preference. These support profile identification, calculations and time correction. Birthplace coordinates are not your device's current location. You can use a nickname instead of a legal name.
Guest information can be stored locally. On sign-in, existing guest profiles and readings are uploaded during account synchronization. Signed-in profiles are stored on the server with local copies for display and offline use. Caches are separated by account; separation does not mean older data has been physically removed from the device.
Relationships and compatibility
We store the two linked profiles and the relationship type you select, and use them to calculate and display compatibility or relevant interpretations. These details may concern private life. Only submit data you are entitled to process, and obtain necessary permission before creating another person's profile or relationship.
AI conversations, reports, guidance and readings
We process questions, conversation history, reading questions and results, relevant profiles, calculated reference material and generated content to answer requests, create reports, restore conversations and display history.
For AI features, our server sends DeepSeek the information needed for the requested generation, which may include nicknames, birth information, relationship types, calculation results, questions and necessary context. Conversations can retrieve your account's existing guidance, relationships and latest reports and include relevant material in the reply context. Login passwords, verification codes and Google authentication credentials that you have not entered into a question are not required model-generation data.
Business content is saved under your account. The system also stores account-linked model-call records to examine generation, usage and faults; these may include complete model inputs and outputs. These records are separate from the conversation and report lists, so deleting a listed item does not mean the model-call record is also deleted. Avoid submitting unrelated sensitive information.
Coins and redemption
Coin top-ups and membership subscriptions use Google Play Billing. Google processes payment details; Yunvia receives purchase tokens, product and order identifiers, payment status, subscription periods and verification results to deliver entitlements, handle renewals, refunds and disputes. We do not receive your complete bank-card number or payment password.
Network requests, operational records and correspondence
Network services receive information needed to handle requests, including IP address, request path, timing, language, client local time and device time zone. These support connectivity, security, troubleshooting and interpretation of relative dates such as “today”. Server logs may also contain request parameters, related account identifiers and error details. They are managed separately and should not be used for unrelated purposes.
If you contact the operator, we use the contact details, issue description and necessary supporting material you provide to handle the request. Identity checks should be proportionate and should not require your full password or verification codes.
Advertising and privacy choices
Non-members may see AdMob app-open and native ads on startup, content pages and waiting screens, and may choose rewarded ads for additional app services. For ad delivery, measurement, analytics and fraud prevention, Google's advertising SDK automatically collects and shares data including IP address (which can indicate approximate location), app and ad interactions, diagnostics such as crashes and performance, and device or account identifiers such as the Android advertising ID and app set ID where available. Actual processing depends on device settings, consent choices and the ad-serving mode. The app does not request GPS location for advertising.
Yunvia does not attach birth profiles, relationship details, chat messages, report contents or login credentials to its AdMob ad requests. Advertising data is processed by Google and participating advertising partners; this is separate from the information submitted for AI generation.
We use Google UMP to obtain applicable privacy-choice information and, where required, display a consent message before requesting ads. Choices can include consenting, declining or managing individual purposes and partners. We request ads only when UMP indicates that requests are permitted. Declining personalized advertising does not necessarily mean no ads or no data processing: non-personalized or limited ads may still be served, depending on your choices and Google's rules. Advertising availability can affect access to ad-supported flows in the current version.
Where UMP requires a privacy-options entry, open About us → Ad privacy settings to review or change your choices. Withdrawing consent does not invalidate earlier lawful processing. You can also use available Android system controls to manage or delete your advertising ID; exact controls depend on your Android version and device.
We use Google Firebase Analytics to measure app usage, registrations, purchases and advertising performance. Processing may include app-instance/device identifiers, app interactions, device and diagnostic information, product/order identifiers and purchase amounts where available. Our custom analytics events do not include birth profiles, chat or report contents, login credentials or payment tokens. Google processes this data under its privacy rules and applicable consent settings.
2. Device permissions and local storage
The Android app uses internet access and optional approximate location permission. When you choose current-location city selection, Android requests permission and the app uses approximate location to match a city; you can decline and select a city manually. We do not request background location, contacts, camera, phone-state or broad storage permissions. Voice input uses the system speech-recognition service, which may process audio under its provider’s rules; recognized text enters the draft before you send it. Read-aloud uses the selected system text-to-speech service. The app does not request its own microphone permission.
The app stores login state, language preferences, profiles, relationships, chats and generated-content caches in its app storage to restore state and reduce duplicate requests. Advertising and consent components may also store identifiers, preferences and consent records on the device. Policy pages can be read without signing in and contain no analytics scripts added by us.
Signing out does not fully erase all local caches. Uninstalling the app or clearing its storage in system settings removes the app data on that device, but does not delete your server account. It also removes guest information that has not synchronized.
3. Service providers
This policy does not authorize unrestricted sale or publication of your personal data. The services below participate in the relevant feature. Providers may process data under their applicable rules; we remain responsible for duties imposed on us by law.
- Google identity services: Used when you choose Google sign-in. We receive the authorized account identifier, email and available name and picture. Google's authentication processing is described in the Google Privacy Policy.
- Google AdMob and UMP: Provide ads, measurement, fraud prevention and privacy-choice management as described above. Google and participating advertising partners may receive the relevant advertising data. See the Google Privacy Policy, How Google uses information from sites or apps that use its services and Google Mobile Ads SDK data disclosures. Where a consent message is displayed, its partner list and options provide additional information about participating partners and purposes.
- Alibaba Cloud DirectMail: Delivers login and deletion codes using the recipient email and message containing the code. This sending service currently uses the Hangzhou region, a separate part of the flow from our Hong Kong servers. See the Alibaba Cloud Privacy Policy.
- DeepSeek (杭州深度求索人工智能基础技术研究有限公司 and its affiliates): Its API receives relevant questions, profiles, calculation results and context and returns generated content. Retention and processing are governed by applicable service rules and arrangements. Yunvia not training its own models must not be read as a promise that a provider has zero retention or no further processing. See the DeepSeek Privacy Policy.
- Cloud infrastructure and logging: Providers host servers, databases and operational logs and process the corresponding data under deployment and operation arrangements. The current logging service uses Alibaba Cloud Log Service.
When delegating processing, we should define its purpose, scope and safeguards. Sharing with an independent controller or other activities requiring separate notice or consent should follow the applicable process. In a business transfer, we should disclose the recipient and its duties, and obtain appropriate authorization if processing purposes or methods change.
4. Storage location and cross-border processing
Yunvia's main servers and databases are in Hong Kong, China. If you use online features from mainland China, submitted account details, profiles, relationships, conversations and generated material are transmitted to Hong Kong for processing and storage. This does not establish every provider's processing location: verification emails, AI services, Google authentication, advertising and consent services may process their respective information in other service regions under the providers’ policies and applicable arrangements. Advertising data is not necessarily stored in Hong Kong.
For cross-border provision covered by applicable law, we should complete the required legal arrangements and disclose the recipient, contact information, purpose, processing method, data categories and rights procedures, and obtain separate consent where required. Accepting general terms or reading this policy does not replace separately required cross-border consent.
5. Retention and deletion scope
Accounts and business data are generally kept while you use the relevant services, until you delete content, delete the account or the relevant purpose no longer requires retention. Verification codes have short validity periods. Login credentials are handled according to their validity and deletion status. Records subject to legal retention requirements are retained as required.
Operational, security and model-call records are stored separately for security, troubleshooting, usage verification and lawful dispute handling, not indefinite unrelated use. The current account-deletion flow does not automatically and immediately erase all operational logs, model-call records or historical device caches.
Deleting a relationship does not delete the two profiles or existing chats. Deleting a profile does not automatically erase every historical conversation, guidance item or log referring to it. Manage visible content separately and contact the operator about records you cannot delete yourself. Data should be deleted or anonymized when no longer needed or when legally required. Where a mandatory retention period prevents immediate deletion, other processing should be restricted.
Google and advertising partners retain advertising and consent data under their applicable policies and legal obligations; we do not promise a fixed retention period on their behalf. Deleting your Yunvia account does not automatically delete data those providers hold separately. Use the privacy controls and provider rights channels linked above for relevant requests.
6. Managing your data
- Access and correction: View profiles, relationships, conversations and reports in their respective screens, and edit profile inputs where supported. AI output is not a factual determination about you, and you may disregard it.
- Content deletion: Use deletion actions provided by the relevant list or detail page, noting the scope described above. For data without a separate delete or export function, contact the operator.
- Account deletion: Go to Me → Account settings → Delete account and complete email verification. The account, corresponding business data, credentials and coin entitlements are removed irreversibly; separately stored logs and local caches are handled as described in this policy.
- Withdrawal and restriction: You may choose not to use optional Google or AI features, stop submitting related data, and request withdrawal, restriction, copies, correction or deletion from the operator. Withdrawal does not invalidate earlier lawful processing. A feature may become unavailable without necessary data, but unrelated features should not be unnecessarily restricted.
- Device data: Before sharing or transferring a device, you can clear the app's data in system settings. This is separate from deleting your server account.
We should verify only necessary identity information, handle requests according to applicable law, explain any lawful limitations and provide available remedies without unreasonable conditions. You may also contact the relevant data-protection authority as permitted by law.
You can request deletion of your account and associated data without signing in through our account and data deletion page.
7. Security and minors
Account permissions, password hashing and access controls help protect information. Transmission security, log redaction and operational safeguards should continue to be improved. No measure guarantees absolute security. Personal-data incidents require timely response and applicable notification and reporting.
The service is primarily for adults. Minors should use it with guardian guidance. Information about children under fourteen receives special legal protection; children should not independently register or submit information. Obtain the necessary guardian authorization before creating a child's profile. If information was submitted without appropriate authorization, the operator should verify the situation, restrict processing and delete information that should not be retained.
8. Updates and contact
New data categories, purposes, recipients or significant changes to rights require updated disclosures. Continued use alone does not replace renewed or separate consent where the law requires it. The current policy is available from the welcome screen, sign-in/registration and Me.
Personal information controller: 上海甲木参天科技有限公司. This Chinese name is the operator's legal name.
Privacy and customer support: support@yunvia.si. Describe your request and account email; do not send passwords, verification codes or complete payment details.