Cookie Policy

How Alta Ignite uses cookies, local storage and similar technologies across our website and client dashboard, and how you can control them.

Version in force · Last updated 6 February 2026

1. Scope and purpose

1.1 This Cookie Policy explains how Lanex Group, LLC, a limited liability company organised under the laws of the United States registered office in the United States ("Alta Ignite", "we", "us"), uses cookies, local storage, session storage and similar tracking technologies on altaignite.com and its client dashboard (together, the "Platform").
1.2 This policy applies to every visitor and customer of the Platform, worldwide, and should be read together with our Privacy Policy and our Terms and Conditions. Where this policy refers to "cookies" it also refers to functionally equivalent technologies such as HTML5 local storage, session storage, pixels and SDKs unless the context requires otherwise.
1.3 We provide this policy to comply with the ePrivacy Directive 2002/58/EC as implemented in EEA member states, and, insofar as cookies involve processing of personal data, Articles 6 and 13 of the General Data Protection Regulation (GDPR).

2. What cookies and local storage are

2.1 A cookie is a small text file placed on your device by a website you visit. Cookies allow the website to recognise your device on return visits, remember choices you made, and collect information about how the site is used.
2.2 Local storage and session storage are browser mechanisms that allow a website to store data on your device without a fixed expiry date (local storage) or for the duration of a browser tab session (session storage). We use both cookies and local/session storage depending on the technical purpose, as set out in the inventory below.
2.3 Cookies and local storage entries may be "first-party" (set directly by altaignite.com) or "third-party" (set by a domain other than altaignite.com, typically a supplier acting as our processor or as an independent controller for its own service, such as Stripe or Plausible).

3. Categories of cookies we use

3.1 Strictly necessary: required for the Platform to function, such as maintaining a login session, securing checkout, and load-balancing. These cannot be switched off through our consent banner because the Platform cannot operate without them, consistent with the exemption in Article 11.7a(3) Telecommunicatiewet and Recital 66 of Directive 2009/136/EC for cookies strictly necessary to provide a service explicitly requested by the user.
3.2 Functional/preference: remember your choices, such as display currency, language locale and dismissed notices, to avoid asking you again on every visit.
3.3 Commercial/marketing-adjacent functional cookies: support time-limited signup mechanics, such as the onboarding countdown described in clause 5.4, which do not track you across other websites but do store state locally to run a feature you triggered.
3.4 Analytics: help us understand aggregate usage of the Platform so we can improve it. We use privacy-preserving, cookie-less-by-default analytics (Plausible) where practicable; where any analytics cookie is used it is deployed only with your consent.
3.5 Payment processing cookies: set by our payment processor, Stripe, during and after checkout to prevent fraud, remember payment method selection and complete 3-D Secure authentication.

4. Legal basis for use

4.1 Strictly necessary cookies and local storage are placed without requesting prior consent because they fall within the statutory exemption for cookies that are technically necessary to provide a service you have explicitly requested (Article 11.7a(3) Telecommunicatiewet; Article 5(3) ePrivacy Directive, second sentence).
4.2 All other cookies, including functional preference cookies that are not strictly necessary, analytics cookies and any third-party marketing cookie, are placed only after you give freely given, specific, informed and unambiguous consent through our cookie banner, in line with Article 11.7a(1) Telecommunicatiewet and, insofar as personal data is processed, Article 6(1)(a) GDPR.
4.3 Where a cookie is used to perform a contract with you, for example Stripe's fraud-prevention and payment-completion cookies at checkout that you initiate, we additionally rely on Article 6(1)(b) GDPR (performance of a contract) and Article 6(1)(f) GDPR (legitimate interest in fraud prevention) as applicable, without prejudice to the ePrivacy consent requirement described in clause 4.1 where the exemption applies.
4.4 You may withdraw or change your consent at any time with effect for the future, as described in clause 7. Withdrawal does not affect the lawfulness of processing carried out before withdrawal.

5. Cookie and local storage inventory

5.1 Session and authentication — Name: `ai_session`. Purpose: maintains your authenticated session on the client dashboard and checkout. Duration: session cookie, cleared on logout or up to 24 hours of inactivity. Party: first-party (altaignite.com). Category: strictly necessary.
5.2 Locale and currency preference — Name: `ai_locale_pref` (local storage). Purpose: remembers your selected display language and billing currency so prices and copy are shown consistently on return visits. Duration: persistent, up to 12 months, refreshed on each visit. Party: first-party. Category: functional/preference, requires consent unless you have actively set the preference yourself in that session (in which case it is treated as necessary to deliver the feature you requested).
5.3 CSRF protection — Name: `ai_csrf`. Purpose: cross-site request forgery protection token for form submissions, including checkout and the client board. Duration: session. Party: first-party. Category: strictly necessary.
5.4 Signup countdown state — Name: `ai_signup_countdown` (local storage). Purpose: stores the timestamp at which a visitor's onboarding-offer countdown began, so the countdown timer displayed during signup persists correctly across page reloads and does not reset or extend when you navigate away and back. Duration: persistent until the offer window expires (typically 30 minutes) or is manually cleared. Party: first-party. Category: functional, requires consent because it is not strictly indispensable to deliver the underlying checkout service, although it does not identify you individually.
5.5 Stripe checkout and fraud prevention — Names include `__stripe_mid` and `__stripe_sid`. Purpose: fraud detection, risk scoring and maintaining state through the hosted Stripe Checkout and payment element flow. Duration: `__stripe_mid` persists for approximately 1 year; `__stripe_sid` persists for approximately 30 minutes. Party: third-party, set by Stripe Payments Europe, Limited on stripe.com and js.stripe.com domains during checkout. Category: strictly necessary for completing the payment transaction you initiate; Stripe acts as an independent controller for fraud-prevention purposes and as our processor for payment processing purposes.
5.6 Analytics — Plausible Analytics is configured in cookie-less mode by default and does not set any cookie or local storage entry; it aggregates page-view counts from request metadata only. If we enable an optional cookie-based analytics feature in the future, it will appear here with its name, duration and purpose before it is activated, and will only run after you consent under clause 4.2.
5.7 Cookie consent record — Name: `ai_cookie_consent` (local storage). Purpose: records which categories of cookies you have accepted or rejected so we do not show the banner on every visit and can honour your choice. Duration: persistent, 6 months, after which consent is re-requested. Party: first-party. Category: strictly necessary to operate the consent mechanism itself.

6. Cookie banner and consent management

6.1 On your first visit from the European Economic Area, the United Kingdom or Switzerland, and by default for all visitors globally, we display a cookie banner allowing you to accept all cookies, reject all non-essential cookies, or configure preferences by category described in clause 3.
6.2 No non-essential cookie is set until you interact with the banner and provide consent. Rejecting non-essential cookies does not prevent you from using the core Platform, though certain convenience features, such as remembering your currency preference, will not persist between visits.
6.3 You can review and change your cookie preferences at any time using the "Cookie preferences" link in the website footer, which reopens the consent management panel.

7. How to withdraw consent

7.1 To withdraw consent for functional, marketing-adjacent or analytics cookies, open the cookie preferences panel referenced in clause 6.3 and deselect the relevant category, or select "reject all non-essential".
7.2 Withdrawing consent takes effect immediately for future cookie placement. Cookies already stored on your device in the relevant category will be deleted or allowed to expire according to their stated duration; you may also delete them manually using your browser controls described in clause 8.
7.3 If you withdraw consent for the signup countdown local storage entry described in clause 5.4, the countdown feature will not function correctly and you may see a generic offer notice instead; this does not affect your statutory rights or the price displayed at checkout.

8. Browser and device controls

8.1 Most browsers allow you to view, block, delete or restrict cookies through browser settings. Refer to your browser's help documentation for Chrome, Firefox, Safari, Edge or your mobile browser for exact steps, as menu locations change between versions.
8.2 You can also clear local storage and session storage through your browser's developer tools or privacy settings, typically found under "Site settings" or "Privacy and security".
8.3 Blocking or deleting all cookies, including strictly necessary ones, will prevent you from logging in, completing checkout or using the client dashboard, because those cookies are technically required for the Platform to function.
8.4 Mobile operating systems (iOS App Tracking Transparency, Android privacy settings) provide additional device-level controls over cross-app tracking; the Platform does not use cross-app tracking SDKs.

9. Do-Not-Track and Global Privacy Control

9.1 Some browsers transmit a "Do Not Track" (DNT) signal or a Global Privacy Control (GPC) signal. There is currently no universally adopted industry standard for interpreting these signals.
9.2 We treat a valid GPC signal received from your browser as equivalent to a rejection of non-essential cookies under clause 6.2 for that browser session, to the extent our consent management technology is able to detect it.
9.3 Because DNT lacks a common technical standard, we do not currently alter non-essential cookie behaviour based on DNT alone; you should use the cookie preferences panel in clause 6.3 to make an explicit choice.

10. Third-party cookies and processors

10.1 Third-party cookies described in clause 5 are placed by suppliers acting either as our data processors under Article 28 GDPR (for example, error-monitoring or infrastructure providers that may set operational cookies) or, in the case of Stripe's fraud-prevention cookies, as an independent controller for that specific purpose.
10.2 A full list of subprocessors that may set or read cookies or otherwise process data in connection with the Platform is maintained at our Subprocessors page, which we update when a subprocessor is added, replaced or removed.
10.3 We do not sell cookie or browsing data to third parties and do not permit our processors to use Platform data for their own independent marketing purposes.

11. International data transfers via cookies

11.1 Where a cookie causes personal data to be transferred outside the European Economic Area, for example to a supplier's servers in the United States, we ensure an appropriate safeguard is in place under Chapter V GDPR, including adequacy decisions, the EU-U.S. Data Privacy Framework where applicable to the recipient, or the Standard Contractual Clauses adopted by Commission Implementing Decision (EU) 2021/914.
11.2 Further detail on transfer mechanisms applicable to specific suppliers is set out in our Privacy Policy and Subprocessors page.

12. Children

12.1 The Platform is directed at business customers and is not intended for use by children. We do not knowingly use cookies to collect personal data from individuals under the age of 16 for marketing or analytics purposes.

13. Changes to this policy

13.1 We may update this Cookie Policy to reflect changes in the cookies and technologies we use, changes in law, or supplier changes recorded on our Subprocessors page.
13.2 Material changes that expand the categories of non-essential cookies used will trigger a renewed consent request through the banner described in clause 6. The "Last updated" date at the top of this page indicates the version currently in force.

14. Contact and complaints

14.1 Questions about this Cookie Policy or our use of cookies can be sent to privacy@altaignite.com or legal@altaignite.com, or by post to Lanex Group, LLC, United States.
14.2 If you are not satisfied with our response, you have the right to lodge a complaint with the data protection authority in your own EU member state of residence or work, or, outside the EEA, with your local competent authority.

Questions about cookies: privacy@altaignite.com — Lanex Group, LLC, United States.