AE Industries Inc | Version 2026-11-17-web-3 | Version date November 17, 2026
Canonical page: https://aeindustries.ai/legal/cookies
1 Purpose and technologies
AE Industries Inc, a Delaware corporation, uses cookies and related storage to support AEOS ERP. This notice covers getaeos.io, aeindustries.ai when published, and the AEOS ERP web, mobile and desktop services and pages that link to it. It supplements our Privacy Notice. Cookies are small values a website stores in the browser and can send back with requests. Local storage persists browser values; session storage generally lasts for the browser tab or session. Native apps also store information on the device. Email pixels and tracked links can record engagement without setting a conventional browser cookie.
We distinguish authentication and security, saved user preferences, local working data, email campaign measurement, marketing-website analytics and advertising, and optional product-improvement analytics. The purpose and actual use determine the required consent or choice under applicable law. Calling a technology essential does not establish a universal exemption.
2 Browser cookies
The historical internal prefix smb-os identifies AEOS ERP storage, not a separate company.
| Name or family | Purpose | Duration or behavior |
|---|---|---|
| smb-os.session_token and __Secure-smb-os.session_token | Authenticate a signed-in session | Session configuration uses a rolling 30-day session, refresh after 24 hours of activity and a five-minute session cache |
| smb-os.current-account-id | Remember the selected tenant for authenticated requests | No fixed maximum age is set; duration depends on browser session handling |
| smb-os.oauth-membership | Carry the selected membership during external-agent OAuth authorization | 600 seconds in the authorization flow |
These are first-party application cookies. Connected identity and security providers may use their own technologies. Authentication configuration includes HttpOnly, SameSite and production Secure controls.
Marketing website tracking
HubSpot visitor tracking is used on getaeos.io, not aeindustries.ai. It can associate visits with submitted contact forms. During the 12 months preceding November 17, 2026, HubSpot was the only marketing-website tracker used on getaeos.io; aeindustries.ai had not been published. Our own AEOS ERP CRM website tracking, Meta Pixel and Google analytics or advertising tools are planned additions. The following descriptions apply where the relevant tool is enabled; they do not assert that all tools currently run or operate on both domains.
| Tool or category | Information and purpose | Storage and duration |
|---|---|---|
| HubSpot on getaeos.io | Visitor identifiers, page history and form context help handle inquiries and associate a submission with visits | Documented cookie examples appear below |
| AEOS ERP CRM for AE's own website relationships | Inquiry/contact information and associated page, referral, campaign or interaction information, where collected, support follow-up and measurement | Identifiers depend on the enabled form or tracking integration; retention follows the purposes and criteria in the Privacy Notice |
| Meta Pixel, where enabled | Website event and conversion measurement; advertising identifiers and interactions may also support audiences and ad personalization | Uses the enabled pixel and related browser identifiers; behavior depends on configuration and applicable choices |
| Google analytics or advertising tools, where enabled | Website use, referral and campaign measurement; advertising tools may add conversion attribution, remarketing or personalized ads | Google tags may use cookies and other identifiers. Analytics and advertising configurations can differ; no single cookie lifetime applies to every Google tool. |
These marketing tools can receive page URLs, visit events, IP addresses, browser/device information and online identifiers. The configured purpose and provider determine the information used. Their presence does not authorize access to customer-controlled ERP records. AE's own prospect records in AEOS CRM are distinct from the records we process for other organizations. See Meta's Pixel overview, Google's partner-site information and Google Analytics cookie settings.
The following are HubSpot's documented cookie lifetimes where those cookies are enabled on getaeos.io.
| Name or family | Purpose | Duration |
|---|---|---|
| __hstc and hubspotutk | Visitor history and matching a form submission to a visitor | Six months |
| __hssc | Visit/session measurement | 30 minutes |
| __hssrc | Detect a new browser session | Browser session |
| __hs_opt_out and __hs_do_not_track | Remember a cookie or tracking choice where configured | Six months |
See HubSpot's cookie description. Availability depends on the page, enabled features and applicable privacy choices.
A cookie's expiration is different from how long a provider or AE retains information already received. The Privacy Notice describes AE's retention rules and criteria. Browser restrictions, cookie renewal and configured settings can affect the actual storage duration.
3 Browser storage and local work
| Storage key or family | Purpose | Duration or clearing behavior |
|---|---|---|
| aeos.data-table.primary-action | Save a table action preference in localStorage | Persists until cleared; no fixed automatic expiry is specified |
| aeos.inventory.scan-standins | Save scanner preferences in localStorage | Persists until cleared; no fixed automatic expiry is specified |
| list-state followed by the page pathname | Keep list filters and scroll state in sessionStorage | Generally lasts for the browser tab or session |
| approve-stroke followed by an approval token | Preserve an unfinished signature drawing in localStorage | Cleared on successful approval; no automatic abandoned-draft expiry is specified |
Browser storage can expose local work to another person using the same device or profile. Clearing it can remove an unfinished signature, unsent work or preferences.
4 Email engagement and improvement analytics
Customer campaign tracking is on by default; customers can disable it. AEOS can embed a small image in campaign email and rewrite links to record opens and clicks associated with that message. Image proxies, privacy features and automated scanners can affect measurement. Per-person open and click records are kept for no more than 12 months, and customers can choose a shorter period.
Campaign outreach is allowed only where both applicable law and the sending provider's terms permit it. Required notices, permissions, suppression and unsubscribe protections still apply. AEOS does not impose a blanket recipient-opt-in rule for all permitted outreach, and a tracking default does not establish legal consent.
AE also uses open and click tracking in its own promotional email, with the same 12-month maximum. Recipients can control remote images through their email client, unsubscribe through the message, or contact privacy@aeindustries.ai. These controls do not retroactively delete event records already collected; privacy and deletion requests remain available under the Privacy Notice.
Optional aggregated, non-identifying analytics for improving AEOS require affirmative customer opt-in and are off by default. They do not permit general-purpose AI model training. This choice is separate from customer campaign measurement, necessary service/security records and marketing-website analytics or advertising choices. Customer ERP data is not sold, shared for cross-context behavioral advertising or used for AE's or its providers' own advertising. Where marketing-website activity is disclosed to Meta or Google for advertising, that separate disclosure may constitute sale, sharing or targeted advertising under applicable law; section 6 explains the available request methods.
5 Third party and native features
Cloudflare Turnstile provides bot protection on careers and application pages. An optional GIF picker can make direct requests to KLIPY, sending the search query and normal network/request information. Connected email, calendar, identity and other services receive data necessary for authorized interactions. Our Subprocessors page identifies providers and their roles; you can also request it from privacy@aeindustries.ai. Independent connected services also have their own notices.
Mobile authentication uses secure device storage. Other query data and timers use application storage; the query-cache configuration has a 24-hour maximum age, which is not a promise that every device copy is securely erased after 24 hours. Firebase handles Android and iOS notifications, with Apple's push service involved in underlying iOS delivery. Push tokens and notification content are processed for delivery. Device settings control notification permissions. Camera/photo permissions support enabled uploads or scanning.
6 Your choices and contact
Organization administrators can disable customer campaign tracking and choose a shorter open/click retention period. Optional AE improvement analytics remain off unless the customer affirmatively opts in. Browser settings can inspect or remove cookies and site storage; device settings manage notifications and permissions. Blocking authentication storage may prevent sign-in or disrupt service. Clearing local storage can delete unsent work. These steps do not delete server records or information already sent to a provider.
Marketing websites. Email privacy@aeindustries.ai to request an opt-out of sale, sharing or targeted advertising for AE-controlled website information; identify the website and the choice requested. You do not need an account to submit that request. Where a page provides Cookie Settings or Your Privacy Choices, you may also use those controls to change the offered optional categories. A website advertising opt-out is separate from unsubscribing from email and from the customer's optional product-improvement analytics selection.
We will honor applicable consent and opt-out requirements. Where law requires prior consent, optional tracking requires that consent before it begins; you may withdraw it. Qualifying opt-out preference signals, including Global Privacy Control where applicable, will be treated as requests under the applicable law, not as permission for additional tracking. See the California Privacy Protection Agency's explanation of opt-out signals.
Provider settings can offer additional controls, such as Google's ad settings. Those settings do not replace a request directed to AE, and blocking or deleting cookies alone does not necessarily stop all information transmission or remove records already received. Privacy and deletion requests remain available through the Privacy Notice.
Contact the Privacy Officer at privacy@aeindustries.ai or AE Industries Inc, 413 Spears Avenue, Chattanooga, TN 37405, United States. We update this notice when the inventory or practices change and provide additional notice or choice where required.