Plain-language summary: ReleaseAtlas does not currently add analytics, advertising, personalization, or product-session cookies through this static website code. A hosting or network provider may still use strictly necessary mechanisms to deliver and protect the site.

1. What cookies and similar technologies are

Cookies are small pieces of data a website or service can ask a browser to store. Similar technologies can include local storage, session storage, pixels, software development kits, and identifiers in network requests. They may support essential operation, preferences, measurement, or advertising, depending on how they are configured.

2. Current site behavior

The current ReleaseAtlas prototype is made of static HTML and CSS. It does not include app-owned JavaScript, analytics tags, advertising pixels, chat widgets, video embeds, or social media trackers. ReleaseAtlas does not currently use the site code to recognize visitors across websites or build advertising profiles.

The mobile navigation and frequently asked question controls use native HTML elements and CSS; they do not require a cookie. The contact and demo forms validate fields in the browser and do not transmit or store submitted values.

3. Hosting, network, and security mechanisms

The companies that host, route, or protect the website may use short-lived cookies, request identifiers, or comparable mechanisms that are strictly necessary for security, traffic management, abuse prevention, and reliable delivery. Their use depends on the deployed configuration and their own service terms.

ReleaseAtlas should review that configuration before public launch, document any mechanism actually present, and avoid classifying optional measurement or advertising technology as essential.

4. Potential future categories

If the site later introduces new technologies, they may fall into categories such as:

  • Strictly necessary: security, load balancing, authentication, or requested functionality.
  • Preferences: choices such as language, region, or interface settings.
  • Measurement: aggregated understanding of site performance and content use.
  • Marketing: campaign attribution or advertising-related tracking.

Optional categories should not be activated without an appropriate notice and choice mechanism where one is required. This list describes possible categories, not technologies currently deployed by ReleaseAtlas.

5. Browser and device controls

Most browsers let you inspect, block, or delete cookies and site data. Blocking strictly necessary mechanisms may affect site security or availability. Device settings may also control autofill and local form history independently of the website.

Because the current ReleaseAtlas site does not set optional app-owned cookies, it does not display a consent banner merely for appearance. A consent interface should be added if the deployed technology and applicable context require one.

6. Browser privacy signals

Browsers and extensions may send signals such as Do Not Track or other preference indicators. Standards and obligations for these signals can differ. ReleaseAtlas should evaluate supported signals against the actual production data practices rather than promise a response that the current static site does not need to perform.

7. Changes to this policy

This policy should be updated before ReleaseAtlas adds analytics, advertising, product sessions, embedded third-party media, or another material tracking technology. The “Last updated” date will identify the current version.

8. Contact

Questions about this Cookie Policy can be sent to info@releaseatlas.com. For broader data-practice information, review the Privacy Policy.