EnthiosHub — KYC & Identity Verification Policy

Operating Entity: [ENTITY LEGAL NAME] · Version: 1.0 · Effective: [EFFECTIVE DATE] · compliance@enthioshub.com

This Policy explains how identity and bank verification ("KYC") is performed for Organizers who receive payments, and how related data is handled. It forms part of the Organizer Agreement and the Privacy Policy.

1. Purpose#

KYC helps prevent fraud, money laundering, and misuse of the Platform, and is required to enable Organizer settlements.

2. Who Must Complete KYC#

Any Organizer who wishes to publish paid Events and receive settlements must complete KYC before publishing and before any payout.

3. How KYC Is Performed#

3.1. KYC is performed by the Company's Payment Partner (Razorpay), an RBI-regulated payment aggregator, as part of connected-account onboarding. The Payment Partner collects and verifies the identity, business, and bank details required under Applicable Law.

3.2. The Company does not itself collect or store Organizer Aadhaar numbers, PAN, or bank-account documents for payment KYC. The Company stores only a verification status flag and the Payment Partner's account reference, together with limited audit metadata (timestamps, actor, IP for security/audit).

3.3. Where the Company conducts any limited supplementary checks (e.g., verifying an email/phone via OTP, or confirming an educational institution or organization), it collects only the minimum data necessary and retains it per the Data Retention Policy.

4. Data Protection#

4.1. Any verification data the Company holds is processed in accordance with the Privacy Policy and the DPDP Act, stored securely with encryption for sensitive fields and access controls, and disclosed only as permitted by law.

4.2. Identity/verification data is retained only as long as necessary and, where held, is subject to expiry (e.g., re-verification after a defined period).

5. Consequences of Non-Verification or Failure#

5.1. Organizers who do not complete KYC cannot publish paid Events or receive settlements. Failed or suspicious verification may lead to hold, review, or suspension per the governance workflow.

6. Ongoing Monitoring#

6.1. The Company and Payment Partner may re-verify or request updated information where risk indicators arise, or as required by law.

7. User Verification#

7.1. Attendees may be required to verify email and/or phone (via OTP) to secure their account and complete registration. This is not financial KYC.

---

Review by a licensed advocate recommended before publication. This Policy assumes payment KYC is delegated to Razorpay; if you ever collect Aadhaar/PAN directly, this Policy and the Privacy Policy must be substantially revised for Aadhaar Act compliance.