LumaWall does not currently use advertising cookies. Payment and infrastructure providers may use their own essential or fraud-prevention technologies when you interact with them.
1. Cookies and similar technologies
Cookies are small values stored by a browser and sent with later requests. Similar technologies include session storage and provider security signals. This policy covers LumaWall’s use of those technologies; provider-controlled pages are also governed by the provider’s policy.
2. What LumaWall uses
| Category | Purpose | Typical duration |
|---|---|---|
| Authentication | Keep you signed in, protect account actions, and maintain a secure session. | Session or the period configured for the account session. |
| Email verification | Temporarily remember the email being verified so the one-time-code flow can continue. | About 30 minutes, or until verification completes. |
| Secure purchase handoff | Hold the short-lived purchase token passed from the desktop app while checkout and activation finish. | The current browser tab session. |
| Security and checkout providers | Prevent fraud, secure traffic, remember checkout state, and present eligible payment methods. | Set by the relevant provider. |
3. Your controls
You can block or delete cookies and site data in your browser settings. Blocking essential storage may sign you out or prevent verification, community access, checkout, payment confirmation, or app-to-browser purchase handoff from working. Clearing a desktop purchase token may require starting checkout again from LumaWall.
4. Analytics and browser signals
The current LumaWall application does not intentionally set advertising or cross-site behavioral-tracking cookies. Because there is no cross-site advertising profile to alter, browser “Do Not Track” signals do not change the essential storage described above. If analytics or optional cookie categories are introduced, this policy and any required controls will be updated before those uses apply.
5. Changes and questions
We may update this policy when browser storage or providers change. The effective date identifies the current version. Questions can be submitted through Support or, if needed, the feedback form.