Version 2026-04 · reviewed April 2026
Privacy Policy
This policy explains how Parinay collects, uses, shares, protects, and retains information for accounts, profiles, discovery, communication, safety, support, and payments.
Processing purposes at a glance
This summary shows the main reasons Parinay uses member information and where members can control optional settings.
Authentication and account access
IdentityPerformance of a contractRequiredPhone OTP, session continuity, and basic account identity are used so members can sign in and reach protected areas of Parinay.
Data used: phone number, account identifiers, session state, security logs
Controls: Delete account, Account access help
Profile, search, and matchmaking
Member profilePerformance of a contractRequiredProfile and preference fields are used to build your member profile, show you in discovery when listed, and improve match relevance.
Data used: profile details, preferences, photos, discovery visibility
Controls: Correct profile data, Profile field visibility, Discovery visibility
Privacy, safety, and abuse prevention
Trust and safetyLegitimate interestsRequiredBlock lists, audit events, and related control state help enforce member privacy choices and investigate abuse or account misuse.
Data used: blocked members, privacy audit events, moderation-related state
Controls: Blocked accounts, Download my data, Delete account
Transactional email alerts
CommunicationsPerformance of a contractAccount and activity emails are used for sign-in support and member updates when the delivery stack is connected.
Data used: email address, notification preferences, interest activity
Controls: Notification preferences, Consent records
Critical SMS alerts
CommunicationsLegitimate interestsOptional critical SMS can be used for urgent account or safety events when enabled by the member.
Data used: phone number, notification preferences
Controls: Notification preferences, Consent records
In-app activity alerts
CommunicationsLegitimate interestsBell and dashboard alerts show pending interests and related activity inside the signed-in experience.
Data used: notification preferences, interest activity
Controls: Notification preferences, Consent records
Push activity alerts
CommunicationsConsentOptional browser push alerts use device subscription data plus your notification preference so Parinay can send immediate member activity updates when you explicitly allow them.
Data used: push subscription, notification preferences, interest activity, message activity
Controls: Notification preferences, Browser notification permission, Consent records
Interest digest preference
CommunicationsLegitimate interestsYou can prefer no digest, daily digest, or weekly digest for interest summaries once delivery channels are active.
Data used: notification preferences, interest activity
Controls: Notification preferences, Consent records
Optional browser preference storage
Cookies and storageConsentLocal browser storage can remember display density, saved searches, sidebar state, and similar convenience settings when the member allows it.
Data used: browser-side preference keys, saved search shortcuts, interface preferences
Controls: Cookie and storage settings, Cookie policy, Download my data
Performance diagnostics logging
Cookies and storageConsentOptional Core Web Vitals console logging may be enabled for product diagnostics when both the site setting and the member preference allow it.
Data used: performance metrics, browser-side diagnostic events
Controls: Cookie and storage settings, Cookie policy, Download my data
Contextual sponsored content
AdvertisingLegitimate interestsParinay may show clearly disclosed sponsored placements using the page context only, such as the current route, search topic, or a safe placement category. These placements do not require profile-based targeting.
Data used: page context, placement metadata, aggregated ad performance
Controls: Cookie and storage settings, Cookie policy, Privacy policy
Personalized sponsored content
AdvertisingConsentWhen you turn this on, Parinay may use limited profile and discovery context such as city, profession, or current search filters to choose more relevant sponsored placements.
Data used: cookie preference, profile city, profession, current discovery filters
Controls: Cookie and storage settings, Consent records, Cookie policy
Ad measurement and reporting
AdvertisingLegitimate interestsParinay records sponsored-placement impressions and clicks so campaigns can be reconciled, brand-safety rules can be reviewed, and advertisers can receive aggregate reporting.
Data used: placement id, campaign id, event type, page path, signed-in member id when available
Controls: Cookie policy, Privacy policy, Download my data
Marketing email opt-in
MarketingConsentOptional product news, tips, and partner-style updates by email stay off unless you explicitly enable them.
Data used: email address, marketing preference
Controls: Notification preferences, Consent records, Download my data
Marketing SMS opt-in
MarketingConsentOptional promotional SMS remains off unless you explicitly enable it and may involve carrier rules or charges.
Data used: phone number, marketing preference
Controls: Notification preferences, Consent records, Download my data
Privacy controls
Parinay keeps practical privacy controls for account data, profile visibility, cookies, retention, and support requests.
Governance and ownership
The standalone product now names a privacy lead route, legal escalation path, and product/platform ownership for privacy changes and incident handling.
RoPA and data inventory
A machine-readable record-of-processing snapshot tracks systems, categories, recipients, purposes, retention references, and transfer references for the current feature set.
Record of processing snapshot
The privacy policy and operations materials publish the current purpose register, lawful basis labels, member controls, and high-level data categories wired into the standalone build.
Incident and breach readiness
Operational guidance names the privacy contact channel, expected first-response steps, and the distinction between product support, security triage, and any future formal breach notification workflow.
Retention and deletion controls
Member-facing delete account, export, consent history, rights workflow, retention disclosures, and a retention sweep script are linked together so erasure behavior is understandable before launch.
Vendor and subprocessor visibility
The standalone product publishes its current vendor inventory, activation state, DPA expectations, and transfer notes while legal review matures.
Privacy review gate
New features, vendors, or high-risk automations must go through the DPIA-lite checklist before launch so notices, retention, and access-control changes are not missed.
Current retention schedule entries: 7.
Current RoPA entries: 6.
Location-based discovery is opt-in. Members can stay at city-only matching or explicitly save an approximate or more precise current-location refine for nearby search, and they can switch that setting off later from discovery controls.
Sponsored placements are contextual by default. Personalized sponsored placements use limited in-product signals only when a signed-in member explicitly enables that setting from Cookie and storage settings.
Terms and privacy review →Privacy hub →Cookie and storage settings →Terms of Use →Contact →Cookie policy →Data partners →Retention schedule →Cross-border transfers →Help center →← Home