Loading AtlasFresh…
Loading AtlasFresh…
Necessary technology keeps checkout, security and consent records working. Optional categories stay off unless you choose them.
Legal and policy information
How AtlasFresh uses necessary storage and controls optional preference, analytics, and marketing technologies.
This policy covers cookies, local storage, pixels, software development kits, and similar browser or device technologies used on atlasfresh.org. AtlasFresh is a trading brand operated by Atlas Digital Assets LLC, the responsible legal business.
Where consent is legally required, AtlasFresh does not load preference, analytics, or marketing scripts before valid consent. The interface provides an equally accessible way to accept or reject optional categories. You can withdraw or change consent later through the cookie-preferences control. Withdrawal does not affect prior lawful processing. Necessary technologies remain available.
The production consent interface will list each active technology, provider, purpose, category, and duration once the associated integration is configured. Optional Tidio onsite features, Klaviyo onsite tracking, analytics, advertising pixels, and generic scripts are disabled by default and must not load until enabled and permitted by the recorded choice. This policy will be revised before a newly enabled provider creates a materially different practice.
Most browsers allow cookies to be viewed, blocked, or deleted. Blocking necessary storage may prevent login, preserve neither cart nor consent choice, interfere with checkout, and reduce security. Browser-based global privacy signals are honoured where applicable law requires and technically supported.
Questions may be sent to support@atlasfresh.org or Atlas Digital Assets LLC's official business mailing address for AtlasFresh correspondence: 8206 Louisiana Blvd NE, Ste A #9970, Albuquerque, NM 87113, United States. This is not a separate AtlasFresh office.
No optional external integration in the AtlasFresh provider registry is currently enabled.
Core hosting, database, domain, and infrastructure providers must also be added to the approved policy version before production launch because they are configured at deployment rather than through this registry.