Introduction and 2026 Consent Standard
This Cookie Policy explains how AssaAalliance uses cookies, local storage, and similar technologies on https://assa-alliance.com. We use the term "cookies" broadly in this notice because visitors often understand the concept more easily when related technologies are grouped together. In practice, the site currently relies primarily on browser storage to remember your cookie preference, and some third-party providers may use their own request-based technologies when serving fonts, maps, or framework files. Our goal is to give visitors a clear explanation of what is active, what is optional, and how control can be exercised in line with modern privacy expectations, including the consent principles associated with GDPR and similar European rules in 2026.
We separate essential functions from optional functions whenever it is reasonably possible to do so. Essential technologies are the ones needed to operate the site, maintain security, preserve your stated cookie preference, or provide a feature you requested directly. Optional technologies are those that measure usage for analytics, support personalization beyond core functionality, or enable future advertising and remarketing activity. If optional technologies are introduced in a jurisdiction that requires prior consent, we intend to request that consent before activating them. The fact that a technology exists in theory does not mean it is active at all times, so this policy also explains the practical state of implementation rather than assuming every possible category is already in use.
What Cookies and Similar Technologies Are
A cookie is a small text file that a website or third-party service can place on your browser so the browser can remember something about your visit. Similar technologies include local storage, session storage, pixels, tags, SDK-like scripts, and embedded service calls that can recognize browser state or record interaction information. Some technologies expire when you close your browser, while others remain until a preset period ends or you delete them manually. These tools can support a wide range of useful tasks, from preserving a consent choice to understanding whether a page is loading correctly for visitors across different devices.
Not every tool stores information in the same way. For example, the AssaAalliance consent mechanism uses browser storage to remember whether you accepted or declined optional categories. An embedded map may not place a cookie directly from our domain, but the external map provider may still process request data when the frame loads. A font provider may not create a traditional cookie at all, yet still receive the browser request necessary to deliver the font file. For that reason, a modern cookie policy should discuss both cookies and comparable technologies that affect privacy or user control, rather than focusing only on classic browser cookies.
Categories We Use
Essential technologies are used to operate the website, keep core features available, preserve security-related behavior, and remember the consent setting you choose in the cookie modal. Without those technologies, the site may fail to remember whether you accepted or declined optional processing, and the user experience can become repetitive or less functional. We treat the storage of your own preference choice as essential because it is necessary to honor the decision you made. These technologies are limited in scope and are not intended to build behavioral profiles or follow you across unrelated websites.
At the time of this policy update, AssaAalliance does not claim to run broad advertising cookies or cross-site tracking systems as a default site feature. We may consider adding privacy-conscious analytics or performance measurement in the future so we can understand how content is used and improved. If those tools would qualify as non-essential in a jurisdiction that requires prior consent, they will remain disabled until you opt in through the preference controls or another valid consent pathway. If we introduce additional categories such as analytics, personalization, or marketing, we will describe them in this policy and explain the practical consequences of accepting or declining them.
Legal Basis and GDPR 2026 Alignment
Where European privacy rules, UK rules, or similar consent-based frameworks apply, our approach is to request consent before activating non-essential cookies or similar technologies. Essential technologies that are strictly necessary to provide a service you requested, such as remembering your cookie choice or loading fundamental site assets, may be used without prior consent where the law allows. This distinction reflects the core principle that users should control optional data processing while websites remain capable of basic operation. We also aim to make the choices intelligible by labeling buttons clearly and linking the consent interface to this policy for more detail.
Alignment with a 2026 GDPR-style standard means more than simply displaying a banner. It means the consent interface should avoid misleading design, should not bundle optional choices into vague language, and should allow the visitor to revisit the decision later. That is why the footer includes a "Manage Cookies" button that removes the saved preference and reopens the modal. We view consent as a continuing state that can be revisited, not a one-time trap. If laws change in a way that requires more detailed category-level controls, we may revise the interface accordingly and update this policy to match the new implementation.
Third-Party and Embedded Services
Some third-party services may process technical request data as part of delivering content embedded or referenced on the site. Examples include Google Maps for the contact page, Google Fonts for typography delivery, and content distribution services such as jsDelivr for Bootstrap framework assets and icons. When your browser requests those resources, the provider may receive your IP address, browser metadata, and the context needed to return the requested file. In some cases, those providers may use cookies or equivalent identifiers under their own policies, even if the core AssaAalliance domain does not set that cookie itself.
Because embedded and CDN-supported services are controlled by external providers, their behavior can change over time. We review such dependencies with a preference for widely used services that support practical website delivery, but we do not represent that the provider's privacy approach will always match our own. You should review the external provider's documentation if you want complete details about how that provider uses browser requests, storage mechanisms, or international transfer infrastructure. If we remove, replace, or add embedded services in a way that materially changes cookie-related behavior, we will revise this policy and update the consent flow where required.
How to Manage Cookies and Storage
You can manage your preference on AssaAalliance by using the cookie modal when it appears or by selecting the "Manage Cookies" button in the footer at any later time. That button clears the saved consent value from browser storage and immediately reopens the preference interface so you can accept or decline again. If optional tools are introduced in the future, this control will continue to serve as the on-site method for revisiting the decision. The site currently keeps the logic intentionally simple so the user can understand how the preference is being remembered.
You can also manage technologies at the browser level. Most browsers allow you to block cookies, clear stored data, limit third-party cookies, or control site-specific storage permissions. Please note that blocking all cookies or all storage mechanisms can affect how many websites work, including the ability to remember your own settings. Browser controls operate separately from our on-site consent flow, so changing browser settings may remove stored choices or interfere with embedded services. If you use multiple devices or browsers, you may need to make the same choice separately on each one because the setting is stored within that specific environment.
Retention Periods and International Access
The length of time a cookie or similar technology remains active depends on the purpose of the storage and the provider involved. Preference-related storage may remain until you clear it, change the setting, or reset your browser data. Session-based technologies may disappear automatically when a browsing session ends. Third-party services may define their own retention periods in their own systems, and those periods can differ from the storage we control directly. Because some site dependencies are delivered through globally distributed infrastructure, request data may also be processed from multiple countries during normal page delivery.
If you access the site from outside the United States, the technologies that support the site may still involve international data flows, whether through hosting, content delivery, or embedded providers. We aim to be transparent about that reality because internet delivery is rarely confined to a single geographic point. Where a law gives you the right to know more about transfers or to object to certain optional processing, you can contact us using the details in this policy. We will respond based on the actual technologies in use at the time of your request and the legal framework that reasonably applies.
Browser Settings, Device Context, and Practical Impact
Cookie and storage controls work differently across browsers, devices, and privacy modes. A preference recorded on one laptop browser may not carry over to a phone, a tablet, or a second browser on the same computer because each environment keeps its own storage area. Some private or incognito modes automatically delete stored values at the end of the session, which means the site may ask for your preference again the next time you visit. Browser extensions, tracking-prevention features, network filters, or enterprise device controls can also change how cookies and local storage behave. We describe these practical differences because a user may reasonably believe that one action applies everywhere when, in reality, the control is often device-specific.
Blocking or clearing storage can also have practical side effects that are not punitive but are worth understanding. If you erase all stored data, the site may lose the record of your previous preference and show the consent modal again. If a browser blocks third-party requests entirely, embedded services such as maps or font delivery may not function as expected, even though the core page remains available. If a corporate network strips external assets, the layout may look simpler or some icons may not load. None of those outcomes are intended to pressure you into accepting cookies; they are simply the technical consequences of how web delivery works across different browsing environments in 2026.
Consent Records and Future Category Controls
When a visitor accepts or declines the current cookie prompt, AssaAalliance records that outcome in browser storage so the site can respect the choice on later page views from the same browser environment. At this stage, the record is intentionally simple because the site currently uses a narrow consent model centered on essential preference storage and the possibility of future optional tools. If we later activate more granular categories, such as analytics, personalization, or marketing, we may expand the stored record so the site can remember which specific categories were allowed and which were refused. Any such expansion would be paired with an updated explanation in this policy and, where required, a refreshed consent request.
We also recognize that some privacy laws and regulator guidance increasingly expect organizations to demonstrate that consent was gathered through a valid mechanism rather than through silence or preselected toggles. For that reason, any future enhancement to our consent system may include clearer category labels, revised records of user selections, and better disclosure around how a visitor can change those selections later. The principle behind those improvements is straightforward: users should be able to understand what they are choosing, keep that choice consistent over time, and revisit it without unnecessary friction. That principle remains part of how we interpret cookie compliance going forward.
Your Rights and Contact Options
Depending on where you live, you may have the right to receive information about the technologies used on the site, withdraw consent for optional processing, request access to related personal data, or ask additional questions about how browser-based storage interacts with your privacy rights. You may also have the ability to lodge a complaint with a supervisory authority if you believe a consent-based rule has been violated. Exercising a cookie choice on the site will not result in retaliation or a lower quality version of our informational content, although some optional features may remain unavailable if they depend on consent.
If you have questions about this Cookie Policy, the best first step is to contact us at hello@assa-alliance.com. You may also call +1 (415) 728-4619 or write to 315 Montgomery Street, Suite 900, San Francisco, CA 94104, United States. Please tell us whether your concern relates to the on-site consent tool, an embedded service, or a browser-level setting so we can route the issue correctly. We may update this policy from time to time as technologies change, legal standards evolve, or the site adds new features. When that happens, the revised date will change and the updated version will become the reference point for future visits.