Effective Date: 12 May 2026 Version: 1.0 Document ID: COOKIES-DRONEFIELD-v1.0 Language: English (binding)
This Cookie Policy explains how DroneSpot Kft. ("Provider", "we", "us") uses cookies and similar technologies on the DroneField Portal at https://my.dronefield.app and on the documentation site at https://doc.dronefield.app (collectively, the "Sites").
This Cookie Policy supplements — and should be read together with — our Privacy Policy (document PRIVACY-DRONEFIELD-v1.0), which is the authoritative document for all data-protection questions. Where this Cookie Policy and the Privacy Policy describe the same matter, the two are designed to say the same thing in compatible language; in the event of any inconsistency, the Privacy Policy prevails on data-protection substance, while this Cookie Policy provides the operational detail about cookies.
Our commitment. We use cookies only where they are strictly necessary to run the Sites or where they implement a preference you have asked us to remember. We do not set advertising, analytics, social-media, or third-party tracking cookies. If you have ever wondered why the Portal does not show you a cookie-consent banner, the answer is simply: the cookies we set do not require one under EU ePrivacy law. We have written this Policy to make that fact verifiable rather than just stated.
Cookies. A cookie is a small text file that a website asks your browser to store on your device. When your browser sends a subsequent request to the same website, it includes the cookie value, allowing the website to recognise the same browser across requests. Cookies are not programs and cannot execute code on your device; they are simple identifiers — typically a random string or a short readable value.
First-party vs. third-party cookies. A first-party cookie is set by the website you are visiting (in our case, by my.dronefield.app or doc.dronefield.app). A third-party cookie is set by a different domain that the website you are visiting has embedded — for example, an advertising network. We do not set any third-party cookies, as further described in Section 8.
Session vs. persistent cookies. A session cookie is automatically deleted when you close your browser. A persistent cookie remains on your device until it reaches its expiry date or until you delete it manually.
Similar technologies. In addition to cookies, websites can store small amounts of data on your device using technologies such as:
The Portal uses a small amount of local storage for non-sensitive UI preferences, as described in Section 7. It does not use session storage, IndexedDB, Web SQL, fingerprinting scripts, ultrasonic beacons, or any other tracking technology.
The cookies we set serve only two purposes:
We do not use cookies for:
The Portal at my.dronefield.app sets the following cookies. All of them are first-party cookies (set by the Portal itself, not by any third party).
Session cookie.
dronefield_session (or equivalent, set by the Laravel framework)Authentication token cookie.
CSRF token cookie.
XSRF-TOKEN (Laravel default)Remember-me cookie (only if you opt in).
Cookie-acceptance cookie (only relevant if and when a future consent banner is introduced).
If we ever add a cookie that requires consent, we will introduce a consent banner; when you make a choice on that banner, we will set a small cookie to remember your choice. We do not set such a cookie at the date of this Policy because we currently use no cookies that would require consent.
The documentation site at doc.dronefield.app is publicly accessible and does not require login. It sets only one cookie.
Theme cookie.
The documentation site does not set any other cookies — no session cookie (because there is no login), no CSRF token (because there are no forms), and no third-party cookies of any kind.
We do not set, run, or allow on the Sites any of the following:
If you inspect the Portal or the documentation site in your browser's developer tools, you can verify these statements: only the cookies and local-storage entries listed in this Policy are present.
The Portal stores a small amount of data in your browser's local storage to remember UI preferences that are not security-sensitive. These values stay on your device, are never transmitted to our servers, and are not used for any tracking purpose. They include, for example:
You can clear these values at any time by clearing your browser's site data for my.dronefield.app. Doing so resets the relevant preferences to their defaults the next time you load the page; it does not affect your Account, your data, or anything stored on our servers.
The documentation site does not use local storage other than what the documentation framework needs to remember your theme preference (which is implemented as a cookie, as described in Section 5).
We do not embed any third-party scripts or iframes that would set cookies on the Sites. Specifically:
Stripe and the checkout flow. When you complete a paid Order on the Portal, the payment form is served by Stripe. The Stripe payment iframe is loaded from js.stripe.com and may set its own cookies for the purpose of fraud detection (Stripe Radar). These cookies are subject to Stripe's privacy notice at https://stripe.com/privacy and are a necessary part of completing a payment under PCI-DSS rules. They are not set unless you actually proceed to the checkout step, and they are not set on the documentation site or on Portal pages outside the checkout flow. You can review the cookies that Stripe sets in your browser's developer tools when you are on the checkout page.
A short reference for each cookie described above:
You can shorten any of the above lifetimes by clearing your browser's cookies for the relevant domain at any time.
You can manage, refuse, or delete cookies in several ways. The right method depends on your browser and on how granular you want the control to be.
Through your browser's settings. Every modern browser lets you view, allow, refuse, or delete cookies on a per-site or global basis, and lets you control how the browser handles cookies in private/incognito windows. The specific menus differ by browser, but most call the relevant section something like "Privacy and security" or "Cookies and site data". Some short references (independent links, not affiliated with the Provider):
Logging out of the Portal. Logging out is the simplest way to invalidate your session and authentication-related cookies. The Portal Logout button is in the top-right user menu, and the Software has a "Log out" option in its settings.
Untick the "Remember me" checkbox. If you do not tick "Remember me" at login, no Remember-me cookie is set and your session ends when you close the browser.
Clearing site data. Most browsers let you clear all data for a specific site (cookies, local storage, cache) in a single action. This is a clean way to reset your Portal state without affecting other sites.
Effect of blocking strictly necessary cookies. If you block the session cookie, the authentication token cookie, or the CSRF token cookie on the Portal, the Portal will not function correctly: you will not be able to stay logged in, and form submissions will be rejected for security reasons. We recommend leaving these cookies enabled.
Effect of blocking functional cookies. If you block the Remember-me cookie or the theme cookie, you simply lose the corresponding preference. You can still use the Sites normally; you will just have to log in every time, or the documentation site will revert to the default light theme.
No cookie-consent banner today. Because the cookies described in this Policy are either strictly necessary or set only with your active choice (the "Remember me" checkbox), we do not show a cookie-consent banner. If we ever change that — by introducing a cookie that requires consent — we will add a banner before activating the new cookie, and we will not load it until you have made an active choice.
The Sites and the cookies set on them are not directed at children. As described in Section 13 of the Privacy Policy, the minimum age to register an Account on the Portal is 18 (or 16 with parental consent), and the minimum age to use the public documentation site is 16, in line with the default age for valid GDPR consent in Hungary.
We may update this Cookie Policy from time to time, for example to add a new cookie, to change the duration of an existing one, or to reflect changes in browser technology and applicable law.
This Cookie Policy is co-ordinated with the Privacy Policy: where a change affects both documents, we update both together.
If you have a question or concern about cookies on the Sites, the simplest way to reach us is:
For data-protection questions that go beyond cookies, please use the same channel and follow Section 12 of the Privacy Policy for the formal data-subject request procedure.
End of Cookie Policy.
Effective Date: 12 May 2026 — Version 1.0 — DroneSpot Kft.
© 2026 DroneField. All rights reserved.