zigora Privacy Policy
English version of V1.2-2026-09-24. Updated and effective: September 24, 2026.
zigora is operated by Guangzhou Zhigezhao Technology Co., Ltd. (广州支个招科技有限公司), the personal information processor. Registered/contact address: B660, Room 207, Building 7, Lingnan V Valley Industrial Design Creative Park, 6 Jinyi Street, Baiyun District, Guangzhou. Privacy, complaints and rights requests: zigora@163.com. We respond within fifteen working days after receiving and verifying your request.
This policy explains collection, storage, use, processing, transmission, provision, disclosure and deletion of information and your controls. Read it before use, especially sensitive information, third parties, cross-border transfers, minors and rights. For consent-based processing, selecting Agree or actively enabling a function indicates consent to the relevant processing. Where separate consent is required, we provide a separate notice and request; this policy does not replace it. If you disagree, choose Disagree and Exit. Refusing optional data or permissions affects only the corresponding functions. Refusing information necessary for a basic function you select may prevent that function.
1. Scope
This policy applies to our mainland China app services: accounts, AI conversation and companionship, tarot, astrology and charts, relationship guides, life-event goals, subscriptions, notifications and support. It does not govern independently provided third-party services. Their own rules apply; relevant pages and our Third-party Services List identify names, purposes, methods, information categories and policy links.
2. Principles and legal bases
We follow lawfulness, propriety, necessity, good faith, clear purpose, minimization, transparency and security. Bases include your consent; necessity to form or perform your contract, such as accounts, submitted profiles, readings and orders; legal duties including security and transaction records, fraud prevention and lawful authority requests; public-health emergencies or urgent protection of life, health and property; reasonable processing of information lawfully made public; and other legal grounds. Changes to purpose, methods or categories require renewed notice and, where required, renewed or separate consent.
3. Collection and use
3.1 Accounts
| Function | Information, purpose and necessity | Retention |
|---|---|---|
| Phone registration, login, linking or change | Phone number, verification code, sending and verification records and a locally generated random device identifier verify ownership, establish accounts and prevent abuse. Necessary only for the phone method; other available login methods remain usable. | Codes serve the current verification and cease use on expiry; account information until closure; security logs as law requires. |
| WeChat account linking | Authorization credentials and authorized identifiers, nickname and avatar link WeChat to your existing account when you choose it. This version does not expose WeChat login. Refusal does not affect other login methods. | Until unlinking or account closure; third-party retention follows its rules. |
| Apple login | Apple user identifier, identity token, authorization code and authorized name/email authenticate and create or link an account. Necessary only if you choose Apple login. | Until unlinking or closure; Apple applies its own rules. |
| Account details and benefits | User ID, nickname, avatar, linked phone, membership level, credits, balance or entitlement quantities display and manage your account and benefits; necessary for those services. | Until closure or expiry of legally required periods after benefits are settled. |
| Sessions and security | Access/refresh tokens, session cookies, login times/status, random device identifier, unusual-login and request records maintain authentication and protect accounts and systems. | Tokens/cookies until logout, expiry or replacement; security logs at least six months or longer if legally required. |
When you actively share a profile or MBTI invitation through WeChat, we pass your selected invitation link, title and description through WeChat Open SDK; you select recipients and confirm sending in WeChat. The link contains an invitation access identifier, so share only with intended recipients. We do not read WeChat contacts or chat history; copying the link is also available. Login, linking and sharing providers may independently collect device information under their own rules. See the Third-party Services List for versions and details. Unlinking a provider does not automatically close zigora or delete independently processed third-party data.
3.2 Birth and relationship profiles
You may create your own or a relationship person's profile. We process its name or designation, relationship to you, gender, birth date/time/place, associated coordinates and timezone, and default-profile status to calculate charts, readings, synastry or relationship suggestions and save/synchronize the profile. Combined birth and relationship details may be private. Processing occurs when you create or edit a profile. Refusal prevents profile-dependent functions while leaving unrelated functions available. Obtain necessary notice and lawful authorization before submitting others' information; use less identifying names and only relevant information. Those people can exercise rights through our contact channel.
3.3 Current location
When you choose current-location chart functions, we request location permission and obtain your current precise or approximate coordinates for chart location and timezone. Precise location is sensitive information; necessity, effects and separate consent are explained before use. Permission is optional. We call it once or at the minimum frequency needed for that request and do not continuously track you. Refusal uses your manually selected place or the current default, Beijing. Coordinates reach our server for timezone resolution and the requested result. Other than completing the request, necessary security logs or a place you choose to save in a profile, we do not retain current location as a long-term movement history.
3.4 AI conversation
We process submitted text, questions, feedback, times, titles, summaries, context, AI replies, conversation/message identifiers and profiles, goals and preferences you choose to associate. Purposes include understanding requests, maintaining dialogue, generating suggestions, saving/synchronizing records, retries, deletion/archiving and safety. Our server calls Tongyi Yunqi (Hangzhou) Information Technology Co., Ltd.'s Alibaba Cloud Bailian and Beijing Volcano Engine Technology Co., Ltd.'s Volcano Ark. According to model routing and function, necessary text, context, questions, feedback and associated profiles/goals are sent to the corresponding provider. A request may involve multiple stages. Disclosed models include Bailian Qwen and Volcano Ark Doubao Seed 2.0 Pro. See sections 6 and 8 for recipients and retention.
You may voluntarily disclose health, mental or emotional state, religious beliefs, sexual orientation, financial accounts, precise location, identity, minors' data or other sensitive information. Provide only what is necessary and avoid identity numbers, passwords, bank passwords and verification codes. Necessary sensitive processing receives purpose-specific notice and separate consent where required; if requirements cannot be met, we may ask you to remove the content or stop processing it. AI may be inaccurate or incomplete and provides general information, entertainment and self-exploration, not professional medical, psychological, legal or financial advice. We do not make decisions significantly affecting prices, credit, employment, education or healthcare solely from AI processing. Without separate authorization we do not train general models for other users on identifiable conversations. Necessary troubleshooting, human sampling and safety review follow minimization, de-identification where possible, access controls and audit logs.
3.5 Tarot and astrology
Questions, selected spreads/cards, upright/reversed positions, draws, readings, feedback, related profile/session identifiers and generated results complete requested readings, follow-ups and history. Keep private health, relationship, family, career and financial information to the necessary minimum. Refusal prevents the corresponding personalized reading but leaves unrelated functions available.
3.6 Guides, life events and goals
When you create, confirm, edit, pause, resume, archive, delete or give feedback, we process titles, content, status, desired outcome, time range, priority, milestones, progress, feedback, related profile IDs, timestamps and operations. These save plans, produce reminders/suggestions, synchronize progress and show history. Submit only relevant information and obtain lawful authorization for others' data. You can delete individual profiles, conversations or events; email us if bulk deletion is unavailable.
3.7 Memory and preferences
When you enable memory or preferences, voluntarily supplied nickname, occupation, interests, values, preferences, things to remember and warmth, affinity, skill or suggestion settings may personalize later interactions. The referenced client version stores these settings locally first. Server synchronization requires updated notice and any necessary consent before enabling. You can disable memory, edit information or clear local data; subsequent personalization stops except processing needed for legal duties or existing service records.
3.8 Voice, camera and images
Actively using voice, recording, photos, scanning or image analysis requests the corresponding microphone or camera permission and processes your recording/photos/video and operation time to complete that function. Both permissions are optional; refusal does not affect typing or account management. We do not activate them in the background without your action, or use images for face recognition or collect voiceprints unless a future function separately provides lawful notice and consent.
When you confirm voice recording, up to 60 seconds of audio passes through our server to Bailian recognition, qwen-audio-3.0-asr-flash, for transcription. The text returns to the input field for editing and becomes conversation content only when you send it. The client deletes temporary audio on normal recognition completion, cancellation or component disposal. Audio is forwarded for transcription, not saved as a conversation attachment. Provider retention and device-file deletion are separate; see section 8. New uploads or third-party image/video processing require separate notice of purposes, recipients, categories, retention and consent.
3.9 Purchases and restoration
On iPhone/iPad, Apple independently handles Apple ID, payment methods and payments; we do not directly receive bank-card numbers or payment passwords. Product/subscription IDs, order and transaction/original-transaction IDs, channel, price, purchase time, payment/subscription status, app-account token and verification results create and verify orders, issue/restore benefits, process refunds/disputes, reconcile, prevent fraud and meet tax, accounting and commerce duties. Refusal prevents purchase or restoration, not free functions. Apple's rules apply to its independent processing.
3.10 Notifications
When you enable notifications, we process user ID, random installation ID, push tokens/aliases, manufacturer, model, OS/version, package/app/SDK versions, permission state, preferences and notification ID, opening time/channel and destination/deep link. Purposes include device registration, daily/relationship/life-event/service notifications, opening statistics and troubleshooting. On iOS, notification permission is requested after privacy consent and login. Initial denial prevents Umeng initialization; later permission followed by opening Notification Management or logging in triggers a new permission check. Permission is optional and can be disabled by type or entirely in Me → Notification Management or system settings. Related device sends then stop, although briefly in-flight messages may arrive before synchronization. Logout or closure unbinds the account and push identifiers. Umeng and device channels, including Apple, Huawei, OPPO, vivo, HONOR and Xiaomi according to device/build, may process data; see the Third-party Services List. Without consent we must not initialize collecting push SDKs or bind aliases.
3.11 Support and complaints
Account identifiers, contacts, inquiries/complaints, correspondence and voluntarily provided screenshots, files and evidence verify identity, locate issues, respond and keep handling records. Mask unrelated information. We may request minimal verification appropriate to your request, but never your account password, complete bank password or verification code.
3.12 Operation and security
For stability, security, anomaly detection, fraud prevention and troubleshooting, we may automatically process IP, request times/pages/interfaces, response status, network type/state, device brand/model, OS/app versions, random device/installation IDs, crash/error logs and login/security events. We do not collect unrelated information without limits under the guise of safety or experience. Third-party analytics, crash or security processing is disclosed in the list. The current version should not collect contacts, call records, SMS content, clipboard, installed-app lists or hardware serials unless a new directly related function separately provides lawful notice and consent.
4. Permissions
| Capability | Purpose and effect of refusal |
|---|---|
| Network connection | Login, loading, synchronization, AI generation, subscription verification and service data; network functions are unavailable without it. |
| Network/Wi-Fi state | Availability, request strategy and troubleshooting; refusal may affect detecting connectivity or loading. |
| Precise/approximate location | Optional current-location charts/timezone; precise location requires separate consent. Manual or default locations remain available. |
| Camera | Optional photos/scanning/images; refusal prevents camera functions. |
| Microphone | Optional recording/voice input; typing remains available. |
| Notifications | Optional daily, relationship, event and service pushes; other features remain available. |
Operating systems control permissions; change them in system privacy/permission settings. Withdrawal does not invalidate previous lawful processing, but further calls cease when no longer needed. Camera, microphone and location are requested at use, rather than forced together at first launch. Names and settings vary by device.
5. Cookies and local storage
Local tokens, cookies, policy-consent status, random identifiers, push state, chat/preferences and chart/guide caches maintain login, settings, performance and stability. You can clear local data using available app or system controls; doing so may remove local settings or require login again. It does not automatically delete synchronized server account or business records. Use section 10 for server deletion.
6. External processing
6.1 Entrusted processors
Cloud, SMS and AI processors follow our instructions. Contracts specify purposes, duration, methods, categories, safeguards and responsibilities; we supervise them and prohibit out-of-scope processing or unauthorized sub-entrusting.
| Processor | Purpose and information | Method/location |
|---|---|---|
| Alibaba Cloud Computing Co., Ltd. | Servers, databases, storage, networking and security; account/profile/conversation/results/goals/order-verification information and operational/security logs plus necessary network/device information. | Storage, transfer, backup, protection and troubleshooting as instructed. Core production and backup resources are in East China 1, Hangzhou, mainland China. |
| Shanghai Puzhikun Information Technology Co., Ltd. | Verification SMS: phone, code-message content, sending time and sending/delivery status. | Server API per request, no client SDK or direct client communication. Only sending, status, troubleshooting and necessary audit. Ask us for its processing rules. |
| Tongyi Yunqi (Hangzhou) Information Technology Co., Ltd. — Bailian AI | Necessary conversations, questions, feedback, context, linked profiles/goals, outputs and request identifiers for understanding, replies and readings. | Server model API per request; identifiable content is not used for general-model training without separate authorization. |
| Beijing Volcano Engine Technology Co., Ltd. — Volcano Ark | Necessary conversations, questions, feedback, context, linked profiles/goals, outputs and request identifiers for AI replies/readings. | Server model API per request; identifiable content is not used for general-model training without separate authorization. |
| Tongyi Yunqi (Hangzhou) — Bailian recognition | Audio, transcription and necessary request information to produce editable text. | Server API for the current transcription; retention in section 8. |
Processors do not acquire independent control of processing purposes/methods. We check actual products, settings and contracts for retention, access, training switches, region and deletion. Any processing beyond the table receives updated notice and necessary consent before use. Official rules include Alibaba Cloud's legal/privacy policy, Bailian privacy information and Volcano Engine's Privacy Policy, linked in the Third-party Services List.
6.2 Independent recipients or joint processing
Login, payment and push providers may process independently. Before legally defined provision to another processor, we disclose identity/contact, purposes, methods and categories and obtain separate consent. We do not sell personal information. Identifiable information is provided only with separate consent; as needed for your selected third-party function after required notice/authorization; under law, dispute processes or lawful authority requests; when necessary for emergency protection of life, health or property; or on other legal grounds. The Third-party Services List individually discloses embedded SDKs, code and plugins, purposes, methods, categories, frequency, scenarios, entities and policies.
6.3 Transfers
For mergers, divisions, restructuring, dissolution, bankruptcy or business/asset transfers involving personal information, we notify you of the recipient and contact and require continued compliance. Changed original purposes/methods require renewed consent.
6.4 Disclosure
We generally do not publicly disclose information. Necessary disclosure receives notice of purpose, categories and effects and separate consent unless law provides otherwise.
6.5 Records
We keep required entrusting, external-provision or joint-processing records; records covered by the Network Data Security Management Regulations are retained for at least three years.
7. Storage and cross-border provision
Core account and business data collected in mainland operations, including production and backup, are stored in mainland China using Alibaba Cloud East China 1, Hangzhou. We currently do not proactively provide such core data outside mainland China. A future cross-border function requires applicable security assessment, certification, standard-contract filing or other legal procedures, safeguards, separate notice of the overseas recipient/contact, purposes, methods, categories, retention and rights procedures, and separate consent before enabling. Without those requirements, the transfer is not enabled.
8. Retention and deletion
Unless law requires otherwise, retention is limited to the shortest period necessary.
| Information | Period |
|---|---|
| Account/linking/details | While the account exists; delete or anonymize after closure except legally required retention. |
| Birth/relationship profiles | Until deletion or closure; verified deletion requests are handled within fifteen working days. |
| Conversations, readings, guides, goals and feedback | Until deletion or closure; history you choose to retain remains during the account's lifetime. |
| Current location | Current request only, not a long-term movement record; voluntarily saved profile locations follow profile retention. |
| Local memory/settings/cache | Until clearing, deletion, logout or uninstall, depending on type and system. |
| Push identifiers/preferences | Until disabling, logout, device invalidation or closure; no targeted push use after unbinding. |
| Orders/subscriptions/transactions | At least three years after completion, longer if tax, accounting, disputes or law require. |
| Operation/security logs | At least six months, longer for incidents, disputes or legal duties. |
| Support/complaints/rights requests | Three years after handling, or a shorter/longer period necessary for disputes or legal duties. |
Expired information is deleted or anonymized. Backup copies are overwritten or deleted through rotation in the shortest technically feasible period once no longer needed; until then, they remain isolated for storage and necessary protection only. Unexpired legal duties, technical backup limits, litigation, complaints, audits, investigations or incidents may require restricted retention within the necessary purpose and period.
AI and voice retention
zigora conversation/output/linked-profile records follow their business retention. Clearing context resets dialogue context; it does not physically delete history, audit records or backups. Request deletion through our contact channel; legal and backup exceptions apply.
Bailian AI and recognition: published agreement clauses 6.2.4–6.2.7 limit conversation data to the shortest service-delivery period; deletion follows customer instructions, legally or technically restricted backup copies are first restricted from further processing, and post-termination buffers depend on purchased rules. No universal fixed number of days is published. Applicable model-service rules determine retention; we do not promise immediate deletion or zero retention.
Volcano Ark: published special terms 3.7.7 and 3.7.11 permit reasonable retention of troubleshooting submissions; abnormal-alert data ceases continued storage/review after the alert is resolved; enabled caching, logging or monitoring may create storage. There is no universal fixed period. Retention depends on purpose, alert state and enabled features; zero retention is not promised in every scenario.
Temporary device WAV files are deleted on normal recognition completion, cancellation or component disposal; crashes may leave files whose cleanup depends on the system. The voice API forwards audio and returns text without storing audio as a conversation attachment; necessary logs follow the periods above. Confirmed text sent by you follows conversation retention. Deleting the client file does not delete provider copies. Published Bailian and Volcano Ark rules do not give a single period for all types/scenarios. Email us to ask about specific processing or request deletion; after verification we help coordinate with the provider.
9. Security
Measures proportionate to risk include encrypted transfer, secure storage, access control, authentication, least privilege, audit, backup/recovery and monitoring; classification and stricter sensitive-data controls; management systems and staff training; legally required impact assessments and records for entrusting, sensitive data, automated decisions, recipients, disclosure and cross-border processing; periodic compliance audits, security testing and risk checks; and incident plans and rehearsals. The internet is not absolutely secure. For actual or potential leakage, alteration or loss, we promptly remedy, report as required and notify affected people of circumstances, risks, actions, protective steps and contacts through app notices, SMS, email, phone or announcements, except lawful notification exceptions.
10. Your rights
You have lawful rights to know and decide, restrict/refuse processing, access/copy, correct/supplement, delete, withdraw consent, close accounts, obtain explanations and transfer information where legal conditions apply.
10.1 Access and correction
Use Me, account, profile, goal, memory and preference pages; email us for unavailable controls.
10.2 Deletion
Delete individual conversations/profiles/goals or use available Me → Privacy Management tools. If support handling is required, email with subject Personal information deletion request. We proactively delete, or accept your request, when purpose is achieved/impossible/unnecessary, services or retention end, consent is withdrawn, processing breaches law/agreement or other legal grounds apply.
10.3 Withdrawal
Disable location, camera, microphone or notifications in system settings, or notification types, memory and personalization in app settings; email for specific activities. Withdrawal does not invalidate prior consent-based processing, or automatically stop contract/legal-duty processing. You can stop the corresponding function or close the account.
10.4 Account closure
Use Me → Account Management → Close Account where available; otherwise email with subject Close zigora account from a linked email or provide minimal verification. We complete closure within fifteen working days after verification or explain lawful reasons for delay. Access to history, profiles and benefits ends. Unused benefits, refunds and renewals follow the Terms and payment rules. Closing zigora does not cancel an Apple subscription; cancel it separately in your Apple account.
10.5 Copies and transfers
Email to request a copy. Where legal and national cyberspace conditions apply, we provide a route to transfer to your nominated processor.
10.6 Complaints and explanations
Request explanations or report concerns by email. We investigate and handle within fifteen working days and explain refusals. You may complain to competent cyberspace, telecommunications, public-security or market-regulation authorities.
10.7 Verification and exceptions
Reasonable, minimal identity verification protects accounts. Unjustified repeated/excessive requests, harm to others, trade secrets or lawful refusal grounds may lead to refusal or necessary-cost charges with explanation.
10.8 Deceased users
Close relatives may lawfully exercise access, copying, correction or deletion for their legitimate interests unless the deceased made other arrangements. Contact us by email.
11. Minors
We do not currently provide registration/personalized services to children under 14 or knowingly collect their information. They must not independently register or use information-submission features. Users aged 14–17 should have a guardian read and agree to the policy and Terms, use under guidance and avoid excessive private details. If future child services or necessary processing arise, dedicated rules and a responsible person will be established, with clear guardian notice of purpose, method, scope, location/period, safety, refusal effects and rights and guardian consent. Sensitive child processing receives required impact assessment and strict safeguards. Guardians can report unauthorized child information by email; verified cases are promptly deleted or otherwise handled as necessary.
12. Service closure
Before closing the app or major services we prominently notify you, stop related collection and delete or anonymize information within a reasonable period except legal duties.
13. Updates
Changes may follow functions, processing or law. We do not reduce statutory rights without express consent. Material changes to purposes/methods/categories/retention, processors/recipients, sensitive processing, automated decisions, third-party sharing/cross-border rules, rights routes or security risk receive conspicuous notice and legally required renewed/separate consent. Review and save the current version under Me → Privacy Policy or our site. Email for older versions and change explanations.
14. Contact
For privacy, minors, questions, complaints and rights, contact the processor at the address above or zigora@163.com. Suggested subjects: Personal information rights / Privacy complaint / Children's information. Normally we respond within fifteen working days after receiving and completing necessary verification. If dissatisfied, contact us again or lawfully complain to a competent regulator.
15. Other provisions
Headings are for convenience. Deletion includes making information inaccessible/unsearchable or anonymizing it; anonymized information is no longer personal information. Conflicts with the Terms on personal information follow the lawful provision better protecting your rights. Mainland Chinese law governs formation, performance, interpretation and disputes.