Required cookies and similar technologies
AssetLed uses required cookies and browser runtime behavior to keep authenticated app sessions secure, preserve anti-forgery protections, and operate interactive Blazor pages.
- .AssetLed.Auth
- Secure, HTTP-only authentication cookie used after login so the Blazor app and API can identify the authenticated account user.
- antiforgery protections
- ASP.NET Core anti-forgery tokens and related browser state used to protect form and interactive requests against cross-site request forgery.
- Blazor runtime state
- Interactive pages may use server-side connection and reconnect behavior to keep authenticated workflows responsive. Static legal pages are rendered without the interactive runtime.
Third-party cookies and redirects
AssetLed does not currently set advertising cookies, behavioral retargeting cookies, or third-party analytics cookies from this web app. If you choose to connect Google data or complete Stripe checkout, Google or Stripe may set cookies or collect data on their own domains under their own policies.
When you open Stripe Checkout or the Stripe Customer Portal for trial signup, cancellation, payment-method changes, invoices, or package upgrades, Stripe may set cookies or browser storage on Stripe-controlled domains. Those cookies are governed by Stripe's policies and are not controlled by AssetLed.
Your controls
You can block or delete cookies through your browser settings. Blocking required cookies will prevent login, billing, compliance, report, API-key, account, Google integration, and other authenticated workflows from working correctly.
The current Cookie Settings page explains why no optional-cookie preference is stored while only required cookies are used.
If you sign out, rotate credentials, revoke API keys, or clear browser cookies, you may need to authenticate again before using protected pages.
Changes
If AssetLed later adds optional analytics, marketing, or preference cookies, this page should be updated before those cookies are enabled publicly.