← Policies & support

Privacy policy

What unoConn collects, why we use it, who can see it, and your choices.

1. Who we are

UNOCONN (OPC) PRIVATE LIMITED operates unoConn. This policy covers our website, mobile and web apps, and account, community, event, booking, social and Host services. Our registered address and privacy contact appear below.

Information you provide directly to an organiser, venue, payment provider or external website is also subject to that service’s privacy practices. This notice describes unoConn’s processing; it does not make every organiser or external service part of unoConn.

2. Account and participation information

We collect information you provide to create and use an account: names, email address, phone number where provided, sign-in credentials or linked provider identifiers, date of birth, gender, interests, photograph and bio. Private account-setup details such as date of birth and gender are distinct from the public profile.

Depending on your activity, we process memberships, invitations, follows, posts, photos, comments, reactions, event or community messages, read receipts, reports and support correspondence.

Registration records can include participant names, contact details, age, locality, event choices, bookings, passes and attendance. If you register another person, tell them how their information will be used and obtain the necessary authority and permission.

3. Payments and Host verification

Payment records include amounts, order and transaction references, payment/refund status and relevant booking details. Hosts may provide account-holder, bank-account and IFSC details for payout setup. Payment authentication happens through the checkout or payment provider. Never send a UPI PIN, card PIN, CVV, password or OTP in email or chat.

Host onboarding can collect identity-document images, extracted identity details, a profile photograph, live selfie images, verification results and location. The supported identity flow includes Aadhaar-card information. Facial comparison and liveness checks help verify the applicant; they are not advertising functions.

Identity and financial records can include sensitive information. Submit them only through the designated onboarding flow. Contact us to ask about, correct or withdraw permission for this processing; withdrawing information needed for verification may prevent Host access. This notice does not promise immediate deletion of verification images or records. Verification is not a guarantee of an organiser’s qualifications or event safety.

4. Location, device and usage information

With device permission, location supports nearby discovery and relevant location-based features. You can also search manually. Saved addresses, event pins and Host verification can involve more precise location information than a city or neighbourhood. Device permissions can be revoked in your operating-system settings.

Requests can include IP addresses, device/browser details, timestamps, errors and security activity. Push delivery uses notification tokens when enabled. Browser and app storage supports preferences, recent searches and authentication; external sign-in and payment services may use their own cookies or storage.

unoConn records first-party recommendation impressions and interactions, including content identifiers, position and interaction time, to operate and improve discovery. This is different from cross-app advertising tracking. We currently do not use advertising/tracking SDKs, sell personal information or share it for targeted advertising.

5. Why we use information

We use information to create and secure accounts, verify contact details, provide discovery and recommendations, manage memberships and bookings, deliver passes and messages, support payments and Host verification, answer support requests, and investigate fraud, abuse and security incidents.

Service activity also helps maintain reliability and improve features. Verification codes and booking updates are service communications, distinct from optional marketing. We do not currently send user posts or conversations to generative-AI services. Automated Host identity/face checks are separate verification functions described above.

We will explain material changes to these purposes and obtain additional permission where required. Information needed for one feature should not be treated as unrestricted permission for unrelated use.

6. Visibility and sharing

Other users can see the profile and content you make available to them. Community, event and conversation visibility depends on the feature, membership and permissions. Other users may copy content they can see; do not post identity documents or private financial/contact details publicly.

Organisers and authorised staff receive participant and booking information needed for the relevant event, membership or check-in. That information must not be used for unrelated marketing or disclosure without the necessary permission.

Providers support hosting/storage, authentication, maps, transactional email, notifications, payments and verification. Our integrations include Google Cloud/Firebase, Google Maps services, Brevo for email, and Apple/Google/Expo notification services. Checkout identifies the payment service used. Information is shared for the relevant service function.

We may disclose information when required by law or valid legal process, or as necessary to investigate fraud, protect safety or enforce our terms. A business transfer may involve relevant records, with appropriate notice and safeguards.

7. Security and processing locations

We use access-controlled services and protected network connections. Protect your credentials and devices and report suspected compromise promptly. No service guarantees absolute security; this policy is not a claim of a particular certification.

Providers may process information in India and other countries. We do not promise India-only storage. Transfers of sensitive information must meet applicable legal requirements and appropriate protections.

8. Retention and deletion

Retention depends on the record and its purpose: account/profile records support your account; transaction records support payments, refunds and accounting; verification records support identity and fraud checks; and security/complaint records support investigations and legal obligations. Sensitive information should not be kept longer than needed for its permitted purpose or a legal requirement.

Request account deletion through our account-deletion page or support email. We may verify ownership and identify unresolved bookings, payments, disputes or legal requirements. Closure does not mean every record is immediately erased: limited legally required records, backups, and copies independently held by other users or organisers may remain.

Ask us about retention for your specific records. In responding to deletion requests, we will explain applicable exceptions and reasons. We do not advertise an unverified fixed deletion deadline.

9. Your choices

Contact us to request access to information you supplied, correction, withdrawal of consent or deletion. We may verify ownership without asking for passwords or OTPs. We will explain the rights and exceptions applicable to your request under the law in force.

You can decline optional permissions or adjust notification settings. A feature may become unavailable if you withhold information necessary for that feature. You can still contact support about your records.

10. Age and children’s information

unoConn accounts are for people aged 18 or older. People under 18 must not create accounts. Contact our Grievance Officer if you believe an under-18 person has created an account or provided information improperly, so we can investigate and take appropriate action.

Account eligibility is separate from an event’s participant eligibility. An adult account does not automatically authorise submission of a child’s information. Child participation requires an appropriate authorised process and necessary parent/guardian permissions. Contact the organiser and unoConn before supplying such information if the process is unclear.

11. Grievances and updates

Anita Panda is our Grievance Officer. Use the details below with the subject “Privacy grievance” and enough information to identify the concern. Do not email passwords, OTPs or identity-document images in the initial message. We will handle complaints within the timelines applicable to their type, including the one-month period applicable to sensitive-personal-information grievances.

We may update this policy as the service or law changes. The date identifies this version. Material changes will be communicated appropriately and additional consent obtained where required.

Contact & grievance officer

UNOCONN (OPC) PRIVATE LIMITED

Block No. G-607, 6th Floor, Aparna Cyberzon, Serilingampally, Lingampalli, K.V. Rangareddy – 500019, Telangana, India

Grievance Officer: Anita Panda

unoconn.admin@unoconn.com
+91 6280849196

Do not send passwords, OTPs, UPI PINs or identity-document images in an initial support message.

Back to unoConn →