This page explains how Lenava uses session cookies, consent records, preferences, and optional browser technologies across the product and its login surfaces.
This Cookie Policy explains how Lenava Group Inc. uses cookies and similar browser or device technologies in connection with Lenava LIMS, related product websites, customer portals, and authentication surfaces. It describes what these technologies are, why we use them, and how you can control non-essential categories inside the product.
Because Lenava LIMS may run on hosted subdomains, customer-specific domains, or on-premise environments, cookie handling is implemented directly in the Laravel application rather than through a third-party banner service. The exact technologies present can vary depending on enabled modules, customer deployment choices, and security features such as captcha, analytics, or support tooling.
Cookies are small data files stored in a browser or device when a user visits a website or application. Similar technologies can also include local storage, session storage, security tokens, and other browser-side mechanisms used to remember state, preserve login continuity, distinguish a real user from an automated process, or remember user choices.
Some of these technologies are created directly by Lenava LIMS and some may be created by integrated services or infrastructure used to operate security, analytics, or authentication features.
We use cookies and similar technologies to keep the service secure, maintain sessions, support authentication, remember interface settings, record cookie preferences, preserve tenant-aware application state, and improve product usability. In some deployments we may also use them for aggregate measurement, diagnostics, support workflows, or optional product analytics where the relevant consent category is accepted.
For internal consent handling, Lenava LIMS groups browser-side technologies into essential, preferences, and analytics categories. Essential technologies are always active because the application cannot function safely without them. Preferences and analytics technologies are optional and can be allowed or rejected through the in-product consent controls.
Essential cookies are used for login, session continuity, CSRF protection, access control, tenant isolation, security monitoring, and other core application features. They may also support rate limiting, secure request validation, and server-side session management.
Without these technologies, Lenava LIMS cannot reliably authenticate users, keep forms secure, or preserve core workflow state. For that reason, essential cookies remain active even when a user declines non-essential categories.
Preferences cookies store user choices such as language, text direction, layout settings, and saved cookie selections. These technologies improve the user experience and reduce the need to re-enter the same settings on every visit, but they are not strictly required for the product to load.
In multilingual environments, these technologies can also support consistent right-to-left or left-to-right rendering choices and related user interface behavior.
Analytics technologies may be used to understand aggregate product usage, improve workflows, identify interface friction, monitor performance trends, or support service planning. These technologies are disabled unless the relevant consent category is accepted.
Depending on deployment choices, analytics may be absent entirely, may rely on internal measurement only, or may be connected to customer-approved measurement providers. Customer-specific environments can differ in whether analytics technologies are enabled at all.
Some authentication flows may use security-related technologies such as captcha or bot-detection mechanisms to distinguish human users from automated abuse. These technologies can involve browser storage, temporary identifiers, or challenge-related tokens necessary to protect login forms, support forms, and other sensitive interactions.
Where such technologies are used for security and abuse prevention, they are treated as part of the essential security surface of the service.
You can accept all supported categories, reject non-essential categories, or open the in-product Cookie Preferences control to make a more specific choice. The consent interface is shown when no valid decision has been recorded for the current consent version.
If you reject non-essential cookies, only essential categories remain active. You can later reopen the cookie preferences control from inside the product and change your choice.
When you make a cookie decision, Lenava LIMS stores that choice in a browser cookie so the banner does not need to appear on every page load. If you are authenticated, the application also records an internal audit entry that can include the consent version, accepted categories, timestamp, IP address, user agent, user identifier, and current business or tenant context when available.
This record helps maintain an internal history of consent decisions without depending on an external consent platform for day-to-day operation.
Lenava LIMS does not hardcode a single production domain for cookie consent behavior. Where deployments use shared subdomains, the consent cookie may follow the configured cookie domain through application configuration. For on-premise or customer-managed environments, the same internal consent mechanism can operate using environment-specific cookie settings.
This allows the legal and consent system to work consistently across multi-tenant, subdomain-based, and customer-hosted installations.
Most browsers provide settings that allow users to clear, restrict, or block cookies and similar local storage. Those browser-level settings can affect how Lenava LIMS behaves. In particular, blocking essential cookies may prevent login, interrupt secure workflows, or reduce application functionality.
If you use browser controls to remove all cookies, the application may ask you to make your consent choice again the next time you visit.
In addition to cookies, the service may use related technologies such as local storage, session storage, temporary security tokens, or browser-side identifiers that support state preservation, security validation, performance troubleshooting, or optional analytics. Many of these mechanisms function together with cookies rather than replacing them.
The presence of a specific technology depends on active features, customer configuration, and the relevant environment.
We may update this Cookie Policy from time to time to reflect changes in legal requirements, product architecture, customer deployment patterns, or the technologies used by the service. Updated versions will be published on this page and reflected by the revised effective date or consent version shown above.
If you have questions about this Cookie Policy or about cookies used by Lenava LIMS, you may contact Lenava Group Inc. at info@lenava.ca.
Mailing address:
Lenava Group Inc.
481 Davisville Ave
Toronto, Ontario M4S 1J2
Canada
For broader information about personal data handling, see the Privacy Policy. For general platform rules, see the Terms and Conditions.
We use essential cookies to keep Lenava LIMS secure and to remember your settings. You can allow or reject non-essential categories below.