Revision draft: 2026-10-17 | Contact: in-app customer support
Draft notice: The operator legal name, address, valid email, effective date, and actual processing locations and retention periods of service providers remain to be verified. This is a review draft, not an official release.
This policy explains how the hiyola operator (legal name to be supplied, “we”) processes personal information through the app and related pages, and your choices. Read it with the User Service Agreement.
Reading this policy does not authorize all processing. Optional permissions, sensitive information, transfers to independent controllers and cross-border processing will be separately explained, with separate consent where legally required. Refusing unnecessary permissions should not affect unrelated services.
Contents: 1. Collection · 2. Permissions · 3. Cookies · 4. Third parties · 5. Storage and transfers · 6. Security · 7. Your rights · 8. Minors · 9. Updates and contact
We process information only on grounds permitted by applicable law, including service provision, security, legal duties or valid consent. Features depend on region and the actual interface. Listing a scenario does not mean it is enabled or authorized.
1.1 Registration, login and security: We process the phone number or email provided for your selected login method, code verification results, account identifier, login time, IP address, device model, system and app versions, necessary device identifiers and security logs to create and authenticate accounts and prevent theft or malicious registration. Third-party login supplies only necessary information shown in its authorization screen, not its password.
1.2 Profiles and social display: Nickname, avatar, gender, birth date, hometown, introduction, albums and posts you provide support profile display and interaction. Required fields and visibility follow the interface. Public content may be viewed, shared or saved by others. Do not disclose another person’s private information.
1.3 Messaging and audio/video: Text, images, audio, video, interaction partners and necessary message and call status and duration records support delivery, connections, billing and diagnostics. Using the service does not authorize public disclosure of private chats. Complaint handling, safety moderation or legal requests requiring content access must be limited to the necessary purpose.
1.4 Location services: Location is processed only for available features you choose and authorize, such as nearby users or regional display, as explained on screen. An approximate IP-based region differs from precise device location. Precise location requires a separate explanation of necessity and impact and consent as legally required. Refusal does not affect unrelated features.
1.5 Payments and paid benefits: Account identifiers, order numbers, items, amounts, currencies, payment status, spending and refund records support orders, delivery, reconciliation and disputes. Payment institutions process necessary payment data under their rules. Support will not ask for payment passwords or card security codes.
1.6 Identity checks and support: Account details, contact information, problem descriptions and evidence are processed when needed for identity checks, reports or appeals. Identity documents, facial data and other sensitive information are processed only when necessary for a feature, after separately explaining the processor, purpose, method and retention, and meeting legal requirements. They are not required from every user by default.
1.7 Operations and diagnostics: Necessary network status, error and crash logs and feature activity records support maintenance, troubleshooting and fraud prevention. Non-essential analytics, personalization or marketing require your choice where applicable law requires it. Security logs do not authorize arbitrary advertising use.
See the Personal Information Collection and Use List for additional details. The list must match the actual version and does not authorize inactive features or excessive collection. The linked list currently remains in Simplified Chinese pending verification and translation.
2.1 Microphone: requested when recording, speaking in rooms or calling. Camera: requested for photography, video calls or separately explained identity checks. Photos, media or storage: requested for selecting, sending or saving chosen media according to system version, preferring narrower options such as system pickers.
2.2 Location and notifications: location supports selected location features; notifications support messages and service reminders. Manage permissions in system settings. Refusal may affect only related features. Revoking permission does not automatically delete information lawfully processed earlier; you may still request deletion.
2.3 System permissions and consent to processing do not replace each other. This policy does not grant blanket permission to read contacts, SMS, call logs, calendars or a full installed-app list, or obtain strong device identifiers such as IMEI, IMSI or MAC. Actual necessity requires assessment of minimal scope, legal basis, system and store restrictions, and a specific notice when the feature is used.
2.4 Before processing precise location, facial data, identity documents or other sensitive information, we will prominently explain the purpose, necessity and possible effects, and obtain separate consent or meet another legal condition. Refusal does not affect basic functions unrelated to that information.
Web and app local storage may maintain login, language or essential settings and security. Non-essential tracking, analytics or advertising must be explained and offer legally required choices. Clearing local data in browser or system settings may log you out or reset settings, but does not delete server-side information.
4.1 Actual suppliers may support cloud infrastructure, messages and audio/video, notifications, payments or security. Processing on our behalf is limited by purpose and necessity and governed by contracts, security requirements and access controls. Sharing with independent controllers requires legally specified notice of recipient, data types, purposes and methods, and separate consent where required.
4.2 The Third-Party Personal Information Sharing List must be checked against the current release for names, functions, data scope and privacy links. Historical entries do not mean all are integrated overseas. SDK collection remains subject to feature use, valid authorization and law, not unlimited collection by accepting this policy. The linked list currently remains in Simplified Chinese pending verification and translation.
4.3 This policy does not authorize selling personal information or using private chats for external advertising. Public disclosure requires appropriate authorization or a clear legal basis. Law-enforcement and judicial requests must be verified and limited to what is necessary.
4.4 For mergers, acquisitions or business transfers involving data, we will legally notify you of the recipient and contact details and require continued protection. Changed purposes or methods require renewed notice, consent or other legally required procedures.
4.5 External sites and independently chosen third-party services have their own policies. Read them when leaving the service. Their terms do not remove our legal security and data protection duties.
5.1 The overseas project main service is deployed in AWS South America (São Paulo, sa-east-1). Information may be processed in Brazil, which may involve transfers from where you live. This does not mean all messaging, audio/video, payment, backup or SDK data is in that region. Actual provider locations and transfer mechanisms must be individually verified and disclosed before official release.
5.2 Before cross-border processing, we will meet applicable notice, impact assessment, contractual safeguards or other compliance requirements, obtaining separate consent where required. Disclosure of a deployment region is not consent to transfers to any country or recipient.
5.3 Data is retained only as needed for services or legal duties. Account details are generally retained until deletion or fulfillment of purpose; messages and media follow the feature, your deletion choices and necessary service period; transaction, security and complaint records follow performance, dispute and legal retention needs. Specific periods for each data type and supplier must be verified before release; no unverified uniform deletion period is promised.
5.4 Data is deleted or anonymized after the necessary period. Legal retention or backup rotation preventing immediate deletion requires isolation and use limited to retention and security until deletion is possible. On closure, information is handled with legally required notice.
We apply risk-appropriate transmission protection, authentication, access controls and audits, limiting access to necessary personnel and suppliers. We do not promise unverified end-to-end anonymity or absolute security. Never share passwords or verification codes.
We will promptly address and remediate security incidents, notifying affected users and authorities of the incident, possible effects and recommended actions as required by law. Lawful public announcements may be used where individual notice is impracticable.
7.1 Use profile and settings pages to access or correct available information, manage visibility and blocking, and use system settings for permissions. Contact in-app support for access, correction, deletion, copies, restriction or objection requests unavailable in the interface. Portability and other statutory rights are handled under applicable law.
7.2 You may withdraw consent for consent-based processing without affecting its prior lawfulness. Dependent features may stop, but unrelated features should not be affected. Any available personalization or marketing must explain how to disable, refuse or unsubscribe; this policy does not replace those controls.
7.3 Account deletion: use the deletion entry in app settings; its name depends on the version. Contact in-app support if unavailable. Review orders, balances, disputes and store subscriptions. Deletion does not waive statutory refunds or remedies. Cancel store subscriptions separately in the original store.
7.4 After a deletion request is verified, information is deleted or anonymized under section 5. Legal retention and backup exceptions cannot support unrelated uses. We do not promise complete deletion within a fixed number of days not verified for this project.
7.5 To prevent impersonation, identity checks may be proportionate to the request, without irrelevant information. We respond within applicable legal deadlines, explaining extensions, refusals and appeal options. You may also seek remedies from competent local data protection or consumer authorities or courts.
Only users aged at least 18 who have reached local legal majority may use the service. Minors are ineligible even with guardian consent. We do not actively solicit their information. When use by a minor is discovered or reported by a guardian, we will verify and lawfully restrict service, delete data or close the account. Safety, child-abuse and legally required records are retained and processed with restricted purposes as required by law.
9.1 Updates are published here. Material changes to purposes, data types, recipients, transfers or rights will be prominently notified, with renewed consent where required. Continued use does not imply consent to newly required authorizations.
9.2 Use in-app support for questions, rights requests, safety reports and complaints. Before official release, supply: the operator legal name, address, privacy email and an independent contact channel usable without login, when restricted or after deletion. Do not substitute another product’s company, address or email.
9.3 This is the full policy. The summary is navigation only and creates no conflicting authorization rules.