Privacy Policy
How Yuvia collects, uses, and protects your personal information across matching, messaging, and account settings — written for members and visitors alike.
Effective date: 8 October 2026
Introduction
What this Policy covers and how it applies when you use Yuvia.
This Privacy Policy (“Policy”) explains how Yuvia (“we”, “us”, or “our”) collects, uses, stores, discloses, and protects personal information when you visit our website, create an account, build a matrimony profile, search for matches, send or receive interests, chat with connections, contact support, or otherwise use our matchmaking platform and related services (collectively, the “Service”).
Please read this Policy carefully together with any terms you accept when you register. By creating an account or using the Service, you acknowledge that you have read this Policy. If you do not agree, please do not use the Service.
Who this Policy applies to
- Visitors who browse public pages such as the landing page and this Privacy Policy.
- Members who register for a matrimony account and use discovery, messaging, and settings.
- People who contact us through support or email about privacy or safety.
Key principles
- We collect information that is needed to run a trustworthy matrimony Service.
- We do not sell your personal information.
- Your email address and phone number are not shown on your public match profile card.
- You can control discovery, photo visibility, online status, and read receipts in Settings.
- Human moderation reviews profiles and photos before full discovery access.
- Yuvia is for adults only — you must be at least 18 and legally eligible to marry.
Who we are
How Yuvia works as a private matchmaking platform.
Yuvia is a digital matrimony and matchmaking Service designed to help adults find compatible life partners with privacy, consent, and safety built into the product flow.
What the Service includes
- Account registration and secure sign-in.
- Detailed member profiles, partner preferences, optional kundli (horoscope) details, and photo galleries.
- Match recommendations and search based on profile and preference data you provide.
- Interests and connections: messaging opens only after a connection is formed (for example, after an interest is accepted).
- In-app chat between connected members, plus a support conversation with our team.
- Privacy controls for discovery, photos, online presence, and read receipts.
- Safety tools such as block, report, and staff moderation of profiles, photos, and reports.
- Optional browser push notifications for messages and other account activity.
Because matrimony involves sensitive personal and family information, we combine product controls with staff review. Profiles and photos typically pass through moderation before they become fully discoverable to other members.
Information we collect
Categories of personal and technical data processed by the Service.
We collect information in three ways: (1) information you provide directly; (2) information generated by your use of the Service; and (3) limited technical and device data required to operate, secure, and improve the Service.
Account and identity information
- Full name as entered at registration and on your profile.
- Email address used for sign-in and account notices.
- Phone number associated with your account.
- Password (stored only in hashed form; we cannot read your plain password).
- Account status (for example active, suspended, or deleted) and related administrative timestamps.
- Optional public username you choose after your profile is approved.
Profile, preference, and kundli information
When you complete your matrimony profile you may provide personal, family, education, career, lifestyle, and location details. Exact fields can evolve with the product, and typically include items such as:
- Profile context (for example, whether the profile is for you or a family member) and candidate name where applicable.
- Gender, date of birth / age, marital status, height, religion, mother tongue, caste or community details where provided.
- Country, state, and city.
- Education, institution, employment type, occupation, and income band where disclosed.
- Family type, family values, and related family information you choose to share.
- Diet, smoking, and drinking preferences.
- About / bio text and other free-text fields you enter.
- Partner preferences such as preferred age range, height, religion, location, education, and other criteria you set.
- Optional kundli details (for example rashi, nakshatra, manglik status, and birth time) used for compatibility features when both members have provided the needed information.
Photos and media
- Profile photographs you upload, including processed variants used for display.
- Photo order, primary photo selection, and moderation status (pending, approved, rejected).
- Photo privacy settings (who may view approved photos) and whether downloads are allowed under platform rules.
- Rejection reasons or moderation notes needed for review and support.
Privacy and discovery choices
- Discovery visibility (for example everyone eligible, matching-only with a minimum match percentage, or hidden from discovery).
- Photo visibility and download preferences.
- Whether other members may see your online status and last seen time.
- Whether read receipts are shared in chats (mutual, WhatsApp-style behaviour).
Matching, social, and messaging activity
- Interest requests you send or receive, their status (pending, accepted, declined), and related timestamps.
- Connection relationships created after mutual acceptance.
- Conversation metadata and message bodies exchanged with another member.
- Read pointers used for unread counts and, when enabled, read receipts.
- Profile views: when an eligible member opens your profile, we may record that event.
- Blocks you place on other members, and reports you submit about content or behaviour.
- Support threads and messages between you and our staff team.
Presence, notifications, and device data
- Last-seen timestamp derived from activity while you use the member app (for online indicators).
- In-app notification records (for example interest received, profile approved, profile viewed).
- Push device tokens if you enable browser or device notifications.
- Approximate technical data such as IP address, browser type, and device characteristics used for security, session management, and diagnostics.
- Server and application logs that may include identifiers needed to investigate errors or abuse.
Information we do not collect today
- Payment card or bank account details through the core Service (if paid plans are added later, payments will be processed by a compliant provider and this Policy will be updated).
- Precise continuous GPS tracking of your movements.
- Third-party advertising profile data for selling ads against your matrimony profile.
If you provide information about another person (for example when creating a profile on behalf of a family member), you confirm you have authority to share that information and that it is accurate.
How we use your information
Purposes for which personal information is processed.
We use personal information only for purposes that are connected to operating a safe, functional matrimony Service. We do not use your profile content to sell advertising to third parties.
Provide and operate the Service
- Create, authenticate, and maintain your account and sessions.
- Display and update your profile, preferences, kundli, photos, and username.
- Power matches, search, compatibility scoring, and discovery according to your settings and eligibility.
- Deliver interests, connections, chat, support messaging, and unread indicators.
- Show online status, last seen, read receipts, and profile-view notices according to product rules and your privacy toggles.
- Send transactional communications such as moderation outcomes, security or account notices, and service messages.
- Receive issues and feature requests you choose to send, show them to authorised staff, and return a reply to you.
Safety, trust, and moderation
- Review profiles and photos for authenticity, policy compliance, and community safety.
- Investigate reports, blocks, and suspected abuse, fraud, or impersonation.
- Suspend, restrict, or remove accounts or content that violate our rules or create risk.
- Maintain audit records of important administrative and safety actions.
Security, reliability, and improvement
- Protect accounts with hashed passwords, access controls, and abuse monitoring.
- Diagnose outages, bugs, and performance issues using logs and technical telemetry.
- Improve product design and matching quality using aggregated or de-identified insights where practical.
Legal and organisational purposes
- Comply with applicable laws, regulation, and lawful requests.
- Establish, exercise, or defend legal claims, and protect the rights, property, and safety of members, the public, and Yuvia.
- Support business continuity, backups, and (if applicable) corporate transactions under appropriate safeguards.
Profile moderation and verification
How staff review works and what becomes visible after approval.
Yuvia uses human moderation to reduce fake, misleading, or unsafe profiles. Before a profile is fully available in member discovery, authorised staff may review the information you submit.
What moderators may see
- Profile sections and free-text fields you submit for review.
- Photos awaiting approval or already approved, including variants used for display.
- Partner preferences and kundli details associated with your account when relevant to review.
- Prior revision history needed to understand what changed since the last decision.
Possible outcomes
- Approval: your profile (or photo) becomes available according to product rules and your privacy settings.
- Rejection: you are informed and may need to correct information or replace a photo before resubmitting.
- Further review or take-down: previously approved content may be removed if new concerns arise.
Identity locking after approval
After approval, certain identity-related fields may be locked so they cannot be casually changed. This reduces impersonation and helps other members trust what they see. Editing moderated text or photos can return content to a pending-review state.
Moderation decisions are recorded for operational accountability. Staff access is limited to authorised roles with permissions for profile and photo review.
Photos and media
Upload, review, visibility, and download controls for your images.
Photos help members recognise and trust one another. They are also sensitive personal data, so they are moderated and governed by privacy settings you control.
Upload and processing
- You may upload profile photos subject to size, format, and content rules set by the platform.
- We may create resized or cropped variants so photos display correctly across devices.
- Photos typically remain pending until a moderator approves them for member viewing.
Who can see your photos
In Settings (and from your profile photos tools) you can choose photo privacy. Depending on product options, this may include limiting approved photos to eligible members generally, or only to people you are connected with. Unapproved or rejected photos are not shown to other members as approved gallery content.
Downloads and misuse
- You may be able to allow or disallow downloads of your approved photos according to platform settings.
- Even when downloads are restricted, other members may still view photos they are permitted to see on screen. Technical measures reduce casual saving but cannot prevent all screenshots.
- Using another member’s photos outside the Service without permission may violate our rules and applicable law. Report misuse to support.
We may remove photos that violate community standards (for example explicit content, stolen images, or misleading media). Moderation history may be retained for safety and dispute handling.
Discovery and profile visibility
How other members find you and what they can see on your card.
Discovery controls whether you appear in Matches and Search. They do not delete your account; they change how findable you are.
Discovery options
- Visible to eligible members: you may appear in discovery for members who meet product eligibility rules (for example approved profiles of the appropriate audience).
- Matching only: you may appear only when mutual compatibility meets a minimum match percentage you choose.
- Hidden: you are not shown in Matches or Search discovery, while existing connections and other product areas may still work according to rules.
What other members typically see
- Display name / identity presentation as designed by the product (which may shorten surnames for privacy).
- Profile details you have filled and that are eligible for display after approval.
- Approved photos according to your photo privacy setting.
- Compatibility information derived from preferences and kundli where available.
- Online status and last seen only if you allow them.
What other members do not see on your profile card
- Your login email address.
- Your phone number.
- Your password or session tokens.
- Staff-only moderation notes and internal audit logs.
Staff using the admin tools may access additional account information as needed for support, moderation, and safety, under role-based permissions.
Matching, interests, and messaging
How interests, connections, and chat use your information.
Matching and search
We use profile and preference data you provide to suggest compatible members and to filter search results. Compatibility scoring may consider criteria you set and, when both parties have kundli details, traditional matching factors. Scores are decision-support tools, not guarantees of suitability.
Interests and connections
- You may send an interest to another eligible member.
- The recipient is notified and can accept or decline.
- When an interest is accepted, a connection is formed and member-to-member chat becomes available.
- Interest and connection history is stored so both parties and (where needed) support can understand the relationship state.
Member chat
- Messages are stored so you and the other participant can view conversation history.
- Unread counts rely on read pointers that advance when you open and mark messages as read.
- Push notifications for new chat messages are designed as data notifications that do not place the message body on the lock screen.
- A block by either member stops further messaging both ways through the Service; the product may present this without revealing unnecessary detail to the blocked party.
Support messaging
You may message the support team from the member app. Staff with support permissions can read those threads to help you. Support messages are also retained for quality, training of authorised staff, and safety follow-up.
Online status, last seen, and read receipts
Presence signals and chat ticks, including how to turn them off.
Online status and last seen
While you use the member app, the Service may periodically record a last-seen timestamp (for example from an activity heartbeat). That timestamp is used to show whether you appear online and when you were last active.
- Default: other eligible members who can see your profile may also see online status and last seen.
- If you turn off “Show when I’m online” in Settings, other members will not see your online indicator or last seen time.
- Turning the setting off does not stop the Service from recording activity privately where needed for product functions (for example keeping your own session experience consistent).
Read receipts
Read receipts (double ticks) show when the other person has read messages up to a certain point. Behaviour is mutual, similar to common messaging apps:
- If both members keep read receipts on, each can see when the other has read messages.
- If either member turns read receipts off, neither side sees read ticks in that relationship context.
- Unread conversation counts still update when you read messages, even if receipts are hidden.
- When receipts are on, a silent push may refresh open chat windows so ticks update without showing a system notification banner.
Profile views
When viewing a profile is recorded and how you are notified.
When an eligible member opens your profile, we may record a profile view. Views help members understand who is interested and are part of the social layer of the Service.
How views work
- A view may create or update a record linking the viewer and the profile owner.
- You may receive an in-app notification (and push, if enabled) according to product rules — for example when someone views you for the first time or again after a period.
- You can open a “Who viewed me” style list in the member app, subject to product availability and eligibility.
- Self-views and failed or unauthorised opens are not treated as meaningful views.
Limits and safety
- Blocks can hide views both ways so blocked relationships do not continue to surface through view lists.
- Suspended or ineligible accounts may drop out of view lists until restored.
- View events are rate-limited on the server to reduce abuse and accidental spam.
Blocking, reporting, and safety tools
How you and our team respond to unwanted or harmful behaviour.
Blocking
- You can block another member from your account tools where available.
- Blocking is intended to stop further contact and reduce visibility between the two accounts according to product rules.
- Block records are stored so the restriction remains effective across sessions.
Reporting
- You may report messages or other concerning behaviour to our team.
- Reports typically include the reason you select, optional details you write, and references to the content involved.
- Authorised staff review reports and may take action such as warning, content removal, suspension, or further investigation.
Meeting check-in
- You may save one trusted contact (a name and email address) so we can email them after an in-person meeting you planned with a connection.
- After the meeting time, we ask you once if you are home safe. If you have notifications turned on, we send that question as a notification. If you say you need help, or you do not answer within two hours, we email only your trusted contact.
- That email includes your name and that you had a meeting. It does not include the other member’s name, profile, or messages.
- The other member cannot see your trusted contact or your answer. You can change the contact in Settings. You can remove it when you have no open meeting.
- After you confirm you are home, you may privately choose to continue or not. If you choose not to continue, the other member is not told.
- If you both choose to continue, you may each share one family contact: a name, how they are related to you, and a phone number or email. That contact is shown only to the other member, and only after both of you choose to continue. You can remove it later.
If you believe you are in immediate danger, contact local emergency services first. Yuvia is not an emergency response service.
Cookies, local storage, and devices
Browser storage, sessions, branding cache, and push tokens.
We use cookies and similar technologies that are necessary to provide the Service. We do not operate a third-party advertising pixel network as part of the core matrimony product.
Essential and functional storage
- Authentication cookies or tokens that keep you signed in securely.
- Preferences such as colour mode (light / dark).
- Cached branding information (app name, logos, footer text) so public pages load consistently.
- Security features that protect forms and sessions against common web attacks.
Push notification devices
- If you enable notifications, we store a device push token linked to your account.
- Tokens are used to deliver data-only or notification payloads for chat, interests, moderation outcomes, and similar events.
- Signing out may remove the browser’s device registration associated with that session.
- You can revoke notification permission in your browser or operating system at any time; we will stop delivering to tokens that are invalid or unregistered.
You can clear cookies and site data in your browser. Doing so may sign you out and reset local preferences.
When we share information
Who can receive your data and under what conditions.
We do not sell your personal information. We share it only as described below.
Other members
Other members see information according to your discovery settings, photo privacy, connection status, and presence/receipt toggles. They never receive your password, and they do not see your email or phone on the standard profile card.
Authorised staff
Employees or contractors with role-based permissions may access account, profile, photo, chat (when investigating reports or providing support), and moderation data as needed to operate the Service. Access is limited by permission and logged for sensitive administrative actions where the product records audits.
Service providers
- Hosting, storage, and database providers that run the application infrastructure.
- Push notification providers (for example Firebase Cloud Messaging) that deliver alerts to your devices.
- Email or SMS providers if used for account or security messages.
- Professional advisers (legal, security) under confidentiality obligations when required.
Providers are expected to process personal information under contractual terms that require appropriate security and use only for providing services to us.
Legal and safety disclosures
- When required by applicable law, regulation, court order, or governmental request.
- To protect the rights, safety, or integrity of members, the public, or Yuvia, including investigating fraud or harm.
- In connection with a merger, acquisition, financing, or sale of assets, subject to continuity of protection and notice where required.
Data retention
How long we keep information and what happens on account deletion.
We retain personal information for as long as needed to provide the Service, maintain safety, resolve disputes, enforce our policies, and comply with legal obligations.
While your account is active
- Profile, preference, kundli, photo, messaging, interest, view, and settings data remain available for the product features you use.
- Logs and security records may be kept for a rolling period appropriate to investigation and reliability needs.
When an account is suspended or deleted
- Suspension may restrict access while preserving data needed for review and restoration.
- Deletion (including soft deletion by administrators) removes or restricts normal use of the account. Associated identifiers such as usernames may be released according to product rules.
- We remove or anonymise personal data that is no longer required, subject to backups and legal holds.
- Limited records may be retained longer when necessary for safety, fraud prevention, dispute resolution, or legal compliance (for example audit logs of moderation actions).
Backup systems may retain residual copies for a limited time until they rotate out according to our backup schedule.
Security
Technical and organisational measures that protect your data.
We implement technical and organisational measures appropriate to the sensitivity of matrimony data. No method of transmission or storage is completely secure, but we work to protect your information against unauthorised access, alteration, disclosure, or destruction.
Measures we use
- Encrypted transport (HTTPS) between your browser and our servers.
- Hashed password storage; passwords are never stored in plain text.
- Session-based authentication with revocation on sign-out and certain security events.
- Role-based access control for staff tools (permissions for members, profiles, photos, support, settings, and reports).
- Audit logging of sensitive administrative and profile changes.
- Validation, rate limiting, and abuse controls on sensitive endpoints (for example search, profile views, username checks).
- Push payloads for chat that avoid placing private message text on device lock screens.
Your responsibilities
- Choose a strong, unique password and do not share it.
- Sign out on shared devices.
- Keep your email and phone recoverable so we can reach you about security or moderation issues.
- Report suspected unauthorised access to support immediately.
If we become aware of a personal data breach that requires notification under applicable law, we will take appropriate remedial steps and notify affected members and authorities as required.
Your choices and rights
Controls in the app and how to make privacy requests.
Depending on where you live, you may have rights under applicable data protection laws (for example rights of access, correction, erasure, withdrawal of consent, or grievance redressal). We honour those rights as required by law.
Controls available in the Service
- Edit profile sections, partner preferences, and kundli details (subject to moderation and identity locks).
- Upload, reorder, or delete photos; change photo privacy and download preferences.
- Change discovery visibility and minimum match threshold.
- Show or hide online status / last seen.
- Turn read receipts on or off (mutual effect).
- Choose or change your username when eligible.
- Block members and submit reports.
- Manage push notification permission in the browser or device.
- Sign out to end the current session and clear associated device registration where applicable.
Requests outside the app
For access, correction, deletion, or other privacy requests you cannot complete yourself, contact us using the details in Contact us. We may ask for information reasonably needed to verify you are the account holder before acting. We may refuse or limit a request where the law allows (for example where fulfilling it would adversely affect others’ rights, ongoing investigations, or legal obligations).
Children’s privacy
Age requirements and what we do if a minor registers.
Yuvia is a matrimony Service for adults. You must be at least 18 years old to create an account. You must also meet any higher minimum age of marriage that applies to you under the laws that govern you.
- We do not knowingly collect personal information from anyone under 18.
- Registration requires you to confirm that you are 18 or older and accept our terms and this Policy.
- Profile date-of-birth rules enforce gender-specific minimum ages consistent with applicable marriage-age rules used by the product.
If you believe a person under 18 has created an account, contact us immediately. We will investigate and delete or disable the account and related personal information as appropriate.
Where information is processed
Hosting locations and cross-border processing.
The Service is operated with a primary focus on members in India and may be accessed from other countries. Personal information may be stored and processed on servers and by service providers located in India and in other jurisdictions.
- Infrastructure and database hosting may be in one or more regions chosen for reliability and latency.
- Push and email providers may process device tokens or message metadata in their operating regions.
- Staff providing support or moderation may access information from the locations where they work, under access controls.
Where cross-border transfers occur, we take steps designed to ensure an appropriate level of protection consistent with this Policy and applicable law.
Changes to this Policy
How we notify you when the Policy is updated.
We may update this Privacy Policy to reflect product changes, legal requirements, or operational improvements.
- We will revise the effective date at the top of this page when the Policy changes.
- For material changes, we may provide additional notice in the Service (for example an in-app notice) or by email when appropriate.
- The updated Policy applies from the effective date stated on this page unless a later date is specified.
We encourage you to review this page periodically. Continued use of the Service after an update constitutes acceptance of the revised Policy to the extent permitted by law.
Contact us
How to reach Yuvia about privacy questions or requests.
If you have questions about this Privacy Policy, want to exercise a privacy right, or need to report a privacy or safety concern, contact us:
- Email: support@yuvia.com
- Suggested subject: “Privacy request – Yuvia”
- In-app: Messages → Support (after you sign in)
- Include the email address on your account and a clear description of your request so we can respond efficiently.
We aim to respond to verifiable privacy requests within a reasonable period and within any timeline required by applicable law.
This page is provided for transparency. It does not replace any separate terms you accept when you create an account. Last updated 8 October 2026.