Cookie Settings & Storage Scope
Learn exactly how local memory buffers optimize multi-threaded queries without infringing upon baseline identity metrics.
Why We Use Client-Side Memory
To operate a cross-regional meta-search engine displaying hundreds of dynamic filter outputs concurrently, Amanose uses small browser tokens known as Cookies alongside local string configurations. These tools allow our interface pages to communicate securely with proxy API endpoints while retaining selected sub-title data (`destinationSubtitle`) across fast window navigations.
Cookie Categorization Matrix
Mandatory system variables maintaining secure API request cycles. These include basic anti-CSRF signatures, short-lived session hydration keys, and dynamic endpoint validation maps matching specific geographical auto-resolve targets. Cannot be deactivated safely.
Buffers capturing custom price scale bounds, active market currency overrides, selected check-out limits, and search layout visual choices. Ensures returning users skip redundant re-input steps.
Anonymous evaluation strings monitoring network hand-off latency, component load dropouts, filter render speeds, and error stack trace summaries. Let us catch proxy errors before they degrade client side speed.
Third-Party Tracking Tokens
When navigating away via an outbound "View Deal" provider card, an anonymous redirection fingerprint (`userTrackId`) is attached transparently to guarantee correct booking rate attribution.
Manual Browser Invalidation
You maintain total command over local token presence. To flush active Amanose session cache buffers instantly, execute standard storage wipes directly within native browser application panels:
- Chrome: Ctrl+Shift+Del
- Safari: Settings > Privacy
- Firefox: Options > Privacy