Legal
Privacy Policy
This policy explains how SubhPhere handles information when you contact us or use our personally assisted matrimonial service.
Full policy
Website: shubhphere.in
At a glance
- Initial enquiry: We ask for basic details so our representative can contact you.
- Later service stages: We explain the information needed for requirements, agreed checks and introductions before collecting it.
- Profile sharing: Relevant details are shared for an introduction with permission. Profiles are not published in a public directory on this website.
- Privacy questions: Contact us through the privacy contact listed in section 11.
This summary is consistent with the detailed policy below. It does not replace the full policy or confirmed operational practices.
1. Who this policy covers
SubhPhere (sample operating name — replace with legal entity), operating as SubhPhere, is responsible for the information handled through https://shubhphere.in/ and the service activities described here.
This policy applies to people making enquiries, people seeking a match, and family members or references whose information is used in the service.
Business / contact address: SubhPhere [Sample] 12 Example Road, Andheri West Mumbai, Maharashtra 400053 India
The privacy and grievance contact is identified in section 11. This policy describes this agency’s handling. Separate providers (for example hosting, email or messaging apps) may process information under their own terms when you use their services.
2. Information we collect and why
The initial website enquiry form does not request biodata, identity documents or payment details. Information needed later is explained at that stage.
| Information | Purpose | When it is collected |
|---|---|---|
| Initial enquiry details: full name, mobile number, city, who the enquiry is for (Myself / Son / Daughter / Sibling / Other), and optional preferred callback time. | To respond, understand the enquiry and discuss service availability and next steps. | When the enquirer submits the website callback form (Fluent Forms enquiry form). |
| Submission and permission records: the enquiry consent response, submission identifier, source page URL, and technical submission metadata kept by the form system (including approximate IP address, browser and device information). | To manage enquiries, document the request and operate the form appropriately. | On form submission. Entries are stored in the form plugin database and also appended to a protected enquiry CSV file on the website server. |
| Later profile and requirement information: background and preference details requested during onboarding if you choose to proceed. | To understand requirements and consider introductions. | Only if the person chooses to proceed, after the relevant explanation and permission. This is not collected on the public website form. |
| Agreed verification information: photographs, stated location details, necessary verification evidence and check notes, limited to the methods explained for that stage (photo, location and family-reference checks described on the site). | To carry out and explain the agreed checks. | During the separately explained verification stage — not through the initial website enquiry form. A normal photograph review for matching a person to a photo is not described here as biometric processing. |
| Family-reference information: the nominated person’s contact details, relationship and information they provide for the stated reference purpose. | To contact the reference and understand relevant details they can confirm. | Through the agreed reference process, with appropriate notice and permission for that person too. |
| Service communications: enquiry messages and service communications we actually retain (for example email or messaging threads with our team). | To respond, coordinate agreed steps and handle questions or complaints. | When you communicate with us about an enquiry or service matter. |
| Technical information: server and form logs as described above. This public theme does not load separate advertising or analytics tags. Logged-in WordPress administrators also receive standard WordPress session cookies needed to use the admin area — that is separate from visitor enquiry behaviour. | Security, reliability and operation of the website and form. | Automatically when you use the website or submit the form. Optional YouTube or Vimeo embeds, if enabled later for consented videos, may set their own cookies when a visitor plays a video. |
Other systems that may also hold enquiry-related information: taff email + WhatsApp Business
Call or video recording: Not by default; ask before any recording
3. Enquiries for someone else and your permission
If you enquire for a family member, use your own contact details for the first conversation. The person seeking a match must agree before their profile details are shared or an introduction is arranged. A family enquiry does not give us unrestricted permission to use another person’s information.
Permission to contact you about an enquiry is separate from permission for later verification, sharing a profile, publishing a testimonial or sending promotional messages. We explain the relevant use before asking for permission where it is required.
Browsing this website or reading this policy is not blanket consent for every use of personal information. Nominating a family reference does not by itself authorise every use of that reference’s own information — we still need appropriate notice and permission for that person.
The website callback form asks you to confirm that you agree to be contacted about the enquiry and that you have read this Privacy Policy. Form email notifications may be configured by the agency; currently they can be enabled or disabled in the form settings without changing the fields collected.
4. When information is shared
We share information only as needed for the purposes below:
- Authorised people in our team who handle enquiries and agreed service activities.
- Service providers that help us run the website and form — currently including the WordPress hosting environment and the Fluent Forms plugin that stores submissions. Additional email, CRM, messaging or verification providers will be listed here once confirmed: WordPress host + Fluent Forms (confirm countries before go-live)
- A prospective match and agreed participants in an introduction, limited to the information the person has agreed to share for that introduction.
- Authorities or other recipients where disclosure is required or otherwise legally permitted for a specific purpose, subject to applicable requirements.
Profiles are not published in a public directory on this website. The representative explains what information will be shared for an introduction and with whom. Raw identity or address evidence is not automatically included in a profile summary shared with a prospective match; sharing follows the permissions explained for that step.
If you withdraw permission, we will stop the relevant future use where we can. We may not be able to erase copies already lawfully disclosed to another person or held independently by a service provider under their own obligations. We will explain the outcome when you ask.
[CONFIRM: no sale of personal information / no advertising data sale — or disclose any secondary commercial use that exists]
5. Third-party tools, cookies and processing locations
| Tool / category | Purpose | Information handled | Notes |
|---|---|---|---|
| WordPress website hosting | Serve the site and store content | Pages, media, technical logs | WordPress host + Fluent Forms (confirm countries before go-live) |
| Fluent Forms (enquiry form) | Collect and store callback enquiries | Form fields, consent, IP, browser/device, source URL, timestamps | Stored in the WordPress database as form entries. |
| Enquiry CSV export (theme) | Operational backup of callback enquiries | Submitted enquiry fields, consent, source URL, timestamps | Saved under a protected uploads directory (not publicly listed). |
| Self-hosted theme fonts | Display typography | No third-party font CDN request for theme fonts | Loaded from the theme assets. |
| YouTube / Vimeo (optional) | Show consented work videos if configured | May include player cookies / device data when a video is played | Not required for the enquiry form. Uses privacy-enhanced YouTube embed URL when configured. |
| Phone, email or WhatsApp links | Let you contact us directly if those details are published | Handled by your device and the provider you choose | Opening an external channel is different from an embed that loads before you click. |
Essential site functions (pages, form, security logs) are separate from optional analytics or advertising. This theme does not currently load a separate analytics or advertising tag. We do not treat continued browsing alone as consent to every possible future use.
Processing locations: WordPress host + Fluent Forms (confirm countries before go-live)
We do not guarantee India-only storage from the website domain alone. Cross-border arrangements will be described here once confirmed.
6. How long information is kept
We keep information for the purposes described in this policy and for applicable record-keeping requirements. Retention depends on the type of information and whether the service or a related issue is still active.
| Record type | Retention / deletion |
|---|---|
| Enquiries that do not proceed | Up to 12 months, then delete/anonymise |
| Active and inactive profile / service records | During engagement + up to 24 months |
| Raw verification evidence vs check outcome notes | Up to 90 days after check (notes may stay with service record) |
| Permission records, complaints and legally required transaction records actually held | Up to 7 years / as law requires |
| Notification copies, technical logs and backups | ~30–90 days (host/form schedule) |
Deletion must be operationally possible across the systems that actually hold the data. Backups may take longer to clear than live records. Justified exceptions will be explained when you make a request.
7. How information is protected
We use organisational and technical measures appropriate to a small assisted-matchmaking practice. Confirmed controls for this deployment: HTTPS, need-to-know staff access, WP/host controls
Known site-level practices today include HTTPS for the published site (when enabled by hosting), WordPress admin access limited to authorised users, and a server-protected directory for the enquiry CSV. A lock icon on this page does not by itself prove security.
If we become aware of a personal-data incident that requires notice under applicable law, we will follow the notice process required at that time and use the privacy contact in section 11. We do not invent a fixed public response deadline here beyond what law and our workflow confirm. Acknowledge in 3 working days; substantive reply in 30 days
8. Your choices and privacy requests
You can contact us to ask about information you have provided, request correction, ask us to stop contacting you about an enquiry, withdraw permission for a relevant use or request deletion. We explain the outcome and any applicable limits or record-keeping requirements.
If information needed for a particular service step is not provided, or permission is withdrawn, that step may not be possible. That does not create permission for unrelated uses.
Use the privacy contact in section 11 — not the matrimonial callback form — for privacy requests. We may ask for a proportionate check before disclosing or changing personal information. We do not require a new matchmaking signup or marketing consent to raise a privacy request, and we do not demand identity documents by default.
This website does not provide an online privacy dashboard, instant automated erasure or an automated data-export download. Requests are handled by our team through the contact channel below.
[LEGAL REVIEW: statutory rights, escalation routes and timeframes applicable on the publication date (SPDI transition / DPDP as then in force) — do not import foreign-law right lists]
9. Adult service and information about children
Our matrimonial service is intended for adults. Please do not submit a child’s profile or documents for matchmaking. If you believe information about a child has been provided to us, contact the privacy contact below so we can review it.
This describes the service scope. It is not a statement that every adult is legally eligible to marry. Parental consent is not treated as permission for child matchmaking.
10. Policy updates
We may update this policy when our practices or applicable requirements change. The updated version will show its effective date and revision date. Where a change requires a new notice or permission, we will provide it before using information for that new purpose.
A policy update is not automatic consent to new verification, profile sharing or promotional uses. Revision history is kept through the site’s normal content workflow.
11. Privacy contact and grievances
Contact us about your information.
Please describe your concern and provide a way to contact you. Share only the information needed to identify the enquiry or service record. We may ask for a proportionate check before disclosing or changing personal information.
Do not use the matrimonial “Request a callback” form for privacy requests. That form is for service enquiries and includes contact consent for that purpose.
Canonical policy URL: https://shubhphere.in/privacy-policy/