Flightcase Help
Cookie & Storage Notice
This notice explains how Flightcase uses cookies, browser storage, embedded services, and optional tracking categories.
Current default
Flightcase uses essential cookies and browser storage for login, security, form protection, workspace state, and core product behavior. Optional analytics and marketing storage are off by default unless a visitor allows them and Flightcase has configured those services.
Storage inventory
| Storage | Purpose | Required | Retention |
|---|---|---|---|
| Session cookies | Keep users signed in, maintain workspace scope, protect forms, and support secure session behavior. | Yes | Session lifetime or logout. |
| CSRF/session state | Protect forms and API actions from cross-site request forgery. | Yes | Session lifetime. |
| Local browser storage | Remember interface state such as builder panels, wallboard cards, read markers, and privacy choices. | Mostly functional | Until cleared by the browser or changed by the user. |
| Session browser storage | Temporarily restore scanner, inventory, and workflow state while a tab is open. | Functional | Usually until the browser tab closes. |
| Stripe.js | Support secure card/payment collection on payment pages. | Only for payment workflows | Managed by Stripe according to its terms. |
| Google Maps / Places | Support venue lookup, mapping, addresses, and logistics features where enabled. | Only for mapping workflows | Managed by Google according to its terms. |
| Analytics | Optional product or website measurement. | No | Disabled unless configured and allowed. |
| Marketing pixels | Optional advertising or campaign measurement. | No | Disabled unless configured and allowed. |
Changing choices
You can reopen the privacy choices panel from this page. Browser-level controls can also clear cookies and local storage. Clearing required storage may sign you out, reset interface state, or interrupt forms and workflows.