Cookies and similar browser storage
Cookies are small values a website can ask a browser to store and send with later requests. Session storage and local storage keep values in the browser under different lifetime and access rules. They should not all be described as advertising trackers; their purpose depends on how the site uses them.
The public marketing website
The current marketing source contains no analytics, advertising trackers or browser-storage calls. Its menus run in the page, and the inquiry request is sent without browser credentials. No nonessential cookie consent banner is added merely for decoration.
The deployed environment must still be checked for cookies introduced by hosting, security proxies or later integrations. This draft describes the application source reviewed on 21 October 2026; it is not a completed production cookie audit.
The signed-in application
The web application uses a protected refresh-session cookie named ab_refresh to support signed-in access. It is HttpOnly, so client scripts cannot read it. Session storage is also used for limited flow state, such as invitation handling and device-registration progress. These uses are separate from browsing the public marketing pages.
The final inventory must confirm the cookie host, configured expiry, purpose and all other deployed storage keys. Do not claim a fixed lifetime unless it has been checked against the deployment configuration.
Your browser choices
You can inspect and remove cookies through your browser settings. Blocking necessary session cookies can prevent sign-in or interrupt a session. Clearing browser data may also remove saved flow state; keep recovery information somewhere safe and do not clear desktop application data to troubleshoot synchronization.
If optional analytics or advertising technologies are introduced, their purposes and available choices must be documented before use. The operator should reassess whether additional consent controls are required.
Contact and updates
Example Accounting Software Private Limited and privacy@example.com are dummy identity details. Replace them with a real operator and monitored privacy channel before publishing an operative policy. Review this page whenever browser storage or service providers change.