Scope and operator
This Privacy Policy explains how Hola handles information across its mobile app, messaging, Discover, Nearby, stories, subscriptions, Hola AI, and its website and business promotion tools. The Terms of Use describe your contractual responsibilities; reading this notice does not itself authorize optional processing.
Operator: Jakkireddy Sanjeev Reddy, operating as Hola: Chat & Discover. Business address: 1-28,Madhura Nagar, B.N Reddy Nagar, Hyderabad, Telangana 500112. Privacy and support: Hola Support Team — support@holamingle.com. Grievance officer: Jakkireddy Sanjeev Reddy — support@holamingle.com. Account holders can also contact us through Profile → File a Complaint → Privacy Request; website advertisers can reply to their enquiry response.
Account, profile and information you provide
- Phone number and country code, account identifiers, sign-in and verification records; email address, email verification status and communication preferences when you add an email.
- Display name, biography, profile photos, interests and contacts you add. Dating profiles also include a private birth date, calculated public age, gender, preferences, prompts, photos and other fields you choose to complete.
- Sensitive information may be inferred from dating preferences or content you choose to share. Avoid unnecessary sensitive details; you can edit optional profile fields or disable dating. Optional sensitive processing requires a separate valid legal basis or consent where applicable.
- Stories, follows, interests, skips, connection invitations and accept/reject decisions; date arrangements, private feedback and safety check-ins you choose to create.
- Reports, appeals, support requests and business enquiries, including contact details, promotional creative, business location, offers and advertising budget.
Private conversations, public content and verification
Message text and chat attachments are encrypted on your device before transmission; Hola stores and routes encrypted payloads. Routing metadata remains visible. Recipients can save or disclose content after decryption. Device compromise can expose it. The current encryption does not provide Signal-style forward secrecy or cloud key recovery.
Profiles, dating photos, published stories and sponsor promotions are service-visible content and can be reviewed for moderation. Stories are distributed through the backend to eligible followers; visibility is subject to follow, block and moderation controls.
Verification uses privately submitted government-issued ID and a challenge selfie/video for age and identity review. When configured, self-hosted CompreFace compares your face with profile photos; liveness and ID age eligibility require authorised review. These checks can be wrong and do not guarantee safety. Raw submissions are removed after a decision; pending submissions expire after seven days. Verification consent can be withdrawn in Privacy Center; queued deletion retries if storage is temporarily unavailable.
Government-ID and selfie/video verification requires a separate signed electronic release before capture. Automated face geometry comparison, when enabled, is limited to matching your submission with your profile photos. Raw submissions and application face scores are destroyed after a decision or seven-day expiry. Provider templates, logs and backups must follow the approved destruction policy; automated processing remains unavailable until those safeguards are approved.
Usage, devices, payments and network data
- Conversation participants, message identifiers, type and size, timestamps, delivery/read state and reactions; call participants, status, duration and connection/signaling information.
- IP/network information, authentication/security events, device and notification tokens, presence and operational logs. WebRTC calls use encrypted transport; independently verified end-to-end encrypted calls are not claimed.
- Subscription tier, entitlement and trial status, store/product identifiers, transaction and renewal records, and billing-provider references. Payment providers process payment credentials; Hola does not need full card details for app-store purchases.
- Campaign submissions, confirmed advertising payments, offer claims, claim codes, redemption state and promotion interactions needed to operate business features.
Location, distance, travel and incognito
With your permission and location sharing enabled, Hola processes precise coordinates to calculate nearby results. Nearby user responses provide distance rather than user coordinates; user profiles are shown in a list and only sponsors appear as map pins. Distances use meters/kilometers for Indian users and miles for US users. A displayed distance can still reveal approximate proximity.
Dating uses an approximate search center to recommend eligible profiles. Travel mode uses the chosen search location and does not verify physical presence. Incognito limits discovery exposure according to the feature settings; it does not hide your account from Hola, existing interactions or people to whom you send interest.
Business map coordinates and addresses are intended to be displayed publicly. Revoke location permission or disable sharing to stop further device-location updates; this does not automatically erase previously stored location data.
Why we process information and legal grounds
- Provide accounts, messaging, calls, profile discovery, follower feeds, date arrangements and features you request: contract performance or another applicable service-delivery basis.
- Verify accounts, protect infrastructure, prevent spam and investigate abuse: legitimate interests where recognized, legal obligations and other applicable safety grounds.
- Process purchases, entitlements, offer claims and business promotions: contract performance, accounting obligations and payment security.
- Send OTP, welcome, connection acceptance, trial-expiry, subscription and renewal emails: account administration and service delivery. Optional discovery and sponsored-place emails use your marketing preference and consent where required.
- Process optional permissions, sensitive profile information or marketing: consent where required. You can withdraw applicable consent; withdrawal does not undo lawful prior processing.
- Respond to lawful requests and protect legal rights: applicable legal duties or legitimate legal interests. The available grounds depend on the jurisdiction and actual processing.
Recommendations, promotions and Hola AI
Discover recommendations use eligibility, preferences, location and interaction data; subscription features can affect filters, boosts, priority and ranking. These recommendations do not certify identity or compatibility. Safety reports do not trigger automatic bans based on report volume; staff decide enforcement and consider appeals.
Nearby promotions use business location and campaign eligibility. Campaign selection does not return your precise location to advertisers. Offers and redemptions involve information needed by the business to honor the offer. Subscription badges may identify your effective Plus, Premium or Elite tier to other users.
Hola AI receives questions and recent turns you deliberately submit, including from the website widget, and forwards them to the configured inference provider, currently Groq. It does not automatically read your private conversations. Do not submit secrets, unnecessary sensitive information or another person’s private data. Provider processing and retention follow its applicable terms.
Advertising SDK processing and personalized ads are optional and off by default. Turn off Personalized ads and advertising sharing in Privacy Center to stop AdMob requests. Additional Google regional privacy choices are available when applicable. First-party sponsored listings may remain visible.
Reports, selected messages and urgent review
A reporter can explicitly consent to submit up to five selected decrypted text messages, with a preview before sending. Those copies become readable by authorized trust reviewers and are stored separately with encryption, restricted access and an access audit. The rest of the conversation is not opened to staff. Reports can omit messages.
Reported text is recipient-submitted evidence: Hola checks message metadata but cannot independently prove that the submitted plaintext is authentic. Staff assess credibility and context. Report descriptions and case metadata are separate from encrypted evidence and may contain information provided by either party.
Child-safety, credible-threat and sexual-exploitation cases enter restricted urgent triage. Human reviewers may preserve evidence and make legally appropriate disclosures. Recording a referral does not automatically contact authorities. Local scam/link warnings run on the device and do not upload message contents or automatically report users.
Anyone, including a person without a Hola account, can request removal of nonconsensual intimate images or digital forgeries through the public removal form. Provide location details, contact information, authority, good-faith declarations and an electronic signature; do not send the intimate image. Keep the private receipt to read the status and decision. Valid requests receive urgent review; reviewers remove qualifying content and known identical copies under Hola control. Recipient device copies and encrypted messages have technical limits.
Public-content removals by authorized reviewers preserve restricted encrypted copies of media hosted by Hola for 180 days, subject to longer scoped legal holds. Remote creative bytes that Hola does not host require separate preservation review. Only audited trust reviewers can retrieve retained evidence.
Who receives information
- Other users receive profile fields, permitted presence/read status, approximate distance, interests and content you choose to share, according to feature settings. Email addresses and private birth dates are not public profile fields. Phone numbers may be visible in contact/profile flows; Hola is not an anonymous service.
- Eligible followers receive published stories. Chosen trusted contacts receive the safety-check-in details you authorize; publishing or sharing cannot prevent recipients from retaining copies.
- Configured infrastructure, storage, SMS, email, notification, payment, subscription, network relay and AI providers receive data necessary for their functions. Examples supported by this build include Cloudflare, Google Cloud/Firebase, MongoDB, Redis, Twilio, Resend, Apple/Google stores, RevenueCat, Stripe, Razorpay, Groq and configured object-storage/TURN providers; actual deployments may use only some of them.
- Authorized staff receive support and moderation data appropriate to their roles. Authorities or other recipients may receive necessary information under valid legal process, applicable duties or an appropriate safety basis. A business transfer may involve necessary data with applicable safeguards.
- This build does not implement sale of personal information or third-party cross-context behavioral-advertising sharing. Sponsored placements are not a promise that all future advertising practices will remain identical; material changes require updated disclosures and applicable choices.
Storage, cookies and international processing
The app uses device storage for encrypted history, authentication and preferences. The website uses browser storage for features such as locally saved votes and business sign-in; necessary authentication/security technologies support account functions. The website does not include a third-party behavioral-advertising tracker. The mobile app uses the separate advertising choices described above. Future optional tracking requires appropriate notice and choices.
Providers may process information outside your country. Applicable transfer requirements and provider contracts must be assessed for each deployment; this policy does not certify that a particular international-transfer mechanism has been executed.
Retention and deletion
Routine report evidence normally expires after 90 days. A documented statutory report or legal order can require a longer bounded hold. Account deletion does not erase open or legally preserved safety cases. Stored face-match scores are removed with verification submissions after a decision or expiry.
- Selected message evidence is retained for 90 days; documented reviewer preservation can extend it to at most 180 days from collection. Access is denied after expiry, and database cleanup may occur later. Backup copies follow the backup lifecycle.
- Stories cease being available after 24 hours; expired story-media cleanup runs separately. Pending verification submissions expire after seven days; decided verification material is removed.
- Messages with a configured expiry expire under that setting; other encrypted messages, profile and interaction records follow the account and service lifecycle. Deleting local history does not necessarily delete server records or recipient copies.
- Account deletion anonymizes the account and removes or disables supported records; it is not a promise of instantaneous deletion of every object, legal record or backup. Billing, security, moderation and other records may require separate retention.
- General case metadata, enforcement history, transaction records and backups do not all have fixed automated deletion periods in this build. The operator must publish the completed retention schedule before treating this notice as the final release policy.
Your controls and privacy requests
Edit your profile, manage email marketing preferences, unsubscribe from optional emails, disable dating/location, change privacy settings, block users and request account deletion through the available app controls. Cancelling a subscription is separate from deleting an account.
Depending on applicable law, you may request access, correction, deletion, a portable copy, restriction or objection, withdrawal of consent, and review or appeal of a denied request. These rights are subject to lawful exceptions; we may verify account control and an authorized agent’s authority without requesting unnecessary sensitive information. Submit a Privacy Request through Profile → File a Complaint.
Where applicable, EEA/UK users may complain to their supervisory authority; Indian users may use applicable data-protection grievance mechanisms; US-state residents may have additional request, appeal and non-discrimination rights. These options depend on which laws apply to Hola and do not replace mandatory local rights. People unable to sign in may contact Hola Support Team at support@holamingle.com. Grievance officer: Jakkireddy Sanjeev Reddy.
Privacy Center provides cursor-paginated JSON exports for listed account-owned records. Sensitive export pages require a recent phone sign-in; ordinary login remains persistent. You may appeal your own rejected request; final decisions require recorded identity/authority and fulfillment evidence. Public parent, agent and consumer requests are available without an account.
Age limits and children
Hola is an adults-only service: all account features, messaging, dating and date planning require age 18 or older. Self-declaration alone is not proof of age. Accounts confirmed under 18 are restricted. Parental consent does not permit use of this adults-only service. Contact the privacy contact for erasure or correction requests if you cannot sign in.
If you suspect a child is using dating or identify exploitation, use Child Safety reporting and avoid uploading illegal imagery. We will assess the report and take appropriate protective action. The operator must confirm its general-app eligibility and child-consent process for each launch market.
The service is for adults. Protected account features require adult onboarding, and communications additionally require the current rules/safety notice. A declaration is not proof that every user is an adult. A parent or guardian may request review/removal of a child’s data through the public request form. We verify authority and preserve only applicable legal exceptions.
Security, updates and contact
We use encryption, authentication, access controls and audits as described above. No security measure guarantees that a device, account or service cannot be compromised. Use a device passcode, protect OTPs and review suspicious identity-key changes.
This version is dated October 7, 2026. Material changes require appropriate notice and any fresh consent required by law. Updated publication dates alone do not replace a notice or consent process. For requests, use the contact routes under Scope and operator.
India privacy choices and requests
Use Profile → Privacy Center to review the versioned notice, choose processing purposes, withdraw consent, see your account-data summary, submit access/correction/erasure/grievance requests, and manage a nominee for death or incapacity. Optional discovery, location, verification and AI purposes are separate. We target a response within 30 days; published grievance timelines must not exceed applicable legal limits. Requests may require identity or authority verification and lawful retention can limit erasure. The Data Protection Board complaint route is available as applicable after our grievance process.
Consent withdrawal stops future processing for the withdrawn purpose. Turning a purpose back on does not automatically re-enable discovery or device permissions. Core withdrawal stops ordinary authenticated API/socket use when privacy enforcement is enabled; Privacy Center and account deletion remain available. Recipient copies are outside our control. Minimum lawful record retention, documented legal holds, vendor erasure and backup expiry require the operator’s approved retention schedule.
India processing must be grounded in valid consent or a specifically applicable legitimate use under the DPDP Act; generic contract or legitimate-interest language is not an independent DPDP legal basis. Provider agreements, transfer restrictions, incident notification and retention requirements must be reviewed before deployment. Placeholder operator contacts are not valid release contact details.