Privacy Policy

Marriage Profile ("we", "us") is operated by an individual based in Ahmedabad, Gujarat, India. This policy explains what happens to personal data on marriageprofile.in. It describes what the service actually does today, and we update it when the product changes.

What we collect

Your account

When you sign up we store your email address and name. If you sign in with Google we also receive your profile picture. Optionally, you may add a phone number, date of birth, city and state in your settings, along with your notification preferences and, once you buy a plan, which plan you hold and when you bought it.

We also record how you first found us, once, when you sign up: for example a search engine, a shared link or a campaign, together with the first page you landed on. For a site that sent you, we keep its domain only, never the full address of the page. Until you sign up, this is kept only in your browser's storage.

Your biodata

A marriage biodata is, by its nature, a detailed personal document, and we store what you put into it. That includes your name, age, height, location, phone number, email, marital status, education, occupation, employer, income, social media handles, family details (parents' names and occupations, siblings, address), religion, caste, surname, gotra, birth date, birth time and birth place, manglik status, rashi, nakshatra, mother tongue, dietary and lifestyle details, what you write about yourself, your partner preferences, and any photographs you upload.

We also keep a version history of your edits so you can revert, and the username you reserve for your profile link.

People who view a profile

This is the part most policies skate over, so we will be plain about it. When someone opens a public profile, we record their IP address on our server, along with the city, region, country, postal code, timezone and continent that we derive from it. We use the IP address to count a visitor only once per day and to resolve an approximate location. We also record how they arrived: through a link shared on WhatsApp, the QR code, the PDF, a search engine or another site, read from the short tag on the link they followed or from the site that sent them (its domain only). If they open one of the profile's social media links, we record which platform it was, not the link itself.

The profile owner never sees the IP address or the postal code. They do see the city: the owner is notified when someone opens their profile, in a message such as "Someone from Rajkot, Gujarat viewed your biodata profile", and on paid plans their analytics dashboard breaks views down by region and city, shows how many arrived by each route and how many opened each social link, and lists recent views with the city and time of each. The service does not tell the owner who a viewer is, and does not identify individual viewers to anybody except the site operator, who can see the underlying records.

If you view a profile, you have not signed up for anything, and you can contact us at the address below about the data we hold on you.

Messages and collaborators

If someone sends an enquiry through a profile's contact form, we store the name, email, phone number and message they provide, and email it to the profile owner. If you invite a family member or collaborator, we store their email address and their role. If you contact us through the contact form, we store and email what you send.

If you subscribe on our blog

The sample biodata on our blog is a plain download. It asks for nothing, and taking it tells us nothing about you beyond an ordinary page visit.

Subscribing is the separate, deliberate thing. If you give us your email address there, we store that address and when you subscribed, send you the sample to start with, and then write only when there is a new guide worth reading. You can leave by replying to any of those emails. These addresses are not shown to anyone else, and are never sold or shared for anybody else's marketing.

Analytics and device data

We use Google Analytics, PostHog and Vercel Analytics to understand how the site is used. These record standard web data such as pages visited, approximate location, device and browser, and the site you arrived from. We also use Microsoft Clarity, which records how visitors move through pages (clicks, scrolling and what is on screen) as session replays and heatmaps, so we can see where the site is confusing. If you enable push notifications, we store a notification token for your device.

Who else receives your data

We rely on the following providers, each of which has its own privacy policy:

• Google Firebase — sign-in and our database, where your account and biodata are stored
• Vercel — hosting, and site analytics
• Cloudinary — the photographs you upload
• Razorpay — payments. Card and banking details go to Razorpay directly and never reach our servers
• Google Gemini — the AI writing assistant and biodata translation. If you use either, the relevant text from your biodata is sent to Google to be processed
• Google Analytics, PostHog and Microsoft Clarity — usage analytics, and session replays in Clarity's case
• Our email provider — delivering enquiry notifications, collaborator invitations, and any other email notifications you leave switched on

We do not sell your personal data, and we do not share it for advertising.

Who can see your profile

You choose. A published profile can be public, so anyone with the link can open it, or password-protected, so only people you give the password to can. Your view password is stored encrypted, never as plain text, and you can change or remove it whenever you like.

Search engine indexing is a separate setting on each biodata and it is off by default. A new biodata does not appear in Google unless you turn that on. Password-protected profiles are never indexed, and their link previews are stripped of personal details so nothing leaks into a search result or a chat preview.

You can also turn off PDF downloads and the contact form on any profile. One thing we cannot do is control what someone does after you have given them access: a person who can open your profile can screenshot it or pass the password on.

Deleting your data

You can delete your account from your settings at any time. Deletion is a genuine cascade rather than a flag: it removes your profile, every biodata you created, your version history, your reserved username, your notification tokens, your family and collaborator records, and the enquiries sent to you. We do not keep a copy.

You can also delete a single biodata and keep your account. That removes the biodata along with its version history, the enquiries it received, the records of who viewed or shared it, and its translated copies.

Three things survive, and we would rather say so. Records that identify no one in particular, such as aggregate view counts, may remain. Our payment provider keeps its own transaction records, because it is required to. And the username in your profile link stays retired, so that nobody else can ever claim it: a link that someone saved or forwarded must never open another person's biodata. We keep only a one-way fingerprint of the username, not the username itself, with no account attached, and the old link says the profile was removed.

Security

Traffic is served over HTTPS. View passwords are encrypted. Access to your account requires a verified email address or a Google sign-in, and our database rules stop one user from reading another's data. No service can promise perfect security, and we are not promising it here.

Children

This service is meant for adults arranging a marriage. It is not intended for anyone under 18, and we do not knowingly collect their data.

Changes

When the product changes, this page changes with it, and the date at the top moves. Material changes will be noted on the site.

Contact

Questions about your data, or a request to see or delete it, go to marriageprofile.in@gmail.com. You can also use the contact form. We are based in Ahmedabad, Gujarat, India.