Cookie Policy
Effective January 8, 2026
1. Introduction
This Cookie Policy explains how Convilyn uses cookies and similar technologies on our website. It complements our Privacy Policy.
When you first visit Convilyn, a consent banner asks you to accept or customise which cookie categories load. You can change your choice at any time by clearing site data and revisiting the site, or via your browser settings.
3. Categories of Cookies We Use
Convilyn uses four categories of cookies. The consent banner lets you accept or decline each category individually:
- Necessary: required for core features such as authentication, security, and remembering your locale. These cannot be disabled.
- Functional: remember preferences such as the billing-cycle toggle or your dashboard view. Disabling these may reduce comfort but not core functionality.
- Analytics: help us understand how the site is used in aggregate so we can improve it. Disabled until you opt in.
- Marketing: may be used to measure the effectiveness of campaigns. Disabled until you opt in.
4. Third-party Cookies
Some cookies are set by third parties that operate parts of the Service. The most relevant are:
- Paddle (payment processor and Merchant of Record): sets cookies during checkout to maintain session state and prevent fraud. See Paddle's Privacy Policy.
- Authentication providers (if you sign in via a federated identity): set cookies as part of the sign-in flow.
A complete list of sub-processors that handle your data — including those that may set cookies — is available at our Sub-processors page.
5. Your Choices
You have several ways to control cookies:
- Use the consent banner the first time you visit the site
- Clear site data in your browser to re-trigger the banner
- Block all cookies in your browser settings (this will break authentication and core features)
- Enable the "Do Not Track" signal in your browser — we respect it for analytics and marketing categories
6. Cookie Retention
Session cookies are removed when you close your browser. Persistent cookies last for the period specified at the time they are set, typically between 30 days and 12 months. Necessary cookies for authentication usually expire 30 days after your last sign-in.
7. Changes to This Policy
We may update this Cookie Policy as the Service evolves or as third-party providers change their cookie practices. Material changes are posted on this page with an updated effective date.
8. Contact Us
If you have questions about how we use cookies, please contact us:
CoreNovus
Email: support@corenovus.com