Cookie Policy
Last updated November 9, 2026
Publication status. This is Aeonav's operational cookie baseline. Aeonav is operated by the Fivecoder team. The final cookie inventory and the production analytics and advertising configuration must be verified against the deployed site before paid commercial launch.
This policy explains how Aeonav uses cookies, localStorage, sessionStorage, and similar technologies on our websites and in the product. It supplements the Privacy Policy.
"Cookies" is used broadly here to include browser storage and similar technologies that read or store information on your device.
The application currently uses a local preference key named elmo.cookie-consent. That name is retained for compatibility with the upstream Elmo codebase and does not mean that Aeonav is operated by Elmo.
These technologies support core operation and security. They are not used for advertising.
| Technology | Purpose | Typical lifetime |
|---|---|---|
| Session and authentication cookies | Keep a signed-in session secure | Session or until sign-out |
| CSRF and callback state | Protect sign-in and form submissions | Short-lived |
elmo.cookie-consent in localStorage | Remember the cookie choice | Until cleared |
| Security and load-balancing storage | Route requests and mitigate abuse | Session or short-lived |
| Error correlation storage | Connect errors from the same visit | Until the tab closes |
The exact cookie names and hostnames can vary by authentication, hosting, and proxy configuration. The deployed service must be inspected to produce a final host-specific inventory.
Aeonav may use analytics, product telemetry, error monitoring, or session replay where enabled and permitted. Based on the current codebase, the following categories may be present:
| Category | Purpose |
|---|---|
| Web analytics | Aggregate page views and referrers |
| Product analytics | Understand feature use and product flows |
| Error monitoring | Diagnose errors and reliability problems |
| Session analytics | Understand interaction and replay sessions |
The presence of code or configuration support does not mean any optional tool is enabled in production. The final list of active providers, cookie names, storage keys, and lifetimes must be verified from the deployed environment and added to the Subprocessors page.
The codebase can support advertising and conversion tags. A final advertising inventory has not been confirmed for Aeonav production.
If advertising tags are enabled, this policy must identify:
Do not assume that every advertising provider supported by the upstream Elmo codebase is active for Aeonav.
Pending confirmation: advertising inventory. No advertising platform is represented as active in this baseline.
Pages may embed third-party content such as video, documentation, or support chat. Those services can set their own storage when loaded or when you interact with them. The deployed site must be checked before a complete third-party embed list is published.
Use the cookie preferences control in the service where available. You can also block or delete cookies and site storage in your browser. Blocking necessary storage can prevent sign-in.
Where applicable law grants a right to withdraw consent or object to processing, email support@fivecoder.com.
Questions about cookies or privacy can be sent to support@fivecoder.com.
Pending confirmation: cookie inventory. The final production cookie table, consent-region behavior, analytics configuration, advertising configuration, and retention periods must be verified before paid commercial launch.
This baseline is adapted from the Basecamp open-source policies under CC BY 4.0, with substantial modifications for Aeonav.