Privacy Policy

1. Who this covers

This policy covers Agaramiya (“we”), a matrimonial platform for the Tamil community, live at agaramiya.com. It applies to anyone who creates an account.

2. What we collect, and why

Only what each feature actually needs to work — nothing is collected “just in case”:

• Account: your email address and password (password is hashed by our authentication provider, Supabase Auth — we never see or store it in plain text).
• Profile: full name, whether you’re registering as a groom or bride, age, city, and an optional about-me note — used to build your profile and find matches.
• Match preferences: your preferred age range, locations, education level, and similar — used only to filter your own matching feed.
• Identity verification: with your explicit consent, we run an identity check against your Aadhaar number. We store only the last 4 digits plus a pending/verified/ failed status — never the full number, and never the raw result from the verification vendor. (Today this check runs against a placeholder mock, clearly labeled as such in the product — see the “Identity verification” section of the project README — while a real vendor integration is being set up.)
• Payments: if you subscribe to Elite, our payment processor, Razorpay, handles your card/UPI/ netbanking details directly — we never see or store them. We keep only the order ID, payment ID, amount, currency, and status, to know your subscription is active.
• Matches and messages: who you’ve expressed interest in, and the content of messages you send once a match is mutual. Messages are only ever readable by the two people in that conversation.
• Reports: if you report another member, we keep the reason you give, tied to that specific conversation, so it can be reviewed.

3. Who can see what

By default, every table in our database is locked down so a member can only ever read or write their own row — this is enforced by the database itself (Postgres row-level security), not just by the app’s screens. Other members only ever see a deliberately narrow, purpose-built slice of your profile: a masked card (first initial, age, location, verification badge) while browsing, and your full name and about-me only after a match becomes mutual — and only if they’ve subscribed to Elite. The one person who runs Agaramiya can see member profiles, verification status, and filed reports for moderation purposes — never private message content, and never gated behind the Elite subscription (that gate exists between members, not between a member and the person operating the platform).

4. Who we share data with

We don’t sell your data. It passes through a small number of service providers, each doing one specific job:

• Supabase — our database, authentication, and hosting for all the data above.
• Razorpay — payment processing for Elite subscriptions; they handle your actual card/UPI details, we don’t.
• Vercel — hosts the application itself.
• Sentry — error monitoring, so we find out when something breaks. This can incidentally capture technical details (like the page you were on) alongside an error, but is not used to build a profile of you.
• [When live] HyperVerge or Signzy — the vendor that will run real Aadhaar identity checks, once connected. Only the minimum data needed for that one check is sent to them, and per Section 2 above we only keep the result, not their raw response.

5. How long we keep it

Today, data is kept for as long as your account exists — we don’t yet have an automated retention/deletion schedule. Building one (and a self-serve export/delete flow) before real members’ data is at stake is an explicit, tracked next step — see “What’s next” in the project README. Until it exists, you can request deletion or an export of your data by emailing us (Section 8), and we’ll handle it by hand.

6. Your rights

Under the DPDP Act, you (as a “Data Principal”) have the right to access what we hold about you, ask us to correct it, ask us to erase it, and withdraw consent you’ve previously given (for example, for identity verification) — withdrawing consent doesn’t affect anything done before the withdrawal. To exercise any of these, contact us using Section 8 below.

7. Consent

Creating an account means you’ve read and agreed to this policy. Identity verification asks for a separate, explicit consent (a checkbox naming the DPDP Act directly) before your Aadhaar number is ever used, exactly as described in Section 2.

8. Grievances & contact

For any question about this policy, to exercise a right under Section 6, or to raise a grievance about how your data has been handled, contact Agaramiya’s Grievance Officer, as required under Section 8 read with Section 13 of the DPDP Act:

Vinothkumar Kannan, Founder & Grievance Officer
Email: support@agaramiya.com

We aim to acknowledge every grievance and respond within 30 days. This is Agaramiya’s general support address — not a personal address — also shown on the Support page. A dedicated grievance-only inbox may be set up separately as the platform grows.

9. Changes

If this policy changes in a way that matters, we’ll update the date at the top and, once Agaramiya has a way to message all members at once, let you know directly.