Privacy Policy

This Privacy Policy explains how BetaQuest X ("we", "us", "our") handles information in connection with betaquestx.com, an India-based educational platform offering articles, videos, courses, quizzes, assignments and membership access. The legal operator and request contacts are identified in the contact section, subject to the publication review noted there.

This notice describes our platform’s processing; external payment, video and advertising services also have their own privacy notices. Reading or using the site does not by itself constitute consent to optional advertising or other processing for which separate consent is required.

• Account information: name, email address, password in hashed form, account identifiers, role, status, verification status and account timestamps. Account records can also include an avatar URL.
• Authentication: email verification and password-reset records, verification attempts and tokens needed to authenticate your account. We send verification and recovery emails through the configured email service.
• Learning activity: course enrollments and unenrollments, lesson completion, video playback position and watch progress, quiz answers, attempts, scores and timestamps, and assignment text, links, uploaded files, grading and reviewer feedback. Corrections to published assignment evaluations can retain earlier evaluation records.
• Interactions: comments, reactions and bookmarks. Comments and associated display information may be visible to other visitors where displayed. Avoid posting sensitive information publicly.
• Contact enquiries: the name, email, subject and message you submit through our contact form are sent to our configured inbox so we can respond. The submitted email is used as the reply address. Contact requests are not stored in an application database; email copies remain subject to the mailbox retention arrangements. Temporary client-IP records are used to limit form abuse.
• Payments: membership plan, subscription and payment identifiers, amount, currency, invoice references, payment status, verified billing periods and cancellation information received from Razorpay. Payment credentials are entered in Razorpay checkout; our membership integration does not store full card numbers, CVVs or UPI PINs.
• Technical information: browser requests disclose information such as IP address and device or browser details to the servers and services you contact. Operational logs may contain request information depending on hosting configuration. Video view counting uses a short-lived cookie and browser session storage.

The footer newsletter form currently has no connected subscription backend; its confirmation does not establish a mailing-list subscription. This notice does not claim a newsletter delivery service is operating.

We use account and authentication information to register and identify you, verify your email, recover access and enforce account permissions. Learning records support saved progress, course dashboards, assessment results and assignment review. Interaction records support the features you use.

Billing records allow us to verify paid periods, grant premium access, reconcile gateway updates and record cancellations or refunds. Information may also be needed to diagnose service issues, investigate misuse, respond to requests and meet applicable legal, accounting or dispute-resolution obligations.

Where processing requires consent under applicable law, consent must be obtained for that purpose. Refusing information necessary for an account, assessment or purchase may prevent us from providing that feature. Optional advertising consent is separate from account access.

The frontend stores the sign-in access token in browser local storage and sends it to the API to authenticate requests. Signing out removes the token from that browser. Local storage is separate from cookies and may persist until removed; clearing it can sign you out.

Video view counting uses a cookie with a six-hour lifetime to avoid repeatedly counting the same view, together with a session-storage timestamp. Browser settings can block or clear cookies and storage, but this may affect sign-in or other functionality. Clearing browser data does not delete server-side account or learning records.

Razorpay checkout and embedded video providers may use their own cookies or related technologies when loaded. Advertising technologies described below are planned and are not represented as already enabled.

Current status: Google AdSense monetization is planned. Publisher account metadata is present, but the reviewed implementation does not load AdSense ads or provide an advertising consent manager. The intended model is advertising for guests and free users, with BetaQuest X advertising removed for members with active premium access. Ads or branding within third-party video players may remain outside our control.

If AdSense is enabled, Google and other participating advertising vendors may use cookies to select ads using earlier visits to this site and other websites. Those cookies allow Google and its partners to personalize advertising across websites. Ad requests may share IP address, browser information, cookie identifiers and page information with advertising providers for ad delivery, measurement and fraud prevention.

You can manage Google personalized advertising through Google My Ad Center and find participating vendors’ opt-out choices at YourAdChoices. These settings do not necessarily remove ads or all advertising-related storage. See how Google uses information from partner sites and Google’s Privacy Policy.

Before activation: the operator must configure required disclosures and consent controls, list participating ad networks with their privacy and opt-out links, and ensure consent choices can be changed or withdrawn. Where required, optional advertising storage and personalization must wait for consent. Google requires a certified consent management platform integrating the IAB Transparency and Consent Framework for personalized ads served to users in the EEA, UK and Switzerland. No such controls are claimed to exist today.

• Razorpay: processes checkout, recurring payment authorizations and subscription payments. It receives information entered into checkout and supplies billing information to us. Read Razorpay’s Privacy Policy.
• Cloudflare R2: the file-storage integration uses R2 for uploaded files and learning assets when configured. Assignment uploads use private storage and authorized download links; public content images may be publicly accessible. Read Cloudflare’s Privacy Policy.
• YouTube / Google and Vimeo: supported external video players and their SDKs load when a viewer chooses to load an authorized video. Requests to those providers disclose technical information and may involve provider storage. Read Google’s Privacy Policy and Vimeo’s Privacy Policy. Provider-hosted content remains subject to their practices.
• Hosting, database and email providers: process information needed to run the site, store account and learning records and deliver authentication emails. [OPERATOR REVIEW: identify the deployed hosting, PostgreSQL database and SMTP providers and their privacy notices.]
• Google AdSense: planned only, as described in the advertising section.

Authorized administrators can access information needed for platform administration, billing and assignment review. Information may also be disclosed where required by law, to respond to lawful requests or to protect users and the platform in connection with abuse or disputes. External links and providers are governed by their own notices.

Account, learning and billing records are stored in a PostgreSQL database; uploaded objects use the configured R2 storage. The implementation uses password hashing, expiring authentication tokens, access checks for protected resources, private storage for learner submissions and signed checks for Razorpay payment confirmations and webhooks.

These measures do not guarantee absolute security. Protect your credentials, use a trusted device and avoid sharing sensitive personal information in assignments unless necessary. Our access controls do not control access to links you host on external services.

Providers may process data outside India. [OPERATOR REVIEW: confirm production storage locations, international processing arrangements, hosting safeguards and any required transfer restrictions or disclosures.] This policy does not claim that all data stays in India or that a particular security certification applies.

Retention must reflect the purposes described here, applicable recordkeeping requirements and legitimate needs such as billing disputes and abuse investigations. Different records, including learning history, assignment files, evaluation revisions and payment records, may require different periods.

Retention schedule pending confirmation: [INSERT APPROVED RETENTION PERIODS FOR ACCOUNTS, LEARNING DATA, FILES, AUTHENTICATION RECORDS, LOGS AND PAYMENT RECORDS, INCLUDING BACKUP HANDLING.] The reviewed application does not establish automatic deletion deadlines or a self-service account-deletion workflow.

Unenrolling from a course or cancelling membership does not delete your account or learning records. Deletion requests need to be reviewed through the contact channel once confirmed. Records may need to be retained where permitted or required by law; deletion from third-party systems follows their own requirements and procedures.

You can sign out, clear browser storage, manage browser cookies, choose whether to load supported external video players and manage automatic membership renewal in the membership area. These controls have the effects described above; they are not a complete account-erasure or data-export mechanism.

Depending on the law applicable to you and the provisions in force, you may have rights to information about processing, access, correction, erasure, withdrawal of consent, grievance redressal or other remedies. Rights may be subject to identity verification, legal exceptions and retention obligations. This notice does not promise every right in every jurisdiction or treat provisions not yet commenced as already operative.

Once the contact details below are confirmed, send the request type, account email and enough context to identify the relevant records. Do not send passwords, OTPs, card details or UPI PINs. [OPERATOR REVIEW: establish a monitored request and grievance process and legally appropriate response periods.] No automated export, correction or deletion workflow is claimed.

The platform does not currently implement age verification or a verifiable parental-consent workflow. [OPERATOR REVIEW: confirm the permitted learner age range and whether minors will be admitted; implement required safeguards before collecting children’s information.]

Under Indian law, protections for children can apply to persons under 18, subject to applicable commencement dates and exceptions. Where legally required, processing children’s data requires appropriate parental or guardian consent, and restrictions may apply to tracking, behavioural monitoring and targeted advertising. A general statement that a parent approved use is not a substitute for any required verification.

If you believe a child has supplied information without the required permission, contact the confirmed privacy contact so the situation can be reviewed. No child-specific advertising or parental control capability is represented as currently implemented.

We may update this notice to reflect changes to the service, providers or legal requirements and revise the last-updated date. Material changes requiring additional notice or consent must be handled as required by applicable law; posting an update alone does not replace required consent.

Relevant Indian law may include the Information Technology Act, 2000 and applicable rules, and the Digital Personal Data Protection Act, 2023 and its rules as their provisions come into force. The framework has phased commencement; this policy is not a certification of compliance. See MeitY’s official acts and policies for the legal texts and notifications.