Effective Date: August 21, 2026 (version 1.0)
This Cookie Policy explains how Edgely uses cookies and similar technologies on our websites and within our online Service. It complements our Privacy Policy and should be read together with it.
Cookies are small text files placed on your device by a website you visit. They allow the website to recognize your device and remember some information about your visit. We also use comparable technologies, in particular your browser's local storage, which keeps you signed in and remembers your display settings, and this Policy applies to them in the same way. We do not use tracking pixels or web beacons.
Required for the website and the Service to function. They cannot be switched off without breaking the Service. Typical uses:
These cookies are set on the basis of our legitimate interest in providing a working, secure Service and, where required, on the basis of contract performance.
Used to remember choices you make so that we can offer a more personalized experience. Typical uses:
Where required by law, these cookies are set with your consent.
We set no analytics cookies, so there is no analytics category for you to accept or refuse. Our websites and the online Service load no analytics script and no tag manager; apart from the anti-abuse widget described in section 4, the only external host our pages contact is Google Fonts, which serves typefaces and is not used to measure your behaviour. No feature-usage counter, session-tracking identifier or plugin-usage signal is collected through cookies or through any comparable technology.
The same is true outside the browser. Our desktop and mobile applications contain no usage analytics, no session tracking and no crash- or error-reporting component, and transmit nothing of that kind from your device. Diagnostic logs and crash dumps are written to a folder on your own device and are never uploaded; attaching them to a support request is your own deliberate act. There is therefore no analytics setting to switch on or off, either in the browser or in the applications.
We set no advertising cookies. There is no advertising on our websites or in our applications, no advertising SDK, no advertising identifier and no third-party tracker, and we build no cross-site advertising profile. If we ever introduce marketing cookies, we will set them only after obtaining your consent and we will update this Policy beforehand.
A small number of counts are recorded by the portal on our own servers, because the portal itself performed the request. They involve no cookie, no comparable technology and no tracking identifier stored on your device; if you are signed in when you download, the record is attached to your account, which is an account function and not tracking.
When you download the software, when your software checks for a new version, or when a plugin is installed or updated, we record:
utm_source, utm_medium, utm_campaign and the referring addressYour IP address is used only, in memory, to resolve that location at the moment of the request, and is then discarded. It is never stored with these records, and it appears in no log and no backup of them.
That is a statement about these counts, not about the whole portal. For a small number of security, consent and account purposes, proof of which version of a legal document you accepted, anti-abuse on our public contact and feedback forms, and device linking, an IP address is retained, and our security logs record a partially masked address when a rate limit is hit, when an anti-abuse check fails, or when a message is sent through our public contact or feedback forms. None of that involves a cookie. Section 2.4 of our Privacy Policy sets out each case, its legal basis and its retention.
Device identifiers used to activate a licence and to link your own devices to your account are an account function, not tracking, and are not cookies. Our Privacy Policy describes this processing in full.
Some cookies may be set by service providers we work with, for example when a payment is completed on our payment provider's own secure pages, when transactional email is delivered, or when the security provider that protects our forms verifies that a request is not automated. We require these providers to handle your information in line with our Privacy Policy and applicable law. We use no analytics provider and no advertising provider, so no cookie is ever set on our sites for those purposes.
Cookies are either _session_ cookies, which are deleted when you close your browser, or _persistent_ cookies, which remain for a defined period or until you delete them. Typical durations:
| Type | Typical duration |
|---|---|
| Session cookies | Until the browser is closed |
| Authentication | Until logout or up to 30 days |
| Preference | Up to 12 months |
This table is short because it is complete: we set no analytics and no advertising cookies, so none appears here at any duration. We will update this Policy if the items we set ever change.
You can control cookies in three ways:
Browser help pages typically provide cookie-management instructions for Chrome, Firefox, Safari, Edge, and other major browsers.
We may update this Cookie Policy from time to time to reflect changes in the cookies we use or in applicable law. We will publish the updated version on our website with the new effective date. If the change is material, we will give reasonable notice before it takes effect.
For questions about our cookie practices, or to exercise your rights: