Cookies are small text files stored on your computer, tablet, or mobile device when you browse websites. They are widely used to make websites function efficiently, improve user experience, and provide analytical telemetry to site operators.
On SmartProcurAI, we strictly minimize cookie usage to focus on infrastructure performance, functional security, and seamless application operations.
SmartProcurAI utilizes cookies for two primary corporate objectives:
Because SmartProcurAI uses stateful computational engines to run high-performance text pipelines, our web layout depends heavily on continuous, unbroken WebSocket connections between your browser and our server infrastructure.
To enable this, we use an AWS Application Load Balancer (ALB) Cookie-Based Sticky Session identifier. This cookie maps your web requests specifically to your dedicated, highly isolated secure Docker container task running on AWS compute layers. Without this cookie, subsequent user interaction events would risk routing randomly to a clean instance thread, resulting in abrupt connection drops and a complete reset of your current proposal drafting section.
| Cookie Name | Classification | Operational Purpose | Retention Window |
|---|---|---|---|
| AWSALB / AWSALBCORS | Strictly Necessary (First-Party) | Enforces Application Load Balancer Sticky Sessions. Pins user connection threads safely to the correct, isolated Docker container container executing data parsing algorithms. | 7 Days |
| smartprocurai_session | Strictly Necessary (First-Party) | Maintains secure user state confirmation, workspace access permissions, and basic encrypted authentication tokens. | Session / End of Browser Close |
| XSRF-TOKEN | Security (First-Party) | Blocks cross-site request forgery attacks to secure corporate subscription portals and data submittals against unauthorized manipulation. | Session |
SmartProcurAI believes in complete data privacy. We do not embed third-party marketing trackers, commercial pixel networks, or behavioral advertising cookies on our application workflow dashboards. Any data required to deliver core generative services is processed ephemerally using internal system API protocols directly bound by non-disclosure conditions.
You have the option to restrict, reject, or wipe cookies entirely via your web browser configuration menu settings (such as in Google Chrome, Mozilla Firefox, Apple Safari, or Microsoft Edge).
Please note: Because our infrastructure cookies are strictly necessary for core load-balancing and protocol management, blocking or rejecting them will significantly destabilize application behaviors, break your interactive WebSockets, and disrupt live proposal writing streams.
We review and update this technical cookies manifest regularly to match infrastructure optimizations and legal refinements under European data protection standards. Any modification regarding technical tracking policies will be listed directly on this page.