Instran
Draft for owner/legal approval before production launch.
Instran processes student profile details, verification statuses, masked payment references, tutor links, payment orders, payout/refund states, wallet activity, support tickets, notifications, audit logs, and provider callback receipts needed to operate the marketplace.
Card references use provider tokens and masked display values. Raw card numbers, CVV values, PAN, Aadhaar, full bank account numbers, passwords, JWT signing keys, provider credentials, and callback secrets must not be stored in unsafe UI output or logs.
Information is used for onboarding, KYC status tracking, verified tutor payment, service-fee and invoice records, payout/refund operations, support workflows, fraud prevention, auditability, and regulatory or operational reporting.
Production KYC, card tokenization, payment, payout, refund, and notification providers must be approved before launch. Provider-specific privacy terms, retention rules, and callback handling must be attached to the release signoff pack.
Retention periods for student, tutor, financial, audit, provider, and support records must be approved by the business, finance, legal, and security owners before production launch.
The production support email, escalation path, and grievance/contact details must be configured and approved before this page is published for live users.