How Codecore handles website and membership information.

Pre-production privacy candidate · version v1-candidate-2026-10-12. Covers the public corporate website, membership accounts, security controls, KYC, support email and payment data when payment is enabled.

Pre-production legal candidate — owner approval pending

Prepared 12 October 2026 to match the current Codecore corporate website and membership architecture. This wording is not represented as legal-counsel-approved. Public paid launch requires owner approval, a final refund/cancellation policy, age/guardian eligibility where relevant, retention decisions and review of applicable legal requirements.

Scope and current website practices

The corporate pages provide public information. The membership area supports registration, email verification, account security, profile records, private uploads, eligibility/KYC workflows and administrator review. Public paid checkout remains disabled until separately approved. The website does not intentionally install advertising cookies or optional analytics trackers, and it has no live URUTOKEN Radar connection or wallet connection.

Information you provide

Account registration may collect full name, email address, mobile number, country and consent acknowledgements. Member profiles may include date of birth, nationality and residence/address details. Mandatory membership KYC may include legal name, date of birth, nationality, residence/address, a private photo/selfie and an approved government photo ID. Support enquiries may include the information you choose to send by email. Do not send passwords, banking passwords, card PIN/CVV, OTPs, wallet recovery phrases or document passwords.

Authentication and account security

Supabase Auth handles password credentials; Codecore application tables do not store plaintext passwords. Account sessions use essential authentication cookies over HTTPS. Device trust stores a hash of a random essential cookie together with coarse browser/operating-system labels rather than an invasive hardware fingerprint. Rate-limit and abuse-prevention records use hashed or bounded identifiers. Security events and authorized administrative actions may be logged for protection and auditability.

Membership, eligibility and KYC records

Membership records may contain plan, status, dates and benefit eligibility. Tuition or Radar entitlement records do not by themselves connect the member to Arivon, Classplus or a private Radar service. KYC documents and selfies are stored in private storage and accessed through controlled server-side or short-lived signed access. KYC review is an internal eligibility and risk-control process and does not amount to government certification.

Payments

The payment foundation is disabled until approved launch steps are completed. If Razorpay is enabled, Razorpay handles checkout while Codecore may store order/payment references, plan/price/tax snapshots, amount, currency, status and verification time. Codecore application tables are not designed to store card numbers, CVV or banking passwords. A final refund/cancellation policy must be approved and published before public paid checkout is enabled.

Why information is used

Information may be used to create and secure accounts, verify email, maintain member profiles, assess eligibility/KYC, provide approved membership benefits, prevent abuse and fraud, respond to support enquiries, maintain audit records, process verified payments when enabled, and operate and secure the website. Information should not be used for unrelated advertising or profiling without a separate approved basis and notice.

Service providers and international processing

Current technical providers may include Supabase for authentication/database/private storage, Vercel for website hosting and delivery, Zoho for company email delivery, Cloudflare Turnstile for bot/security challenges, and Razorpay for payments when enabled. These providers may process technical or account information under their own service terms and infrastructure, which may involve processing outside your state or country. Provider configuration and data flows must be reviewed before production approval.

Hosting and technical logs

Hosting, authentication and security providers may process technical information such as IP address, request time, requested path, browser/device information and security signals to deliver, diagnose and protect the service. Codecore should limit retained technical information to what is reasonably necessary for operations, security, dispute handling and applicable obligations.

Retention and deletion

No final universal retention schedule is asserted in this candidate. Account, KYC, payment, audit, security and support records may require different retention periods. Before production approval, Codecore must document practical retention/deletion rules, including any records that must be preserved for security, disputes, accounting or applicable legal obligations. Backups and provider logs may not disappear immediately when an account-facing record is deleted.

Privacy requests

Depending on applicable law and the circumstances, you may have rights concerning access, correction, deletion, restriction or other handling of personal information. Contact the company using the official email to make a privacy request. Identity verification may be required before releasing or changing protected account information.

Children and guardian considerations

Codecore operates education-related ventures, but this membership/KYC candidate does not yet establish a complete child-account or guardian-consent policy. Public launch must define age eligibility and guardian requirements wherever minors may use an account or submit personal/KYC information.

Security

Codecore uses layered controls including email verification, restricted database access, private storage, rate limiting, bot protection, trusted-device controls and stronger administrator authentication. No online system can guarantee absolute security, and users should protect their credentials and report suspected account compromise promptly.

External sites and future services

External links lead to independently operated websites with their own terms and privacy practices. New analytics, social login, wallets, connected Radar services, additional payment providers or other material integrations require a separate privacy and security review before activation.

Questions, requests and updates

Contact Codecore Network Private Limited (CIN U66190KL2025PTC097996) at contact@codecorenetwork.com. Registered/operating office: NO. 331/B, 331/C, Near Kadhriya Juma Masjid, Tanur Nagaram, Tirur, Malappuram - 676302, Kerala, India. Approved notices may be updated when website practices or services change; material service changes may require updated terms or fresh consent.

Start a meaningful conversation.

Contact Codecore Network about ventures, technology and partnership opportunities.

contact@codecorenetwork.com Contact details