Cookie Policy

1. Scope

This policy separately explains browser storage used by the AXVIA marketing website, the customer console at dash.axvia.net and related external services. Website page code, console login, hosting platforms and identity-authentication services each have their own mechanisms. For personal-data processing purposes, recipients and requests, see the Privacy Policy.

2. Cookies and Browser Storage

Cookies are small pieces of information stored by the browser that can be sent with matching subsequent requests, and are used to identify states such as sign-in sessions. localStorage can retain settings on subsequent visits, while sessionStorage is used for temporary state in the current tab. These mechanisms differ in purpose and storage, so they can be reviewed separately by website and storage type when managing them.

3. Marketing website code and examples

The presentation website's own page code does not set cookies; it uses localStorage to save the manual language selection described below. The pages, scripts and graphic assets are used to present the products, and the interface and graphic examples run only in browser memory; they do not call customer APIs or read production account data. The current production site also uses cookie-free access analytics and email link protection provided by Cloudflare; the corresponding access processing is described below.

4. Language preference

On the first visit, the website matches a supported language to your browser preferences, using English if there is no match. Your manual choice is saved in this site’s localStorage under axvia-language for subsequent visits until you change it or clear this site’s storage. The setting stays in the browser, is not automatically sent as a cookie with website requests and is not sent to the customer console. Clearing it makes the website select a language from browser preferences again.

5. Menu and animation choices

Navigation expansion and animation pausing apply only to the current page and are reset after a refresh. The browser's reduced-motion setting affects the default animation playback. These choices are not written to cookies or persistent browser storage.

6. Console sign-in verification

The customer console uses the __Host-axvia-customer-transaction cookie to link the login-verification flow. It remains valid for up to 10 minutes and is cleared during authentication callback processing. The console server sets it with Secure, HttpOnly and SameSite=Lax attributes for use in the login flow.

7. Console sign-in session

The console uses the __Host-axvia-customer-session cookie to identify the browser session. For ordinary logins, both the cookie and server-side session remain valid for 24 hours. The server sets the cookie with Secure, HttpOnly and SameSite=Lax attributes. Logging out deletes the corresponding server-side session and clears the cookie; you must log in again after expiry. Administrator-assisted temporary sessions follow the duration of their authorization and may be shorter than ordinary login sessions.

8. Console functional storage

The Console uses localStorage to remember the currently selected team and the read status of product introductions and feature tips. sessionStorage is used for the temporary flow state of source admission and face verification, and to retain non-secret drafts in the Agent creation form before re-authentication. This data supports team switching, tip display and flow continuity.

9. External identity authentication and payments

Logging in to the Console takes you to the configured identity authentication service; identity verification or payment may also take you to the relevant provider's page. External services may use their own cookies and storage to complete authentication, protection or transactions. The specific cookie names, durations and settings are determined by each service, and the complete list with related explanations is set out in the schedule to be confirmed.

10. Network delivery, analytics and access security

The production website is delivered through Cloudflare, which currently injects its cookie-free Web Analytics and email-address link protection. The provider may process request, network and security information. Cookie-free analytics still processes visit data and does not mean there is no third-party processing. The analytics measures website visits and is not used for advertising tracking. The access-security layer and private previews may use necessary verification mechanisms or sessions according to their configuration; these are separate from customer-console accounts. See the Web Analytics documentation and Cloudflare cookie documentation for information on analytics and security cookies Cloudflare may use. Whether a mechanism is enabled depends on the actual deployment; not all listed cookies are necessarily used on this site.

11. Viewing, clearing and choosing

You can view, restrict or delete cookies and other storage per website in your browser settings, and you can also reselect the language on the website. Clearing the site's language storage restores language selection based on browser preferences; clearing Console feature storage may reset your team selection or read tips. Blocking or deleting necessary sessions may affect login or cause the Console and private previews to require re-authentication. Clearing your browser profile does not delete server-side orders, configurations, audit records or tickets; please submit personal data requests in accordance with the Privacy Policy. Cookie-free analytics does not rely on advertising cookies, and clearing cookies alone does not amount to deleting visit data that has already been processed.

12. Updates and contact

If we introduce new cookies or browser storage purposes, we will update this policy to describe the purpose, retention method and related choices, and provide notice as required by applicable law. For legal and privacy questions, contact [email protected]. For questions about Console login or account use, please submit them through Help and Support.

Additional notes

Complete storage and deletion schedule

The complete names, durations and deletion arrangements for Console feature storage and for external authentication, face verification, payment and preview verification will be added after verification against the actual deployment.

Logs and arrangements for new choices

Specific retention arrangements for website delivery and web analytics data will be added once verified. Before introducing optional browser storage features, we will explain the notice and choice procedures.