1. What cookies and similar technologies are
Cookies are small data values stored or sent by a browser. Similar technologies may include local or session storage, anti-forgery tokens, device or session identifiers, server logs, pixels or SDK-generated identifiers where such tools are enabled.
Some technologies last only for the current browser session. Others remain until their configured expiry or until removed through browser or device controls. Ovhok's protected authentication cookie is configured with an absolute expiry of up to 1 day for a normal sign-in and up to 365 days only when the user expressly selects “Keep me signed in”; logout, password/security changes, account revocation or security-stamp validation may end it earlier.
2. Categories we may use
Strictly necessary
Security, session continuity, authentication, anti-forgery protection, load distribution, consent state and core functionality requested by the user.
Preference
Remember language, display, accessibility, dismissed notices and other user-selected settings where implemented.
Analytics and performance
Used only when an analytics/performance provider is actually enabled and lawfully configured; such tools may measure page performance, navigation, errors, referrals and aggregated usage patterns.
Marketing and measurement
Used only when an optional marketing/measurement integration is enabled and any required consent is obtained. Ovhok does not classify the authentication or anti-forgery cookies required for account security as marketing cookies.
3. How Ovhok uses these technologies
- Operate secure sign-in, authenticated sessions, account features and anti-forgery protections.
- Maintain secure checkout/return state, anti-replay and anti-forgery protections around course purchase and payment-verification workflows.
- Remember user-requested preferences and avoid repeatedly showing the same notices where appropriate.
- Detect abuse, automated attacks, unusual traffic, failed authentication and security incidents.
- Diagnose errors, measure availability and performance, understand how public pages are used and improve navigation or content.
- Measure marketing or campaign performance where optional technology has been enabled lawfully.
4. First-party and third-party technologies
First-party cookies are set by Ovhok-controlled domains. Third-party technologies may be set or processed by providers used for hosting, security, analytics, embedded media, maps, social content, payments or other integrations.
Third-party providers may process information under their own terms and privacy practices. Ovhok may add, replace or remove providers as Services change. Where applicable law requires consent before an optional provider is activated, Ovhok will use the relevant consent mechanism before enabling that technology.
When you leave Ovhok for an enabled bank or payment gateway, that provider may set its own cookies or similar technologies. Ovhok does not control those provider-side technologies; returning to Ovhok does not by itself mark a payment successful because settlement is verified server-to-server where supported.
5. Your browser and consent controls
You may delete or block cookies through browser settings and may use any consent control presented by Ovhok for optional technologies. Browser controls vary by provider and device.
Blocking strictly necessary cookies, session storage or security tokens may prevent sign-in, secure forms, account access or other core features. Ovhok is not responsible for functionality that becomes unavailable because a user or browser blocks technology required to perform that functionality.
Browser privacy signals such as “Do Not Track” or similar signals are not standardized for every use case. Ovhok will comply with any signal that applicable law expressly requires us to recognize for the relevant processing.
6. Retention and server logs
Cookie and browser-storage duration depends on purpose and configuration. The primary authenticated Identity ticket is absolute rather than sliding: up to 1 day by default or up to 365 days when “Keep me signed in” is selected. Anti-forgery/session-supporting values may have different shorter lifetimes. Optional provider cookies, if enabled, follow the relevant provider and consent configuration.
Security, access and diagnostic logs may be retained separately from browser cookies for a risk-based period required for service operation, abuse prevention, incident investigation, audit, legal obligations or dispute resolution.
7. Relationship with the Privacy Policy
Information collected through cookies and similar technologies is handled under the Privacy Policy and applicable customer agreements. The Privacy Policy explains broader collection, sharing, security, retention, rights and contact practices.
8. Changes to this Cookie Policy
Ovhok may update this Policy when technologies, providers, legal requirements or Services change. The published version will show its current effective and review dates. Material changes will receive any additional notice or consent required by applicable law.
9. Contact
Ovhok Software Solutions Pvt. Ltd.
Arjundhara-8, Jhapa, Nepal
Email: [email protected]
Phone: +977 9862911301
10. Applicable law
This Policy is intended to operate subject to applicable Nepal law, including privacy and electronic-transaction requirements. Any mandatory statutory requirement prevails to the extent of a conflict.