Privacy Policy

Analytics, advertising measurement and your choices

Updated: 24 October 2026. Visiting this website or signing in does not by itself grant permission for optional individual analytics or advertising matching.

One optional choice

After about 4–5 seconds on an undecided visit, our popup offers Allow analytics & ads and Maybe later. Privacy settings also provides Keep optional tracking off to withdraw permission. Allow covers the analytics and advertising uses described here. All choices let you use the website, sign in, purchase and access your courses. Earlier analytics-only choices require a new decision before advertising is enabled. We normally remember Allow on that browser for up to 400 days. Off or Maybe later lasts the current visit, expiring after about 30 minutes of inactivity. Browser deletion or earlier expiry can require another choice. Tracking pauses if permission expires; later Allow starts collection from that point and does not backfill activity from a declined period.

You can change or withdraw your choice through Privacy & analytics on the Login page, without signing in. Signed-in users can also manage it on their dashboard. The footer does not contain a separate analytics control. Browser Global Privacy Control keeps optional analytics and advertising off.

When optional tracking is off or undecided

Our own database may keep summarized page/product/course counts, broad source/device categories, click and engagement buckets, performance/error categories and popup impressions/decisions. These counts do not create a persistent behavioral visitor/session identity, associate browsing with an account or reconstruct an individual journey. They are not necessarily unique people. A short-lived keyed abuse throttle can be derived from an IP address for request protection; security and hosting logs are separate. Optional Meta advertising events and enhanced customer matching are not dispatched by the new integration without permission.

When you allow analytics and ads

We use random browser identities and consented session/account linkage to understand returning visits, traffic sources/campaigns, products and courses viewed, menu and contact clicks, checkout steps, coarse scroll percentages and visible active-time buckets. Relevant outcomes include first registration, subsequent sign-in, successful phone verification, monetization application and final payment approval. Required account, order, payment, course and referral records exist separately to provide our services.

Google Tag Manager routes browser measurement to Google Analytics, Google Ads, Meta Pixel and Microsoft Clarity. Our hosting server sends permitted matching events to Meta Conversions API, Google Ads and Google Analytics. Matching can include verified email/mobile formatted as SHA-256 hashes, opaque account/browser identifiers, real advertising click identifiers and browser identifiers such as fbp/fbc or Analytics client IDs. Hashing does not make these identifiers anonymous. We do not fabricate identifiers or infer missing personal details. Browser and server event IDs/transaction IDs help prevent duplicate reporting. An unapproved payment declaration is not an approved Purchase.

These tools help measure advertising effectiveness, build eligible remarketing audiences, improve product recommendations and understand website usability. Clarity receives masked interface activity and opaque identifiers, rather than email/phone names in identity hints. Provider matching, retention, audience eligibility and ad attribution are governed by those providers and cannot be guaranteed by our website.

Information excluded and withdrawal

We do not add fingerprinting, keystroke collection or collection of passwords, OTP codes, private messages, bank/wallet destinations, payment receipt contents, private course materials or precise GPS location for behavioral marketing. Contact information deliberately submitted for an enquiry remains service information, not automatically advertising permission.

Choosing Off stops optional future tracking on that browser. Pending marketing deliveries are cancelled when permission is withdrawn; previously sent provider events cannot be recalled through that switch. Our existing browser-level first-party analytics withdrawal removes detailed journey/linkage records, while summarized counts, minimal delivery receipts and required account/order records have separate purposes. Existing collected history is not deleted solely because a permission cookie reaches its expiry; any permitted reconnection requires renewed permission and an available browser/account identity. We cannot guarantee reconnection after cookie deletion or across unrelated devices, and we do not fingerprint to bypass that boundary.

For access, correction, deletion or provider-related assistance, contact [email protected]. This analytics/advertising choice is separate from consent for marketing emails, calls or SMS.

Mobile number verification

When you choose to verify a mobile number in Edit profile, we send that number and a verification message through TingTing, our SMS service provider. This is a service message, separate from optional website analytics and marketing permission. Our current verification service supports Nepal mobile numbers.

A code is valid for one hour, can be used once, and permits up to five verification attempts. Each account and destination number can request at most one code in a rolling 24-hour period. A delivery failure or timeout may still consume that request window to prevent duplicate charged messages. Our own database keeps a keyed code digest rather than the plaintext code, together with pending number, expiry, attempt count and request-limit records. The SMS provider processes the destination and message, including the code, according to its own service practices.

Only successful code verification marks the number verified. Earlier saved numbers are not automatically considered verified. Changing a number requires verification again; clearing it removes its verified status. Phone verification confirms control of that number at that time and does not replace Google account sign-in.