CurNext · Legal
Cookie Policy
How CurNext uses cookies and similar technologies on curnext.app, how categories work, what is stored today, and how you can change or withdraw consent.
Controller: CurNext (Finland). Privacy requests: [email protected]. Cookie choices are stored in this browser and can be changed at any time.
This policy explains cookies and similar technologies for transparency under the ePrivacy Directive and GDPR. It is not a substitute for the Privacy Policy, GDPR Policies, or legal advice. Where this page and a signed contract conflict, the signed contract controls for that relationship.
Last updated: 11 August 2026
Purpose of this policy
CurNext operates a marketing website and related product surfaces that need a small set of technologies to function. Some are strictly necessary. Others are optional and only run when you consent.
- - Explain what cookies and similar technologies are on CurNext properties.
- - Describe consent categories and how the on-site consent widget works.
- - List the technologies CurNext uses today, without inventing vendors that are not active.
- - Tell you how to change or withdraw optional consent.
- - Point to GDPR Policies, Privacy Policy, and Knowledge Base AI consent where relevant.
Who is responsible
For cookie and similar-technology processing on the marketing site where CurNext determines the purposes and means, the controller is:
- CurNext
- Registered in Finland
- Business ID Coming soon
- Website: https://curnext.app
Questions about cookies or privacy: [email protected]. Security incidents: [email protected].
What cookies and similar technologies are
Cookies are small text files stored on your device. CurNext may also use local storage, session storage, pixels, or scripts that serve a similar purpose.
- - First-party technologies set by CurNext on curnext.app and related domains we operate.
- - Third-party technologies set by providers that help us deliver specific features (for example bot protection on forms).
- - Session technologies that expire when you close the browser, and longer-lived storage when needed for a stated purpose.
- - Similar technologies such as local storage used for theme preference or consent records.
Consent categories
The CurNext consent widget groups technologies into four categories. Necessary is always on. Optional categories stay off until you accept them.
Necessary
Required to deliver the site securely and reliably: locale routing, security and abuse protection on forms (Cloudflare Turnstile), authentication cookies when you use invite-only features, and storing your cookie consent choice itself.
Preferences
Optional technologies that remember choices such as appearance (light / dark / system). They are not required to browse the site.
Analytics
Optional measurement tools that help us understand site usage. CurNext does not currently load a third-party analytics vendor on the marketing site. This category is reserved so tags can be gated behind consent when configured.
Marketing
Optional advertising or campaign technologies. None are loaded today. This category is reserved for future tags that must not run without consent.
Cookie and storage inventory
The following inventory reflects technologies CurNext documents for the marketing site. Entries marked reserved are categories only - no vendor script runs until enabled and consented.
| Name / type | Category | Purpose | Duration | Provider |
|---|---|---|---|---|
| curnext-cookie-consent | Necessary | Stores your cookie preference choices and consent version for this browser. | Local storage - until cleared or consent version changes | CurNext (first-party) |
| Theme preference | Preferences | Remembers light / dark / system appearance when you set a theme. | Local storage - until cleared | CurNext (first-party) |
| Locale / routing | Necessary | Delivers the correct language route and locale handling for the marketing site. | Session / as required by the framework | CurNext (first-party) |
| Supabase auth session | Necessary | Keeps you signed in for invite-only product features when authentication is used. | Session / managed auth cookie lifetime | CurNext via Supabase |
| Cloudflare Turnstile | Necessary | Bot protection on contact, quote, demo, subscribe, and job application forms. | As set by Cloudflare for the challenge widget | Cloudflare |
| Analytics tags (reserved) | Analytics | Reserved for optional measurement tags. No analytics vendor is loaded until this category is enabled and a vendor is configured. | N/A until enabled | None active |
| Marketing tags (reserved) | Marketing | Reserved for optional advertising or campaign tags. None are loaded until this category is enabled and a vendor is configured. | N/A until enabled | None active |
Legal bases
Depending on the technology and your location, CurNext relies on the following bases.
Necessary / legitimate interest or contract
Strictly necessary technologies that deliver a service you request, keep the site secure, or store your consent record. Where ePrivacy requires it, these are exempt from consent.
Consent
Optional preferences, analytics, and marketing technologies run only after you opt in through the consent widget (or an equivalent control).
Withdrawal
You may withdraw optional consent at any time via Cookie settings. Withdrawal does not affect the lawfulness of processing before withdrawal.
Retention
Storage lifetimes depend on the technology and purpose.
- - Consent records remain until you clear site data or we publish a new consent version that invalidates prior choices.
- - Session technologies expire when the browser session ends, unless a longer lifetime is required for security or authentication.
- - Third-party durations (for example Turnstile) follow the provider's documented lifetime for that feature.
- - Reserved analytics and marketing entries have no retention until a vendor is actually enabled.
How to manage cookies
You control optional categories on CurNext through the on-site widget and your browser.
- - Use Accept all, Reject optional, or Customize on the consent banner.
- - Reopen Cookie settings anytime from the floating control or this page.
- - Clear site data in your browser to remove local storage and cookies for curnext.app.
- - Browser settings can block third-party cookies; blocking necessary technologies may break forms or sign-in.
Changing preferences updates the consent record stored in this browser under the current consent version.
Third parties
Some features rely on processors or service providers that may set their own cookies or similar technologies when the feature runs.
- - Cloudflare Turnstile for form bot protection.
- - Supabase for authentication cookies when invite-only features are used.
- - Hosting and edge infrastructure that may set strictly necessary operational cookies.
- - No advertising network or analytics SaaS is loaded on the marketing site today under the reserved categories.
Knowledge Base AI consent
The Knowledge Base assistant asks for a separate, explicit GDPR consent before sending your question to an AI provider. That product-flow consent is not the same as the sitewide cookie categories, though both can be withdrawn. See the Knowledge Base page for details.
Changes to this policy
We may update this Cookie Policy when products, vendors, or law change. The Last updated date will change for material revisions. A new consent version may ask you to choose again.
Translations are provided for convenience. Where a signed agreement exists, the English instrument controls.