How we handle data
Privacy Policy
H1BShaadi is a free matchmaking service for H-1B professionals and partners. This policy describes the personal information the product collects, why it is used, who can see it, how long it is kept, and which processors help run the service. It is a product description, not legal advice, and it does not claim certification under any privacy framework.
Last updated September 2026.
Who this applies to
This policy covers the H1BShaadi website and the account, profile, discovery, connection, messaging, and safety features on it. It applies to visitors, people who create an account, and members who use matchmaking features.
H1BShaadi is operated as a small production service. If you have a privacy or data-control question, email support@h1bshaadi.com.
Categories of information we collect
Account and authentication data: email address, password (handled by Supabase Auth, not stored as a recoverable password in application records), Google sign-in identifiers when you choose Google, and session cookies. Application identity rows store the Auth user id and email so profiles and safety records can be linked.
Profile and matchmaking data: display name, date of birth (used to derive age), gender, who you are seeking, marital status, religion or Prefer not to say, optional mother tongue and additional languages, location (country, state or region, and city), job title and optional company (company is visible after a mutual connection), career and education details, visa or immigration status bucket, destination and immigration goals, relocation plans, optional height, optional bio and values, and an optional profile photo.
Preferences: the partner criteria you mark Required or Preferred, including age range, location, visa, education, career, religion, language, height, and future-plan filters.
Interactions: connection requests and their status, plain-text messages between mutually connected members, blocks, and reports (category plus optional details).
Safety and moderation data: blocks, reports, moderator decisions, notes, and account suspension or restoration history. Reporter identity and internal notes are not shown to the reported member.
Technical data needed to run the site: cookies used for the signed-in session, and standard hosting logs that a processor may retain. The product does not infer location from IP address for matching.
Why we collect it
We use this information to create and secure your account, show a labeled profile, apply inspectable matching rules, deliver connection requests and messages, enforce blocks and reports, and operate an internal moderation console for authorized reviewers.
We do not sell member profiles, and this product does not use advertising trackers or AI scoring. Matching is rule-based and inspectable from the preferences you save.
Visibility rules
Signed-in members can see member-safe profile fields: display name, derived age, gender, marital status, disclosed religion, disclosed languages, location, job title, education context, visa or status, destination and immigration goals, bio, values, photo only when you mark it visible to members, and height only when you mark it visible to members. Exact company or employer name is not member-safe.
After both people accept a connection, each person can also see company name, plus height or a photo you hid from discovery. A hidden photo stays visible only to you. Login email is never treated as contact information. Exact date of birth stays private to you.
Visitors who are not signed in do not see other members' profiles. Blocking, unmatching, or ending a connection immediately removes connection-only access. Private owner fields, passwords, session tokens, storage identifiers, internal user ids, reporter identity, and moderator notes are not exposed to other members.
Third-party processors
Supabase provides authentication (email/password and Google) and, in deployed environments, Postgres storage for application records. Session cookies are written by the application through Supabase Auth helpers.
Vercel hosts the production website and serverless handler. Google is used only if you choose Continue with Google.
These processors receive the data needed to provide their service. The application does not send profile photos or matchmaking fields to advertising or scoring vendors.
Retention, pause, and deletion
You can pause discovery so other members no longer see you, while your account, profile, and existing connections remain until you unpause or delete.
If you confirm account deletion, the product immediately anonymizes your profile, deletes your photo, ends connections, and removes message bodies you sent or received. Matching preferences are removed. You are signed out and cannot use that account again.
Safety records are treated differently: blocks, reports, and moderation history are retained with your internal user id so abuse investigations are not erased by deletion. Those records are not shown as a live member profile. Authentication identity in Supabase Auth may remain until an operator completes a later cleanup; the application blocks sign-in after deletion.
If you want a copy of the account data we can assemble, email support@h1bshaadi.com. Export is handled as a support request, not an automated download.
Your controls
Signed-in members can review visibility labels on the profile form, pause or resume discovery, change a password, request a reset, and delete the account from Account. Help explains how those controls work.
You can also block or report another member from discovery, connections, or a conversation. Community Standards describe conduct we ask members to follow.
Also see Privacy, Terms, Community Standards, and Help.