Trust & Compliance

Cookie Policy

The cookies and similar technologies we use, and the choices available to you.

Last updated: 29 October 2026 Applies to all Luveedu Cloud services
Cookie Policy

Luveedu Cloud · Wenxenith Technologies LLP · Last updated 29 October 2026 · luveedu.cloud

This Cookie Policy explains how Ariyan Debnath, trading as Wenxenith Technologies LLP, uses cookies and similar technologies across the Luveedu and Luveedu Cloud websites and applications. It describes the categories of cookies we set, the purpose of each category, the periods for which cookies are retained, and the controls available to the visitor.

We have written this Policy in plain English and organised it into sections so that a specific question can be answered quickly. Where the law requires a particular disclosure, we say so. This Policy should be read together with our Privacy Policy, which explains how we handle personal data more broadly.

1.Purpose and Scope

This Cookie Policy explains how Ariyan Debnath, trading as Wenxenith Technologies LLP, uses cookies and similar technologies on the websites and applications that we operate under the Luveedu and Luveedu Cloud brands. It applies to luveedu.cloud, luveedu.com, manager.luveedu.cloud, and all current and future subdomains of those domains, including product consoles, documentation portals, status pages, and application programming interfaces.

The Policy applies to visitors of our websites, to customers who sign in to the client area, and to anyone who receives email from us or interacts with our support channels. It sets out the categories of cookies we use, the purposes served by each category, the choices available to the visitor, and the periods for which cookies are kept.

This Policy does not govern cookies set by websites that our customers publish on our infrastructure. Where a customer uses shared hosting, cloud hosting, WordPress hosting, reseller hosting, a Linux VPS, or a Windows VPS, that customer decides which cookies are set on the hosted website and is responsible for obtaining any consent that the law requires. We do not control those cookies and cannot disable them on behalf of the customer.

This Policy forms part of the information we provide about our processing of personal data. It should be read with our Privacy Policy, Terms and Conditions, Service Level Agreement, Refund Policy, and Acceptable Use Policy. Terms that are defined in the Privacy Policy carry the same meaning here.

2.What Cookies Are

A cookie is a small text file that a web server asks a browser to store. It contains a name, a value, and attributes such as the domain, the path, an expiry date, and security settings including the Secure flag, the HttpOnly flag, and the SameSite attribute. When the browser later requests a resource from the same domain, it sends the cookie back, which allows the server to recognise the browser across separate requests.

Cookies are either session cookies or persistent cookies. A session cookie exists only for the duration of a browsing session and is deleted when the browser is closed. A persistent cookie remains on the device for a defined period, or until the visitor deletes it, and is used where a setting or a state must survive between visits.

Cookies are also described as first-party or third-party. A first-party cookie is set by the domain that the visitor is visiting. A third-party cookie is set by a different domain, usually because the page embeds a resource from a provider such as a payment processor, a support chat service, or a content delivery network. First-party and third-party cookies are subject to the same browser controls, but they are governed by the privacy notices of different organisations.

Cookies do not contain executable code and cannot read files stored on the device. They identify a browser rather than a person, although a cookie that is linked to an account becomes personal data, and we treat it accordingly. Other technologies that store or read information on a device, such as local storage, session storage, and pixel tags, are described in the section on local storage and similar technologies.

3.Who We Are

Luveedu and Luveedu Cloud are trademarks of Ariyan Debnath, trading as Wenxenith Technologies LLP, a limited liability partnership registered in India. Our corporate address is Luveedu Corporate Office, Bishalgarh, Sepahijala, Tripura, 799102 - India.

For the personal data that we collect through our own websites and the client area, including analytics data, preference data, and security logs, we act as the data controller, or Data Fiduciary under the Digital Personal Data Protection Act, 2023. We determine why that data is collected and how it is used, and this Policy describes that processing.

For the content that customers store and transmit using the Services, we act as a data processor, or Data Processor, and the customer acts as the controller. That relationship is governed by our Data Processing Addendum, which is published as a separate document and forms part of our Terms and Conditions where it applies.

Questions about this Policy, and requests relating to personal data, may be sent to [email protected]. Legal and privacy notices may be sent to [email protected]. Full contact details appear in the final section and in the contact block on this page.

4.Strictly Necessary Cookies

Strictly necessary cookies are required for our websites and the client area to operate securely and correctly. They cannot be switched off through our interface, because disabling them would prevent core functions from working. These cookies do not store information for advertising purposes and are not used to build profiles of visitors.

  • Authentication - a session cookie that keeps a signed-in customer recognised in the client area and routes each request to the correct session store.
  • Security tokens - values that protect forms and state-changing requests against cross-site request forgery, and that bind a session to the browser that created it.
  • Load balancing - a cookie that records which application server is serving a session, so that requests remain consistent during a visit.
  • Fraud prevention - signals used during sign-up, sign-in, and payment to detect automated abuse, credential stuffing, and payment fraud.
  • Payment flow - cookies set during checkout and on return from a payment provider or a bank authentication step, so that an order is completed against the correct account.
  • Consent state - a record of the cookie choices made by the visitor, so that the choice is respected on later pages and on later visits.
  • Service integrity - cookies that maintain request routing, rate limiting, and protection of administrative interfaces.

These cookies are set on the basis of the contract between us and the customer, and on our legitimate interest in operating a secure and reliable service. Where the law treats a particular cookie as strictly necessary for the provision of a service requested by the user, we set it without seeking consent.

If a visitor blocks these cookies, sign-in to the client area may fail, forms may be rejected, checkout may not complete, and support chat may not connect. We cannot provide the affected functions without them.

5.Preference Cookies

Preference cookies remember choices that a visitor or customer has made, so that the experience remains consistent between pages and between visits. They do not track activity across unrelated websites and are not used for advertising.

  • Language and region - the language and regional format selected, so that pages load in the expected version.
  • Currency - the display currency, so that prices remain consistent throughout a session.
  • Theme and display - the selected appearance and interface density.
  • Dismissed notices - a record that a service notice or announcement has already been seen, so that it is not shown repeatedly.
  • Billing term selection - the billing cycle chosen while comparing plans, so that the selection survives navigation.
  • Dashboard layout - the arrangement of panels in the client area.

Where a preference cookie is absent, we apply a default derived from the browser language, the approximate location of the connection, or the settings of the account. The default has no effect on the content of a service and can be changed at any time.

Preference cookies are set only with consent where the law requires it. They are retained for up to twelve months, and a new choice replaces the previous value rather than adding a second record.

6.Analytics Cookies

Analytics cookies help us measure, in aggregate, how our websites are used. They record page views, session counts, entry and exit pages, the referring source, the device class, the browser family, the approximate country of the connection, and the time taken to load a page.

We use this information to understand which content is useful, to identify navigation problems, to prioritise improvements, and to report aggregate usage internally. Reports are produced at aggregate level, and we do not use them to make decisions about an individual visitor.

The purpose is limited. We do not use analytics cookies to build advertising profiles, to follow visitors across third-party websites, to infer sensitive characteristics, or to sell data. Where a provider offers cross-site advertising features, we do not enable them on our properties.

We minimise the data by truncating or hashing IP addresses where the tool allows, by disabling user identifier features that are not needed, and by configuring retention periods. Analytics identifiers are generally retained for no longer than fourteen months, after which the data is aggregated or deleted.

Analytics cookies that are not strictly necessary are set only with consent where the law requires it. A visitor who declines may still use every part of the public website and the client area; the only consequence is that the visit is not counted in our measurement.

7.Performance and Diagnostic Cookies

Performance and diagnostic cookies support the operation of our own properties. They are used to sample errors, to measure page and interface timing, and to correlate a failure with the release that caused it.

We run synthetic monitoring from multiple regions against our websites and public endpoints. These checks measure availability and response time and do not use cookies in the browser of a visitor. Where a diagnostic cookie is placed in a real browser, it carries a random identifier that is used only to join a client-side timing record to a server-side log entry.

These cookies are not used for marketing and are not shared with advertising networks. They are retained for short periods, generally no longer than thirty days, and are deleted as soon as the diagnostic purpose is complete. Where a diagnostic cookie is not strictly necessary, we treat it as an analytics cookie for the purpose of consent.

Diagnostic data helps us meet the availability targets described in our Service Level Agreement. Access to the underlying records is limited to engineers who investigate faults and to staff who handle security incidents.

8.Marketing and Referral Cookies

We use marketing and referral cookies only where a marketing programme is active and the law permits. They serve two purposes: to attribute a sign-up to a referral or affiliate link, and to measure the performance of a campaign that we run on our own properties.

Where a visitor arrives through a referral or affiliate link, we may set a first-party cookie that records the reference and the landing page, so that a later order can be attributed correctly and any commission calculated. The cookie does not contain the content of the visit and is not used to follow the visitor to other websites.

Marketing and referral cookies are set only after consent where the law requires it. A visitor who declines is not excluded from any offer; the referral is simply not recorded. Referral cookies are retained for a limited attribution window, generally no longer than sixty days, and are deleted when the window closes or when the visitor clears cookies.

We do not sell personal data, and we do not permit third-party advertising networks to set cookies on the client area for behavioural advertising. Where we use a third-party measurement service, we configure it so that it does not combine our data with data collected from other customers of that service.

Marketing email may contain pixel tags that record whether a message was opened and which links were followed. Those tags are described in the section on local storage, pixels, and similar technologies, and a visitor can limit them by blocking remote images in the email client.

9.Third-Party Cookies and Services

Some pages embed services provided by other organisations, and those organisations may set their own cookies. Examples include the payment processor used at checkout, the support chat widget in the client area, the content delivery network that serves static assets, the analytics service that produces aggregate reports, the email delivery provider that tracks delivery and engagement, and the anti-fraud service consulted during sign-up and payment.

Each provider acts under its own privacy notice and its own retention periods. We select providers that offer appropriate safeguards, and we limit the data that they receive to what the relevant function requires. We do not control the duration of cookies that a third party sets on its own domain. A visitor who wishes to limit these cookies should use the controls described in the section on managing cookies and should also review the notices of the relevant providers.

Where a third-party cookie is set on our domain, it is set for the function described in this Policy and not for the independent advertising purposes of the provider. We do not permit a provider to use data collected on our properties to build advertising audiences, and our contracts with providers restrict that use.

If a provider is replaced, the categories described in this Policy remain the same. We update this Policy when a change materially affects the categories of cookies in use or the purposes that they serve.

11.Managing and Disabling Cookies

Every major browser allows the visitor to view, block, and delete cookies. The controls are usually found in the privacy or security section of the browser settings, and most browsers allow an exception list so that cookies can be allowed for a trusted site and blocked elsewhere. Deleting cookies removes both first-party and third-party cookies stored for the sites in that browser profile.

Private or incognito windows discard cookies when the window is closed, which is useful for a one-off visit but does not prevent cookies from being set during the session. Mobile operating systems also provide controls for advertising identifiers, and browsers on mobile devices expose the same cookie controls as their desktop versions.

Blocking all cookies has consequences. The client area may not keep a customer signed in, forms may be rejected because security tokens cannot be validated, checkout may fail, and support chat may not connect. Where a blocking rule applies only to third-party cookies, the impact is usually limited to embedded functions such as payment and chat.

For analytics, several providers offer a browser add-on or an opt-out link that prevents measurement across all websites that use the provider. Where we use such a provider, we honour the opt-out that the provider implements. A visitor may also use a browser extension that blocks analytics scripts, and we do not attempt to circumvent these controls.

We do not require a visitor to accept non-essential cookies in order to reach any part of the public website. Access to the client area depends on strictly necessary cookies, which cannot be disabled without losing the function that they support.

12.Do Not Track and Global Privacy Control

Some browsers send a Do Not Track header with each request. No common industry standard defines how a site should interpret that signal, and the header is not sent by every browser. For that reason we do not currently treat a generic Do Not Track signal as a binding instruction, and our behaviour is the same whether the header is present or absent.

We recognise the Global Privacy Control signal as a valid opt-out preference where the law applicable to the visitor requires it, and we treat it as an objection to the sale or sharing of personal data and to non-essential analytics and marketing cookies. Where the signal can be detected reliably and applied without breaking the service, we apply it automatically. Where a browser or extension sends the signal in a form that cannot be verified, we may ask the visitor to confirm the choice through the cookie settings.

Because we do not sell personal data, the practical effect of an opt-out signal on our properties is limited to measurement and referral attribution. A visitor who sends the signal can still use every part of the public website and the client area.

If industry practice or applicable law establishes a binding interpretation of Do Not Track, we will update our approach and this Policy. We review our position at least once a year.

13.Local Storage, Pixels, and Similar Technologies

Cookies are not the only technology that stores or reads information on a device. We also use local storage and session storage, pixel tags, and server-side identifiers, and the principles in this Policy apply to them as well.

Local storage and session storage are areas that a website can use to keep data in the browser. Data in local storage persists until it is deleted by the site or by the visitor, while data in session storage is cleared when the tab is closed. We use local storage for interface state, such as an unsaved draft in an editor, the layout of a dashboard, the state of a guided tour, and the record of a dismissed notice. We do not store credentials in local storage.

Pixel tags, also called web beacons or clear pixels, are small image requests embedded in a page or an email. They tell the sender whether a message was opened and whether a link was followed. We use pixel tags in email to measure delivery and engagement, and in our own pages as part of the analytics described above. A visitor can limit email pixels by blocking remote images in the email client, and can limit page pixels with the same browser controls that apply to scripts.

A visitor can clear local storage and session storage through the site data controls of the browser. Clearing them may reset interface preferences and may discard an unsaved draft, so work should be saved before site data is cleared.

Server-side identifiers, such as a session identifier held in a log or a database, are not stored on the device and are not cookies. They are described in the Privacy Policy together with the other technical data that we collect.

14.Retention

Session cookies are deleted when the browser is closed, or earlier if the session ends through sign-out or through an inactivity timeout. The timeout for the client area is deliberately short, and re-authentication is required after it expires.

Persistent cookies are kept only for the shortest period needed for the purpose that they serve. As a general guide, preference cookies are retained for up to twelve months, analytics identifiers for up to fourteen months, referral and attribution cookies for up to sixty days, and diagnostic identifiers for up to thirty days. No cookie that we set is retained for more than twenty-four months, except a consent record, which is kept for as long as necessary to demonstrate that a choice was made and respected.

When a cookie is no longer needed, it expires or is deleted. Expiry is enforced by the browser through the attributes of the cookie, and our servers also delete associated session records when a session ends.

Cookies set by third parties are subject to the retention periods of those providers, which we do not control and cannot shorten. Where a provider offers a configurable retention period, we select the shortest period that still supports the relevant function.

15.Changes to This Policy

We may update this Policy to reflect changes in the cookies we use, in the providers we engage, in our services, or in applicable law. Changes apply from the date on which the updated Policy is published, and the date at the top of the page is changed at the same time.

Where a change materially affects the categories of cookies in use or the choices available to visitors, we will provide additional notice. Notice may take the form of a banner on the website, a message in the client area, or an email to account holders, and it will be given before the change takes effect where the law requires it.

Continued use of our websites after the effective date indicates that the visitor has had the opportunity to review the updated Policy. Where consent is the applicable basis, we will request consent again if the change requires it.

Previous versions of this Policy are available on request from [email protected].

16.Contact

Questions about this Policy, requests relating to personal data, and complaints about the handling of cookies should be directed to the contact named in the block below. We acknowledge requests within 48 hours and aim to resolve them within 30 days.

  • Privacy, legal, and data protection - [email protected], for questions about this Policy, cookie choices, and rights requests.
  • Legal and formal notices - [email protected], for formal notices and regulatory correspondence.
  • Technical support - [email protected], or a ticket from the client area, for browser settings and service problems.
  • Postal address - Luveedu Corporate Office, Bishalgarh, Sepahijala, Tripura, 799102 - India.

If a visitor is not satisfied with the response, the visitor may complain to the Data Protection Board of India or, where applicable, to the supervisory authority of the country in which the visitor resides. We ask that the internal process be used first, so that we have the opportunity to correct the matter.

This Policy is governed by the laws of India, and the courts of Tripura have exclusive jurisdiction over any dispute arising from it, subject to any mandatory right of a consumer or data subject under applicable law.

Grievance Redressal

Grievance Officer

Wenxenith Technologies LLP has appointed a Grievance Officer for complaints and notices under this policy. He acts independently of our sales and support teams, and there is no charge to raise a grievance.

Email the Grievance Officer at [email protected]
Include your account email, the policy concerned, and any reference number
Expect an acknowledgement within 48 hours
We provide a written outcome within 30 days
Technical support remains available at [email protected]
Designated Grievance Officer
Shyamal Debnath
Grievance Officer
[email protected]
+91 7641818218
Luveedu Corporate Office, Bishalgarh, Sepahijala, Tripura, 799102 - India
We acknowledge every grievance within 48 hours and aim to resolve it within 30 days.