Operator and scope
Operator: Identity not yet published.
Privacy contact: Not yet published.
Publication requirement: operator identity and working contact details must be supplied before public launch. Do not submit sensitive information until you know who operates the service.
This notice describes the current application. Before public deployment, the operator must confirm its hosting arrangements, lawful basis, consent process, retention schedule and grievance contact, and obtain appropriate legal/privacy review. This template is not a claim of compliance with every applicable law.
Information collected
- Registration and profile information: name, sex, date/time/place of birth, contact details, addresses, physical details, education, occupation, caste/religion, diet, marital status, languages, family details, references and photographs.
- Partner expectations, preferences and medical-history text. Share only what is necessary; “None” or “Not applicable” may be used where true. Obtain permission before providing another person’s references, contact details or photographs.
- Account and security information: username, a salted password hash, encrypted authenticator secret, sessions, one-time CAPTCHA records and deletion-confirmation records. Passwords are not stored as plaintext.
- Application reviews, interests and decisions, notifications, saved search criteria, relevant audit/security records and deletion reasons. IP addresses may be processed for rate limiting, auditing and hosting/security logs.
Why information is used
Administrator reports also use minute-level signed-in member activity to calculate an hourly online average. Visible member tabs send a heartbeat every 30 seconds; authenticated API requests count as activity too. These records contain an internal account ID and minute, not browsing content or page history. Only aggregate reports are exposed. Activity is removed on profile deletion and records older than the rolling hour are pruned on the next API request; backups may retain older copies.
To process applications, authenticate accounts, review profiles, calculate age eligibility, provide search and saved criteria, manage interests and notifications, protect the service against misuse, and maintain administrator-only business and security records. We do not guarantee compatibility, identity, marriage outcomes or the absence of fraud.
Who can see information
- Unauthenticated visitors cannot browse member profiles.
- Active, approved members with completed numbered profiles may browse limited eligible opposite-sex profiles and their photographs.
- While an interest between two members is accepted, both can view each other’s full member details: contact information, exact addresses, references, medical history and family contacts. Acceptance is a deliberate sharing action. Rejection, pending or withdrawal ends future full-detail access unless another accepted interest remains.
- Administrators can review applications, private profile records and the read-only Deleted Profiles archive. Password hashes, authenticator secrets and session credentials are not displayed to other members.
- The operator may need hosting/technical providers and may disclose information where legally required. The operator must publish the actual provider, processing-location and cross-border arrangements before public launch. No advertising or analytics integration is included in this build.
Restrict what you share. We cannot retract screenshots, downloads or information already copied by another person, and no technical system can guarantee absolute confidentiality.
Cookies and security checks
Essential HttpOnly, SameSite=Strict cookies maintain sign-in and bind the registration security question to your browser. Authentication sessions have limited lifetimes; the CAPTCHA cookie/challenge lasts up to ten minutes and each question permits one attempt. This build does not include advertising cookies, third-party CAPTCHA tracking, SMS verification or automated email delivery.
Security and photographs
Access controls protect private records and photographs. Supported uploaded images are decoded, resized, re-encoded and stripped of metadata. Authenticator secrets are encrypted, passwords are salted and hashed, and sessions can be revoked. Use HTTPS in a public deployment. These measures reduce risk but do not make the service breach-proof or certify uploaded material as safe.
Retention and Delete Profile
Delete Profile is an archive operation, not complete erasure. After a selected reason and reconfirmation, live profile/account records and related communications are moved to an administrator-only, read-only Deleted Profiles archive. Normalized photographs are preserved in that archive. Member-facing interests and notifications involving the deleted account are removed, and all its sessions are revoked. Security credentials are destroyed or revoked rather than exposed in the archive.
This build has no automated purge, fixed archive-expiry period or self-service restoration. Existing backups may still retain older data. The operator must define and publish specific retention periods and lawful grounds for retention before public launch; a request for erasure must be assessed under applicable law rather than assumed to be satisfied by the archive button.
Your choices and requests
You can edit your profile except its locked name, sex and permanent profile number, manage saved searches, choose interest decisions, withdraw interests and initiate profile deletion. For correction of locked information, access, erasure, consent-related requests or complaints, contact the privacy contact above. The operator must verify identity securely and handle requests under applicable law; do not post identity documents or medical evidence into public-facing profile text.
Age and policy changes
The service is not for children: women must be at least 18 and men at least 21, and applicants must be no older than completed age 65. Report suspected underage accounts to the operator. Material changes to collection, sharing, fees or retention should be clearly notified before they apply, and consent obtained where required. This policy must be updated when the deployed service changes.